Skip to content

Commit

Permalink
Merge branch 'public' into release-notes
Browse files Browse the repository at this point in the history
  • Loading branch information
denisebmsft authored Sep 20, 2024
2 parents 47e865b + b45efb7 commit ecb32d8
Show file tree
Hide file tree
Showing 15 changed files with 70 additions and 56 deletions.
8 changes: 4 additions & 4 deletions defender-endpoint/mac-whatsnew.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,12 +40,12 @@ For more information on Microsoft Defender for Endpoint on other operating syste
> [!NOTE]
> - 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.
> - 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.
> - 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.
> - 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.

**Sequoia support**

Microsoft Defender supports macOS Sequoia (15) in the current Defender release.
Microsoft Defender is working with Apple on a network stack change that is impacting Network Protection's Network Filter with macOS Sequoia (15).

**macOS Deprecation**

Expand Down Expand Up @@ -89,7 +89,7 @@ Behavior monitoring monitors process behavior to detect and analyze potential th

##### What's new

- [[device control](mac-device-control-overview.md)] Secure Digital cards are not recognized on newer macOS
- [[device control](mac-device-control-overview.md)] Secure Digital cards aren't recognized on newer macOS
- Bug and performance fixes

### May-2024 (Build: 101.24042.0008 | Release version: 20.124042.8.0)
Expand Down Expand Up @@ -1026,7 +1026,7 @@ Live Response for macOS is now available for all Mac devices onboarded to Defend
> 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.
> > The mechanism for granting this consent depends on how you deployed Microsoft Defender for Endpoint:
> - For manual deployments, see the updated instructions in the [Manual deployment topic](mac-install-manually.md#allow-full-disk-access).
- 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.
- 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.

- Performance improvements & bug fixes

Expand Down
48 changes: 16 additions & 32 deletions defender-endpoint/microsoft-defender-antivirus-updates.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,11 +3,11 @@ title: Microsoft Defender Antivirus security intelligence and product updates
description: Manage how Microsoft Defender Antivirus receives protection and product updates.
ms.service: defender-endpoint
ms.localizationpriority: high
ms.date: 08/12/2024
ms.date: 09/19/2024
audience: ITPro
ms.topic: reference
author: siosulli
ms.author: siosulli
author: denisebmsft
ms.author: deniseb
ms.custom: nextgen
ms.reviewer: pahuijbr, tudobril, yongrhee
manager: deniseb
Expand Down Expand Up @@ -151,21 +151,6 @@ All our updates contain:
- 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.
- 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.

### May-2024 (Engine: 1.1.24050.5 | Platform: 4.18.24050.7)

- Security intelligence update version: **1.413.1.0**
- Release date: **May 30, 2024** (Engine) / **June 4, 2024** (Platform)
- Engine: **1.1.24050.5**
- Platform: **4.18.24050.7**
- Support phase: **Security and Critical Updates**

#### What's new

- Improved performance when running configuration queries.
- Optimized how scans are prioritized.
- Fixed a crash caused by a race condition with a device control driver.
- Added Event Viewer Logging for scan start event where the scan originates from PowerShell.

### Previous version updates: Technical upgrade support only

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).
Expand Down Expand Up @@ -228,14 +213,13 @@ Updates are released for x86, x64, and ARM64 Windows architecture.

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).

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).
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).

### 1.415.295.0
### 1.417.472.0

- Defender package version: `1.415.295.0`
- Security intelligence version: `1.415.295.0`
- Engine version: `1.24070.1`
- Platform version: `4.18.24070.5`
- Defender package version: `1.417.472.0`
- Security intelligence version: `1.417.472.0`
- Engine version: `1.24080.9`

#### Fixes

Expand All @@ -245,10 +229,10 @@ After a new package version is released, support for the previous two versions i

- None

### 1.415.235.0
### 1.415.295.0

- Defender package version: `1.415.235.0`
- Security intelligence version: `1.415.235.0`
- Defender package version: `1.415.295.0`
- Security intelligence version: `1.415.295.0`
- Engine version: `1.24070.1`
- Platform version: `4.18.24070.5`

