Skip to content

Commit e42d8a2

Browse files
authored
Update alerts-incidents-correlation.md
1 parent c244445 commit e42d8a2

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

defender-xdr/alerts-incidents-correlation.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,12 +111,13 @@ Even when the correlation logic indicates that two incidents should be merged, D
111111
When two or more incidents are merged, a new incident is not created to absorb them. Instead, the contents of one incident are migrated into the other incident, and the incident abandoned in the process is automatically closed. The abandoned incident is no longer visible or available in Microsoft Defender XDR, and any reference to it is redirected to the consolidated incident. The abandoned, closed incident remains accessible in Microsoft Sentinel in the Azure portal. The contents of the incidents are handled in the following ways:
112112

113113
- Alerts contained in the abandoned incident are removed from it and added to the consolidated incident.
114+
- Any tags applied to the abandoned incident are removed from it and added to the consolidated incident.
115+
- A **`Redirected`** tag is added to the abandoned incident.
114116
- Entities (assets etc.) follow the alerts they're linked to.
115117
- Analytics rules recorded as involved in the creation of the abandoned incident are added to the rules recorded in the consolidated incident.
116-
- Any tags applied to the abandoned incident are removed, and a **`Redirected`** tag is added to the abandoned incident.
117118
- Currently, comments and activity log entries in the abandoned incident are *not* moved to the consolidated incident.
118119

119-
To see the abandoned incident's comments and activity history, open the incident in Microsoft Sentinel in the Azure portal. The activity history includes the adding and removal of alerts, tags, and other items related to the incident merge.
120+
To see the abandoned incident's comments and activity history, open the incident in Microsoft Sentinel in the Azure portal. The activity history includes the closing of the incident and the adding and removal of alerts, tags, and other items related to the incident merge. These activities are attributed to the identity *Microsoft Defender XDR - alert correlation*.
120121

121122
## Manual correlation
122123

0 commit comments

Comments
 (0)