04a63e05e6
- Backported from 2.4 - Running a stix export for a specific ID that doesn't exist results in a full STIX export for the user (events visible to the user) - This leads for an unnecesarily long export process when a quick export is expected |
||
|---|---|---|
| INSTALL | ||
| PyMISP@205baa2f65 | ||
| app | ||
| build | ||
| format/2.3 | ||
| plugins | ||
| tools | ||
| travis | ||
| .gitignore | ||
| .gitmodules | ||
| .pydevproject | ||
| .travis.yml | ||
| AUTHORS | ||
| LICENSE | ||
| README.md | ||
| VERSION.json | ||
README.md
MISP - Malware Information Sharing Platform
The problem that we experienced in the past was the difficulty to exchange information about (targeted) malwares and attacks within a group of trusted partners, or a bilateral agreement. Even today much of the information exchange happens in unstructured reports where you have to copy-paste the information in your own text-files that you then have to parse to export to (N)IDS and systems like log-searches, etc...
A huge challenge in the Cyber Security domain is the information sharing inside and between organizations. This Malware Information Sharing Platform has as goal to facilitate:
- central IOC database: storing technical and non-technical information about malwares and attacks, ... Data from external instances is also imported into your local instance
- correlation: automatically creating relations between malwares, events and attributes
- storing data in a structured format (allowing automated use of the database for various purposes)
- export: generating IDS, OpenIOC, plain text, xml output to integrate with other systems (network IDS, host IDS, custom tools, …)
- import: bulk-import, batch-import, import from OpenIOC, GFI sandbox, ThreatConnect CSV, ...
- data-sharing: automatically exchange and synchronization with other parties and trust-groups using MISP
- STIX support: export data in the STIX format (XML and json)
Exchanging info results in faster detection of targeted attacks and improves the detection ratio while reducing the false positives. We also avoid reversing similar malware as we know very fast that others already worked on this malware. The Red October malware for example gives a similar view:
Some people might think about CIF (Collective Intelligence Framework) and CRITs (Collaborative Research Into Threats), however those tools are different. Each one has its strenghts and weaknesses, but in the end MISP will rule the world of course.
Website / Support
Checkout the website for more information about MISP like features, roadmap, (commercial) support, ... : http://misp-project.org
Documentation
MISP user-guide is available online or as PDF or as EPUB or as MOBI/Kindle.
Contributing
Feel free to fork the code, play with it, make some patches and send us the pull requests.
Feel free to contact us, create issues, if you have questions, remarks or bug reports.
There are 2 branches:
- develop: (very active development) new features and improvements
- main: what we consider as stable
License
This software is licensed under GNU Affero General Public License version 3
- Copyright (C) 2012 Christophe Vandeplas
- Copyright (C) 2012 Belgian Defence
- Copyright (C) 2012 NATO / NCIRC
- Copyright (C) 2013-2015 Andras Iklody
- Copyright (C) 2015 CIRCL - Computer Incident Response Center Luxembourg
For more information, the list of authors and contributors is available.