Skip to the content.

Events mapping

MISP Events are exported within STIX packages, where some of the metadata fields are embedded within incidents:

This is a very basic example to show how the MISP Event fields are ported into STIX 2.1, but let us see now what happens when we start adding data to the event or change some fields value:

We can already see the published timestamp is exported as well when the event is published and instead of a Grouping object, the event metadata fields are exported with a Report object.
Now we can have a look at the results when we add attributes, objects, galaxies, or tags (Links to the detailed mappings for each structure type are available below).

Exporting tags is pretty much straight forward and does not require a complex mapping.
Nonetheless, with STIX 2.1 and STIX2 in general, Marking objects only support the tlp and the statement definition type. Thus, with the following example you can see that out of the 4 different tags, only one is exported in a Marking object, and the other one are set as labels.

As shown with this example, tags are basically exported as marking structures.

If you are familiar with the MISP format, you can already see there are some tags representing MISP galaxies, because galaxies are referenced in the tags where their definition is embedded within the Galaxy field.
With the next example we will see that every galaxy actually included in the event and referenced within the tags is exported as any galaxy (detailed mapping available below) and no longer as tag only:
misp-galaxy:mitre-attack-pattern="Access Token Manipulation - T1134" is the tag name for the mitre-attack-pattern galaxy Access Token Manipulation - T1134 and is in the list of tags, but exported as a galaxy since it is included in the galaxies, but misp-galaxy:mitre-attack-pattern="Code Signing - T1116" is only a tag.

Exporting attributes differs from exporting objects in terms of complexity of the parsing, but both result in the creation of Indicators or Observable in most cases. The parameter that triggers one or the other case is simply the to_ids flag:

Embedded galaxies also trigger some specific computation in order to build the corresponding references between the different STIX 2.1 objects.

There is ultimately a last specific use case to mention: the references between MISP Objects.

Those examples provide a simple overview of the events mapping as STIX 2.1.
For more information about the mapping as STIX 2.1, please find above the detailed mappings for attributes, objects and galaxies export.

The other detailed mappings

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

(Go back to the main documentation)