MISP (core software) - Open Source Threat Intelligence and Sharing Platform (formely known as Malware Information Sharing Platform) https://www.misp-project.org/
 
 
 
 
 
 
Go to file
Steve Peak 19c2e90e3b Create .coveragerc 2015-09-27 10:55:55 +02:00
INSTALL Added gcc in dependencies (related to https://github.com/MISP/MISP/issues/302) 2015-09-15 20:33:33 +02:00
PyMISP@81fa4e5bdd Add pymisp as a submodule 2015-09-22 17:05:28 +02:00
app Fix to an issue that blocked event blacklist entries from being added manually, fixes #676 2015-09-24 11:26:23 +02:00
build Big update, Almost ready to run tests. 2015-09-11 19:23:20 +02:00
plugins Integration of plugins / cake core into MISP as submodules 2014-02-07 09:03:28 +01:00
tools Fixed various issues with the attribute REST api 2015-04-14 13:50:51 +02:00
travis [Travis] Fix DB 2015-09-12 22:23:07 +02:00
.coveragerc Create .coveragerc 2015-09-27 10:55:55 +02:00
.gitignore Complete rework of the ZeroMQ implementation 2015-06-29 08:56:45 +02:00
.gitmodules Update default version for cakephp, make sure PyMISP follows master 2015-09-22 17:36:41 +02:00
.pydevproject minor changes 2013-06-24 15:12:30 +02:00
.travis.yml Debugging coverage 2015-09-27 10:45:51 +02:00
AUTHORS Parse authorization headers for a valid MISP auth key, fixes #478 2015-05-04 19:01:12 +02:00
LICENSE updated structure of the documentation 2013-02-15 08:20:14 +01:00
README.md Fix travis message in README. 2015-09-08 17:40:01 +02:00
VERSION.json Fix to an issue that blocked event blacklist entries from being added manually, fixes #676 2015-09-24 11:26:23 +02:00

README.md

Build Status

MISP - Malware Information Sharing Platform

logo

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:

red october

red october

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

Feel free to have a look at the (pdf) documentation in the INSTALL directory.

We are actively developing this tool and many (code, documentation, export formats,...) improvements are coming.

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, 2013 Christophe Vandeplas, Belgian Defence, NATO / NCIRC.