deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-17 07:47:22 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Update windows/security/threat-protection/microsoft-defender-atp/indicator-ip-domain.md

Browse Source 
Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com>
This commit is contained in:
Denise Vangel-MSFT 2020-12-30 09:29:20 -08:00 committed by GitHub
parent c18f5cf456
commit f9ff878940
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
windows/security/threat-protection/microsoft-defender-atp/indicator-ip-domain.md
View File

@ -51,8 +51,8 @@ It's important to understand the following prerequisites prior to creating indic
> Only external IPs can be added to the indicator list. Indicators cannot be created for internal IPs. > Only external IPs can be added to the indicator list. Indicators cannot be created for internal IPs.
> For web protection scenarios, we recommend using the built-in capabilities in Microsoft Edge. Microsoft Edge leverages [Network Protection](network-protection.md) to inspect network traffic and allows blocks for TCP, HTTP, and HTTPS (TLS). For all other processes, web protection scenarios leverage Network Protection for inspection and enforcement: <br> > For web protection scenarios, we recommend using the built-in capabilities in Microsoft Edge. Microsoft Edge leverages [Network Protection](network-protection.md) to inspect network traffic and allows blocks for TCP, HTTP, and HTTPS (TLS). For all other processes, web protection scenarios leverage Network Protection for inspection and enforcement: <br>
> NOTE: > NOTE:
>- IP is supported for all three protocols > - IP is supported for all three protocols
>- Only single IP addresses are supported (no CIDR blocks or IP ranges) > - Only single IP addresses are supported (no CIDR blocks or IP ranges)
>- Encrypted URLs (full path) can only be blocked on first party browsers (Internet Explorer, Edge) >- Encrypted URLs (full path) can only be blocked on first party browsers (Internet Explorer, Edge)
>- Encrypted URLS (FQDN only) can be blocked outside of first party browsers (Internet Explorer, Edge) >- Encrypted URLS (FQDN only) can be blocked outside of first party browsers (Internet Explorer, Edge)
>- Full URL path blocks can be applied on the domain level and all unencrypted URLs >- Full URL path blocks can be applied on the domain level and all unencrypted URLs