MISP integrations in IntelMQ

While MISP and IntelMQ seem to solve similar problems in the first hindsight, their intentions and strengths differ significantly.

In a nutshell, MISP stores manually curated indicators (called attributes) grouped in events. An event can have an arbitrary number of attributes. MISP correlates these indicators with each other and can synchronize the data between multiple MISP instances.

On the other side, IntelMQ in it's essence (not considering the EventDB <eventdb>) has no state or database, but is stream-oriented. IntelMQ acts as a toolbox which can be configured as needed to automate processes of mass data with little or no human interaction At the end of the processing the data may land in some database or be sent to other systems.

Both systems do not intend to replace each other or do compete. They integrate seamless and combine each other enabling more use-cases and

MISP API Collector

The MISP API Collector fetches data from MISP via the MISP API .

Look at the Bots documentation page for more information.

MISP Expert

The MISP Expert searches MISP by using the MISP API for attributes/events matching the source.ip of the event. The MISP Attribute UUID and MISP Event ID of the newest attribute are added to the event.

Look at the Bots documentation page for more information.

MISP Feed Output

This bot creates a complete MISP feed ready to be configured in MISP as incoming data source.

Look at the Bots documentation page for more information.

MISP API Output

Can be used to directly create MISP events in a MISP instance by using the MISP API.

Look at the Bots documentation page for more information.