Skip to content

Commit 7e37d9b

Browse files
committed
added critical attack path
1 parent 6ff1a74 commit 7e37d9b

File tree

1 file changed

+9
-2
lines changed

1 file changed

+9
-2
lines changed

defender-xdr/investigate-incidents.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.topic: conceptual
1616
search.appverid:
1717
- MOE150
1818
- MET150
19-
ms.date: 09/24/2024
19+
ms.date: 11/18/2024
2020
appliesto:
2121
- Microsoft Defender XDR
2222
- Microsoft Sentinel in the Microsoft Defender portal
@@ -97,7 +97,14 @@ The resulting logs or alerts can be linked to an incident by selecting a results
9797
:::image type="content" source="/defender/media/investigate-incidents/fig2-gohunt-attackstory.png" alt-text="Highlighting the link to incident option in go hunt query results" lightbox="/defender/media/investigate-incidents/fig2-gohunt-attackstory.png":::
9898

9999
If the incident or related alerts were the result of an analytics rule you've set, you can also select ***Run query*** to see other related results.
100-
100+
101+
(Preview) The incident graph also contains information about **critical attack paths**. These paths allows security analysts to identify what other entities an attacker is likely to target next. To view an attack path, you can click on an entity and select **View attack path**.
102+
103+
Attack paths are available for entities with the **critical asset** tag.
104+
105+
> [!NOTE]
106+
> To view the details of an attack path, you must have read access permissions in the Microsoft Defender portal. To view attack path details in the unified security operations platform, a *Sentinel Reader* role is required. To create new attack paths, the Security Administrator role is required.
107+
101108
## Alerts
102109

103110
On the **Alerts** tab, you can view the alert queue for alerts related to the incident and other information about them like the following:

0 commit comments

Comments
 (0)