Expand All @@ -260,12 +244,12 @@ After a new package version is released, support for the previous two versions i

- None

### 1.411.111.0
### 1.415.235.0

- Defender package version: `1.411.111.0`
- Security intelligence version: `1.411.111.0`
- Engine version: `1.24050.2`
- Platform version: `4.18.24050.7`
- Defender package version: `1.415.235.0`
- Security intelligence version: `1.415.235.0`
- Engine version: `1.24070.1`
- Platform version: `4.18.24070.5`

#### Fixes

Expand Down
6 changes: 3 additions & 3 deletions defender-endpoint/microsoft-defender-endpoint-mac.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ ms.collection:
ms.topic: conceptual
ms.subservice: macos
search.appverid: met150
ms.date: 09/17/2024
ms.date: 09/19/2024
---

# Microsoft Defender for Endpoint on Mac
Expand Down Expand Up @@ -71,12 +71,12 @@ There are several methods and deployment tools that you can use to install and c

The three most recent major releases of macOS are supported.

- 15 (Sequoia)

- 14 (Sonoma)

- 13 (Ventura)

- 12 (Monterey)

> [!IMPORTANT]
> 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).
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,11 +2,11 @@
title: Microsoft Defender Antivirus updates - Previous versions for technical upgrade support
description: Understand the type of technical support offered for previous versions of Microsoft Defender Antivirus
ms.service: defender-endpoint
ms.author: siosulli
author: siosulli
ms.author: deniseb
author: denisebmsft
ms.localizationpriority: medium
ms.reviewer: pahuijbr
ms.date: 08/12/2024
ms.date: 09/19/2024
manager: deniseb
audience: ITPro
ms.collection:
Expand All @@ -29,6 +29,21 @@ Microsoft regularly releases [security intelligence updates and product updates

## Engine and platform updates

### May-2024 (Engine: 1.1.24050.5 | Platform: 4.18.24050.7)

- Security intelligence update version: **1.413.1.0**
- Release date: **May 30, 2024** (Engine) / **June 4, 2024** (Platform)
- Engine: **1.1.24050.5**
- Platform: **4.18.24050.7**
- Support phase: **Technical upgrade support (only)**

#### What's new

- Improved performance when running configuration queries.
- Optimized how scans are prioritized.
- Fixed a crash caused by a race condition with a device control driver.
- Added Event Viewer Logging for scan start event where the scan originates from PowerShell.

### April-2024 (Engine: 1.1.24040.1 | Platform: 4.18.24040.4)

- Security intelligence update version: **1.411.7.0**
Expand Down Expand Up @@ -1106,6 +1121,21 @@ Microsoft regularly releases [security intelligence updates and product updates

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).

### 1.411.111.0

- Defender package version: `1.411.111.0`
- Security intelligence version: `1.411.111.0`
- Engine version: `1.24050.2`
- Platform version: `4.18.24050.7`

#### Fixes

- None

#### Additional information

- None

### 1.411.9.0

- Defender package version: `1.411.9.0`
Expand Down
2 changes: 1 addition & 1 deletion defender-office-365/attack-simulation-training-insights.md
Original file line number Diff line number Diff line change
Expand Up @@ -459,7 +459,7 @@ How user activity signals are captured is described in the following table.
|Opened Attachment|A user opened the attachment.|The signal comes from the client (for example, Outlook or Word).|
|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>|
|Out of Office|Determines whether the user is out of office.|Currently calculated by the Automatic replies setting from Outlook.|
|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>|
|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>|
|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).|
|Forwarded Message|The user forwarded the message.||
|Replied to Message|The user replied to the message.||
Expand Down
2 changes: 1 addition & 1 deletion defender-office-365/defender-for-office-365-whats-new.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ For more information on what's new with other Microsoft Defender security produc

- **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.

- **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.
- **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.

- (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.

Expand Down
Loading

0 comments on commit ecb32d8

Please sign in to comment.