Skip to content

Commit 61390f9

Browse files
authored
Merge pull request #1859 from MicrosoftDocs/diannegali-gohuntexport
Preview for export to pdf for XDR customers
2 parents edb9458 + 0dd8429 commit 61390f9

File tree

3 files changed

+20
-21
lines changed

3 files changed

+20
-21
lines changed

defender-xdr/investigate-incidents.md

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Investigate incidents in Microsoft Defender XDR
3-
description: Investigate incidents related to devices, users, and mailboxes.
2+
title: Investigate incidents in the Microsoft Defender portal
3+
description: Investigate incidents on various assets from correlated signals of various Defender services and other Microsoft security products like Microsoft Sentinel.
44
ms.service: defender-xdr
55
f1.keywords:
66
- NOCSH
@@ -16,20 +16,19 @@ ms.topic: conceptual
1616
search.appverid:
1717
- MOE150
1818
- MET150
19-
ms.date: 12/04/2023
19+
ms.date: 11/13/2024
20+
appliesto:
21+
- Microsoft Defender XDR
22+
- Microsoft Sentinel in the Microsoft Defender portal
2023
---
2124

22-
# Investigate incidents in Microsoft Defender XDR
25+
# Investigate incidents in the Microsoft Defender portal
2326

2427
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/microsoft-defender.md)]
2528

26-
**Applies to:**
27-
28-
- Microsoft Defender XDR
29+
The Microsoft Defender portal presents correlated alerts, assets, investigations, and evidence from across all your assets into an incident to give you a comprehensive look into the entire breadth of an attack.
2930

30-
Microsoft Defender XDR aggregates all related alerts, assets, investigations, and evidence from across your devices, users, and mailboxes into an incident to give you a comprehensive look into the entire breadth of an attack.
31-
32-
Within an incident, you analyze the alerts that affect your network, understand what they mean, and collate the evidence so that you can devise an effective remediation plan.
31+
Within an incident, you analyze the alerts, understand what they mean, and collate the evidence so that you can devise an effective remediation plan.
3332

3433
## Initial investigation
3534

@@ -84,7 +83,9 @@ From the graph, you can:
8483

8584
- Hunt for entity information of a device, file, IP address, or URL.
8685

87-
The *go hunt* option takes advantage of the [advanced hunting](advanced-hunting-go-hunt.md) feature to find relevant information about an entity. The *go hunt* query checks relevant schema tables for any events or alerts involving the specific entity you're investigating. You can select any of the options to find relevant information about the entity:
86+
### Go hunt
87+
88+
The ***go hunt*** action takes advantage of the [advanced hunting](advanced-hunting-go-hunt.md) feature to find relevant information about an entity. The *go hunt* query checks relevant schema tables for any events or alerts involving the specific entity you're investigating. You can select any of the options to find relevant information about the entity:
8889

8990
- See all available queries – the option returns all available queries for the entity type you're investigating.
9091
- All Activity – the query returns all activities associated with an entity, providing you with a comprehensive view of the incident's context.
@@ -96,7 +97,7 @@ The resulting logs or alerts can be linked to an incident by selecting a results
9697

9798
:::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":::
9899

99-
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+
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.
100101

101102
## Summary
102103

defender-xdr/manage-incidents.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.topic: how-to
1919
search.appverid:
2020
- MOE150
2121
- MET150
22-
ms.date: 08/21/2024
22+
ms.date: 11/18/2024
2323
appliesto:
2424
- Microsoft Defender XDR
2525
- Microsoft Sentinel in the Microsoft Defender portal
@@ -291,12 +291,10 @@ When doing a postmortem of an incident, view the incident's **Activity log** to
291291

292292
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.
293293

294-
### Export incident data to PDF
295-
296294
> [!IMPORTANT]
297295
> Some information in this article relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
298-
>
299-
> The export incident data feature is currently available to Microsoft Defender XDR and Microsoft unified security operations center (SOC) platform customers with the Microsoft Copilot for security license.
296+
297+
## Export incident data to PDF
300298

301299
You can export an incident's data to PDF through the **Export incident as PDF** function and save it into PDF format. This function allows security teams to review an incident's details offline at any given time.
302300

@@ -343,9 +341,7 @@ The report is cached for a couple of minutes. The system provides the previously
343341

344342
## Next steps
345343

346-
For new incidents, begin your [investigation](investigate-incidents.md).
347-
348-
For in-process incidents, continue your [investigation](investigate-incidents.md).
344+
For new and in-process incidents, continue your [incident investigation](investigate-incidents.md).
349345

350346
For resolved incidents, perform a [post-incident review](respond-first-incident-remediate.md).
351347

defender-xdr/whats-new.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: defender-xdr
66
ms.author: diannegali
77
author: diannegali
88
ms.localizationpriority: medium
9-
ms.date: 10/17/2024
9+
ms.date: 11/18/2024
1010
manager: dansimp
1111
audience: ITPro
1212
ms.collection:
@@ -31,6 +31,8 @@ You can also get product updates and important notifications through the [messag
3131

3232
## November 2024
3333

34+
- (Preview) Microsoft Defender XDR customers can now export incident data to PDF. Use the exported data to easily capture and share incident data to other stakeholders. For details, see **[Export incident data to PDF](manage-incidents.md#export-incident-data-to-pdf)**.
35+
- (GA) The **last update time** column in the [incident queue](incident-queue.md#incident-queue) is now generally available.
3436
- (Preview) Cloud-native investigation and response actions are now available for container-related alerts in the Microsoft Defender portal. Security operations center (SOC) analysts can now investigate and respond to container-related alerts in near real-time with cloud-native response actions and investigation logs to hunt for related activities. For more information, see [Investigate and respond to container threats in the Microsoft Defender portal](investigate-respond-container-threats.md).
3537
- (GA) The `arg()` operator in [advanced hunting](advanced-hunting-defender-use-custom-rules.md#use-arg-operator-for-azure-resource-graph-queries) in Microsoft Defender portal is now generally available. Users can now use the *arg()* operator for Azure Resource Graph queries to search over Azure resources, and no longer need to go to Log Analytics in Microsoft Sentinel to use this operator if already in Microsoft Defender.
3638
- (Preview) The [CloudProcessEvents](advanced-hunting-cloudprocessevents-table.md) table is now available for preview in advanced hunting. It contains information about process events in multicloud hosted environments. You can use it to discover threats that can be observed through process details, like malicious processes or command-line signatures.

0 commit comments

Comments
 (0)