You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ATPDocs/deploy/remote-calls-sam.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.topic: how-to
8
8
# Configure SAM-R to enable lateral movement path detection in Microsoft Defender for Identity
9
9
10
10
> [!IMPORTANT]
11
-
> Remote collection of local administrators' group members on endpoints (using SAM-R queries) feature in Microsoft Defender for Identity will be disabled by mid-May 2025.
11
+
> Remote collection of local administrators' group members on endpoints (using SAM-R queries) feature in Microsoft Defender for Identity will be disabled by mid-May 2025. This change will happen automatically by the specified dates. No admin action is required.
12
12
>
13
13
14
14
Microsoft Defender for Identity mapping for [potential lateral movement paths](/defender-for-identity/understand-lateral-movement-paths) relies on queries that identify local admins on specific machines. These queries are performed with the SAM-R protocol, using the Defender for Identity [Directory Service account](directory-service-accounts.md) you configured.
Copy file name to clipboardExpand all lines: ATPDocs/whats-new.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ For updates about versions and features released six months ago or earlier, see
25
25
## May 2025
26
26
27
27
### Local administrators collection (using SAM-R queries) feature will be disabled
28
-
Remote collection of local administrators' group members on endpoints (using SAM-R queries) feature in Microsoft Defender for Identity will be disabled by mid-May 2025. The details collected are used to build the potential lateral movement paths map. Alternative methods are currently being explored.
28
+
Remote collection of local administrators' group members on endpoints (using SAM-R queries) feature in Microsoft Defender for Identity will be disabled by mid-May 2025. The details collected are used to build the potential lateral movement paths map. Alternative methods are currently being explored. This change will happen automatically by the specified dates. No admin action is required.
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/activity-filters-queries.md
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,8 +170,21 @@ You can export all activities from the past six months by clicking the Export bu
170
170
171
171

