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
Copy file name to clipboardExpand all lines: defender-xdr/manage-incidents.md
+45-17Lines changed: 45 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,18 +37,21 @@ Manage your incidents from **Investigation & response > Incidents & alerts > Inc
37
37
38
38
This article shows you how to perform various incident management tasks associated with different stages in an incident's lifecycle.
39
39
40
-
**Incident triage:**
40
+
**[Incident triage:](#incident-triage)**
41
+
41
42
-[Assign the incident to an owner](#assign-an-incident-to-an-owner).
42
43
-[Assign or change severity](#assign-or-change-incident-severity).
43
44
-[Add incident tags](#add-incident-tags).
44
45
-[Change the incident status](#change-the-incident-status).
45
46
46
-
**Incident investigation and resolution:**
47
-
-[Specify an incident's classification](#specify-the-classification).
47
+
**[Incident investigation and resolution:](#incident-investigation-and-resolution)**
48
+
49
+
-[Specify an incident's classification](#specify-the-incidents-classification).
48
50
-[Resolve an incident](#resolve-an-incident).
49
-
-[Add comments to an incident](#add-comments).
51
+
-[Add comments to an incident](#add-comments-to-an-incident).
52
+
53
+
**[Incident logging and reporting:](#incident-logging-and-reporting)**
50
54
51
-
**Incident logging and reporting:**
52
55
-[Edit the incident name](#edit-the-incident-name).
53
56
- Assess the activity audit and add comments in the [Activity log](#activity-log).
54
57
-[Export incident data to PDF](#export-incident-data-to-pdf).
@@ -84,6 +87,11 @@ Most of these tasks are accessible from the **Manage incident** pane for an inci
84
87
85
88
The following management tasks are closely associated with incident triage, though they can be performed at any time.
86
89
90
+
-[Assign the incident to an owner](#assign-an-incident-to-an-owner).
91
+
-[Assign or change severity](#assign-or-change-incident-severity).
92
+
-[Add incident tags](#add-incident-tags).
93
+
-[Change the incident status](#change-the-incident-status).
94
+
87
95
### Assign an incident to an owner
88
96
89
97
By default, new incidents are created with no owner. Ideally, your SecOps team should have mechanisms and procedures in place to automatically assign incidents to owners. You might need to reassign an incident in the case of escalation or mistaken original assignment.
@@ -239,19 +247,39 @@ All comments are added to the historical events of the incident. You can see the
239
247
240
248
## Incident logging and reporting
241
249
250
+
### Edit the incident name
251
+
252
+
Microsoft Defender automatically assigns a name based on alert attributes such as the number of endpoints affected, users affected, detection sources or categories. The incident name allows you to quickly understand the scope of the incident. For example: *Multi-stage incident on multiple endpoints reported by multiple sources.*
253
+
254
+
To edit the incident name, take the following steps:
255
+
256
+
1. Follow the instructions in the opening section to [Access the *Manage incident* pane](#access-the-manage-incident-pane).
257
+
258
+
1. Type a new name in the **Incident name** field on the **Manage incident** pane.
259
+
260
+
1. Select **Save**.
261
+
262
+
> [!NOTE]
263
+
>
264
+
> - Incidents that existed before the rollout of the automatic incident naming feature retain their names.
265
+
>
266
+
> - If another incident is merged into a renamed incident, Defender gives the incident a new name, overwriting any custom name you gave it beforehand.
267
+
242
268
### View the activity log of an incident
243
269
244
-
When doing a postmortem of an incident, view the incident's **Activity log** to see the history of actions performed on the incident and any comments recorded. All changes made to the incident, whether by a user or by the system, are recorded in the activity log. The activity log is available from the **Activity log** option on the incident page or on the incident side pane.
270
+
When doing a postmortem of an incident, view the incident's **Activity log** to see the history of actions performed on the incident (called "Audits") and any comments recorded. All changes made to the incident, whether by a user or by the system, are recorded in the activity log.
245
271
246
-
:::image type="content" source="/defender/media/incidents-queue/fig3-manageincidents-new.png" alt-text="Screenshot highlighting the activity log option from the incident pagein the Microsoft Defender portal." lightbox="/defender/media/incidents-queue/fig3-manageincidents-new.png":::
272
+
1. Open the incident's activity log. From the incident page, or from the incident details panel on the incident queue page, select the three dots in the upper right corner, and from the resulting menu, select **Activity log**.
247
273
248
-
You can filter the activities within the log by comments and actions. Click the **Content: Audits, Comments** then select the content type to filter activities. Here's an example.
274
+
:::image type="content" source="media/manage-incidents/activity-log.png" alt-text="Screenshot highlighting the activity log option from the incident page in the Microsoft Defender portal." lightbox="media/manage-incidents/activity-log.png":::
249
275
250
-
:::image type="content" source="/defender/media/incidents-queue/fig4-manageincidents.png" alt-text="Screenshot highlighting the filter options within the activity log pane from the incident page in the Microsoft Defender portal." lightbox="/defender/media/incidents-queue/fig4-manageincidents.png":::
276
+
1. Filter the activities within the log by comments and actions. Select **Content: Audits, Comments** then select the content type to filter activities. Here's an example.
251
277
252
-
You can also add your own comments using the comment box available within the activity log. The comment box accepts text and formatting, links, and images.
278
+
:::image type="content" source="media/manage-incidents/filter-activity-log.png" alt-text="Screenshot highlighting the filter options within the activity log pane from the incident page in the Microsoft Defender portal." lightbox="media/manage-incidents/filter-activity-log.png":::
279
+
280
+
1. Select **Apply**.
253
281
254
-
:::image type="content" source="/defender/media/incidents-queue/fig5-res-manageincidents.png" alt-text="Screenshot highlighting the comment box from the incident page in the Microsoft Defender portal." lightbox="/defender/media/incidents-queue/fig5-manageincidents.png":::
282
+
You can also [add your own comments](#add-comments-to-an-incident) using the comment box available within the activity log. The comment box accepts text and formatting, links, and images.
255
283
256
284
### Export incident data to PDF
257
285
@@ -272,7 +300,7 @@ The incident data exported includes the following information:
272
300
273
301
Here's an example of the exported PDF:
274
302
275
-
:::image type="content" source="/defender/media/incidents-queue/export-results-small.png" alt-text="Screenshot of the exported PDF's first page." lightbox="/defender/media/incidents-queue/export-results.png":::
303
+
:::image type="content" source="media/manage-incidents/export-results-small.png" alt-text="Screenshot of the exported PDF's first page." lightbox="media/manage-incidents/export-results.png":::
276
304
277
305
If you have the [Copilot for Security](/security-copilot/microsoft-security-copilot) license, the exported PDF contains the following additional incident data:
278
306
@@ -281,25 +309,25 @@ If you have the [Copilot for Security](/security-copilot/microsoft-security-copi
281
309
282
310
The export to PDF function is also available in the Copilot side panel. When you select the **More actions** ellipsis (...) on the upper right corner of the incident report results card, you can choose **Export incident as PDF**.
283
311
284
-

312
+
:::image type="content" source="media/manage-incidents/export-incident-more-actions1.png" alt-text="Screenshot of additional actions in the incident report results card.":::
285
313
286
314
To generate the PDF, perform the following steps:
287
315
288
316
1. Open an incident page. Select the **More actions** ellipsis (...) on the upper right corner and choose **Export incident as PDF**.
289
317
290
-
:::image type="content" source="/defender/media/incidents-queue/export-ellipsis-small.png" alt-text="Screenshot highlighting the More actions ellipsis on the incident page." lightbox="/defender/media/incidents-queue/export-ellipsis.png":::
318
+
:::image type="content" source="media/manage-incidents/export-ellipsis-small.png" alt-text="Screenshot highlighting the More actions ellipsis on the incident page." lightbox="media/manage-incidents/export-ellipsis.png":::
291
319
292
320
1. In the dialog box that appears next, confirm the incident information that you want to include or exclude in the PDF. All incident information is selected by default. Select **Export PDF** to proceed.
293
321
294
-
:::image type="content" source="/defender/media/incidents-queue/export-options.png" alt-text="Screenshot highlighting the export incident to PDF option.":::
322
+
:::image type="content" source="media/manage-incidents/export-options.png" alt-text="Screenshot highlighting the export incident to PDF option.":::
295
323
296
324
1. A status message indicating the current state of the download appears below the incident title. The export process may take a few minutes depending on the incident's complexity and the amount of data to be exported.
297
325
298
-
:::image type="content" source="/defender/media/incidents-queue/export-prepare-small.png" alt-text="Screenshot highlighting export message and status before download." lightbox="/defender/media/incidents-queue/export-prepare.png":::
326
+
:::image type="content" source="media/manage-incidents/export-prepare-small.png" alt-text="Screenshot highlighting export message and status before download." lightbox="media/manage-incidents/export-prepare.png":::
299
327
300
328
1. Another dialog box appears indicating that the PDF is ready. Select **Download** from the dialog box to save the PDF to your device. The status message below the incident title also updates to indicate that the download is available.
301
329
302
-
:::image type="content" source="/defender/media/incidents-queue/export-download-small.png" alt-text="Screenshot highlighting export message and status when download is available." lightbox="/defender/media/incidents-queue/export-download.png":::
330
+
:::image type="content" source="media/manage-incidents/export-download-small.png" alt-text="Screenshot highlighting export message and status when download is available." lightbox="media/manage-incidents/export-download.png":::
303
331
304
332
The report is cached for a couple of minutes. The system provides the previously generated PDF if you try to export the same incident again within a short time frame. To generate a newer version of the PDF, wait for a few minutes for the cache to expire.
0 commit comments