You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[Microsoft Defender for Endpoint Plan 1](microsoft-defender-endpoint.md)
27
28
-[Microsoft Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)
28
29
-[Microsoft Defender XDR](/defender-xdr)
@@ -31,12 +32,13 @@ ms.date: 07/01/2024
31
32
32
33
The **Incidents queue** shows a collection of incidents that were flagged from devices in your network. It helps you sort through incidents to prioritize and create an informed cybersecurity response decision.
33
34
34
-
By default, the queue displays incidents seen in the last 6 months, with the most recent incident showing at the top of the list, helping you see the most recent incidents first.
35
+
By default, the queue displays incidents seen in the last six months, with the most recent incident showing at the top of the list, helping you see the most recent incidents first.
35
36
36
37
There are several options you can choose from to customize the Incidents queue view.
> **Defender Boxed** appears for a limited time during January and July of each year. It's a series of cards showcasing your organization's security successes, improvements, and response actions in the past six months/year. Learn how you can share your [Defender Boxed](/defender-xdr/incident-queue#defender-boxed) highlights.
52
+
> **Defender Boxed**, a series of cards showcasing your organization's security successes, improvements, and response actions in the past six months/year, appears for a limited time during January and July of each year. Learn how you can share your [Defender Boxed](incident-queue.md#defender-boxed) highlights.
51
53
52
54
## Sort and filter the incidents queue
55
+
53
56
You can apply the following filters to limit the list of incidents and get a more focused view.
High </br>(Red) | Threats often associated with advanced persistent threats (APT). These incidents indicate a high risk due to the severity of damage they can inflict on devices.
60
63
Medium </br>(Orange) | Threats rarely observed in the organization, such as anomalous registry change, execution of suspicious files, and observed behaviors typical of attack stages.
61
-
Low </br>(Yellow) | Threats associated with prevalent malware and hack-tools that do not necessarily indicate an advanced threat targeting the organization.
64
+
Low </br>(Yellow) | Threats associated with prevalent malware and hack-tools that don't necessarily indicate an advanced threat targeting the organization.
62
65
Informational </br>(Grey) | Informational incidents might not be considered harmful to the network but might be good to keep track of.
63
66
64
67
## Assigned to
68
+
65
69
You can choose to filter the list by selecting assigned to anyone or ones that are assigned to you.
66
70
67
71
### Category
72
+
68
73
Incidents are categorized based on the description of the stage by which the cybersecurity kill chain is in. This view helps the threat analyst to determine priority, urgency, and corresponding response strategy to deploy based on context.
69
74
70
75
### Status
76
+
71
77
You can choose to limit the list of incidents shown based on their status to see which ones are active or resolved.
72
78
73
79
### Data sensitivity
80
+
74
81
Use this filter to show incidents that contain sensitivity labels.
75
82
76
83
## Incident naming
77
84
78
-
To understand the incident's scope at a glance, incident names are automatically generated based on alert attributes such as the number of endpoints affected, users affected, detection sources or categories.
85
+
To understand the incident's scope at a glance, incident names are automatically generated based on alert attributes such as the number of endpoints affected, users affected, detection sources, or categories.
79
86
80
87
For example: *Multi-stage incident on multiple endpoints reported by multiple sources.*
81
88
82
89
> [!NOTE]
83
-
> Incidents that existed prior the rollout of automatic incident naming will retain their name.
90
+
> Incidents that existed prior to the rollout of automatic incident naming retains their original name.
Copy file name to clipboardExpand all lines: defender-xdr/incidents-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ The Microsoft Defender portal includes tools and methods to automate or otherwis
75
75
|**[Harness AI with Microsoft Copilot for Security](/defender-xdr/security-copilot-in-microsoft-365-defender)**| Add AI to support analysts with complex and time-consuming daily workflows. For example, Microsoft Copilot for Security can help with end-to-end incident investigation and response by providing clearly described attack stories, step-by-step actionable remediation guidance and incident activity summarized reports, natural language KQL hunting, and expert code analysis—optimizing on SOC efficiency across data from all sources. <br><br>This capability is in addition to the other AI-based functionality that Microsoft Sentinel brings to the unified platform, in the areas of user and entity behavior analytics, anomaly detection, multi-stage threat detection, and more. |
76
76
77
77
> [!TIP]
78
-
> **Defender Boxed** appears for a limited time during January and July of each year. It's a series of cards showcasing your organization's security successes, improvements, and response actions in the past six months/year. Learn how you can share your [Defender Boxed](incident-queue.md#defender-boxed) highlights.
78
+
> **Defender Boxed**, a series of cards showcasing your organization's security successes, improvements, and response actions in the past six months/year, appears for a limited time during January and July of each year. Learn how you can share your [Defender Boxed](incident-queue.md#defender-boxed) highlights.
Copy file name to clipboardExpand all lines: defender-xdr/investigate-incidents.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -255,7 +255,7 @@ Some incidents might have similar incidents listed on the **Similar incidents**
255
255
:::image type="content" source="/defender/media/investigate-incidents/incident-similartab-small.png" alt-text="Screenshot that shows the Similar incidents tab for an incident in the Microsoft Defender portal." lightbox="/defender/media/investigate-incidents/incident-similartab.png":::
256
256
257
257
> [!TIP]
258
-
> **Defender Boxed** appears for a limited time during January and July of each year. It's a series of cards showcasing your organization's security successes, improvements, and response actions in the past six months/year. Learn how you can share your [Defender Boxed](incident-queue.md#defender-boxed) highlights.
258
+
> **Defender Boxed**, a series of cards showcasing your organization's security successes, improvements, and response actions in the past six months/year, appears for a limited time during January and July of each year. Learn how you can share your [Defender Boxed](incident-queue.md#defender-boxed) highlights.
Copy file name to clipboardExpand all lines: defender-xdr/manage-incidents.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,17 +50,15 @@ This article shows you how to perform various incident management tasks associat
50
50
-[Specify an incident's classification](#specify-the-incidents-classification).
51
51
-[Add comments to an incident](#add-comments-to-an-incident).
52
52
53
-
> [!TIP]
54
-
> **Defender Boxed** appears for a limited time during January and July of each year. It's a series of cards showcasing your organization's security successes, improvements, and response actions in the past six months/year. Learn how you can share your [Defender Boxed](incident-queue.md#defender-boxed) highlights.
55
-
56
-
Here are the ways you can manage your incidents:
57
-
=======
58
53
**[Incident logging and reporting:](#incident-logging-and-reporting)**
59
54
60
55
-[Edit the incident name](#edit-the-incident-name).
61
56
- Assess the activity audit and add comments in the [Activity log](#view-the-activity-log-of-an-incident).
62
57
-[Export incident data to PDF](#export-incident-data-to-pdf).
63
58
59
+
> [!TIP]
60
+
> **Defender Boxed**, a series of cards showcasing your organization's security successes, improvements, and response actions in the past six months/year, appears for a limited time during January and July of each year. Learn how you can share your [Defender Boxed](incident-queue.md#defender-boxed) highlights.
61
+
64
62
## Access the *Manage incident* pane
65
63
66
64
Most of these tasks are accessible from the **Manage incident** pane for an incident. You can reach this pane from any of several locations.
> **Defender Boxed** appears for a limited time during January and July of each year. It's a series of cards showcasing your organization's security successes, improvements, and response actions in the past six months/year. Learn how you can share your [Defender Boxed](incident-queue.md#defender-boxed) highlights.
92
+
> **Defender Boxed**, a series of cards showcasing your organization's security successes, improvements, and response actions in the past six months/year, appears for a limited time during January and July of each year. Learn how you can share your [Defender Boxed](incident-queue.md#defender-boxed) highlights.
0 commit comments