Skip to content

Commit ff45733

Browse files
authored
Merge branch 'main' into patch-35
2 parents bbcb78e + 6a2acab commit ff45733

File tree

6 files changed

+78
-51
lines changed

6 files changed

+78
-51
lines changed
-19 KB
Loading

ATPDocs/okta-integration.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -100,9 +100,8 @@ After assigning both roles, you can remove the Super Admin role. This ensures th
100100
1. Select **Create new role**.
101101
1. Set the role name to **Microsoft Defender for Identity**.
102102
1. Select the permissions you want to assign to this role. Include the following permissions:
103-
- **Suspend users**
104-
- **Unsuspend users**
105-
- **Clear users’ session**
103+
- **Edit user's lifecycle states**
104+
- **Edit user's authenticator operations**
106105
- **View roles, resources, and admin assignments**
107106
1. Select **Save role**.
108107

CloudAppSecurityDocs/anomaly-detection-policy.md

Lines changed: 66 additions & 29 deletions
Large diffs are not rendered by default.

CloudAppSecurityDocs/release-notes.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,14 @@ For news about earlier releases, see [Archive of past updates for Microsoft Defe
2727
> Learn more: [Network requirements](https://aka.ms/MDANetworkDocs).
2828
2929

30+
31+
## June 2025
32+
33+
### New Dynamic Threat Detection model
34+
35+
Microsoft Defender for Cloud Apps new dynamic threat detection model continuously adapts to the ever-changing SaaS apps threat landscape. This approach ensures your organization remains protected with up-to-date detection logic without the need for manual policy updates or reconfiguration. Several legacy anomaly detection policies have already been seamlessly transitioned to this adaptive model, delivering smarter and more responsive security coverage.
36+
For more information, see [Create Defender for Cloud Apps anomaly detection policies](anomaly-detection-policy.md).
37+
3038
## May 2025
3139

3240

defender-xdr/automatic-attack-disruption.md

Lines changed: 1 addition & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ ms.topic: concept-article
1818
search.appverid:
1919
- MOE150
2020
- MET150
21-
ms.date: 04/25/2025
21+
ms.date: 06/22/2025
2222
appliesto:
2323
- Microsoft Defender XDR
2424
---
@@ -76,21 +76,6 @@ Automatic attack disruption uses Microsoft-based XDR response actions. Examples
7676

7777
For more information, see [remediation actions](m365d-remediation-actions.md) in Microsoft Defender XDR.
7878

79-
### Automated response actions for SAP with Microsoft Sentinel
80-
81-
If you [onboarded Microsoft Sentinel to the Defender portal](microsoft-sentinel-onboard.md) and deployed the Microsoft Sentinel solution for SAP applications, you can also deploy automatic attack disruption for SAP.
82-
83-
For example, deploy attack disruption for SAP to contain compromised assets by locking suspicious SAP users in case of a financial process manipulation attack.
84-
85-
After the risk is mitigated, Microsoft Defender admins can manually unlock the users that had been automatically locked by the attack disruption response. The ability to manually unlock users is available from the Microsoft Defender action center, and only for users that were locked by attack disruption.
86-
87-
To use attack disruption for SAP, deploy a new data connector agent, or make sure that your agent is using version 90847355 or higher, and then assign and apply the required Azure and SAP roles. For more information, see:
88-
89-
- [Deploy and configure the container hosting the SAP data connector agent](/azure/sentinel/sap/deploy-data-connector-agent-container)
90-
- [Update Microsoft Sentinel's SAP data connector agent](/azure/sentinel/sap/update-sap-data-connector), especially [Update your system for automatic attack disruption](/azure/sentinel/sap/update-sap-data-connector#update-your-data-connector-agent-for-attack-disruption).
91-
92-
While you configure attack disruption in the Azure portal and your SAP system, automatic attack disruption itself surfaces only in the Microsoft Defender portal.
93-
9479
## Identify when an attack disruption happens in your environment
9580

9681
The Defender XDR incident page will reflect the automatic attack disruption actions through the attack story and the status indicated by a yellow bar (Figure 1). The incident shows a dedicated disruption tag, highlight the status of the assets contained in the incident graph, and add an action to the Action Center.

unified-secops-platform/gov-support.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: batamig
55
ms.author: bagol
66
ms.service: unified-secops-platform
77
ms.topic: concept-article #Don't change.
8-
ms.date: 03/11/2025
8+
ms.date: 06/22/2025
99
ms.collection:
1010
- usx-security
1111

@@ -26,8 +26,6 @@ This article provides information about support for US Government customers by u
2626

2727
- Features still in preview are available only in the commercial cloud.
2828

29-
While [automatic attack disruption](/defender-xdr/automatic-attack-disruption) with Microsoft Defender XDR is generally available, [SAP support for attack disruption](/defender-xdr/automatic-attack-disruption) with Microsoft Sentinel and Microsoft Defender XDR is available only in the commercial cloud.
30-
3129
For more information, see:
3230

3331
- [Microsoft Defender XDR for US Government customers](/defender-xdr/usgov)

0 commit comments

Comments
 (0)