From ed4e39ec8c49bdd5bc239c8ca110891deea03fd1 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Dec 2020 09:29:39 -0800 Subject: [PATCH] Update windows/security/threat-protection/microsoft-defender-atp/indicator-ip-domain.md Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- .../microsoft-defender-atp/indicator-ip-domain.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/indicator-ip-domain.md b/windows/security/threat-protection/microsoft-defender-atp/indicator-ip-domain.md index b32d4960f4..f859c87358 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/indicator-ip-domain.md +++ b/windows/security/threat-protection/microsoft-defender-atp/indicator-ip-domain.md @@ -53,9 +53,9 @@ It's important to understand the following prerequisites prior to creating indic > NOTE: > - IP is supported for all three protocols > - 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 (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 +> - 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) +> - Full URL path blocks can be applied on the domain level and all unencrypted URLs >[!NOTE] >There may be up to 2 hours of latency (usually less) between the time the action is taken, and the URL and IP being blocked.