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/network-protection.md
+21-22Lines changed: 21 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,10 @@ Want to experience Microsoft Defender for Endpoint? [Sign up for a free trial](h
40
40
Network protection helps protect devices by preventing connections to malicious or suspicious sites. Examples of dangerous domains are domains that host phishing scams, malicious downloads, tech scams, or other malicious content. 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(S) traffic that attempts to connect to poor-reputation sources (based on the domain or hostname).
41
41
42
42
Network protection extends the protection in [Web protection](web-protection-overview.md) to the operating system level, and is a core component for [Web Content Filtering](web-content-filtering.md) (WCF). It provides the web protection functionality found in Microsoft Edge to other supported browsers and nonbrowser applications. Network protection also provides visibility and blocking of indicators of compromise (IOCs) when used with [Endpoint detection and response](overview-endpoint-detection-response.md). For example, network protection works with your [custom indicators](indicators-overview.md) to block specific domains or host names.
43
+
44
+
Watch this video to learn how network protection helps reduce the attack surface of your devices from phishing scams, exploits, and other malicious content:
@@ -51,9 +55,11 @@ The following table summarizes network protection areas of coverage.
51
55
|[Custom Indicators](indicators-overview.md)| SmartScreen must be enabled | Network protection must be in block mode | Network protection must be in block mode |
52
56
|[Web Content Filtering](web-content-filtering.md)| SmartScreen must be enabled | Network protection must be in block mode | Not supported |
53
57
58
+
To ensure that SmartScreen is enabled for Microsoft Edge, use [Edge Policy: SmartScreen Enabled](/deployedge/microsoft-edge-policies#smartscreenenabled).
59
+
54
60
> [!NOTE]
55
-
> On Mac and Linux, you must have network protection in block mode for these features to be supported in the Microsoft Edge browser.
56
61
> On Windows, network protection doesn't monitor Microsoft Edge. For processes other than Microsoft Edge and Internet Explorer, web protection scenarios leverage network protection for inspection and enforcement.
62
+
> On Mac and Linux, the Microsoft Edge browser only integrates Web Threat Protection. Network protection must be enabled in block mode to support Custom Indicators and Web Content Filtering in Edge and other browsers.
57
63
58
64
### Known issues & limitations
59
65
- IP addresses are supported for all three protocols (TCP, HTTP, and HTTPS (TLS))
@@ -64,11 +70,7 @@ The following table summarizes network protection areas of coverage.
64
70
- FQDNs loaded via HTTP2 connection coalescing can only be blocked in Microsoft Edge
65
71
- Network Protection will block connections on all ports (not just 80 and 443).
66
72
67
-
There might be up to two hours of latency (usually less) between the time when the action is taken and the URL/IP is blocked.
68
-
69
-
Watch this video to learn how network protection helps reduce the attack surface of your devices from phishing scams, exploits, and other malicious content:
There might be up to two hours of latency (usually less) between when an indicator/policy is added and a matching URL/IP is blocked.
72
74
73
75
## Requirements for network protection
74
76
@@ -112,7 +114,7 @@ The network protection component of Defender for Endpoint identifies and blocks
112
114
113
115
#### Network protection: C2 detection and remediation
114
116
115
-
In its initial form, ransomware is a commodity threat that's preprogrammed and focused on limited, specific outcomes (like encrypting a computer). However, ransomware has evolved into a sophisticated threat that is human-driven, adaptive, and focused on larger scale and more widespread outcomes, like holding an entire organization's assets or data for ransom.
117
+
Ransomware has evolved into a sophisticated threat that is human-driven, adaptive, and focused on large scale outcomes, like holding an entire organization's assets or data for ransom.
116
118
117
119
Support for Command and Control servers (C2) is an important part of this ransomware evolution, and it's what enables these attacks to adapt to the environment they target. Breaking the link to the command-and-control infrastructure stops the progression of an attack to its next stage. For more information about C2 detection and remediation, see [Tech Community blog: Detecting and remediating command and control attacks at the network layer](https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/detecting-and-remediating-command-and-control-attacks-at-the/ba-p/3650607).
118
120
@@ -155,8 +157,10 @@ A user visits a website. If the url has an unknown or uncertain reputation, a to
155
157
> The images shown in this article for both the `warn` experience and `block` experience use "blocked url" as example placeholder text. In a functioning environment, the actual url or domain is listed.
156
158
157
159
#### Use CSP to enable `Convert warn verdict to block`
160
+
By default, SmartScreen verdicts for malicious sites result in a warning that can be overridden by the user. A policy can be set to convert the warning to blocks, preventing such overrides.
For non-Edge browsers, see [Defender CSP: Configuration/EnableConvertWarnToBlock](/windows/client-management/mdm/defender-csp#configurationenableconvertwarntoblock).
163
+
For Edge browsers, see [Edge Policy: Prevent SmartScreen Prompt Override](/en-us/deployedge/microsoft-edge-policies#preventsmartscreenpromptoverride).
160
164
161
165
#### Use Group Policy to enable Convert warn verdict to block
162
166
@@ -202,7 +206,7 @@ Network protection is enabled per device, which is typically done using your man
202
206
> [!NOTE]
203
207
> Microsoft Defender Antivirus must be in active mode to enable network protection.
204
208
205
-
You can enable network protection in `audit` mode or `block` mode. If you want to evaluate the impact of enabling network protection before actually blocking IP addresses or URLs, you can enable network protection in audit mode, and gather data on what would be blocked. Audit mode logs whenever end users connect to an address or site that would otherwise be blocked by network protection. In order for indicators of compromise (IoC) or Web content filtering (WCF) to work, network protection must be in `block` mode.
209
+
You can enable network protection in `audit` mode or `block` mode. If you want to evaluate the impact of enabling network protection before actually blocking IP addresses or URLs, you can enable network protection in [audit mode](overview-attack-surface-reduction.md). Audit mode logs whenever end users connect to an address or site that would otherwise be blocked by network protection. To enforce blocking of custom indicators or Web content filtering categories, network protection must be in `block` mode.
206
210
207
211
For information about network protection for Linux and macOS see the following articles:
208
212
@@ -229,7 +233,7 @@ DeviceEvents
229
233
:::image type="content" source="media/network-protection-advanced-hunting.png" alt-text="Advanced hunting for auditing and identifying events." lightbox="media/network-protection-advanced-hunting.png":::
230
234
231
235
> [!TIP]
232
-
> These entries have data in the **AdditionalFields** column which gives you great info around the action, if you expand **AdditionalFields** you can also get the fields: **IsAudit**, **ResponseCategory**, and **DisplayName**.
236
+
> These entries have data in the **AdditionalFields** column which supplies more info around the action, including the fields: **IsAudit**, **ResponseCategory**, and **DisplayName**.
233
237
234
238
Here's another example:
235
239
@@ -266,21 +270,19 @@ DeviceEvents
266
270
267
271
```
268
272
269
-
You can use the resulting list of URLs and IPs to determine what would be blocked if network protection is set to block mode on the device. You can also see which features would block URLs and IPs. Review the list to identify any URLS or IPs that are necessary for your environment. You can then create an allow indicator for those URLs or IP addresses. Allow indicators take precedence over any blocks.
273
+
You can use the resulting list of URLs and IPs to determine what would be blocked if network protection is set to block mode on the device. You can also see which features would block URLs and IPs. Review the list to identify any URLS or IPs that are necessary for your environment. You can then create an allow indicator for those URLs or IP addresses. Allow indicators take precedence over any blocks. See [Order of precedence for Network protection blocks](web-protection-overview.md#order-of-precedence).
270
274
271
-
Once you've created an indicator, you can look at resolving the underlying issue as follows:
275
+
After creating an indicator to unblock a site, you may attempt to resolve the original block as follows:
272
276
273
-
-**SmartScreen**: request review
277
+
-**SmartScreen**: report false positive, if appropriate
274
278
-**Indicator**: modify existing indicator
275
279
-**MCA**: review unsanctioned app
276
280
-**WCF**: request recategorization
277
281
278
-
Using this data you can make an informed decision on enabling network protection in Block mode. See [Order of precedence for Network protection blocks](web-protection-overview.md#order-of-precedence).
279
-
280
282
> [!NOTE]
281
-
> As this is a per-device setting, if there are devices that cannot move to Block mode you can simply leave them on audit until you can rectify the challenge and you will still receive the auditing events.
283
+
> As this is a per-device setting, if there are devices that cannot move to Block mode you can simply leave them on audit to receive the auditing events.
282
284
283
-
For information about how to report false positives see [Report false positives](web-protection-overview.md#report-false-positives).
285
+
For information about how to report false positives in SmartScreen data, see [Report false positives](web-protection-overview.md#report-false-positives).
284
286
285
287
For details on how to create your own Power BI reports, see [Create custom reports using Power BI](api/api-power-bi.md).
286
288
@@ -301,9 +303,7 @@ In non-Microsoft Edge processes, Network Protection determines the fully qualifi
301
303
302
304
Network protection works best with [Microsoft Defender for Endpoint](microsoft-defender-endpoint.md), which gives you detailed reporting into exploit protection events and blocks as part of [alert investigation scenarios](investigate-alerts.md).
303
305
304
-
When network protection blocks a connection, a notification is displayed from the Action Center. Your security operations team can [customize the notification](attack-surface-reduction-rules-deployment-implement.md#customize-attack-surface-reduction-rules) with your organization's details and contact information.
305
-
306
-
You can also use [audit mode](overview-attack-surface-reduction.md) to evaluate how network protection would impact your organization if it were enabled.
306
+
When network protection blocks a connection, a notification is displayed on the client. Your security operations team can [customize the notification](attack-surface-reduction-rules-deployment-implement.md#customize-attack-surface-reduction-rules) with your organization's details and contact information.
0 commit comments