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, 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.
Now we can have a look at the results when we add attributes, objects, galaxies, or tags (TLinks 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:

As shown with this example, tags are basically exported as is in a list of marking structures, depending whether they are TLP marking or not.

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 exported as any galaxy (detailed mapping available below) and not longer exported in the markings list:
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.

We can see in this case the Galaxy is exported as TTP and is then in the list of TTPs, where its reference is in the list of Leveraged TTPs within the Incident.
The principle remains the same if the Galaxy would have been a Threat Actor or a Course of Action: the data itself is embedded within the list of (respectively) Threat Actors or Courses of Action, and their reference is in the list of (respectively) Attributed Threat Actors or COA Taken

We will now focus on the data contained in the Incident because the STIX Package is going to remain the same, keep in mind it is not skipped or removed, we just simplify here the examples display

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:

Those two last examples were very simple to have an overview of what happens.

The other detailed mappings

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

(Go back to the main documentation)