Skip to content

Commit 1ef49d2

Browse files
Pencil edit
1 parent 459c1ef commit 1ef49d2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

defender-xdr/irm-investigate-alerts-defender.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ The following alert classification mapping is used to sync the alert classificat
132132
|Microsoft Defender alert classification|Microsoft Purview Insider Risk Management alert classification|
133133
|:---|:---|
134134
|True positive </br> Includes multi-staged attack, phishing, etc.|Confirmed|
135-
|Information, expected activity (benign positive) </br> Includes Ssecurity testing, confirmed activity, etc.|Dismissed|
135+
|Information, expected activity (benign positive) </br> Includes security testing, confirmed activity, etc.|Dismissed|
136136
|False positive </br> Includes not malicious, not enough data to validate, etc.|Dismissed|
137137

138138
For more information about alert statuses and classifications in Microsoft Defender XDR, see [Manage alerts in Microsoft Defender](investigate-alerts.md#manage-alerts).
@@ -213,4 +213,4 @@ If you are using automation on Microsoft Sentinel incidents, note that automatio
213213
After investigating an insider risk incident or alert, you can do any of the following:
214214

215215
- Continue to respond to the alert in the Microsoft Purview portal.
216-
- Use advanced hunting to investigate other insider risk management events in the Microsoft Defender portal.
216+
- Use advanced hunting to investigate other insider risk management events in the Microsoft Defender portal.

0 commit comments

Comments
 (0)