Skip to content

Commit ee8fcc8

Browse files
committed
fixes
1 parent 3004c0e commit ee8fcc8

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

defender-xdr/incident-queue.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Prioritize incidents in the Microsoft Defender portal
3-
description: Learn how to filter incidents from the incident queue in the Microsoft Defender portal.
3+
description: Learn how to prioritize and filter incidents in the Microsoft Defender portal to improve your organization's security response. Discover actionable steps to manage incidents effectively.
44
ms.service: defender-xdr
55
f1.keywords:
66
- NOCSH
@@ -40,14 +40,15 @@ Select **Most recent incidents and alerts** to toggle a timeline chart of the nu
4040

4141
:::image type="content" source="./media/incidents-queue/most-recent-incidents.png" alt-text="Screenshot of 24-hour incident graph." lightbox="./media/incidents-queue/most-recent-incidents.png":::
4242

43-
The incident queue includes Defender Queue Assistant that helps security teams cut through alert noise and focus on the incidents that matter most. Using an AI-based, machine learning prioritization algorithm, the Queue Assistant surfaces the highest-priority incidents, explains the reasoning behind each score, and provides intuitive tools for sorting and filtering the incident queue. The priority score to each incident can be based on Microsoft native alerts, custom detections, or third-party signals. The algorithm is trained on real-world anonymized data and considers the following data points when calculating the priority score:
43+
The incident queue includes Defender Queue Assistant that helps security teams cut through the large number of incidents and focus on the incidents that matter most. Using a machine learning prioritization algorithm, the Queue Assistant surfaces the highest-priority incidents, explains the reasoning behind the prioritization, and provides intuitive tools for sorting and filtering the incident queue. The algorithm is runs for all alerts, Microsoft native alerts, custom detections, or third-party signals. The algorithm is trained on real-world anonymized data and considers, among other things, the following data points when calculating the priority score:
4444
+ Attack disruption signals
4545
+ Threat analytics
4646
+ Severity
4747
+ SnR
4848
+ MITRE techniques
4949
+ Asset criticality
5050
+ Alert types and rarity
51+
+ High profile threats such as ransomware and nation-state attacks.
5152

5253
Incidents are automatically assigned a priority score from 0 to 100, with 100 being the highest priority. Score ranges are color-coded as follows:
5354
+ Red: Top priority (score > 85)
73.5 KB
Loading

0 commit comments

Comments
 (0)