-
-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MISP connector #12
Labels
Milestone
Comments
Closed
This is something of really high priority. WE are looking for people who are willing to work on that :) |
7 tasks
eshaan7
pushed a commit
that referenced
this issue
Jul 26, 2021
* Add alpha misp connector * Add hash check, job tags, config * Refactor: add md5, mimetype for file and add tlp option * Add job_id, analyzers executed to misp * small fixes * Add monkeypatch and instance url * mock pymisp * minor refactor in get hash type * change docstring of mocks
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
IntelOwl was designed to be integrated with other security tools very easily.
In particular, it is a perfect fit for Threat Intelligence Platforms because it can enrich the data available in those platform and can be customized on its own needs.
So, in order to help the community to achieve this result, we should add new connectors for the most used open source TIPs, for example: MISP
We should study their project and add a relative connector to integrate IntelOwl with MISP.
An idea could be to create a new expansion module (https://github.com/MISP/misp-modules) to allow MISP users to enrich an indicator via IntelOwl and integrate the results on the relative event.
We should leverage the official IntelOwl client for this purpose.
The text was updated successfully, but these errors were encountered: