Skip to content

Commit 2ddac2f

Browse files
authored
Update alerts-incidents-correlation.md
1 parent 8c166ec commit 2ddac2f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

defender-xdr/alerts-incidents-correlation.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -43,13 +43,13 @@ When the Defender portal is configured to include Microsoft Sentinel as a data s
4343

4444
### Manual correlation of alerts
4545

46-
While Microsoft Defender already uses advanced correlation mechanisms, you might want to decide differently whether a given alert belongs with a particular incident or not. In such a case, you can unlink an alert from one incident and link it to another. Every alert must belong to an incident, so you can either link the alert to another existing incident, or to a new incident that you create on the spot.
46+
While Microsoft Defender already uses advanced correlation mechanisms, you might want to decide differently whether a given alert belongs with a particular incident. In such a case, you can unlink an alert from one incident and link it to another. Every alert must belong to an incident, so you can either link the alert to another existing incident, or to a new incident that you create on the spot.
4747

4848
For more information on moving an alert from one incident to another, see [Move alerts from one incident to another in the Microsoft Defender portal](move-alert-to-another-incident.md).
4949

5050
## Incident correlation and merging
5151

52-
The Defender portal's correlation activities don't stop when incidents are created. Defender continues to detect commonalities and relationships between incidents and alerts across incidents. When two or more incidents are determined to be sufficiently alike, Defender merges the incidents into a single incident.
52+
The Defender portal's correlation activities don't stop when incidents are created. Defender continues to detect commonalities and relationships between incidents and alerts across incidents. When multiple incidents are determined to be sufficiently alike, Defender merges the incidents into a single incident.
5353

5454
### Criteria for merging incidents
5555

@@ -97,7 +97,7 @@ For example, if the incidents weren't merged because they were assigned to two d
9797

9898
Merging incidents together is preferable to unlinking alerts from one incident and linking them to another, because all the incident information (for example, the activity log) is preserved.
9999

100-
For now, only two incidents at a time can be merged manually.
100+
Currently, five incidents at a time can be merged manually.
101101

102102
Other rules governing manual merging are the same as automatic merging. See [Details of the merge process](#details-of-the-merge-process) above.
103103

0 commit comments

Comments
 (0)