Skip to content

Commit 02e074a

Browse files
Merge branch 'main' into patch-14
2 parents 84410db + e69f90c commit 02e074a

19 files changed

+146
-38
lines changed

ATPDocs/deploy/active-directory-federation-services.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,9 +55,6 @@ Configure the SQL server to allow the Directory Service Account with the followi
5555
- *read*
5656
- *select*
5757

58-
> [!NOTE]
59-
> If the AD FS database runs on a dedicated SQL server instead of the local AD FS server, and you're using a group Managed Service Account (gMSA) as the Directory Service Account, make sure that you grant the SQL server the [required permissions](create-directory-service-account-gmsa.md#prerequisites-grant-permissions-to-retrieve-the-gmsa-accounts-password) to retrieve the gMSA's password.
60-
6158
### Grant access to the AD FS database
6259

6360
Grant access to the AD FS database by using SQL Server Management Studio, Transact-SQL (T-SQL), or PowerShell.

defender-xdr/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -132,6 +132,8 @@
132132
href: configure-attack-disruption.md
133133
- name: View details and results
134134
href: autoad-results.md
135+
- name: Exclude assets from automated responses
136+
href: automatic-attack-disruption-exclusions.md
135137
- name: Manage the deception capability
136138
items:
137139
- name: Overview
Lines changed: 123 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,123 @@
1+
---
2+
title: Exclude assets from automated response in attack disruption
3+
description: Learn more about how to exclude identities and devices from being automatically contained from automatic attack disruption.
4+
ms.service: defender-xdr
5+
f1.keywords:
6+
- NOCSH
7+
ms.author: diannegali
8+
author: diannegali
9+
ms.localizationpriority: medium
10+
manager: deniseb
11+
audience: ITPro
12+
ms.collection:
13+
- m365-security
14+
- tier1
15+
- usx-security
16+
- usx-security
17+
ms.topic: conceptual
18+
search.appverid:
19+
- MOE150
20+
- MET150
21+
ms.date: 02/16/2025
22+
appliesto:
23+
- Microsoft Defender XDR
24+
---
25+
26+
# Exclude assets from automated responses in automatic attack disruption
27+
28+
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/microsoft-defender.md)]
29+
30+
This article provides information on how to exclude assets from being automatically contained by [automatic attack disruption](automatic-attack-disruption.md) in Microsoft Defender XDR.
31+
32+
Automatic attack disruption enables the exclusion of specific user accounts, devices, and IP addresses from automated containment actions. Once excluded, these assets won't be affected by automated actions triggered by attack disruption.
33+
34+
> [!CAUTION]
35+
> Excluding assets from automated responses is not recommended. Excluding assets from automated responses can reduce the effectiveness of automatic attack disruption in protecting your environment from sophisticated, high-impact attacks.
36+
37+
## Prerequisites
38+
39+
To exclude assets from automated responses in automatic attack disruption, you must have one of the following roles assigned in either Microsoft Entra ID ([https://portal.azure.com](https://portal.azure.com)) or in the Microsoft 365 admin center ([https://admin.microsoft.com](https://admin.microsoft.com)):
40+
41+
- Global Administrator
42+
- Security Administrator
43+
44+
## Review or change automated response exclusions for assets
45+
46+
To exclude assets from automated responses in automatic attack disruption, follow these steps:
47+
48+
1. Go to the Microsoft Defender portal ([https://security.microsoft.com](https://security.microsoft.com)) and sign in.
49+
50+
2. Go to **Settings** \> **Microsoft Defender XDR**.
51+
52+
### Exclude user accounts
53+
54+
1. Under **Automated response**, select **Identities**.
55+
56+
2. To exclude a user account, select **Add user exclusion**. A flyout pane appears.
57+
58+
:::image type="content" source="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-identity-add-small.png" alt-text="Identities page in the automated response settings for attack disruption" lightbox="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-identity-add.png":::
59+
60+
3. In the flyout pane, enter the user account names in the **Select users** box and select the user accounts you want to exclude.
61+
62+
:::image type="content" source="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-identity-flyout-small.png" alt-text="Flyout pane when adding and selecting users to exclude in the automated response settings for attack disruption" lightbox="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-identity-flyout.png":::
63+
64+
4. Select **Exclude users** to save the exclusion.
65+
66+
### Exclude device groups
67+
68+
> [!CAUTION]
69+
> Excluding device groups from automated responses also impacts [automated investigation and response](m365d-autoir.md) actions.
70+
71+
1. Under **Automated responses**, select **Devices**.
72+
73+
2. In the **Device groups** tab, choose a device group by selecting the checkbox next to the group name from the list to configure attack disruption automation settings.
74+
75+
:::image type="content" source="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-device-select-small.png" alt-text="Device groups tab in the automated response settings for attack disruption" lightbox="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-device-select.png":::
76+
77+
3. In the flyout pane, select the appropriate automation level for the device group. You can choose from any of the following automation levels appropriate for your device group:
78+
- **Full - remediate threats automatically**: Automatically contain devices when a threat is detected.
79+
- **Semi - require approval for core folders**: Automatically investigate devices when an alert is received and apply remediation actions except to items within core system folders. Remediation actions for the core folders require approval.
80+
- **Semi - require approval for non-temp folders**: Automatically investigate and apply remediation to actions within temp and download folders when an alert is received. All other remediation actions require approval.
81+
- **Semi - require approval for all folders**: Automatically investigate devices when an alert is received. All remediation actions require approval.
82+
- **No automated response**: No automated investigation or response is taken for devices in this group.
83+
84+
:::image type="content" source="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-device-flyout-small.png" alt-text="Flyout pane when configuring automation levels for a device group" lightbox="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-device-flyout.png":::
85+
86+
4. Select **Save** to save the automation level for the device group.
87+
88+
> [!IMPORTANT]
89+
> Some information in this article relates to a prereleased product, which may be substantially modified before it's commercially released. Microsoft makes no warranties expressed or implied, with respect to the information provided here.
90+
91+
### Exclude IPs
92+
93+
1. Under **Automated responses**, select **Devices**.
94+
95+
2. In the **IPs** tab, select **Exclude IP** to exclude an IP address.
96+
97+
:::image type="content" source="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-ip-add-small.png" alt-text="IPs tab in the automated response settings for attack disruption" lightbox="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-ip-add.png":::
98+
99+
3. In the flyout pane, enter the IP address/IP range/IP subnet you want to exclude. You can add multiple IP addresses and IP subnets by separating them with a comma.
100+
101+
:::image type="content" source="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-ip-flyout-small.png" alt-text="Flyout pane when adding IP addresses to exclude in the automated response settings for attack disruption" lightbox="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-ip-flyout.png":::
102+
103+
4. Add a name and note for the exclusion. Select **Create** to save the exclusion.
104+
105+
### Remove exclusions
106+
107+
To remove an exclusion:
108+
109+
- Go to the **Identities** page. Select the user account you want to remove from the list and then select **Remove**.
110+
111+
:::image type="content" source="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-user-remove.png" alt-text="Highlighting the removal option when removing an excluded user in the Identities page of attack disruption automation settings":::
112+
113+
- Go to the **Devices** page and navigate to the **IPs** tab. Select the IP address you want to remove from the list and then select **Remove exclusion**.
114+
115+
:::image type="content" source="/defender/media/automatic-attack-disruption/exclusions/attack-disrupt-exclude-ip-remove.png" alt-text="Highlighting the removal option when removing an excluded IP in the IP tab of attack disruption automation settings":::
116+
117+
- Device group exclusions can be configured in the **Device groups** tab. Select the device group you want to configure from the list and choose the appropriate exclusion from the flyout pane. Select **Save** to save the exclusion.
118+
119+
## See also
120+
121+
- [View details and results of automated attack disruption actions](autoad-results.md)
122+
123+
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/defender-m3d-techcommunity.md)]

defender-xdr/configure-attack-disruption.md

Lines changed: 17 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Configure automatic attack disruption capabilities in Microsoft Defender XDR
3-
description: Configure automatic attack disruption options in Microsoft Defender XDR
2+
title: Configure automatic attack disruption in Microsoft Defender XDR
3+
description: Learn how to set up automatic attack disruption in Microsoft Defender XDR and ensure prerequisites are met.
44
search.appverid: MET150
55
ms.author: diannegali
66
author: diannegali
@@ -9,7 +9,7 @@ audience: ITPro
99
ms.topic: how-to
1010
ms.service: defender-xdr
1111
ms.localizationpriority: medium
12-
ms.date: 12/24/2024
12+
ms.date: 02/16/2025
1313
ms.collection:
1414
- m365-security
1515
- tier2
@@ -20,30 +20,25 @@ ms.reviewer: evaldm, isco
2020
f1.keywords: CSH
2121
---
2222

23-
# Configure automatic attack disruption capabilities in Microsoft Defender XDR
23+
# Configure automatic attack disruption in Microsoft Defender XDR
2424

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

2727
Microsoft Defender XDR includes powerful [automated attack disruption](automatic-attack-disruption.md) capabilities that can protect your environment from sophisticated, high-impact attacks.
2828

29-
This article describes how to configure automatic attack disruption capabilities in <a href="https://go.microsoft.com/fwlink/p/?linkid=2077139" target="_blank">Microsoft Defender XDR</a> with these steps:
29+
This article describes how to configure automatic attack disruption capabilities in <a href="https://go.microsoft.com/fwlink/p/?linkid=2077139" target="_blank">Microsoft Defender XDR</a>. After you're all set up, you can view and manage containment actions in Incidents and the Action center. And, if necessary, you can make changes to settings.
3030

31-
1. [Review the prerequisites](#prerequisites-for-automatic-attack-disruption-in-microsoft-365-defender).
32-
2. [Review or change the automated response exclusions for users](#review-or-change-automated-response-exclusions-for-users).
31+
## Prerequisites
3332

34-
Then, after you're all set up, you can view and manage containment actions in Incidents and the Action center. And, if necessary, you can make changes to settings.
35-
36-
<a name='prerequisites-for-automatic-attack-disruption-in-microsoft-365-defender'></a>
37-
38-
## Prerequisites for automatic attack disruption in Microsoft Defender XDR
33+
The following are prerequisites for configuring automatic attack disruption in Microsoft Defender XDR:
3934

4035
|Requirement|Details|
4136
|---|---|
4237
|Subscription requirements|One of these subscriptions: <ul><li>Microsoft 365 E5 or A5</li><li>Microsoft 365 E3 with the Microsoft 365 E5 Security add-on</li><li>Microsoft 365 E3 with the Enterprise Mobility + Security E5 add-on</li><li>Microsoft 365 A3 with the Microsoft 365 A5 Security add-on</li><li>Windows 10 Enterprise E5 or A5</li><li>Windows 11 Enterprise E5 or A5</li><li>Enterprise Mobility + Security (EMS) E5 or A5</li><li>Office 365 E5 or A5</li><li>Microsoft Defender for Endpoint (Plan 2)</li><li>Microsoft Defender for Identity</li><li>Microsoft Defender for Cloud Apps</li><li>Defender for Office 365 (Plan 2)</li><li>Microsoft Defender for Business</li></ul> <p> See [Microsoft Defender XDR licensing requirements](./prerequisites.md#licensing-requirements).|
4338
|Deployment requirements|<ul><li>Deployment across Defender products (e.g., Defender for Endpoint, Defender for Office 365, Defender for Identity, and Defender for Cloud Apps)</li><ul><li>The wider the deployment, the greater the protection coverage is. For example, if a Microsoft Defender for Cloud Apps signal is used in a certain detection, then this product is required to detect the relevant specific attack scenario.</li><li>Similarly, the relevant product should be deployed to execute an automated response action. For example, Microsoft Defender for Endpoint is required to automatically contain a device. </li></ul><li>Microsoft Defender for Endpoint's device discovery is set to 'standard discovery' (prerequisite for the automatic initiation of the "Contain Device" action)</li></ul>|
4439
|Permissions|To configure automatic attack disruption capabilities, you must have one of the following roles assigned in either Microsoft Entra ID (<https://portal.azure.com>) or in the Microsoft 365 admin center (<https://admin.microsoft.com>): <ul><li>Global Administrator</li><li>Security Administrator</li></ul>To work with automated investigation and response capabilities, such as by reviewing, approving, or rejecting pending actions, see [Required permissions for Action center tasks](m365d-action-center.md#required-permissions-for-action-center-tasks).|
4540

46-
### Microsoft Defender for Endpoint Prerequisites
41+
### Microsoft Defender for Endpoint prerequisites
4742

4843
#### Minimum Sense Client version (MDE client)
4944

@@ -65,10 +60,10 @@ Review the configured automation level for your device group policies, whether a
6560

6661
Device discovery settings must be activated to "Standard Discovery" at a minimum. Learn how to configure device discovery in [Set up device discovery](/defender-endpoint/configure-device-discovery).
6762

68-
>[!NOTE]
69-
>Attack disruption can act on devices independent of a device's Microsoft Defender Antivirus operating state. The operating state can be in Active, Passive, or EDR Block Mode.
63+
> [!NOTE]
64+
> Attack disruption can act on devices independent of a device's Microsoft Defender Antivirus operating state. The operating state can be in Active, Passive, or EDR Block Mode.
7065
71-
### Microsoft Defender for Identity Prerequisites
66+
### Microsoft Defender for Identity prerequisites
7267

7368
#### Set up auditing in domain controllers
7469

@@ -82,12 +77,12 @@ You can find more information on the action accounts in [Configure Microsoft Def
8277

8378
The Defender for Identity sensor needs to be deployed on the domain controller where the Active Directory account is to be turned off.
8479

85-
>[!NOTE]
86-
>If you have automations in place to activate or block a user, check if the automations can interfere with Disruption. For example, if there is an automation in place to regularly check and enforce that all active employees have enabled accounts, this could unintentionally activate accounts that were deactivated by attack disruption while an attack is detected.
80+
> [!NOTE]
81+
> If you have automation in place to activate or block a user, check if the automation can interfere with disruption. For example, if there is an automation in place to regularly check and enforce that all active employees have enabled accounts, this could unintentionally activate accounts that were deactivated by attack disruption while an attack is detected.
8782
8883
### Microsoft Defender for Cloud Apps prerequisites
8984

90-
#### Microsoft Office 365 Connector
85+
#### Microsoft Office 365 connector
9186

9287
Microsoft Defender for Cloud Apps must be connected to Microsoft Office 365 through the connector. To connect Defender for Cloud Apps, see [Connect Microsoft 365 to Microsoft Defender for Cloud Apps](/defender-cloud-apps/protect-office-365#connect-microsoft-365-to-microsoft-defender-for-cloud-apps).
9388

@@ -113,27 +108,15 @@ The following mailbox events need to be audited by minimum:
113108

114109
Review [manage mailbox auditing](/purview/audit-mailboxes) to learn about managing mailbox auditing.
115110

116-
#### Safelinks policy needs to be present.
117-
118-
## Review or change automated response exclusions for users
119-
120-
Automatic attack disruption enables the exclusion of specific user accounts from automated containment actions. Excluded users won't be affected by automated actions triggered by attack disruption. You must be a global administrator or security administrator to perform the following procedure:
121-
122-
1. Go to the Microsoft Defender portal ([https://security.microsoft.com](https://security.microsoft.com)) and sign in.
123-
124-
2. Go to **Settings** \> **Microsoft Defender XDR** \> **Identity automated response**. Check the user list to exclude accounts.
125-
:::image type="content" source="/defender/media/automatic-attack-disruption/Fig3-exclude-specific-users.png" alt-text="Selecting user accounts for automated response exclusion" lightbox="/defender/media/automatic-attack-disruption/Fig3-exclude-specific-users.png":::
126-
127-
3. To exclude a new user account, select **Add user exclusion**.
128-
129-
Excluding user accounts is not recommended, and accounts added to this list won't be suspended in all supported attack types like business email compromise (BEC) and human-operated ransomware.
111+
#### Safelinks policy needs to be present
130112

131113
## Next steps
132114

133115
- [View details and results](autoad-results.md)
116+
- [Set and manage attack disruption exclusions](automatic-attack-disruption-exclusions.md)
134117
- [Get email notifications for response actions](m365d-response-actions-notifications.md)
135118

136-
## See also
119+
## Related content
137120

138121
- [Automatic attack disruption in Microsoft Defender XDR](automatic-attack-disruption.md)
139122
- [Automatic attack disruption for SAP](/azure/sentinel/sap/deployment-attack-disrupt)

defender-xdr/whats-new.md

Lines changed: 4 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: 01/17/2025
9+
ms.date: 02/16/2025
1010
manager: dansimp
1111
audience: ITPro
1212
ms.collection:
@@ -33,6 +33,9 @@ For more information on what's new with other Microsoft Defender security produc
3333
You can also get product updates and important notifications through the [message center](https://admin.microsoft.com/Adminportal/Home#/MessageCenter).
3434

3535
## February 2025
36+
37+
- (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).
38+
3639
- (Preview) The `PrivilegedEntraPimRoles` column is available for preview in the advanced hunting [IdentityInfo](advanced-hunting-identityinfo-table.md) table.
3740

3841

109 KB
Loading
275 KB
Loading
74.7 KB
Loading
185 KB
Loading
62.8 KB
Loading

0 commit comments

Comments
 (0)