Last Updated: October 23, 2026
Overview
Event-incident correlation checks events against criteria that matter to your organization and links the events that match to a D3 Morpheus incident. Instead of one incident per alert, related events are investigated together. For example:
-
Phishing: emails with the same sender or subject line.
-
Denial of service: events with the same source or target IP address.
-
Malware: events with the same host name or file hash, or a hash with a given reputation.
Events can be correlated by hand, from an event, or automatically, by a preprocessing playbook as events are ingested. Automation is where most of the value is: the analyst sees one incident with its related events already attached.
READER NOTE
Correlation groups different alerts that belong to one incident. It is a separate job from recognizing the same alert arriving twice, which is handled at ingestion by the event key in your field mapping. For both jobs side by side, and for which tool to reach for, see How D3 Handles Duplicate Alerts.
Escalating an Event
-
Go to WORKSPACE > Events.
-
In the view list at the top left, select a view that shows open events, such as All Open.
-
Select an event's ID to open it.
The event opens with Dismiss and Escalate at the top right, and four tabs: Overview, Artifact Behaviour, Event/Incident Correlation and Event Log.
An open event
Select Escalate to open the Escalate Event(s) to Incident window. A line at the top says how many events will be escalated, for example 1 event will be escalated to a new incident. The window asks for:
-
Incident Type and Title, which are required;
-
Description, Escalation Reason, Severity, Playbook, Incident Owner, Timezone and Due Date;
-
under Show Additional Settings, the Site and a File.
Fill in the fields and select Escalate, or select Cancel to leave the event as it is.
Related events you have selected on the Event/Incident Correlation tab are counted in the window. With one related event selected, it reads 2 events will be escalated to a new incident.
Finding Related Events
The Event/Incident Correlation tab finds events and incidents that share artifacts with this event. It has two tabs: Relevant Events and Relevant Incidents. The number on each shows how many were found.
On Relevant Events:
-
In From, choose where to search: Imported Events, under NONE, or one of the event sources listed below it, grouped by category, for example GENERAL.
-
In Top Recent, set how many of the most recent matches to list, for example 5.
-
Turn on Include Escalated/Dismissed Events to include events that are already closed.
-
In Search Conditions, enter artifact names or keywords, then select Search.
-
Select + beside each event that belongs with this one. It is added to the Selected Event(s) list on the right. The + in the header row adds all the events found.
Relevant Events
The From list
When you then select Escalate, the selected events are escalated into the same incident.
Adding an Event to an Incident
An event can also join an incident that already exists.
-
On Relevant Incidents, set Top Recent, and turn on Include Closed Incidents Reported in to include incidents closed in the last number of days you enter.
-
Enter artifact names or keywords in Search Conditions, then select Search.
-
Select the incidents the event belongs to.
-
Select the arrow beside Escalate, then select Add to selected relevant incident(s).
Relevant Incidents
The Escalate menu
Seeing an Incident's Events
Every event linked to an incident is listed in the incident's Events view, grouped by how and when it was escalated, for example Manual Escalation. See Incident Workspace.
An incident's events
Automating Correlation
Automated correlation is done by a preprocessing playbook that runs on every ingested event and decides whether to escalate it, and to which incident, or to dismiss it.
The step that does the grouping is the Escalate task. Rather than creating an incident for every event, it first searches the incidents that already exist. When one matches the conditions you set, the event is attached to that incident. When none matches, a new incident is created, and that incident is what the next matching event attaches to. The analyst opens one incident with its related events already on it.
OLDER PLAYBOOKS
An existing playbook may use a Create Incident With Conditions utility command instead. It does the same job and its settings read the same way. New playbooks use the Escalate task, which is what the task list offers.
Where to Put the Check
Put the search inside the Escalate task itself, not in a step before it.
Alerts about one attack usually arrive together, within the same second. A playbook that runs a separate "does an incident already exist?" step first, and then escalates, asks the question before any of those events has produced an incident, so every one of them gets the same answer and every one creates its own incident. Because the Escalate task searches and creates in a single step, the first event’s incident is there for the second event to find.
Setting Up the Search
-
Go to CONFIGURATION > Preprocessing Playbooks and open the playbook that runs on the events you want grouped, on the On Event Ingestion trigger.
-
Add an Escalate task on the branch that escalates the event.
-
Fill in the incident the command creates. Incident Type and Playbook are required; Title, Description, Severity, Owner, External Key and Custom Fields are optional.
-
In Search Conditions, set the conditions that decide whether an existing incident counts as a match — the artifact that ties the alerts together, such as the host name, the source IP address or the phishing sender.
-
Optionally set Assignment Group to file a new incident into a queue; it then starts unowned. Choose what happens in each case with Link to Relevant Incidents, Create a new Incident, and The number of relevant incidents to link, which sets how many of the oldest matching incidents the event joins. All three default to linking one incident and creating one when nothing matches.
-
Save the playbook.
LET MORPHEUS WRITE THE CONDITIONS
Rather than writing the JSON by hand, open the draft playbook and use Modify with AI on the editor toolbar. Describe the grouping you want in a sentence and Morpheus proposes the change for you to approve. For example: correlate all events ingested within 12 hours that have the same tactic or the same agent into the same incident. It works on drafts only, so a live playbook is untouched until you publish. See Modifying a Playbook with AI.
What matters in how you fill it in:
-
The search reads incident fields. It looks at the incidents that already exist, not at the raw alert, so a value matches only when an earlier event’s run already put it on the incident. In practice the same task both sets the value, through Custom Fields, and searches for it.
-
Only incident fields may be named. You can search on an incident’s own fields, such as
Status,Type,Severity,TitleorExternalKey, and on any custom field, whose name begins withCustom. An artifact you ingest, such as an IP address, is not a built-in incident field: write it to a custom field and search on that name. A field written asIPAddressis stored and searched asCustomIPAddress, because theCustomprefix is added for you. Naming anything else fails the task with a message listing the invalid fields. -
Conditions combine as AND inside an object, OR between objects. Search Conditions takes an array of JSON objects, so
[ { "a": 1, "b": 2 }, { "a": 3 } ]means(a = 1 AND b = 2) OR (a = 3). Within a condition you can use$in,$nin,$ne,$regex, and$gtor$ltwith$datefor a date field. Normalize the values the playbook writes — one letter case, no surrounding spaces — or use$regex, so two spellings of one host do not read as two hosts. -
Give the search a scope. Matches are ordered oldest first and are not limited to recent or open incidents, so a condition as broad as "same incident type" keeps finding the oldest incident that ever matched. Add a
Statuscondition, or a created-time range, to limit matches to incidents still being worked. Matches are also scoped to the event’s own site. -
With no conditions, every event creates its own incident. When Search Conditions is empty there is nothing to match on, and the event is escalated to a new incident. Set at least one condition that identifies the shared activity.
FAQ
How many events can belong to one incident? Any number. Several events can be escalated into the same incident, and events can be added to an existing one.
Why did ten alerts that arrived together create ten incidents? The grouping check ran before any incident existed. Alerts about one attack arrive within the same moment, so a playbook that checks for an existing incident in a step before escalation gets the same answer for all ten. Do the search and the escalation in one step, in the Escalate task. See Automating Correlation.
Is correlation the same as deduplication? No. Correlation groups different alerts that belong to one incident. Recognizing the same alert arriving twice is a separate mechanism, configured at ingestion with the event key in your field mapping. See How D3 Handles Duplicate Alerts.
My condition matches but the event still created a new incident. What should I check? Check that the value you search on is written onto the incident by the same task that searches for it, that the field is an incident field or a Custom-prefixed custom field, that Link to Relevant Incidents is on, and that the two values are spelled identically.
Does the search have a time limit? No. Unless your conditions narrow it, the search can match an incident of any age, including a closed one. Scope the conditions to the window your workflow investigates in.
Can an event join an incident that is already closed? A search with no scope beyond the shared artifact can match a closed incident, which is rarely what you want. Add a Status condition, or a created-time range using $gt with $date, so matches are limited to incidents still being worked.
RELATED ARTICLES
-
Preprocessing Playbook Viewer
-
Incident Workspace
-
How D3 Handles Duplicate Alerts
-
Field Mappings
-
Utility Commands