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
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,8 @@ To get the latest features, including preview capabilities (such as endpoint det
44
44
45
45
## Known issues
46
46
47
+
- In version 2506 (101.25062.0005), attempts to upgrade Microsoft Defender for Endpoint on macOS consistently failed. Other versions of Defender are not impacted. To overcome this issue, there is a supported workaround for supported macOS versions and beta versions of macOS 26. The instructions for the workaround can be found [here](https://github.com/microsoft/mdatp-xplat/tree/master/macos/upgrade_from_2506_helper).
48
+
47
49
- Apple fixed an issue on macOS [Ventura upgrade](https://developer.apple.com/documentation/macos-release-notes/macos-13_1-release-notes) and macOS [Sonoma upgrade](https://developer.apple.com/documentation/macos-release-notes/macos-14-release-notes) with the latest OS update. The issue impacts Defender for Endpoint security extensions, and might result in losing Full Disk Access Authorization, impacting the ability of Defender for Endpoint to function properly.
48
50
49
51
- In [macOS Sonoma 14.3.1](https://developer.apple.com/documentation/macos-release-notes/macos-14_3-release-notes), Apple made a change to the handling of Bluetooth devices that impacts Defender for Endpoint device control's ability to intercept and block access to Bluetooth devices. At this time, the recommended mitigation is to use a version of macOS earlier than 14.3.1.
Copy file name to clipboardExpand all lines: defender-office-365/tenant-allow-block-list-about.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
@@ -106,7 +106,7 @@ Unnecessary allow entries expose your organization to malicious email that the s
106
106
- If spoof intelligence already blocked the message as spoofing, use the **Submissions** page at <https://security.microsoft.com/reportsubmission> to [report the email to Microsoft](submissions-admin.md#report-good-email-to-microsoft) as **I've confirmed it's clean**, and then select **Allow this message**.
107
107
- You can proactively create [an allow entry for a spoofed sender](tenant-allow-block-list-email-spoof-configure.md#create-allow-entries-for-spoofed-senders) on the **Spoofed sender** tab in the Tenant Allow/Block List before [spoof intelligence](anti-spoofing-spoof-intelligence.md) identifies and blocks the message as spoofing.
108
108
109
-
-**IP Addresses**: You can proactively create an [an allow entry for an IP address](tenant-allow-block-list-ip-addresses-configure.md#create-block-entries-for-ipv6-addresses) on the **IP addresses** tab in the Tenant Allow/Block List to override the IP filters for incoming messages.
109
+
-**IP Addresses**: You can proactively create [an allow entry for an IP address](tenant-allow-block-list-ip-addresses-configure.md#create-block-entries-for-ipv6-addresses) on the **IP addresses** tab in the Tenant Allow/Block List to override the IP filters for incoming messages.
110
110
- An IP address allow entry bypasses IP-based filtering checks (for example, connection filtering or IP reputation checks).
111
111
- An IP address allow entry doesn't change message throttling behavior.
112
112
- An IP address block entry rejects messages at the service edge.
Copy file name to clipboardExpand all lines: defender-office-365/threat-explorer-real-time-detections-about.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
@@ -245,7 +245,7 @@ The filterable properties that are available in the **Delivery action** box in t
245
245
> - Undelivered email where delivery has failed.
246
246
> - Email where the sender IP address is Microsoft internal. For example, system generated notifications, alerts, or forwarded messages delivered from Microsoft IP addresses.
247
247
>
248
-
> IP addresses in these scenarios might be visisble in Exchange message trace.
248
+
> IP addresses in these scenarios might be visible in Exchange message trace.
249
249
>
250
250
> - ³ By default, a URL search maps to `http`, unless another value is explicitly specified. For example:
251
251
> - Searching with and without the `http://` prefix in **URL**, **URL Domain**, and **URL Domain and Path** should show the same results.
Copy file name to clipboardExpand all lines: exposure-management/classify-critical-assets.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,7 @@ Review critical assets as follows.
59
59
1. In the [Microsoft Defender portal](https://security.microsoft.com), select **Settings > Microsoft XDR > Rules > Critical asset management**.
60
60
1. On the **Critical asset management** page, review predefined and custom critical asset classifications, including the number of assets in the classification, whether assets are on or off, and criticality levels.
61
61
62
-
:::image type="content" source="./media/classify-critical-assets/critical-asset-management-window.png" alt-text="Screenshot of the Critical asset management window.":::
62
+
:::image type="content" source="./media/classify-critical-assets/critical-asset-management-window.png" alt-text="Screenshot of the Critical asset management window.":::
63
63
64
64
> [!NOTE]
65
65
> You can also see critical assets in **Assets > Devices** > **Classify critical asset**. In addition, you can view the **Critical Asset Protection** initiative in **Exposure insights -> Initiatives**.
@@ -105,7 +105,7 @@ Set levels as follows.
105
105
1. In the **Overview** tab, select the desired criticality level.
106
106
1. Select **Save**.
107
107
108
-
:::image type="content" source="./media/classify-critical-assets/edit-criticality-levels.png" alt-text="Screenshot of the Critical asset management criticality editing feature.":::
108
+
:::image type="content" source="./media/classify-critical-assets/edit-criticality-levels.png" alt-text="Screenshot of the Critical asset management criticality editing feature.":::
109
109
110
110
> [!NOTE]
111
111
> You can set critical levels manually in the device inventory. We recommend creating criticality rules that allow broad application of critical levels across assets.
@@ -121,16 +121,16 @@ Edit custom classifications as follows.
121
121
122
122
1. On the **Critical asset management** page, select the relevant asset classification. The **Pending Approval** column helps find classifications with assets that didn't meet the automatic classification threshold and require user approval.
123
123
124
-
:::image type="content" source="media/classify-critical-assets/add-assets.png" alt-text="Screenshot of predefined classifications in the asset management interface.":::
124
+
:::image type="content" source="media/classify-critical-assets/add-assets.png" alt-text="Screenshot of predefined classifications in the asset management interface.":::
125
125
126
126
1. To see all assets in the classification that are currently considered critical, select the **Assets** tab.
127
127
1. To approve assets that fit the classification but are out of threshold, browse to **Pending Approval**.
128
128
1. Review the listed assets. Select the **plus** button next to the assets you want to add.
129
129
130
-
> [!NOTE]
131
-
> **Pending Approval** only displays when there are assets to review.
130
+
> [!NOTE]
131
+
> **Pending Approval** only displays when there are assets to review.
132
132
133
-
:::image type="content" source="media/classify-critical-assets/pending-approval.png" alt-text="Screenshot of the pending approval tab in asset management.":::
133
+
:::image type="content" source="media/classify-critical-assets/pending-approval.png" alt-text="Screenshot of the pending approval tab in asset management.":::
134
134
135
135
You can change the criticality levels and turn off the classification for all assets. You can also edit and delete custom critical assets.
136
136
@@ -140,14 +140,14 @@ You can change the criticality levels and turn off the classification for all as
140
140
1. To see all assets in the classification that are currently considered critical, select the **Assets** tab.
141
141
1. Select the **X** next to the assets you want to remove.
142
142
143
-
:::image type="content" source="media/classify-critical-assets/assets-tab.png" alt-text="Screenshot of the assets tab in asset management.":::
143
+
:::image type="content" source="media/classify-critical-assets/assets-tab.png" alt-text="Screenshot of the assets tab in asset management.":::
144
144
145
145
## Sort by criticality
146
146
147
147
1. Select **Devices** in the **Device Inventory**.
148
148
1. Sort by **Criticality level** to view business critical assets with a "very high" level of criticality.
149
149
150
-
:::image type="content" source="./media/classify-critical-assets/device-inventory.png" alt-text="Screenshot of the Device inventory window showing criticality sorting.":::
150
+
:::image type="content" source="./media/classify-critical-assets/device-inventory.png" alt-text="Screenshot of the Device inventory window showing criticality sorting.":::
0 commit comments