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/mac-whatsnew.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,12 +40,12 @@ For more information on Microsoft Defender for Endpoint on other operating syste
40
40
> [!NOTE]
41
41
> - Apple fixed an issue on macOS [Ventura upgrade](https://developer.apple.com/documentation/macos-release-notes/macos-13_1-release-notes), and [Sonoma upgrade](https://developer.apple.com/forums/thread/737824#773449022) with the latest OS update. The issue impacts Microsoft Defender for Endpoint security extensions, and might result in losing Full Disk Access Authorization, impacting its ability to function properly.
42
42
> - In macOS Sonoma 14.3.1, Apple made a change to the [handling of Bluetooth devices](https://developer.apple.com/forums/thread/738748) that impacts Defender for Endpoint device controls ability to intercept and block access to Bluetooth devices. At this time, the recommended mitigation is to use a version of macOS less than 14.3.1.
43
-
> - In both macOS Sonoma and Sequoia builds, Network Protection capabilities may be impacted due to changes in Apple's internal networking structure resulting in crashes of the network extension (NetExt). This will result in intermittent network connectivity issues for end users. We are recommending that customers who have Network Protection enabled in their organization refrain from upgrading to Sonoma / Seqouia builds at this time.
43
+
> - In macOS Sequoia, Network Protection capabilities may be impacted due to changes in Apple's internal networking structure resulting in crashes of the network extension (NetExt). This will result in intermittent network connectivity issues for end users. We are recommending that customers who have Network Protection enabled in their organization refrain from upgrading to Sequoia builds at this time.
44
44
45
45
46
46
**Sequoia support**
47
47
48
-
Microsoft Defender supports macOS Sequoia (15) in the current Defender release.
48
+
Microsoft Defender is working with Apple on a network stack change that is impacting Network Protection's Network Filter with macOS Sequoia (15).
49
49
50
50
**macOS Deprecation**
51
51
@@ -89,7 +89,7 @@ Behavior monitoring monitors process behavior to detect and analyze potential th
89
89
90
90
##### What's new
91
91
92
-
-[[device control](mac-device-control-overview.md)] Secure Digital cards are not recognized on newer macOS
92
+
-[[device control](mac-device-control-overview.md)] Secure Digital cards aren't recognized on newer macOS
@@ -1026,7 +1026,7 @@ Live Response for macOS is now available for all Mac devices onboarded to Defend
1026
1026
> macOS 10.15 (Catalina) contains new security and privacy enhancements. Beginning with this version, by default, applications are not able to access certain locations on disk (such as Documents, Downloads, Desktop, etc.) without explicit consent. In the absence of this consent, Microsoft Defender for Endpoint is not able to fully protect your device.
1027
1027
> > The mechanism for granting this consent depends on how you deployed Microsoft Defender for Endpoint:
1028
1028
> - For manual deployments, see the updated instructions in the [Manual deployment topic](mac-install-manually.md#allow-full-disk-access).
1029
-
- For managed deployments, see the updated instructions in the [JAMF-based deployment](mac-install-with-jamf.md) and [Microsoft Intune-based deployment](mac-install-with-intune.md#create-system-configuration-profiles)topics.
1029
+
- For managed deployments, see the updated instructions in the [JAMF-based deployment](mac-install-with-jamf.md) and [Microsoft Intune-based deployment](mac-install-with-intune.md#create-system-configuration-profiles)articles.
Copy file name to clipboardExpand all lines: defender-endpoint/microsoft-defender-antivirus-updates.md
+16-32Lines changed: 16 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,11 +3,11 @@ 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: 08/12/2024
6
+
ms.date: 09/19/2024
7
7
audience: ITPro
8
8
ms.topic: reference
9
-
author: siosulli
10
-
ms.author: siosulli
9
+
author: denisebmsft
10
+
ms.author: deniseb
11
11
ms.custom: nextgen
12
12
ms.reviewer: pahuijbr, tudobril, yongrhee
13
13
manager: deniseb
@@ -151,21 +151,6 @@ All our updates contain:
151
151
- Fixed an issue where an Outlook exclusion for the ASR rule [Block Office applications from injecting code into other processes](/defender-endpoint/attack-surface-reduction-rules-reference#block-office-applications-from-injecting-code-into-other-processes) was not honored.
152
152
- Fixed a race condition during the startup of [endpoint data loss prevention](/purview/endpoint-dlp-getting-started) such that, in certain environments, some system files could be corrupted.
- Support phase: **Security and Critical Updates**
161
-
162
-
#### What's new
163
-
164
-
- Improved performance when running configuration queries.
165
-
- Optimized how scans are prioritized.
166
-
- Fixed a crash caused by a race condition with a device control driver.
167
-
- Added Event Viewer Logging for scan start event where the scan originates from PowerShell.
168
-
169
154
### Previous version updates: Technical upgrade support only
170
155
171
156
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).
@@ -228,14 +213,13 @@ Updates are released for x86, x64, and ARM64 Windows architecture.
228
213
229
214
For more information, see [Microsoft Defender update for Windows operating system installation images](https://support.microsoft.com/help/4568292/defender-update-for-windows-operating-system-installation-images).
230
215
231
-
After a new package version is released, support for the previous two versions is reduced to technical support only. To view a list of previous versions, see [Previous DISM updates (no longer supported)](msda-updates-previous-versions-technical-upgrade-support.md#previous-dism-updates-no-longer-supported).
216
+
After a new package version is released, support for the previous two versions is reduced to technical support only. To view a list of previous versions, see [Previous DISM updates](msda-updates-previous-versions-technical-upgrade-support.md#previous-dism-updates-no-longer-supported).
232
217
233
-
### 1.415.295.0
218
+
### 1.417.472.0
234
219
235
-
- Defender package version: `1.415.295.0`
236
-
- Security intelligence version: `1.415.295.0`
237
-
- Engine version: `1.24070.1`
238
-
- Platform version: `4.18.24070.5`
220
+
- Defender package version: `1.417.472.0`
221
+
- Security intelligence version: `1.417.472.0`
222
+
- Engine version: `1.24080.9`
239
223
240
224
#### Fixes
241
225
@@ -245,10 +229,10 @@ After a new package version is released, support for the previous two versions i
245
229
246
230
- None
247
231
248
-
### 1.415.235.0
232
+
### 1.415.295.0
249
233
250
-
- Defender package version: `1.415.235.0`
251
-
- Security intelligence version: `1.415.235.0`
234
+
- Defender package version: `1.415.295.0`
235
+
- Security intelligence version: `1.415.295.0`
252
236
- Engine version: `1.24070.1`
253
237
- Platform version: `4.18.24070.5`
254
238
@@ -260,12 +244,12 @@ After a new package version is released, support for the previous two versions i
Copy file name to clipboardExpand all lines: defender-endpoint/microsoft-defender-endpoint-mac.md
+3-3Lines changed: 3 additions & 3 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: macos
17
17
search.appverid: met150
18
-
ms.date: 09/17/2024
18
+
ms.date: 09/19/2024
19
19
---
20
20
21
21
# Microsoft Defender for Endpoint on Mac
@@ -71,12 +71,12 @@ There are several methods and deployment tools that you can use to install and c
71
71
72
72
The three most recent major releases of macOS are supported.
73
73
74
-
- 15 (Sequoia)
75
-
76
74
- 14 (Sonoma)
77
75
78
76
- 13 (Ventura)
79
77
78
+
- 12 (Monterey)
79
+
80
80
> [!IMPORTANT]
81
81
> On macOS 11 (Big Sur) and above, Microsoft Defender for Endpoint requires additional configuration profiles. If you are an existing customer upgrading from earlier versions of macOS, make sure to deploy the additional configuration profiles listed on [New configuration profiles for macOS Big Sur and newer versions of macOS](mac-sysext-policies.md).
@@ -1106,6 +1121,21 @@ Microsoft regularly releases [security intelligence updates and product updates
1106
1121
1107
1122
The versions listed in this section are no longer supported. To view current versions, see [Updates for Deployment Image Servicing and Management (DISM)](microsoft-defender-antivirus-updates.md#updates-for-deployment-image-servicing-and-management-dism).
Copy file name to clipboardExpand all lines: defender-office-365/attack-simulation-training-insights.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
@@ -459,7 +459,7 @@ How user activity signals are captured is described in the following table.
459
459
|Opened Attachment|A user opened the attachment.|The signal comes from the client (for example, Outlook or Word).|
460
460
|Read Message|The user read the simulation message.|Message read signals might experience issues in the following scenarios: <ul><li>The user reported the message as phishing in Outlook without leaving the reading pane, and **Mark items as read when viewed in the Reading Pane** wasn't configured (default).</li><li>The user reported the unread message as phishing in Outlook, the message was deleted, and **Mark messages as read when deleted** wasn't configured (default).</li></ul>|
461
461
|Out of Office|Determines whether the user is out of office.|Currently calculated by the Automatic replies setting from Outlook.|
462
-
|Compromised User|The user was compromised. The compromise signal varies based on the social engineering technique.|<ul><li>**Credential Harvest**: The user entered their credentials on the login page (credentials aren't stored by Microsoft).¹</li><li>**Malware Attachment**: The user opened the payload attachment and selected **Enable Editing** in [Protected View](https://support.microsoft.com/office/d6f09ac7-e6b9-4495-8e43-2bbcdbcb6653).</li><li>**Link in Attachment**: The user opened the attachment and clicked on the payload link.</li><li>**Link to Malware**: The user clicked on the payload link and entered their credentials.</li><li>**Drive by URL**: The user clicked on the payload link (entering credentials isn't required).¹</li><li>**OAuth Consent Grant**: The user clicked on the payload link and accepted the prompt to share permissions.¹</li></ul>|
462
+
|Compromised User|The user was compromised. The compromise signal varies based on the social engineering technique.|<ul><li>**Credential Harvest**: The user entered their credentials on the login page (credentials aren't stored by Microsoft).¹</li><li>**Malware Attachment**: The user opened the payload attachment and selected **Enable Editing** in [Protected View](https://support.microsoft.com/office/d6f09ac7-e6b9-4495-8e43-2bbcdbcb6653).</li><li>**Link in Attachment**: The user opened the attachment and entered their credentials after clicking on the payload link.</li><li>**Link to Malware**: The user clicked on the payload link and entered their credentials.</li><li>**Drive by URL**: The user clicked on the payload link (entering credentials isn't required).¹</li><li>**OAuth Consent Grant**: The user clicked on the payload link and accepted the prompt to share permissions.¹</li></ul>|
463
463
|Clicked Message Link|The user clicked on the payload link in the simulation message.|The URL in the simulation is unique for each user, which allows individual user activity tracking. Third-party filtering services or email forwarding can lead to false positives. For more information, see [I see clicks or compromise events from users who insist they didn't click the link in the simulation message](attack-simulation-training-faq.md#i-see-clicks-or-compromise-events-from-users-who-insist-they-didnt-click-the-link-in-the-simulation-message).|
464
464
|Forwarded Message|The user forwarded the message.||
465
465
|Replied to Message|The user replied to the message.||
Copy file name to clipboardExpand all lines: defender-office-365/defender-for-office-365-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
@@ -49,7 +49,7 @@ For more information on what's new with other Microsoft Defender security produc
49
49
50
50
-**Tenant Allow/Block List in Microsoft 365 GCC, GCC High, DoD, and Office 365 operated by 21Vianet environments**: The [Tenant Allow/Block List](tenant-allow-block-list-about.md) is now available these environments. They are on parity with the WW commercial experiences.
51
51
52
-
-**45 days after last used date**: The value **Remove allow entry after**\>**45 days after last used date** is now the default on new allow entries from submissions and existing allow entries in the [Tenant Allow/Block List](tenant-allow-block-list-about.md). The allow entry is triggered and the **LastUsedDate** property is updated when the entity is encountered and identified as malicious during mail flow or at time of click. After the filtering system determines that the entity is clean, the allow entry is automatically removed after 45 days. By default, allow entries for spoofed senders never expire.
52
+
-**45 days after last used date**: The value **Remove allow entry after**\>**45 days after last used date** is now the default on new allow entries from submissions. The existing allow entries in the [Tenant Allow/Block List](tenant-allow-block-list-about.md) can also be modified to include the value **Remove allow entry after**\>**45 days after last used date**. The allow entry is triggered and the **LastUsedDate** property is updated when the entity is encountered and identified as malicious during mail flow or at time of click. After the filtering system determines that the entity is clean, the allow entry is automatically removed after 45 days. By default, allow entries for spoofed senders never expire.
53
53
54
54
- (GA) Learning hub resources have moved from the Microsoft Defender portal to [learn.microsoft.com](https://go.microsoft.com/fwlink/?linkid=2273118). Access Microsoft Defender XDR Ninja training, learning paths, training modules and more. Browse the [list of learning paths](/training/browse/?products=m365-ems-cloud-app-security%2Cdefender-for-cloud-apps%2Cdefender-identity%2Cm365-information-protection%2Cm365-threat-protection%2Cmdatp%2Cdefender-office365&expanded=m365%2Coffice-365), and filter by product, role, level, and subject.
0 commit comments