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/identity-inventory.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
@@ -110,7 +110,7 @@ Sort option applies to Display name, Domain, and Created time columns.
110
110
111
111
-**Critical Active Directory service accounts** card helps you quickly identify all Active Directory accounts designated as critical, making it easier to focus on identities most at risk.
112
112
113
-
At the top of each device inventory tab, the following device counts are available:
113
+
At the top of the page, the following identities counts are available:
114
114
115
115
-__Total__: The total number of identities.
116
116
@@ -120,7 +120,7 @@ At the top of each device inventory tab, the following device counts are availab
120
120
121
121
-**Services:** The number of all service accounts both on-premises and cloud.
122
122
123
-
You can use this information to help you prioritize devices for security posture improvements.
123
+
You can use this information to help you prioritize identities for security posture improvements.
Copy file name to clipboardExpand all lines: ATPDocs/ops-guide/ops-guide.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
@@ -13,7 +13,7 @@ This article summarizes the Microsoft Defender for Identity activities we recomm
13
13
14
14
|Cadence |Tasks |
15
15
|---------|---------|
16
-
|**Daily**| - [Triage incidents by priority](ops-guide-daily.md#triage-incidents-by-priority) <br> - [Investigate users with a high investigation score](ops-guide-daily.md#investigate-users-with-a-high-investigation-score) <br>- [Configure tuning rules for benign true positives / false positive alerts](ops-guide-daily.md#configure-tuning-rules-for-benign-true-positives--false-positive-alerts)<br> - [Review the ITDR dashboard](ops-guide-daily.md#review-the-itdr-dashboard) <br>- [Proactively hunt](ops-guide-daily.md#proactively-hunt) <br> - [Review Defender for Identity health issues](ops-guide-daily.md#review-defender-for-identity-health-issues)|
16
+
|**Daily**| - [Triage incidents by priority](ops-guide-daily.md#triage-incidents-by-priority) <br>- [Configure tuning rules for benign true positives / false positive alerts](ops-guide-daily.md#configure-tuning-rules-for-benign-true-positives--false-positive-alerts)<br> - [Review the ITDR dashboard](ops-guide-daily.md#review-the-itdr-dashboard) <br>- [Proactively hunt](ops-guide-daily.md#proactively-hunt) <br> - [Review Defender for Identity health issues](ops-guide-daily.md#review-defender-for-identity-health-issues)|
17
17
|**Weekly**|- [Review Secure score recommendations](ops-guide-weekly.md#review-secure-score-recommendations) <br> - [Review and respond to emerging threats](ops-guide-weekly.md#review-and-respond-to-emerging-threats) <br>- [Proactively hunt](ops-guide-weekly.md#proactively-hunt)|
18
18
|**Monthly**| - [Review tuned alerts and adjust tuning if needed](ops-guide-monthly.md#review-tuned-alerts-and-adjust-tuning-if-needed) <br> - [Track new changes in Microsoft Defender XDR and Defender for Identity](ops-guide-monthly.md#track-new-changes-in-microsoft-defender-xdr-and-defender-for-identity)|
19
19
|**Quarterly / Ad hoc** <br>Depending on your organization's needs and processes | - [Review Microsoft service health](ops-guide-quarterly.md#review-microsoft-service-health) <br> - [Review server setup process to include sensors](ops-guide-quarterly.md#review-server-setup-process-to-include-sensors) <br>- [Check domain configuration via PowerShell](ops-guide-quarterly.md#check-domain-configuration-via-powershell)|
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/governance-actions.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,8 +83,7 @@ The following governance actions can be taken for connected apps either on a spe
83
83
84
84
-**Trash** – Move the file to the trash folder. (Box, Dropbox, Google Drive, OneDrive, SharePoint)
85
85
86
-
> [!NOTE]
87
-
> These actions are restricted to users with specific administrative roles. If the options described are not visible or accessible, please confirm with your system administrator that your account has one of the following roles assigned:
86
+
These actions are restricted to users with specific administrative roles. If the options described are not visible or accessible, please confirm with your system administrator that your account has one of the following roles assigned:
Copy file name to clipboardExpand all lines: defender-endpoint/isolation-exclusions.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
@@ -14,7 +14,7 @@ ms.collection:
14
14
ms.topic: how-to
15
15
ms.subservice: edr
16
16
search.appverid: met150
17
-
ms.date: 06/22/2025
17
+
ms.date: 07/01/2025
18
18
---
19
19
20
20
# Isolation exclusions (preview)
@@ -57,7 +57,7 @@ There are two steps to using isolation exclusion: defining isolation exclusion r
57
57
58
58
### Prerequisites
59
59
60
-
* Isolation exclusion is available on Windows (minimum client version 10.8470) and macOS (minimum client version 101.240902).
60
+
* Isolation exclusion is available on Windows 11, Windows 10 version 1703 or later, Windows Server 2025, Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, and macOS.
61
61
* Isolation exclusion must be enabled. Enabling isolation exclusion requires Security Admin or Manage Security settings permissions or above. To enable isolation exclusion, sign in to the [Microsoft Defender portal](https://security.microsoft.com) and go to **Settings** > **Endpoints** > **Advanced features** and enable **Isolation Exclusion Rules** feature.
62
62
63
63
:::image type="content" source="./media/isolation-exclusions/enable-exclusions.png" alt-text="Screenshot showing how to enable isolation exclusions." lightbox="./media/isolation-exclusions/enable-exclusions.png":::
- Removed external dependency of uuid-runtime from MDE package
57
+
- The Defender for Endpoint package rollout into production happens gradually. From the time the release notes are published, it might take up to a week for the package to be pushed to all production machines.
58
+
- Removed external dependency of uuid-runtime from the Defender for Endpoint package
Copy file name to clipboardExpand all lines: defender-endpoint/manage-protection-updates-microsoft-defender-antivirus.md
+27-1Lines changed: 27 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ Each source has typical scenarios that depend on how your network is configured,
81
81
|---|---|
82
82
|Windows Server Update Service|You're using Windows Server Update Service to manage updates for your network.|
83
83
|Microsoft Update|You want your endpoints to connect directly to Microsoft Update. This option is useful for endpoints that irregularly connect to your enterprise network, or if you don't use Windows Server Update Service to manage your updates.|
84
-
|File share|You have devices that aren't connected to the Internet (such as virtual machines, or VMs). You can use your Internet-connected VM host to download the updates to a network share, from which the VMs can obtain the updates. See the [VDI deployment guide](deployment-vdi-microsoft-defender-antivirus.md) for how file shares are used in virtual desktop infrastructure (VDI) environments.|
84
+
|UNC Share|You have devices that aren't connected to the Internet (such as virtual machines, or VMs). You can use your Internet-connected VM host to download the updates to a network share, from which the VMs can obtain the updates. See the [VDI deployment guide](deployment-vdi-microsoft-defender-antivirus.md) for how file shares are used in virtual desktop infrastructure (VDI) environments. Platform updates can also be deployed using this method. |
85
85
|Microsoft Endpoint Configuration Manager|You're using Microsoft Endpoint Configuration Manager to update your endpoints.|
86
86
|Security intelligence updates and platform updates for Microsoft Defender Antivirus and other Microsoft anti-malware (formerly referred to as MMPC)|[Make sure devices are updated to support SHA-2](https://support.microsoft.com/help/4472027/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus). Microsoft Defender Antivirus Security intelligence and platform updates are delivered through Windows Update. As of October 21, 2019, security intelligence updates and platform updates are SHA-2 signed exclusively. <br/>Download the latest protection updates because of a recent infection or to help provision a strong, base image for [VDI deployment](deployment-vdi-microsoft-defender-antivirus.md). This option should be used only as a final fallback source, and not the primary source. It's only to be used if updates can't be downloaded from Windows Server Update Service or Microsoft Update for [a specified number of days](manage-outdated-endpoints-microsoft-defender-antivirus.md#set-the-number-of-days-before-protection-is-reported-as-out-of-date).|
87
87
@@ -274,6 +274,32 @@ On a Windows File Server set up a network file share (UNC/mapped drive) to downl
274
274
> [!NOTE]
275
275
> Do not add the x64 (or x86) folder in the path. The `mpcmdrun.exe` process adds it automatically.
276
276
277
+
## Enable platform updates using UNC share
278
+
279
+
To enable platform updates using UNC share, download KB4052623 and copy it into the architecture folders as `updateplatform.exe`. These files are updated monthly and need to get manually updated by you.
280
+
281
+
KB4052623 is available for the following architectures:
Copy file name to clipboardExpand all lines: defender-endpoint/mde-linux-prerequisites.md
+12-11Lines changed: 12 additions & 11 deletions
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: conceptual
16
16
ms.subservice: linux
17
17
search.appverid: met150
18
-
ms.date: 04/08/2025
18
+
ms.date: 06/30/2025
19
19
---
20
20
21
21
# Prerequisites for Microsoft Defender for Endpoint on Linux
@@ -117,8 +117,7 @@ The following Linux server distributions and x64 (AMD64/EM64T) versions are supp
117
117
> The workstation and desktop versions of these distributions are unsupported
118
118
> Distributions and versions that aren't explicitly listed are unsupported (even if they're derived from the officially supported distributions).
119
119
> After a new package version is released, support for the previous two versions is reduced to technical support only. Versions older than that which are listed in this section are provided for technical upgrade support only.
120
-
> Currently, Rocky and Alma distributions aren't supported in Microsoft Defender Vulnerability Management. However, Microsoft Defender for Endpoint is kernel-version agnostic for all other supported distributions and versions.
121
-
> The minimal requirement for the kernel version is `3.10.0-327` or later.
120
+
> Microsoft Defender for Endpoint is kernel-version agnostic for all other supported distributions and versions. The minimal requirement for the kernel version is `3.10.0-327` or later.
122
121
123
122
> [!WARNING]
124
123
> Running Defender for Endpoint on Linux with other fanotify-based security solutions isn't supported. It can lead to unpredictable results, including hanging the operating system.
@@ -186,12 +185,14 @@ If the Microsoft Defender for Endpoint installation fails due to missing depende
186
185
> - The mdatp RPM package requires `audit`, `semanage`.
187
186
> - For DEBIAN, the mdatp package requires `auditd`.
188
187
> - For Mariner, the mdatp package requires `audit`.
> - The `mde-netfilter` package also has the following package dependencies:
193
-
- For DEBIAN, the mde-netfilter package requires `libnetfilter-queue1` and `libglib2.0-0`
194
-
- For RPM, the mde-netfilter package requires `libmnl`, `libnfnetlink`, `libnetfilter_queue`, and `glib2`
188
+
>
189
+
> For versions older than `101.25032.0000`, the following requirements apply:
190
+
> - RPM package needs: `mde-netfilter` and `pcre`
191
+
> - DEBIAN package needs: `mde-netfilter` and `libpcre3`
192
+
>
193
+
> The `mde-netfilter` package also has the following package dependencies:
194
+
> - For DEBIAN, the `mde-netfilter` package requires `libnetfilter-queue1` and `libglib2.0-0`
195
+
> - For RPM, the `mde-netfilter` package requires `libmnl`, `libnfnetlink`, `libnetfilter_queue`, and `glib2`
195
196
196
197
## Installation instructions
197
198
@@ -226,5 +227,5 @@ If you experience any installation issues, self-troubleshooting resources are av
226
227
-[Troubleshoot missing events or alerts issues for Microsoft Defender for Endpoint on Linux](linux-support-events.md)
227
228
-[Troubleshoot performance issues for Microsoft Defender for Endpoint on Linux](linux-support-perf.md)
228
229
229
-
> [!TIP]
230
-
> Do you want to learn more? Engage with the Microsoft Security community in our Tech Community: [Microsoft Defender for Endpoint Tech Community](https://techcommunity.microsoft.com/category/microsoft-defender-for-endpoint/discussions/microsoftdefenderatp)
230
+
> [!TIP]
231
+
> Do you want to learn more? Engage with the Microsoft Security community in our Tech Community: [Microsoft Defender for Endpoint Tech Community](https://techcommunity.microsoft.com/category/microsoft-defender-for-endpoint/discussions/microsoftdefenderatp)
Copy file name to clipboardExpand all lines: defender-endpoint/mde-plugin-wsl.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,16 +15,15 @@ ms.collection:
15
15
ms.custom:
16
16
- partner-contribution
17
17
audience: ITPro
18
-
ms.date: 11/11/2024
18
+
ms.date: 07/01/2025
19
19
search.appverid: MET150
20
20
---
21
21
22
22
# Microsoft Defender for Endpoint plug-in for Windows Subsystem for Linux (WSL)
23
23
24
24
**Applies to:**
25
25
26
-
- Microsoft Defender for Endpoint for servers
27
-
- Microsoft Defender for Servers Plan 1 or Plan 2
26
+
-[Microsoft Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)
28
27
29
28
## Overview
30
29
@@ -134,7 +133,7 @@ If your host machine contains multiple proxy settings, the plug-in selects the p
134
133
135
134
3. Network & Internet proxy settings.
136
135
137
-
For example, if your host machine has both `Winhttp proxy` and `Network & Internet proxy`, the plug-in selects `Winhttp proxy` as the proxy configuration.
136
+
For example, if your host machine has both `Winhttp proxy` and `Network & Internet proxy`, the plug-in selects `Winhttp proxy` as the proxy configuration.
138
137
139
138
> [!NOTE]
140
139
> The `DefenderProxyServer` registry key is no longer supported. Follow the steps described earlier in this article to configure proxy in plug-in.
@@ -294,7 +293,7 @@ Check the following things:
294
293
- If your machine has a proxy setup, run the command `healthCheck --extendedProxy`. This will provide information on which proxy(s) is set on your machine and whether these configurations are invalid for WSL defender.
- If the steps mentioned above do not fix the problem, include the following configuration settings in the `.wslconfig` located in your `%UserProfile%` and restart WSL. Details about settings can be found in [WSL Settings](/windows/wsl/wsl-config#main-wsl-settings).
0 commit comments