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/mtd.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.subservice: onboard
7
7
ms.author: ewalsh
8
8
author: emmwalshh
9
9
ms.localizationpriority: medium
10
-
ms.date: 03/28/2025
10
+
ms.date: 04/08/2025
11
11
manager: deniseb
12
12
audience: ITPro
13
13
ms.collection:
@@ -74,7 +74,6 @@ The following table summarizes how to deploy Microsoft Defender for Endpoint on
74
74
|MAM|Yes, (need to just install, setup isn't required) | Protects only enrolled apps. MAM supports with/without Device enrollment or enrolled with non-Microsoft Enterprise Mobility Management.|[Configure Microsoft Defender for Endpoint on Android risk signals using App Protection Policies (MAM)](android-configure-mam.md)|
75
75
|Device Administrator (Deprecated on 31 December 2024)|Yes|Intune and Defender for Endpoint are ending support for android device administrator management on devices with access to Google Mobile Services (GMS) on December 31, 2024.|[Deploy Microsoft Defender for Endpoint on Android with Microsoft Intune](android-intune.md#deploy-on-device-administrator-enrolled-devices)|
76
76
77
-
78
77
### Unsupported Android enrollment scenarios
79
78
80
79
These scenarios aren't currently supported:
@@ -88,9 +87,9 @@ These scenarios aren't currently supported:
88
87
|Scenarios|Company portal app required on the device?|Protection Profile/Prerequisites|How to deploy|
89
88
| -------- | -------- | -------- | -------- |
90
89
|Supervised Devices (ADE and Apple Configurator Enrollment|Yes|Protects the entire device. For ADE, if users who use Just in Time (JIT) registration, the Company portal app isn't required because app enrolls the device automatically by connecting to Intune server|[Deploy Microsoft Defender for Endpoint on iOS with Microsoft Intune](ios-install.md#deployment-steps-applicable-for-both-supervised-and-unsupervised-devices)|
91
-
|Unsupervised Devices (Device Enrollment)|Yes|Protects the entire device. For web-based device enrollment, the company portal app isn't required because after the managed app signs in, the app downloads configuration policies directly and not the company portal app)|[Deploy Microsoft Defender for Endpoint on iOS with Microsoft Intune](ios-install.md#deployment-steps-applicable-for-both-supervised-and-unsupervised-devices)|
90
+
|Unsupervised Devices (Device Enrollment)|Yes|Protects the entire device. For web-based device enrollment, the company portal app isn't required because after the managed app signs in, the app downloads configuration policies directly and not the company portal app|[Deploy Microsoft Defender for Endpoint on iOS with Microsoft Intune](ios-install.md#deployment-steps-applicable-for-both-supervised-and-unsupervised-devices)|
92
91
|Unsupervised Devices (User Enrollment)|Yes|Protects work data only. The VPN has access to entire device, and the VPN can scan all app traffic|[Deploy Microsoft Defender for Endpoint on iOS with Microsoft Intune](ios-install.md#user-enrollment-setup-only-for-intune-user-enrolled-devices)|
93
-
|MAM|No|Protects only enrolled apps. The VPN has access to entire device and can scan all app traffic)|[Deploy Microsoft Defender for Endpoint on iOS with Mobile Application Management](ios-install-unmanaged.md)|
92
+
|MAM|No|Protects only enrolled apps. The VPN has access to entire device and can scan all app traffic|[Deploy Microsoft Defender for Endpoint on iOS with Mobile Application Management](ios-install-unmanaged.md)|
Copy file name to clipboardExpand all lines: defender-endpoint/network-protection-macos.md
+21-21Lines changed: 21 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,11 +3,11 @@ title: Use network protection to help prevent macOS connections to bad sites
3
3
description: Protect your network by preventing macOS users from accessing known malicious and suspicious network addresses
4
4
ms.service: defender-endpoint
5
5
ms.localizationpriority: medium
6
-
ms.date: 11/10/2024
6
+
ms.date: 04/08/2025
7
7
audience: ITPro
8
8
author: denisebmsft
9
9
ms.author: deniseb
10
-
ms.reviewer:
10
+
ms.reviewer: ericlaw
11
11
manager: deniseb
12
12
ms.custom: asr
13
13
ms.subservice: macos
@@ -48,7 +48,9 @@ Network protection helps reduce the attack surface of your devices from Internet
48
48
- exploits
49
49
- other malicious content on the Internet
50
50
51
-
Network protection expands the scope of Microsoft Defender XDR [SmartScreen](/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview) to block all outbound HTTP/HTTPS traffic that attempts to connect to low-reputation sources. The blocks on outbound HTTP/HTTPS traffic are based on the domain or hostname.
51
+
Network protection expands the scope of Microsoft Defender [SmartScreen](/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview) to block all outbound HTTP/HTTPS traffic that attempts to connect to low-reputation sources across all major browsers. Blocks on outbound HTTP/HTTPS traffic are based on the domain or hostname.
52
+
53
+
In non-Microsoft Edge processes, Network Protection determines the fully qualified domain name for each HTTPS connection by examining the content of the TLS handshake that occurs after a TCP/IP handshake. This requires that the HTTPS connection use TCP/IP (not UDP/QUIC) and that the ClientHello message not be encrypted. To disable QUIC and Encrypted Client Hello in Google Chrome, see [QuicAllowed](https://chromeenterprise.google/policies/#QuicAllowed) and [EncryptedClientHelloEnabled](https://chromeenterprise.google/policies/#EncryptedClientHelloEnabled). For Mozilla Firefox, see [Disable EncryptedClientHello](https://mozilla.github.io/policy-templates/#disableencryptedclienthello) and [network.http.http3.enable](https://support.mozilla.org/ml/questions/1408003#answer-1571474).
52
54
53
55
## Availability
54
56
@@ -69,7 +71,7 @@ To roll out Network Protection for macOS, we recommend the following actions:
69
71
70
72
- Block website categories scoped to device groups through policies created in the Microsoft Defender portal.
71
73
72
-
- Policies are applied to browsers, including Chromium Microsoft Edge for macOS.
74
+
- Policies are applied to browsers, including Microsoft Edge for macOS.
73
75
74
76
- Advanced Hunting - Network Events are reflected in the Machine Timeline, and queryable in Advanced Hunting to aid security investigations.
75
77
@@ -87,17 +89,15 @@ To roll out Network Protection for macOS, we recommend the following actions:
87
89
88
90
### Known issues
89
91
90
-
- Block/Warn UX isn't customizable and might require other look and feel changes. (Customer feedback is being collected to drive further design improvements)
91
-
92
92
- There's a known application incompatibility issue with VMware's "Per-App Tunnel" feature. (This incompatibility might result in an inability to block traffic that goes through the "Per-App Tunnel.")
93
93
94
94
- There's a known application incompatibility issue with Blue Coat Proxy. (This incompatibility might result in network layer crashes in unrelated applications when both Blue Coat Proxy and Network Protection are enabled.)
95
95
96
96
### Important notes
97
97
98
-
- We don't recommend controlling network protection from System Preferences by using the **Disconnect** button. Instead, use the mdatp command-line tool or JamF/Intune to control network protection for macOS.
98
+
- We don't recommend controlling network protection from System Preferences. Instead, use the mdatp command-line tool or JamF/Intune to control network protection for macOS.
99
99
100
-
- To evaluate effectiveness of macOS web threat protection, we recommend trying it in browsers other than Microsoft Edge for macOS (for example, Safari). Microsoft Edge for macOS has built-in web threat protection (Microsoft Defender Browser Protection extension which provides Smartscreen capabilities) that is enabled regardless of whether the Mac network protection feature you're evaluating, is turned on or not.
100
+
- To evaluate effectiveness of macOS web threat protection, we recommend trying it in browsers other than Microsoft Edge for macOS (for example, Safari). Microsoft Edge for macOS has built-in web threat protection (Smartscreen) that is enabled regardless of the state of Network Protection.
101
101
102
102
## Deployment instructions
103
103
@@ -111,7 +111,7 @@ Install the most recent product version through Microsoft AutoUpdate. To open Mi
111
111
open /Library/Application\ Support/Microsoft/MAU2.0/Microsoft\ AutoUpdate.app
112
112
```
113
113
114
-
Configure the product with your organization information using the instructions in our public documentation.
114
+
Configure the product with your organization information using the instructions in our documentation.
115
115
116
116
Network protection is disabled by default, but it can be configured to run in one of the following modes (also called enforcement levels):
117
117
@@ -299,7 +299,7 @@ The following scenarios are supported.
299
299
300
300
### Web threat protection
301
301
302
-
Web threat protection is part of web protection in Microsoft Defender XDR for Endpoint. It uses network protection to secure your devices against web threats. By integrating with Microsoft Edge for macOS and popular non-Microsoft browsers, such as Brave, Chrome, Firefox, Safari, Opera, web threat protection stops web threats without a web proxy. For more information about browser support, see [Prerequisites](#prerequisites) Web threat protection can protect devices while they're onpremises or away. Web threat protection stops access to the following types of sites:
302
+
Web threat protection is part of web protection in Microsoft Defender XDR for Endpoint. It uses network protection to secure your devices against web threats. By integrating with Microsoft Edge for macOS and popular non-Microsoft browsers (such as Brave, Chrome, Firefox, Safari, Opera), web threat protection stops web threats without requiring a web proxy. For more information about browser support, see [Prerequisites](#prerequisites) Web threat protection can protect devices while they're on-premises or away. Web threat protection stops access to the following types of sites:
303
303
304
304
- phishing sites
305
305
- malware vectors
@@ -327,25 +327,27 @@ For more information, see: [Create indicators for IPs and URLs/domains](indicato
327
327
328
328
Web content filtering is part of the [Web protection](web-protection-overview.md) capabilities in Microsoft Defender for Endpoint and Microsoft Defender for Business. Web content filtering enables your organization to track and regulate access to websites based on their content categories. Many of these websites (even if they're not malicious) might be problematic because of compliance regulations, bandwidth usage, or other concerns.
329
329
330
-
Configure policies across your device groups to block certain categories. Blocking a category prevents users within specified device groups from accessing URLs associated with the category. For any category that's not blocked, the URLs are automatically audited. Your users can access the URLs without disruption, and you gather access statistics to help create a more custom policy decision. Your users see a block notification if an element on the page they're viewing is making calls to a blocked resource.
330
+
Configure policies across your device groups to block certain categories. Blocking a category prevents users within specified device groups from accessing URLs associated with the category. For any category that's not blocked, the URLs are automatically audited. Your users can access the URLs without disruption, and you gather access statistics to help create a more custom policy decision. Your users will see a block notification if an element on the page they're viewing is making calls to a blocked resource.
331
331
332
-
Web content filtering is available on the major web browsers, with blocks performed by Network Protection (Brave, Chrome, Firefox, Safari, and Opera). For more information about browser support, see [Prerequisites](#prerequisites).
332
+
Web content filtering supports major web browsers (Brave, Chrome, Firefox, Safari, and Opera) with blocking enforced by Network Protection.
333
+
334
+
For more information about browser support, see [Prerequisites](#prerequisites).
For more information about reporting, see [Web content filtering](web-content-filtering.md).
337
339
338
340
### Microsoft Defender for Cloud Apps
339
341
340
-
The Microsoft Defender for Cloud Apps / Cloud App Catalog identifies apps you would want end users to be warned upon accessing with Microsoft Defender XDR for Endpoint, and mark them as _Monitored_. The domains listed under monitored apps would be later synced to Microsoft Defender XDR for Endpoint:
342
+
The Microsoft Defender for Cloud Apps / Cloud App Catalog identifies apps you want end users to be warned upon accessing, and mark them as _Monitored_. The domains listed under monitored apps are later synced to Microsoft Defender XDR for Endpoint:
Within 10-15 minutes, these domains are listed in Microsoft Defender XDR under Indicators > URLs/Domains with Action=Warn. Within the enforcement SLA (see details at the end of this article), end users are getting warn messages when attempting to access these domains:
346
+
Within 10-15 minutes, these domains are listed in Microsoft Defender XDR under Indicators > URLs/Domains with Action=Warn. Within the enforcement SLA (see details at the end of this article), end users receive warn messages when attempting to access these domains:
345
347
346
348
:::image type="content" source="media/network-protection-macos-indicators-urls-domains-warn.png" alt-text="Shows network protection indicators for urls or domains warning.":::
347
349
348
-
When the end user is attempting to access monitored domains, they're warned by Defender for Endpoint. The user gets a plain block experience accompanied by the following toast message, which is displayed by the operating system including the name of the blocked application (e.g Blogger.com)
350
+
When a end user attempts to access monitored domains, they're warned by Defender for Endpoint. The user gets a plain block experience accompanied by the following toast message, which is displayed by the operating system including the name of the blocked application (e.g Blogger.com)
@@ -372,17 +374,15 @@ For many organizations, it's important to take the cloud controls provided by Mi
372
374
373
375
- the specific incident
374
376
- why it has happened
375
-
-what is the thinking behind this decision
376
-
- how encountering block sites can be mitigated
377
+
- the rationale behind this decision
378
+
- how encountering blocked sites can be mitigated
377
379
378
380
Upon facing an unexpected behavior, users' confusion might be reduced by providing them as much information as possible, not only to explain about what has happened but to also educate them to be more aware the next time they choose a cloud app to complete their job. For example, this information can include:
379
381
380
382
- Organization security and compliance policies and guidelines for internet and cloud use
381
383
- Approved/recommended cloud apps for use
382
384
- Restricted/blocked cloud apps for use
383
385
384
-
For this page, we recommend that your organization uses a basic SharePoint site.
385
-
386
386
### Important things to know
387
387
388
388
1. It can take up to two hours (typically less) for app domains to propagate and to be update in the endpoint devices, after it's marked as _Monitored_.
@@ -391,10 +391,10 @@ For this page, we recommend that your organization uses a basic SharePoint site.
391
391
392
392
3. Full URLs are currently not supported and aren't sent from Microsoft Defender for Cloud Apps to Microsoft Defender for Endpoint. If any full URLs are listed under Microsoft Defender for Cloud Apps as monitored apps, users aren't warned when they attempt to access a site. (For example, `google.com/drive` isn't supported, while `drive.google.com` is supported.)
393
393
394
-
4.Network protection doesn't support the use of QUIC on browsers. Administrators need to ensure that QUIC is disabled when testing to ensure sites are blocked correctly.
394
+
4. Administrators need to ensure that Encrypted Client Hello and QUIC are disabled when testing to ensure sites are blocked correctly. See instructions above.
395
395
396
396
> [!TIP]
397
-
> No end-user notifications are appearing on third party browsers? Check your toast message settings.
397
+
> No end-user notifications are appearing on third party browsers? Ensure you've allowed notifications from Microsoft Defender in **System Settings** > **Notifications**.
0 commit comments