Skip to content

Commit 4437e8a

Browse files
authored
Merge pull request #3069 from MicrosoftDocs/diannegali-incidentdesc
incident description
2 parents 831434a + e726a3d commit 4437e8a

File tree

4 files changed

+15
-1
lines changed

4 files changed

+15
-1
lines changed

defender-xdr/investigate-incidents.md

Lines changed: 12 additions & 1 deletion
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: 01/17/2025
19+
ms.date: 03/11/2025
2020
appliesto:
2121
- Microsoft Defender XDR
2222
- Microsoft Sentinel in the Microsoft Defender portal
@@ -119,6 +119,17 @@ Selecting an attack path from the list displays the attack path graph, which sho
119119
> To view the details of an attack path, you must have read access permissions in the Microsoft Defender portal and the license for [Microsoft Security Exposure Management](/security-exposure-management/microsoft-security-exposure-management). </br></br>
120120
> To view attack path details with Microsoft Sentinel in the unified security operations platform, a *Sentinel Reader* role is required. To create new attack paths, the *Security Administrator* role is required.
121121
122+
### Incident details
123+
124+
You can view an incident's details on the right pane of an incident page. The incident details include incident assignment, ID, classification, categories, and first and last activity date and time. It also includes a description of the incident, impacted assets, active alerts, and where applicable, the related threats, recommendations, and disruption summary and impact. Here's an example of the incident details where the incident description is highlighted.
125+
126+
:::image type="content" source="/defender/media/investigate-incidents/incident-desc-small.png" alt-text="An example of incident details where the description is highlighted." lightbox="/defender/media/investigate-incidents/incident-desc.png":::
127+
128+
The incident description provides a brief overview of the incident. In some cases, the first alert in the incident is used as the incident description. In this case, the description is only shown in the portal and not stored in the activity log, advanced hunting tables, or the Microsoft Sentinel in Azure portal.
129+
130+
> [!TIP]
131+
> Microsoft Sentinel customers can also view and overwrite the same incident description in the Azure portal by setting the incident description through API or automation.
132+
122133
## Alerts
123134

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

defender-xdr/whats-new.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,10 @@ You can also get product updates and important notifications through the [messag
3434

3535
## March 2025
3636

37+
- (Preview) The incident description has moved within the incident page. The incident description is now displayed after the incident details. For more information, see [Incident details](investigate-incidents.md#incident-details).
38+
3739
- The Microsoft 365 alert policies can now only be managed in the Microsoft Defender portal. For more information, see [Alert policies in Microsoft 365](alert-policies.md).
40+
3841
- You can now link Threat analytics reports when setting up custom detections. [Learn more](threat-analytics.md#set-up-custom-detections-and-link-them-to-threat-analytics-reports)
3942

4043
## February 2025
213 KB
Loading
273 KB
Loading

0 commit comments

Comments
 (0)