Skip to content

Commit b359071

Browse files
authored
Merge branch 'main' into WI474425-mda-usernames-must-contain-alphanumeric-characters
2 parents d4a51f6 + e72b198 commit b359071

17 files changed

+290
-30
lines changed

ATPDocs/whats-new.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,14 @@ For updates about versions and features released six months ago or earlier, see
2525

2626
## August 2025
2727

28-
**Suspected Brute Force attack (Kerberos, NTLM):** Improved detection logic now includes scenarios where accounts were locked during the attacks. As a result, the number of triggered alerts might increase.
28+
### Sensor version 2.246
29+
30+
This version includes bug fixes and stability improvements for the Microsoft Defender for Identity sensor.
31+
32+
### Detection update: Suspected Brute Force attack (Kerberos, NTLM)
33+
34+
Improved detection logic to include scenarios where accounts were locked during attacks. As a result, the number of triggered alerts might increase.
35+
2936

3037
## July 2025
3138

CloudAppSecurityDocs/proxy-intro-aad.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,8 @@ ms.topic: concept-article
66
---
77
# Conditional Access app control in Microsoft Defender for Cloud Apps
88

9-
In today's workplace, it's not enough to know what happened in your cloud environment after the fact. You need to stop breaches and leaks in real time. You also need to prevent employees from intentionally or accidentally putting your data and organization at risk.
10-
11-
You want to support users in your organization while they use the best cloud apps available and bring their own devices to work. However, you also need tools to protect your organization from data leaks and theft in real time. Microsoft Defender for Cloud Apps integrates with any identity provider (IdP) to deliver this protection with [access](access-policy-aad.md) and [session](session-policy-aad.md) policies.
9+
In today’s workplace, it’s not enough to understand what happened in your cloud environment after the fact, you need to stop breaches and data leaks as they happen. That includes preventing employees from intentionally or accidentally putting your data and organization at risk.
10+
Microsoft Defender for Cloud Apps helps you strike the right balance: enabling productivity with the best cloud apps while protecting your data in real time. It delivers deep visibility and control over **browser-based sessions** through integration with any identity provider (IdP), using powerful [access](access-policy-aad.md) and [session](session-policy-aad.md) policies.
1211

1312
For example:
1413

