Skip to content

Commit af04175

Browse files
committed
added image
1 parent 782a4ad commit af04175

File tree

3 files changed

+10
-2
lines changed

3 files changed

+10
-2
lines changed

defender-xdr/threat-analytics.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ With more sophisticated adversaries and new threats emerging frequently and prev
5959
Each report provides an analysis of a tracked threat and extensive guidance on how to defend against that threat. It also incorporates data from your network, indicating whether the threat is active and if you have applicable protections in place.
6060

6161
## Required roles and permissions
62-
To access Threat analytics in the Defender portal, you need to have a license for at least one Microsoft Defender XDR. For more information, see [Microsoft Defender XDR prerequisites](prerequisites.md).
62+
To access Threat analytics in the Defender portal, you need to have a license for at least one Microsoft Defender XDR product. For more information, see [Microsoft Defender XDR prerequisites](prerequisites.md).
6363

6464
>[!NOTE]
6565
> The Microsoft Defender for Endpoint P1 license is an exception to this prerequisite and will not grant Threat analytics access.
@@ -200,7 +200,11 @@ In the **Recommended actions** tab, review the list of specific actionable recom
200200

201201
## Set up custom detections and link them to Threat analytics reports
202202

203-
You can set up [custom detection rules](custom-detections-overview.md) and link them to Threat analytics reports. If these rules get triggered and an alert generates an incident, the report shows up in that incident and the incident appears under the **Related incidents** tab, just like any other Microsoft-defined detection. [Learn more about creating and managing custom detections rules](custom-detection-rules.md)
203+
You can set up [custom detection rules](custom-detections-overview.md) and link them to Threat analytics reports. If these rules get triggered and an alert generates an incident, the report shows up in that incident and the incident appears under the **Related incidents** tab, just like any other Microsoft-defined detection.
204+
205+
:::image type="content" source="/defender/media/threat-analytics/ta-custom-detection.png" alt-text="Screenshot of custom detection setup page with Threat analytics option highlighted." lightbox="/defender/media/threat-analytics/ta-custom-detection.png":::
206+
207+
[Learn more about creating and managing custom detections rules](custom-detection-rules.md)
204208

205209
## Set up email notifications for report updates
206210

defender-xdr/whats-new.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,10 @@ For more information on what's new with other Microsoft Defender security produc
3232

3333
You can also get product updates and important notifications through the [message center](https://admin.microsoft.com/Adminportal/Home#/MessageCenter).
3434

35+
## March 2025
36+
37+
- 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)
38+
3539
## February 2025
3640

3741
- (Preview) IP addresses can now be excluded from automated responses in attack disruption. This feature allows you to exclude specific IPs from automated containment actions triggered by attack disruption. For more information, see [Exclude assets from automated responses in automatic attack disruption](automatic-attack-disruption-exclusions.md).
143 KB
Loading

0 commit comments

Comments
 (0)