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: defender-endpoint/indicators-overview.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -159,10 +159,9 @@ The IoC API schema and the threat IDs in Advanced Hunting are updated to align w
159
159
160
160
Microsoft Store apps cannot be blocked by Microsoft Defender because they're signed by Microsoft.
161
161
162
-
Customers might experience issues with alerts for IoCs. The following scenarios are situations where alerts aren't created or are created with inaccurate information. Each issue is investigated by our engineering team.
162
+
Customers might experience issues with alerts for IoCs. The following scenarios are situations where alerts aren't created or are created with inaccurate information.
163
163
164
-
-**Block indicators**: Generic alerts with informational severity only are created. Custom alerts (that is, custom title and severity) aren't fired in these cases.
165
-
-**Warn indicators**: Generic alerts and custom alerts are possible in this scenario; however, the results aren't deterministic due to an issue with the alert detection logic. In some cases, customers might see a generic alert, whereas a custom alert might show in other cases.
164
+
-**Block and Warn indicators**: Generic alerts with informational severity only are created. Custom alerts (that is, custom title and severity) aren't fired in these cases.
166
165
-**Allow**: No alerts are generated (by design).
167
166
-**Audit**: Alerts are generated based on the severity provided by the customer (by design).
168
167
- In some cases, alerts coming from EDR detections might take precedence over alerts stemming from antivirus blocks, in which case an information alert is generated.
Copy file name to clipboardExpand all lines: defender-endpoint/linux-preferences.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -446,17 +446,18 @@ Configure filesystems to be unmonitored/excluded from real-time protection (RTP)
446
446
> [!NOTE]
447
447
> Configured filesystem is unmonitored only if it's present in Microsoft's list of permitted unmonitored filesystems.
448
448
449
-
By default, NFS and Fuse are unmonitored from RTP, Quick, and Full scans. However, they can still be scanned by a custom scan. For example, to remove NFS from the list of unmonitored filesystems list, update the managed config file as shown below. This will automatically add NFS to the list of monitored filesystems for RTP.
449
+
By default, `cifs`, `fuse`, `nfs`, `nfs4` and `smb` are unmonitored from RTP, Quick, and Full scans. However, they can still be scanned by a custom scan. For example, to remove `nfs` and `nfs4` from the list of unmonitored filesystems list, update the managed config file as shown below. This will add `nfs`/`nfs4` to the list of monitored filesystems for RTP.
450
+
Currently monitoring `nfs4`, `cifs` and `smb` filesystems is in preview mode for RTP mode.
450
451
451
452
```JSON
452
453
{
453
454
"antivirusEngine":{
454
-
"unmonitoredFilesystems": ["Fuse"]
455
+
"unmonitoredFilesystems": ["cifs","fuse","smb"]
455
456
}
456
457
}
457
458
```
458
459
459
-
To remove both NFS and Fuse from unmonitored list of filesystems, use the following snippet:
460
+
To remove all entries from unmonitored list of filesystems, use the following snippet:
460
461
461
462
```JSON
462
463
{
@@ -1126,4 +1127,4 @@ To verify that your `/etc/opt/microsoft/mdatp/managed/mdatp_managed.json` is wor
1126
1127
1127
1128
Once you've built the configuration profile for your enterprise, you can deploy it through the management tool that your enterprise is using. Defender for Endpoint on Linux reads the managed configuration from `/etc/opt/microsoft/mdatp/managed/mdatp_managed.json`.
1128
1129
1129
-
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]
1130
+
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]
- Vulnerability detection for Langflow, an open-source Python framework for building AI workflows and agents, has been enhanced with dynamic detection using advanced telemetry and Python package scanning. This includes the detection of CVE-2025-3248 with a CVSS score of 9.8, ensuring comprehensive vulnerability coverage.
62
+
63
+
- Client Analyzer is now bundled directly within the MDE package, eliminating the need for separate downloads. Both the binary and Python versions are included by default and can be found at /opt/microsoft/mdatp/tools/client_analyzer/. This ensures consistent availability across environments and streamlines troubleshooting for customers by making diagnostic tools readily accessible out-of-the-box.
- The `mdatp threat quarantine add` command now requires superuser (root) privileges.
78
96
- Custom definition path can now be updated without stopping Defender for Endpoint. Previously, this required stopping the service, but with this release onwards, updates to the definition path can be made dynamically, improving operational efficiency and reducing downtime.
79
97
- Running Defender for Endpoint on Linux alongside Fapolicyd is now supported on RHEL and Fedora-based distributions, enabling both antivirus (real-time protection) and EDR functionality to operate without conflict. For other fanotify-based tools, MDE can still be used safely by setting the antivirus enforcement level to passive, helping avoid system instability.
80
-
- Both the binary and Python versions of Client Analyzer are now included in the local package. There is no longer a need to download it separately, as it comes bundled by default. You can find it at the location `/opt/microsoft/mdatp/conf/client_analyzer/`.
Copy file name to clipboardExpand all lines: defender-endpoint/mac-install-manually.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,9 +44,10 @@ Before you get started, see [the main Microsoft Defender for Endpoint on macOS p
44
44
45
45
> [!IMPORTANT]
46
46
> Manual installation of Microsoft Defender for Endpoint on macOS requires changes to the Privacy & Security Settings on macOS. Please consult Apple's documentation for details.
47
-
> [Change Privacy & Security settings on MacOS Sonoma 14](https://support.apple.com/guide/mac-help/change-privacy-security-settings-on-mac-mchl211c911f/14.0/mac/14.0)
48
-
> [Change Privacy & Security settings on MacOS Sequoia 15](https://support.apple.com/guide/mac-help/change-privacy-security-settings-on-mac-mchl211c911f/15.0/mac/15.0)
49
-
>
47
+
> -[Change Privacy & Security settings on MacOS Sonoma 14](https://support.apple.com/guide/mac-help/change-privacy-security-settings-on-mac-mchl211c911f/14.0/mac/14.0)
48
+
> -[Change Privacy & Security settings on MacOS Sequoia 15](https://support.apple.com/guide/mac-help/change-privacy-security-settings-on-mac-mchl211c911f/15.0/mac/15.0)
49
+
> -[Change Privacy & Security settings on MacOS Tahoe 26](https://support.apple.com/guide/mac-help/change-privacy-security-settings-on-mac-mchl211c911f/mac)
50
+
50
51
## Download installation and onboarding packages
51
52
52
53
Download the installation and onboarding packages from Microsoft Defender portal.
Copy file name to clipboardExpand all lines: defender-endpoint/mac-whatsnew.md
-8Lines changed: 0 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,14 +59,6 @@ To get the latest features, including preview capabilities (such as endpoint det
59
59
60
60
If an end user encounters a prompt for Defender for Endpoint on macOS processes such as `wdavdaemon_enterprise` or `Microsoft Defender Helper`, the end user can safely choose the **Deny** option. This selection doesn't affect Defender for Endpoint's functionality. Enterprises can also add *Microsoft Defender* to allow [incoming connections](https://support.apple.com/en-ca/guide/deployment/dep8d306275f/web). This issue is fixed in macOS Sequoia 15.2.
61
61
62
-
## Tahoe support
63
-
64
-
- Microsoft Defender for Endpoint supports version 26.0 or newer.
65
-
66
-
## Sequoia support
67
-
68
-
- Microsoft Defender for Endpoint supports version 15.0.1 or newer.
69
-
70
62
## macOS Deprecation
71
63
72
64
- Microsoft Defender for Endpoint no longer supports macOS 11 (Big Sur), 12 (Monterey) and 13 (Ventura)
Copy file name to clipboardExpand all lines: defender-endpoint/microsoft-defender-antivirus-updates.md
+29-43Lines changed: 29 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,70 +3,45 @@ title: Microsoft Defender Antivirus security intelligence and product updates
3
3
description: Manage how Microsoft Defender Antivirus receives protection and product updates.
4
4
ms.service: defender-endpoint
5
5
ms.localizationpriority: high
6
-
ms.date: 07/23/2025
6
+
ms.date: 09/18/2025
7
7
audience: ITPro
8
8
ms.topic: reference
9
-
author: batamig
10
-
ms.author: bagol
11
-
ms.custom: nextgen
12
-
ms.reviewer: pahuijbr, tudobril, yongrhee
13
-
manager: bagol
9
+
author: KesemSharabi
10
+
ms.author: kesharab
14
11
ms.subservice: ngp
15
-
ms.collection:
16
-
- m365-security
17
-
- tier2
18
-
- mde-ngp
19
12
search.appverid: met150
13
+
appliesto:
14
+
- Microsoft Defender for Endpoint Plan 1
15
+
- Microsoft Defender for Endpoint Plan 2
20
16
---
21
17
22
18
# Microsoft Defender Antivirus security intelligence and product updates
23
19
24
-
**Applies to:**
20
+
Keeping Microsoft Defender Antivirus up to date is critical to assure your devices are protected against new malware and attack techniques. Update your antivirus protection, even if Microsoft Defender Antivirus is running in [passive mode](microsoft-defender-antivirus-compatibility.md). You can find the lates engine, platform, and signature date in [Security intelligence updates for Microsoft Defender Antivirus and other Microsoft anti-malware](https://www.microsoft.com/en-us/wdsi/defenderupdates)
25
21
26
-
-[Microsoft Defender for Endpoint Plans 1 and 2](microsoft-defender-endpoint.md)
27
-
- Microsoft Defender Antivirus
28
-
29
-
**Platforms**
30
-
31
-
- Windows
32
-
33
-
Keeping Microsoft Defender Antivirus up to date is critical to assure your devices have the latest technology and features needed to protect against new malware and attack techniques. Update your antivirus protection, even if Microsoft Defender Antivirus is running in [passive mode](microsoft-defender-antivirus-compatibility.md). This article includes information about the two types of updates for keeping Microsoft Defender Antivirus current:
22
+
This article is aimed at **Windows** devices, and includes information about the following two types of updates:
-[How to roll back an update](#how-to-roll-back-an-update) (if necessary)
42
-
-[Platform version included with Windows 10 releases](#platform-version-included-with-windows-10-releases)
43
-
-[Updates for Deployment Image Servicing and Management (DISM)](#updates-for-deployment-image-servicing-and-management-dism)
44
-
45
-
To see the most current engine, platform, and signature date, see [Security intelligence updates for Microsoft Defender Antivirus and other Microsoft anti-malware](https://www.microsoft.com/en-us/wdsi/defenderupdates).
Microsoft Defender Antivirus uses [cloud-delivered protection](cloud-protection-microsoft-defender-antivirus.md) (also called the*Microsoft Advanced Protection Service*, or MAPS) and periodically downloads dynamic security intelligence updates to provide more protection. These dynamic updates don't take the place of regular security intelligence updates via security intelligence update KB2267602.
30
+
Microsoft Defender Antivirus uses [cloud-delivered protection](cloud-protection-microsoft-defender-antivirus.md), also known as*Microsoft Advanced Protection Service*, or *MAPS*. Defender Antivirus periodically downloads dynamic security [intelligence updates](https://www.microsoft.com/en-us/wdsi/defenderupdates). These updates don't replace regular security intelligence updates. Engine updates are included with security intelligence updates and are released monthly.
52
31
53
-
> [!NOTE]
54
-
> Updates are released under the following KBs:
55
-
>
56
-
> - Microsoft Defender Antivirus: KB2267602
57
-
> - System Center Endpoint Protection: KB2461484
32
+
Updates are released under the following KBs:
58
33
59
-
Cloud-delivered protection is always on and requires an active connection to the Internet to function. Security intelligence updates occur on a scheduled cadence (configurable via policy). For more information, see [Use Microsoft cloud-provided protection in Microsoft Defender Antivirus](cloud-protection-microsoft-defender-antivirus.md).
34
+
-Microsoft Defender Antivirus: KB2267602
60
35
61
-
For a list of recent security intelligence updates, see [Security intelligence updates for Microsoft Defender Antivirus and other Microsoft anti-malware](https://www.microsoft.com/en-us/wdsi/defenderupdates).
36
+
- System Center Endpoint Protection: KB2461484
62
37
63
-
Engine updates are included with security intelligence updates and are released on a monthly cadence.
38
+
[Cloud-delivered protection](cloud-protection-microsoft-defender-antivirus.md) is always on and requires an active connection to the internet to function. Security intelligence updates occur on a scheduled cadence which you can configure using a policy.
64
39
65
40
## Product updates
66
41
67
42
Microsoft Defender Antivirus requires monthly updates (KB4052623) known as *platform updates*.
68
43
69
-
You can manage the distribution of updates through one of the following methods:
44
+
You can manage the distribution of updates using one of the following methods:
70
45
71
46
-[Windows Server Update Service (WSUS)](/mem/configmgr/protect/deploy-use/endpoint-definitions-wsus#to-synchronize-endpoint-protection-definition-updates-in-standalone-wsus)
@@ -181,17 +167,17 @@ Refined exclusion processing and resolved false positives for the Attack Surface
181
167
182
168
### Previous version updates: Technical upgrade support only
183
169
184
-
After a new package version is released, support for the previous two versions is reduced to technical support only. For more information about previous versions, see [Microsoft Defender Antivirus updates: Previous versions for technical upgrade support](msda-updates-previous-versions-technical-upgrade-support.md).
170
+
After a new package version is released, support for the previous two versions is reduced to technical upgrade support only. For more information about previous versions, see [Microsoft Defender Antivirus updates: Previous versions for technical upgrade support](msda-updates-previous-versions-technical-upgrade-support.md).
185
171
186
172
## Microsoft Defender Antivirus platform and engine support
187
173
188
174
Platform and engine updates are provided on a monthly cadence. To be fully supported, keep current with the latest platform and engine updates. Our support structure is dynamic, evolving into two phases depending on the availability of the latest platform and engine version:
189
175
190
176
-**Security and Critical Updates servicing phase** - When running the latest platform and engine version, you're eligible to receive both Security and Critical updates to the anti-malware platform.
191
177
192
-
-**Technical Support (Only) phase** - After a new platform and engine version is released, support for older versions (N-2) reduce to [technical support only](msda-updates-previous-versions-technical-upgrade-support.md). Platform and engine versions older than N-2 are no longer supported. Technical support continues to be provided for upgrades from the Windows 10 release version (see [Platform version included with Windows 10 releases](#platform-version-included-with-windows-10-releases)) to the latest platform version.
178
+
-**Technical Upgrade Support (Only) phase** - After a new platform and engine version is released, support for older versions (N-2) reduce to [technical upgrade support only](msda-updates-previous-versions-technical-upgrade-support.md). Platform and engine versions older than N-2 are no longer supported. Technical upgrade support continues to be provided for upgrades from the Windows 10 release version (see [Platform version included with Windows 10 releases](#platform-version-included-with-windows-10-releases)) to the latest platform version.
193
179
194
-
During the technical support (only) phase, commercially reasonable support incidents are provided through Microsoft Customer Service & Support and Microsoft's managed support offerings (such as Premier Support). If a support incident requires escalation to development for further guidance, requires a nonsecurity update, or requires a security update, customers are asked to upgrade to the latest platform version or an intermediate update (*).
180
+
During the technical upgrade support (only) phase, commercially reasonable support incidents are provided through Microsoft Customer Service & Support and Microsoft's managed support offerings (such as Premier Support). If a support incident requires escalation to development for further guidance, requires a nonsecurity update, or requires a security update, customers are asked to upgrade to the latest platform version or an intermediate update (*).
195
181
196
182
> [!NOTE]
197
183
> If you're manually deploying Microsoft Defender Antivirus Platform Update, or if you're using a script or a non-Microsoft management product to deploy Microsoft Defender Antivirus Platform Update, make sure that version `4.18.2001.10` is installed from the [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Search.aspx?q=4.18.2001.10) before the latest version of Platform Update (N-2) is installed.
0 commit comments