Specifications used in the MISP project including MISP core format
 
 
 
Go to file
Christophe Vandeplas 49081ef470
Cluster value mandatory uuid and optional official-refs
2024-06-25 17:33:32 +02:00
misp-core-format Update raw.md 2024-06-25 08:27:24 +02:00
misp-galaxy-format Cluster value mandatory uuid and optional official-refs 2024-06-25 17:33:32 +02:00
misp-noticelist-format
misp-object-template-format chg: [object] updated to the latest version 2023-12-24 14:26:34 +01:00
misp-query-format
misp-taxonomy-format chg: [misp-taxonomies] updated 2024-02-22 08:05:30 +01:00
misp-warninglist-format
sightingdb-format Generate the new txt file 2020-04-13 18:05:31 -07:00
threat-actor-naming chg: [threat-actor-naming] feedback merged + need to add reference to MISP galaxy format 2020-06-12 21:59:36 +02:00
README.md chg: [doc] fix mmark repo 2023-02-26 12:42:27 +01:00

README.md

MISP standards and RFCs

This repository is the official source of the specification and formats used in the MISP project.

The formats are described to support other implementations which reuse the format and ensuring an interoperability with existing MISP software, other Threat Intelligence Platforms and security tools at large.

All the formats can be freely reused by everyone.

MISP Formats in use and implemented in multiple software

MISP Format in design phase and implemented in at least one software prototype

  • misp-modules-protocol which describes the misp-modules protocol used between MISP and misp-modules.

MISP Format in design phase

  • misp-collaborative-voting-format which describes the collaborative voting and scoring format for the feeds providers.

Sample files

If you want to see how a threat intelligence can be easily expressed in MISP standard, the following resources might give you some ideas:

Installing MISP is also another option to see the MISP standards in action. The MISP standards are actively used in the MISP threat intelligence platform to support the complete chain from intelligence creation, sharing, distribution and synchronisation.

Building the RFCs

These RFCs use mmark to generate - get a release from the Github Repo and make sure it's in your PATH.

You'll also need xml2rfc - install using sudo pip3 isntall xml2rfc

for directory in $(find . -type d -iname "misp*"); do;
    echo "Building $directory...";
    cd $directory;
    make;
    cd ..;
done;

Contribution

If you want to contribute to the MISP specifications, feel free to open an issue.