172
172
173
-
When exporting data:
173
+
> [!NOTE]
174
+
> **Required Permissions for Exporting Capabilities:** To utilize the exporting features, users must be assigned one of the following roles:
175
+
> -**Built-in admin roles in Defender for Cloud Apps-** These roles must be granted via [Microsoft Defender for Cloud Apps Permissions and roles settings](/defender-cloud-apps/manage-admins):
176
+
> - Global Admin
177
+
> - Cloud Discovery Global Admin
178
+
> - Security Operator
179
+
> - Compliance Admin
180
+
> - Security Reader
181
+
> -**Microsoft Entra ID Roles-** These roles must be assigned through [Microsoft Entra ID built-in roles](/entra/identity/role-based-access-control/permissions-reference):
182
+
> - Global Administrator
183
+
> - Security Administrator
184
+
> - Cloud App Security Administrator
185
+
> - Global Reader
174
186
187
+
When exporting data:
175
188
- You can choose a date range of up to six months.
176
189
- You can choose to exclude private activities.
177
190
- The exported file is limited to 100,000 records and is delivered in CSV format.
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/in-browser-protection.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ To use in-browser protection, users must also have the following environmental r
27
27
|**Operating systems**|Windows 10 or 11, macOS|
28
28
|**Identity platform**|Microsoft Entra ID|
29
29
|**Microsoft Edge for Business versions**|The last two stable versions. For example, if the newest Microsoft Edge is 126, in-browser protection works for v126 and v125. <br> For more information, see [Microsoft Edge releases](/deployedge/microsoft-edge-release-schedule#microsoft-edge-releases).|
30
-
|**Supported session policies**|<ul><li>Block\Monitor of file download (all files\sensitive files)</li><li>Block\Monitor file upload (all files\sensitive files)</li><li>Block\Monitor copy\cut\paste</li><li>Block\Monitor print</li><li>Block\Monitor malware upload</li><li>Block\Monitor malware download</li></ul> <br> Users that are served by multiple policies, including at least one policy that's *not* supported by Microsoft Edge for Business, their sessions are always served by the reverse proxy. <br><br> Policies defined in the Microsoft Entra ID portal are also always served by reverse proxy.|
30
+
|**Supported session policies**|<ul><li>Block\Monitor of file download (all files\\*sensitive files)</li><li>Block\Monitor file upload (all files\\*sensitive files)</li><li>Block\Monitor copy\cut\paste</li><li>Block\Monitor print</li><li>Block\Monitor malware upload</li><li>Block\Monitor malware download</li></ul> <br> Users that are served by multiple policies, including at least one policy that's *not* supported by Microsoft Edge for Business, their sessions are always served by the reverse proxy. <br><br> Policies defined in the Microsoft Entra ID portal are also always served by reverse proxy.<br> *Sensitive files identified by built-in DLP scanning are not supported for Edge in-browser protection|
31
31
32
32
All other scenarios are served automatically with the standard reverse proxy technology, including user sessions from browsers that don't support in-browser protection, or for policies not supported by in-browser protection.
33
33
@@ -105,7 +105,7 @@ Administrators who understand the power of Microsoft Edge browser protection can
105
105
106
106
4. When you're finished on the **Edge for Business protection** page, select **Save**.
107
107
108
-
:::image type="content" source="media/in-browser-protection/edge-for-business-protection-settings.png" alt-text="Screenshot of Microsoft Edge for business protection settings." lightbox="media/in-browser-protection/edge-for-business-protection-settings.png":::
108
+
:::image type="content" source="media/in-browser-protection/edge-for-business-protection-settings.png" alt-text="Screenshot of Microsoft Edge for business protection settings." lightbox="media/in-browser-protection/edge-for-business-protection-settings.png":::
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/session-policy-aad.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,6 @@ This procedure describes how to create a new session policy in Defender for Clou
97
97
98
98
1. <aname="inspection"></a>In the **Apply to** area (Preview):
99
99
100
-
- Select whether to apply the policy to all files, or files in specified folders only
101
100
- Select an inspection method to use, such as data classification services, or malware. For more information, see [Microsoft Data Classification Services integration](dcs-inspection.md).
102
101
- Configure more detailed options for your policy, such as scenarios based on elements like fingerprints or trainable classifiers.
Copy file name to clipboardExpand all lines: defender-endpoint/android-configure.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,7 +109,15 @@ In the Microsoft Intune admin center, navigate to Apps > App configuration polic
109
109
> [!NOTE]
110
110
> - The other config keys of Network Protection will only work if the parent key '**Enable Network Protection in Microsoft Defender'** is enabled.
111
111
> - To ensure comprehensive protection against Wi-Fi threats, users should enable location permission and select the "Allow All the Time" option. This permission is optional but highly recommended, even when the app is not actively in use. If location permission is denied, Defender for Endpoint will only offer limited protection against network threats and will only safeguard users from rogue certificates.
112
-
**An open wi-fi network alert** is generated whenever a user connects to an open Wi-Fi network. If the user reconnects to the same network within a seven-day period, no new alert will be generated. However, connecting to a different open Wi-Fi network will result in an immediate alert.
112
+
113
+
> [!IMPORTANT]
114
+
> Starting May 19, 2025, alerts are no longer generated in the Microsoft Defender portal for mobile devices connecting or disconnecting to an open wireless network and for downloading/installing/deleting self-signed certificates. Instead, these activities are now generated as events and are viewable in the device timeline.</br></br>
115
+
> Here are a key changes about this new experience:</br>
116
+
> - For these changes to take effect, end-users must update to the latest version of Defender for Endpoint on Android available on May 2025. Otherwise, the previous experience of generating alerts will still be in place. If auto-remediation key is enabled by the admin, old alerts are resolved automatically after the changes take effect.</br>
117
+
> - WWhen an end-user connects or disconnects to an open wireless network multiple times within the same 24-hour period, only one event each for the connection and disconnection is generated in that 24-hour period and sent to the device timeline.</br>
118
+
> - Enable Users to Trust Networks: After the update, connection and disconnection events to open wireless networks, including to trusted networks, are sent to the device timeline as events.
119
+
> - Users allow-listed certificates: After the update, downloading/installing/deleting self-signed certificates events, including user-trusted certificates, are sent to the device timeline as events.</br>
120
+
> - The previous experience of generating alerts for these activities still continue to apply to GCC tenants.
Copy file name to clipboardExpand all lines: defender-endpoint/android-whatsnew.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.collection:
15
15
ms.topic: reference
16
16
ms.subservice: android
17
17
search.appverid: met150
18
-
ms.date: 04/18/2025
18
+
ms.date: 05/15/2025
19
19
---
20
20
21
21
# What's new in Microsoft Defender for Endpoint on Android
@@ -28,6 +28,17 @@ ms.date: 04/18/2025
28
28
29
29
Want to experience Microsoft Defender for Endpoint? [Sign up for a free trial.](https://go.microsoft.com/fwlink/p/?linkid=2225630)
30
30
31
+
#### Alerts for activities related to open wireless connection and certificates are now detected as events
32
+
33
+
May 2025
34
+
35
+
Starting May 19, 2025, security operations center (SOC) analysts can now view the following as events instead of alerts:
36
+
37
+
- Connecting or disconnecting to open wireless networks
38
+
- Download/installation/removal of self-signed certificates
39
+
40
+
These events can be viewed in the Timeline tab of a device page. For more information, see [Network protection](android-configure.md#network-protection).
41
+
31
42
#### Deploy Defender for Endpoint prerelease builds on Android devices using Google Play preproduction tracks
1. On your Windows device, select Start, type `powershell`, right-click **Windows PowerShell**, and then select **Run as administrator**.
76
-
77
-
2. Run the following cmdlet:
78
-
79
-
```PowerShell
80
-
Set-MpPreference -EnableNetworkProtection Enabled
81
-
```
82
-
83
-
3. For Windows Server, use the additional commands that listed in the following table:
84
-
85
-
| Windows Server version | Commands |
86
-
|---|---|
87
-
| Windows Server 2019 and later |`set-mpPreference -AllowNetworkProtectionOnWinServer $true`|
88
-
| Windows Server 2016 <br/>Windows Server 2012 R2 with the [unified agent for Microsoft Defender for Endpoint](/defender-endpoint/enable-network-protection)|`set-MpPreference -AllowNetworkProtectionDownLevel $true` <br/> `set-MpPreference -AllowNetworkProtectionOnWinServer $true`|
89
-
90
-
4. (This step is optional.) To set network protection to audit mode, use the following cmdlet:
To turn off network protection, use the `Disabled` parameter instead of `AuditMode` or `Enabled`.
97
-
98
-
### Mobile device management (MDM)
99
-
100
-
1. Use the [EnableNetworkProtection](/windows/client-management/mdm/policy-csp-defender#enablenetworkprotection) configuration service provider (CSP) to enable or disable network protection or enable audit mode.
101
-
102
-
2.[Update Microsoft Defender antimalware platform to the latest version](https://support.microsoft.com/topic/update-for-microsoft-defender-antimalware-platform-92e21611-8cf1-8e0e-56d6-561a07d144cc) before you enable or disable network protection or enable audit mode.
71
+
-[PowerShell](#powershell)
103
72
104
73
### Microsoft Intune
105
74
@@ -155,6 +124,12 @@ To enable network protection, you can use one of the following methods:
155
124
156
125
8. Review all the information, and then select **Create**.
157
126
127
+
### Mobile device management (MDM)
128
+
129
+
1. Use the [EnableNetworkProtection](/windows/client-management/mdm/policy-csp-defender#enablenetworkprotection) configuration service provider (CSP) to turn network protection on or off, or to enable audit mode.
130
+
131
+
2.[Update Microsoft Defender anti-malware platform to the latest version](https://support.microsoft.com/topic/update-for-microsoft-defender-antimalware-platform-92e21611-8cf1-8e0e-56d6-561a07d144cc) before you turn network protection on or off.
132
+
158
133
### Group Policy
159
134
160
135
Use the following procedure to enable network protection on domain-joined computers or on a standalone computer.
@@ -163,19 +138,19 @@ Use the following procedure to enable network protection on domain-joined comput
163
138
164
139
*-Or-*
165
140
166
-
On a domain-joined Group Policy management computer, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and select **Edit**.
141
+
On a domain-joined Group Policy management computer, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx). Right-click the Group Policy Object you want to configure and select **Edit**.
167
142
168
143
2. In the **Group Policy Management Editor**, go to **Computer configuration** and select **Administrative templates**.
169
144
170
145
3. Expand the tree to **Windows components**\>**Microsoft Defender Antivirus**\>**Microsoft Defender Exploit Guard**\>**Network protection**.
171
146
172
-
Note that on older versions of Windows, the Group Policy path might have *Windows Defender Antivirus* instead of *Microsoft Defender Antivirus*.
147
+
On older versions of Windows, the Group Policy path might have *Windows Defender Antivirus* instead of *Microsoft Defender Antivirus*.
173
148
174
149
4. Double-click the **Prevent users and apps from accessing dangerous websites** setting and set the option to **Enabled**. In the options section, you must specify one of the following options:
175
150
176
151
-**Block** - Users can't access malicious IP addresses and domains.
177
152
-**Disable (Default)** - The Network protection feature won't work. Users aren't blocked from accessing malicious domains.
178
-
-**Audit Mode** - If a user visits a malicious IP address or domain, an event will be recorded in the Windows event log. However, the user won't be blocked from visiting the address.
153
+
-**Audit Mode** - If a user visits a malicious IP address or domain, an event is recorded in the Windows event log. However, the user won't be blocked from visiting the address.
179
154
180
155
> [!IMPORTANT]
181
156
> To fully enable network protection, you must set the Group Policy option to **Enabled** and also select **Block** in the options drop-down menu.
@@ -203,11 +178,42 @@ Use the following procedure to enable network protection on domain-joined comput
203
178
204
179
7. From the ribbon, select **Deploy** to deploy the policy to a collection.
205
180
181
+
### PowerShell
182
+
183
+
1. On your Windows device, click **Start**, type `powershell`, right-click **Windows PowerShell**, and then select **Run as administrator**.
184
+
185
+
2. Run the following cmdlet:
186
+
187
+
```PowerShell
188
+
Set-MpPreference -EnableNetworkProtection Enabled
189
+
```
190
+
191
+
3. For Windows Server, use the additional commands listed in the following table:
192
+
193
+
| Windows Server version | Commands |
194
+
|---|---|
195
+
|Windows Server 2019 and later |`set-mpPreference -AllowNetworkProtectionOnWinServer $true`|
196
+
|Windows Server 2016 <br/>Windows Server 2012 R2 with the [unified agent for Microsoft Defender for Endpoint](/defender-endpoint/enable-network-protection)|`set-MpPreference -AllowNetworkProtectionDownLevel $true` <br/> `set-MpPreference -AllowNetworkProtectionOnWinServer $true` <br/> `set-MpPreference -AllowDatagramProcessingOnWinServer $true`|
197
+
198
+
> [!IMPORTANT]
199
+
> For Domain Controllers and Microsoft Exchange servers, set the `AllowDatagramProcessingOnWinServer` parameter to `$false`. These roles often generate high volumes of UDP traffic, which can affect network performance and reliability when datagram processing is enabled. Disabling this setting helps maintain network stability and optimize resource usage in demanding environments.
200
+
201
+
4. (This step is optional.) To set network protection to audit mode, use the following cmdlet:
To turn off network protection, use the `Disabled` parameter instead of `AuditMode` or `Enabled`.
208
+
206
209
#### Important information about removing Exploit Guard settings from a device
207
210
208
-
Once an Exploit Guard policy is deployed using Configuration Manager, Exploit Guard settings aren't removed from the clients if you remove the deployment. Furthermore, if you remove the client's Exploit Guard deployment, `Delete not supported` is recorded in the client's `ExploitGuardHandler.log` in Configuration Manager. <!--CMADO8538577-->
211
+
When you deploy an Exploit Guard policy using Configuration Manager, the settings remain on the client even if you later remove the deployment. If the deployment is removed, the client logs `Delete` not supported in the `ExploitGuardHandler.log` file.
212
+
213
+
<!--CMADO8538577-->
209
214
210
-
Use the following PowerShell script in the SYSTEM context to remove Exploit Guard settings correctly:<!--CMADO9907132-->
215
+
Use the following PowerShell script in the `SYSTEM` context to remove Exploit Guard settings correctly:
0 commit comments