Skip to the content.

MISP Objects to STIX1 mapping

MISP Objects are containers of single MISP attributes that are grouped together to highlight their meaning in a real use case scenario.
For instance, if you want to share a report with suspicious files, without object templates you would end up with a list of file names, hashes, and other attributes that are all mixed together, making the differentiation of each file difficult. In this case with the file object template, we simply group together all the attributes which belong to each file.
The list of currently supported templates is available here.

As we can see in the detailed Events mapping documentation, objects within their event are exported in different STIX objects embedded in a STIX Package. Indicators and observables are also embedded in the Incident but it is not the case for TTPS for instance.
So for he rest of this documentation, in order to keep the content clear enough and to skip the irrelevant part, we will consider the followings:

Current mapping

Unmapped objects

As for attributes, the variety of available MISP object templates is larger than the STIX scope, which makes it impossible to map every MISP object to a specific STIX object.
Again we do not skip those pieces of data and export them as Custom objects instead. Let us see some examples of custom objects exported from MISP objects:

The other detailed mappings

For more detailed mappings, click on one of the link below:

(Go back to the main documentation)