@@ -26,6 +25,8 @@ Microsoft Edge users benefit from [direct, in-browser protection](in-browser-pro
2625

2726
Users of other browsers are redirected via reverse proxy to Defender for Cloud Apps. Those browsers display an `*.mcas.ms` suffix in the link's URL. For example, if the app URL is `myapp.com`, the app URL is updated to `myapp.com.mcas.ms`.
2827

28+
To prevent bypassing this protection, admins should configure access policies to block native client access and allow only browser-based sessions.
29+
2930
This article describes Conditional Access app control in Defender for Cloud Apps through [Microsoft Entra Conditional Access](/entra/identity/conditional-access/overview) policies.
3031

3132
## Activities in Conditional Access app control

defender-endpoint/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -803,6 +803,8 @@
803803
href: microsoft-defender-endpoint-antivirus-performance-mode.md
804804
- name: Compatibility with other security products
805805
href: microsoft-defender-antivirus-compatibility.md
806+
- name: Defender for Endpoint passive mode
807+
href: microsoft-defender-passive-mode.md
806808
- name: Microsoft Defender Antivirus and third-party antivirus solutions without
807809
Defender for Endpoint
808810
href: defender-antivirus-compatibility-without-mde.md

defender-endpoint/attack-surface-reduction-rules-reference.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -583,6 +583,9 @@ Dependencies: Microsoft Defender Antivirus
583583

584584
### Block rebooting machine in Safe Mode
585585

586+
> [!NOTE]
587+
> This feature isn't supported in Threat and Vulnerability Management, so the Attack Surface Reduction rule report will show as "Not applicable" for Windows and Windows Servers.
588+
586589
This rule prevents the execution of commands to restart machines in Safe Mode. Safe Mode is a diagnostic mode that only loads the essential files and drivers needed for Windows to run. However, in Safe Mode, many security products are either disabled or operate in a limited capacity, which allows attackers to further launch tampering commands, or execute and encrypt all files on the machine. This rule blocks such attacks by preventing processes from restarting machines in Safe Mode.
587590

588591
Intune Name: ` Block rebooting machine in Safe Mode`
@@ -621,6 +624,9 @@ Dependencies: Microsoft Defender Antivirus
621624

622625
### Block use of copied or impersonated system tools
623626

627+
> [!NOTE]
628+
> This feature isn't supported in Threat and Vulnerability Management, so the Attack Surface Reduction rule report will show as "Not applicable" for Windows and Windows Servers.
629+
624630
This rule blocks the use of executable files that are identified as copies of Windows system tools. These files are either duplicates or impostors of the original system tools. Some malicious programs might try to copy or impersonate Windows system tools to avoid detection or gain privileges. Allowing such executable files can lead to potential attacks. This rule prevents propagation and execution of such duplicates and impostors of the system tools on Windows machines.
625631

626632
Intune Name: `Block use of copied or impersonated system tools`
@@ -652,7 +658,7 @@ GUID: `a8f5898e-1dc8-49a9-9878-85004b8a61e6`
652658
Dependencies: Microsoft Defender Antivirus
653659

654660
> [!NOTE]
655-
> When managing ASR rules using Microsoft Defender for Endpoint security settings management, the setting for **Block Webshell creation for Servers** must be configured as `Not Configured` in Group Policy or other local settings. If this rule is set to any other value (such as `Enabled` or `Disabled`), it could cause conflicts and prevent the policy from applying correctly through security settings management.
661+
> When managing ASR rules using Microsoft Defender for Endpoint security settings management, the setting for **Block Webshell creation for Servers** must be configured as `Not Configured` in Group Policy or other local settings. If this rule is set to any other value (such as `Enabled` or `Disabled`), it could cause conflicts and prevent the policy from applying correctly through security settings management. This feature isn't supported in Threat and Vulnerability Management, so the Attack Surface Reduction rule report will show as "Not applicable" for Exchange servers.
656662
657663
### Block Win32 API calls from Office macros
658664

defender-endpoint/configure-endpoints-vdi.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -103,6 +103,10 @@ The following steps guide you through onboarding VDI devices and highlight steps
103103
| Single entry for each device | 1. Select the **PowerShell Scripts** tab, then select **Add** (Windows Explorer opens directly in the path where you copied the onboarding script earlier). <br/>2. Navigate to onboarding PowerShell script `Onboard-NonPersistentMachine.ps1`. There's no need to specify the other file, as it's triggered automatically. |
104104
| Multiple entries for each device | 1. Select the **Scripts** tab, then select **Add** (Windows Explorer opens directly in the path where you copied the onboarding script earlier). <br/>2. Navigate to the onboarding bash script `WindowsDefenderATPOnboardingScript.cmd`. |
105105

106+
> [!NOTE]
107+
> When using the 'Single entry for each device' onboarding method for non-persistent VDI environments, ensure that the Onboard-NonPersistentMachine.ps1 script is executed only after the virtual machine has received its final hostname and completed its final reboot.<br>
108+
> For example, if your VDI provisioning process includes multiple reboots or configuration stages after the VM is cloned from a master image, delay the script execution until the last reboot is complete and final machine name is assigned.<br> Running the script too early may result in duplicate device entries or inconsistent onboarding to Microsoft Defender for Endpoint.
109+
106110
5. Test your solution by following these steps:
107111

108112
1. Create a pool with one device.

defender-endpoint/indicator-file.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: defender-endpoint
66
ms.author: deniseb
77
author: denisebmsft
88
ms.localizationpriority: medium
9-
ms.date: 06/06/2025
9+
ms.date: 07/30/2025
1010
manager: deniseb
1111
audience: ITPro
1212
ms.collection:
@@ -79,7 +79,7 @@ Understand the following prerequisites before you create indicators for files:
7979

8080
## Create an indicator for files from the settings page
8181

82-
1. In the navigation pane, select **Settings** \> **Endpoints** \> **Indicators** (under **Rules**).
82+
1. In the navigation pane, select **System** \> **Settings** \> **Endpoints** \> **Indicators** (under **Rules**).
8383

8484
2. Select the **File hashes** tab.
8585

defender-endpoint/microsoft-defender-core-service-overview.md

Lines changed: 21 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -33,37 +33,50 @@ To enhance your endpoint security experience, Microsoft is releasing the Microso
3333
- Mid April 2024 to Enterprise customers running Windows clients.
3434
- Beginning of July 2024 to U.S. Government customers running Windows clients.
3535

36-
- Mid January 2025 to Enterprise customers running Windows Server.
36+
The Microsoft Defender Core service for Windows Server is releasing with [Microsoft Defender Antivirus platform version 4.18.25050.5.](/defender-endpoint/microsoft-defender-antivirus-updates)
3737

38-
3. If you're using the Microsoft Defender for Endpoint **streamlined** device connectivity experience, you don't need to add any other URLs.
38+
- Mid July 2025 to Enterprise customers running Windows Server 2019 or later.
39+
40+
- Mid September 2025 to Enterprise customers running the [unified Microsoft Defender for Endpoint client](/defender-endpoint/update-agent-mma-windows) for Windows Server 2012 R2 or Windows Server 2016.
41+
42+
1. If you're using the Microsoft Defender for Endpoint **streamlined** device connectivity experience, you don't need to add any other URLs.
3943

40-
4. If you're using the Microsoft Defender for Endpoint **standard** device connectivity experience:
44+
1. If you're using the Microsoft Defender for Endpoint **standard** device connectivity experience:
4145

4246
Enterprise customers should allow the following URLs:
4347

4448
- `*.endpoint.security.microsoft.com`
49+
4550
- `ecs.office.com/config/v1/MicrosoftWindowsDefenderClient`
51+
4652
- `*.events.data.microsoft.com`
4753

4854
If you don't want to use the wildcards for `*.events.data.microsoft.com`, you can use:
4955

5056
- `us-mobile.events.data.microsoft.com/OneCollector/1.0`
5157
- `eu-mobile.events.data.microsoft.com/OneCollector/1.0`
58+
5259
- `uk-mobile.events.data.microsoft.com/OneCollector/1.0`
60+
5361
- `au-mobile.events.data.microsoft.com/OneCollector/1.0`
62+
5463
- `mobile.events.data.microsoft.com/OneCollector/1.0`
55-
64+
5665
Enterprise U.S. Government customers should allow the following URLs:
5766

5867
- `*.events.data.microsoft.com`
68+
5969
- `*.endpoint.security.microsoft.us (GCC-H & DoD)`
70+
6071
- `*.gccmod.ecs.office.com (GCC-M)`
72+
6173
- `*.config.ecs.gov.teams.microsoft.us (GCC-H)`
74+
6275
- `*.config.ecs.dod.teams.microsoft.us (DoD)`
6376

64-
5. If you're using [Application Control for Windows](/windows/security/application-security/application-control/windows-defender-application-control/wdac), or you're running non-Microsoft antivirus or endpoint detection and response software, make sure to add the processes mentioned earlier to your allowlist.
77+
1. If you're using [Application Control for Windows](/windows/security/application-security/application-control/windows-defender-application-control/wdac), or you're running non-Microsoft antivirus or endpoint detection and response software, make sure to add the processes mentioned earlier to your allowlist.
6578

66-
6. Consumers don't need to take any actions to prepare.
79+
1. Consumers don't need to take any actions to prepare.
6780

6881
## Microsoft Defender Antivirus processes and services
6982

@@ -191,7 +204,8 @@ On the script page of the Run Script wizard, choose your script from the list (M
191204
#### Use the Registry to update the policies for Microsoft Defender Core service.
192205

193206
1. Select **Start**, and then open Regedit.exe as an administrator.
194-
2. Go to `HKLM\Software\Policies\Microsoft\Windows Defender\Features`
207+
1. Go to `HKLM\Software\Policies\Microsoft\Windows Defender\Features`
208+
195209
3. Set the values:
196210

197211
`DisableCoreService1DSTelemetry` (dword) 0 (hex)
Lines changed: 114 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,114 @@
1+
---
2+
title: Defender for Endpoint with Defender Antivirus in passive mode
3+
ms.topic: conceptual
4+
description: Understand how Defender Antivirus in passive mode works and when to use it.
5+
ms.service: defender-endpoint
6+
author: KesemSharabi
7+
ms.author: kesharab
8+
ms.localizationpriority: high
9+
audience: ITPro
10+
ms.collection:
11+
- m365-security
12+
- tier1
13+
- mde-ngp
14+
ms.subservice: ngp
15+
search.appverid: met150
16+
ms.date: 03/26/2025
17+
---
18+
19+
# Defender Antivirus in passive mode
20+
21+
[!INCLUDE [side-by-side-scenarios](includes/side-by-side-scenarios.md)]
22+
23+
Microsoft Defender for Endpoint is a comprehensive security solution designed to protect your devices from evolving threats. One of its key features enables Microsoft Defender Antivirus to coexist with non-Microsoft antimalware solutions while still providing valuable endpoint detection and response capabilities.
24+
25+
Some of the key benefits of Defender Antivirus in passive mode are:
26+
27+
* **EDR Block mode** - Post-breach protection by detecting and remediating threats missed by the active antimalware solution
28+
29+
* **Data Loss Prevention (DLP)** - Endpoint DLP functionalities operate normally, ensuring sensitive data is safeguarded.
30+
31+
* **Security intelligence updates** - Microsoft Defender Antivirus continues to receive updates to stay aware of the latest threats.
32+
33+
* **Data Loss Prevention (DLP)** - Endpoint DLP functionalities operate normally, ensuring sensitive data is safeguarded.
34+
35+
For more information, see [How Microsoft Defender Antivirus affects Defender for Endpoint functionality](microsoft-defender-antivirus-compatibility.md#how-microsoft-defender-antivirus-affects-defender-for-endpoint-functionality).
36+
37+
>[!NOTE]
38+
>Passive mode disables Microsoft Defender Antivirus scheduled scans unless specific configurations are applied.
39+
40+
## Prerequisites
41+
42+
* Operating system
43+
* Windows 10 or newer
44+
* Windows Server 2012 R2 or newer
45+
46+
* The device must be onboarded to Microsoft Defender for Endpoint
47+
48+
* Microsoft Defender Antivirus has to be installed and enabled
49+
50+
## Configure passive mode
51+
52+
On Windows 10 or newer, Defender Antivirus automatically enters passive mode when a non-Microsoft antimalware solution is installed and registered.
53+
54+
For Windows Server operating systems, follow the instructions in this section to configure passive mode for Microsoft Defender for Endpoint.
55+
56+
### Set the registry key
57+
58+
To avoid conflicts between Microsoft Defender Antivirus and a third-party antivirus solution, if you're using Windows Server, set the following registry key before onboarding the device to Microsoft Defender for Endpoint:
59+
60+
* **Path** - HKLM\SOFTWARE\Policies\Microsoft\Windows Advanced Threat Protection
61+
62+
* **Name** - ForceDefenderPassiveMode
63+
64+
* **Type** - REG_DWORD
65+
66+
* **Value** - 1
67+
68+
### Enable EDR in block mode
69+
70+
When Microsoft Defender Antivirus is in passive mode, EDR in block mode can provide post-breach protection by detecting and remediating threats. Ensure this feature is enabled in Defender for Endpoint.
71+
72+
### Avoid service modifications
73+
74+
Don't disable, stop, or modify associated services such as `wscsvc`, `WinDefend`, or `MsMpEng`. Stopping these services can cause instability and make your device vulnerable to threats.
75+
76+
### Exclude Defender binaries in third-party antivirus
77+
78+
To prevent performance issues or conflicts, add Microsoft Defender Antivirus and Defender for Endpoint binaries to the exclusion list of your third-party antivirus solution.
79+
80+
## Verify that passive mode is enabled
81+
82+
This section describes how to confirm whether Microsoft Defender Antivirus is in passive mode.
83+
84+
### Windows PowerShell
85+
86+
Run the following PowerShell cmdlet:
87+
88+
```powershell
89+
Get-MpComputerStatus | select AMRunningMode
90+
```
91+
92+
The `AMRunningMode` value indicates the current Defender Antivirus state:
93+
94+
* **Normal** - Active mode
95+
96+
* **Passive** - Passive mode
97+
98+
* **EDR Block Mode** - EDR is operating in block mode
99+
100+
### Windows security app
101+
102+
Follow these steps to verify that Microsoft Defender Antivirus is in passive mode (Windows 10 and later only).
103+
104+
1. Open the Windows Security app.
105+
106+
2. Select **Virus & threat protection**.
107+
108+
3. Under **Who’s protecting me?**, select **Manage providers**.
109+
110+
4. On the *Security providers* page, verify the antivirus provider and state.
111+
112+
## Additional resources
113+
114+
[Microsoft Defender Antivirus compatibility with other security products](microsoft-defender-antivirus-compatibility.md)

defender-endpoint/overview-attack-surface-reduction.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
- m365-security
1616
- tier2
1717
- mde-asr
18-
ms.date: 06/04/2024
18+
ms.date: 07/30/2025
1919
search.appverid: met150
2020
---
2121

@@ -38,8 +38,6 @@ search.appverid: met150
3838
3939
Attack surfaces are all the places where your organization is vulnerable to cyberthreats and attacks. Defender for Endpoint includes several capabilities to help reduce your attack surfaces. Watch the following video to learn more about attack surface reduction.
4040

41-
> [!VIDEO https://learn-video.azurefd.net/vod/player?id=06675c1f-cd4d-4c79-96f5-f695aee327e5]
42-
4341
## Configure attack surface reduction capabilities
4442

4543
To configure attack surface reduction in your environment, follow these steps:

defender-office-365/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -253,6 +253,8 @@
253253
href: tenant-allow-block-list-urls-configure.md
254254
- name: Allow or block IPv6 addresses using the Tenant Allow/Block List
255255
href: tenant-allow-block-list-ip-addresses-configure.md
256+
- name: Block domains in Microsoft Teams using the Tenant Allow/Block List
257+
href: tenant-allow-block-list-teams-domains-configure.md
256258
- name: Admin submissions
257259
href: submissions-admin.md
258260
- name: Create block sender lists

0 commit comments

Comments
 (0)