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/indicator-file.md
+14-12Lines changed: 14 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.service: defender-endpoint
6
6
ms.author: siosulli
7
7
author: siosulli
8
8
ms.localizationpriority: medium
9
-
ms.date: 03/20/2024
9
+
ms.date: 08/26/2024
10
10
manager: deniseb
11
11
audience: ITPro
12
12
ms.collection:
@@ -115,17 +115,15 @@ Choose if to Generate an alert on the file block event and define the alerts set
115
115
:::image type="content" source="media/indicators-generate-alert.png" alt-text="The Alert settings for file indicators" lightbox="media/indicators-generate-alert.png":::
116
116
117
117
> [!IMPORTANT]
118
-
>
119
-
> - Typically, file blocks are enforced and removed within a couple of minutes, but can take upwards of 30 minutes.
120
-
> - If there are conflicting file IoC policies with the same enforcement type and target, the policy of the more secure hash will be applied. An SHA-256 file hash IoC policy will win over an SHA-1 file hash IoC policy, which will win over an MD5 file hash IoC policy if the hash types define the same file. This is always true regardless of the device group.
121
-
> - In all other cases, if conflicting file IoC policies with the same enforcement target are applied to all devices and to the device's group, then for a device, the policy in the device group will win.
122
-
> - If the EnableFileHashComputation group policy is disabled, the blocking accuracy of the file IoC is reduced. However, enabling `EnableFileHashComputation` may impact device performance. For example, copying large files from a network share onto your local device, especially over a VPN connection, might have an effect on device performance.
123
-
>
118
+
> - Typically, file blocks are enforced and removed within15 minutes, average 30 minutes but can take upwards of 2 hours.
119
+
- If there are conflicting file IoC policies with the same enforcement type and target, the policy of the more secure hash will be applied. An SHA-256 file hash IoC policy will win over an SHA-1 file hash IoC policy, which will win over an MD5 file hash IoC policy if the hash types define the same file. This is always true regardless of the device group.
120
+
- In all other cases, if conflicting file IoC policies with the same enforcement target are applied to all devices and to the device's group, then for a device, the policy in the device group will win.
121
+
- If the EnableFileHashComputation group policy is disabled, the blocking accuracy of the file IoC is reduced. However, enabling `EnableFileHashComputation` may impact device performance. For example, copying large files from a network share onto your local device, especially over a VPN connection, might have an effect on device performance.
122
+
124
123
> For more information about the EnableFileHashComputation group policy, see [Defender CSP](/windows/client-management/mdm/defender-csp).
125
-
>
126
-
> For more information on configuring this feature on Defender for Endpoint on Linux and macOS, see [Configure file hash computation feature on Linux](linux-preferences.md#configure-file-hash-computation-feature) and [Configure file hash computation feature on macOS](mac-preferences.md#configure-file-hash-computation-feature).
124
+
> > For more information on configuring this feature on Defender for Endpoint on Linux and macOS, see [Configure file hash computation feature on Linux](linux-preferences.md#configure-file-hash-computation-feature) and [Configure file hash computation feature on macOS](mac-preferences.md#configure-file-hash-computation-feature).
127
125
128
-
## Advanced hunting capabilities (preview)
126
+
> ## Advanced hunting capabilities (preview)
129
127
130
128
> [!IMPORTANT]
131
129
> Information in this section (**Public Preview for Automated investigation and remediation engine**) relates to prerelease product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
@@ -158,11 +156,17 @@ The response action activity can also be viewable in the device timeline.
158
156
Cert and File IoC policy handling conflicts follow this order:
159
157
160
158
1. If the file isn't allowed by Windows Defender Application Control and AppLocker enforce mode policies, then **Block**.
159
+
161
160
2. Else, if the file is allowed by the Microsoft Defender Antivirus exclusions, then **Allow**.
161
+
162
162
3. Else, if the file is blocked or warned by a block or warn file IoCs, then **Block/Warn**.
163
+
163
164
4. Else, if the file is blocked by SmartScreen, then **Block**.
165
+
164
166
5. Else, if the file is allowed by an allow file IoC policy, then **Allow**.
167
+
165
168
6. Else, if the file is blocked by attack surface reduction rules, controlled folder access, or antivirus protection, then **Block**.
169
+
166
170
7. Else, **Allow** (passes Windows Defender Application Control & AppLocker policy, no IoC rules apply to it).
Copy file name to clipboardExpand all lines: defender-endpoint/indicator-ip-domain.md
+22-18Lines changed: 22 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.collection:
15
15
ms.topic: conceptual
16
16
ms.subservice:
17
17
search.appverid: met150
18
-
ms.date: 10/06/2023
18
+
ms.date: 08/26/2024
19
19
---
20
20
21
21
# Create indicators for IPs and URLs/domains
@@ -46,38 +46,42 @@ You can block malicious IPs/URLs through the settings page or by machine groups,
46
46
> [!NOTE]
47
47
> Classless Inter-Domain Routing (CIDR) notation for IP addresses is not supported.
48
48
49
-
## Before you begin
50
-
51
-
It's important to understand the following prerequisites prior to creating indicators for IPS, URLs, or domains:
52
-
53
-
### Network Protection requirements
54
-
55
-
URL/IP allow and block requires that the Microsoft Defender for Endpoint component _Network Protection_ is enabled in block mode. For more information on Network Protection and configuration instructions, see [Enable network protection](enable-network-protection.md).
56
-
57
49
### Supported operating systems
58
50
59
-
- Windows 10, version 1709 or later
60
51
- Windows 11
61
-
- Windows Server 2016
62
-
- Windows Server 2012 R2
63
-
- Windows Server 2019
52
+
- Windows 10, version 1709 or later
64
53
- Windows Server 2022
54
+
- Windows Server 2019
55
+
- Windows Server 2016 running [Defender for Endpoint modern unified solution](/defender-endpoint/configure-server-endpoints) (requires installation through MSI)
56
+
- Windows Server 2012 R2 running [Defender for Endpoint modern unified solution](/defender-endpoint/configure-server-endpoints) (requires installation through MSI)
65
57
- macOS
66
58
- Linux
67
59
- iOS
68
60
- Android
69
61
70
-
### Windows Server 2016 and Windows Server 2012 R2 requirements
62
+
##Before you begin
71
63
72
-
Windows Server 2016 and Windows Server 2012 R2 must be onboarded using the instructions in [Onboard Windows servers](configure-server-endpoints.md#windows-server-2016-and-windows-server-2012-r2).
64
+
It's important to understand the following prerequisites prior to creating indicators for IPS, URLs, or domains.
73
65
74
66
### Microsoft Defender Antivirus version requirements
75
67
76
-
The _Antimalware client version_ must be 4.18.1906.x or later.
68
+
This feature is available if your organization uses [Microsoft Defender Antivirus](/defender-endpoint/microsoft-defender-antivirus-windows) (in active mode)
69
+
70
+
[Behavior Monitoring](/defender-endpoint/behavior-monitor) is enabled
71
+
72
+
[Cloud-based protection](/windows/security/threat-protection/microsoft-defender-antivirus/deploy-manage-report-microsoft-defender-antivirus) is turned on.
73
+
74
+
[Cloud Protection network connectivity](/defender-endpoint/configure-network-connections-microsoft-defender-antivirus) is functional
75
+
76
+
The antimalware client version must be `4.18.1906.x` or later. See [Monthly platform and engine versions](/defender-endpoint/microsoft-defender-antivirus-updates).
77
+
78
+
### Network Protection requirements
79
+
80
+
URL/IP allow and block requires that the Microsoft Defender for Endpoint component _Network Protection_ is enabled in **block mode**. For more information on Network Protection and configuration instructions, see [Enable network protection](enable-network-protection.md).
77
81
78
82
### Custom network indicators requirements
79
83
80
-
Ensure that **Custom network indicators**is enabled in **Microsoft Defender XDR**\>**Settings**\>**Advanced features**. For more information, see [Advanced features](advanced-features.md).
84
+
To start blocking IP addresses and/or URL's, turn on "**Custom network indicators"**feature in the [Microsoft Defender portal](https://security.microsoft.com), go to **Settings**> **Endpoints**> **General**> **Advanced features**. For more information, see [Advanced features](advanced-features.md).
81
85
82
86
For support of indicators on iOS, see [Microsoft Defender for Endpoint on iOS](ios-configure-features.md#configure-custom-indicators).
83
87
@@ -138,7 +142,7 @@ In the case where multiple different action types are set on the same indicator
138
142
2. Warn
139
143
3. Block
140
144
141
-
_Allow_ overrides _warn_ which overrides _block_: Allow > Warn > Block. Therefore, in the above example, Microsoft.com would be allowed.
145
+
_Allow_ overrides _warn_ which overrides _block_: Allow > Warn > Block. Therefore, in the above example, `Microsoft.com` would be allowed.
Copy file name to clipboardExpand all lines: defender-office-365/anti-spam-policies-asf-settings-about.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ ms.custom:
18
18
- seo-marvel-apr2020
19
19
description: Admins can learn about the Advanced Spam Filter (ASF) settings that are available in anti-spam policies in Exchange Online Protection (EOP).
- ✅ <a href="https://learn.microsoft.com/defender-office-365/mdo-about#defender-for-office-365-plan-1-vs-plan-2-cheat-sheet" target="_blank">Microsoft Defender for Office 365 Plan 1 and Plan 2</a>
@@ -73,7 +73,7 @@ The following **Increase spam score** ASF settings result in an increase in spam
73
73
|**Image links to remote websites** (_IncreaseScoreWithImageLinks_)|Messages that contain `<Img>` HTML tag links to remote sites (for example, using http) are marked as spam.|`X-CustomSpam: Image links to remote sites`|
74
74
|**Numeric IP address in URL** (_IncreaseScoreWithNumericIps_)|Messages that contain numeric-based URLs (typically, IP addresses) are marked as spam.|`X-CustomSpam: Numeric IP in URL`|
75
75
|**URL redirect to other port** (_IncreaseScoreWithRedirectToOtherPort_)|Messages that contain hyperlinks that redirect to TCP ports other than 80 (HTTP), 8080 (alternate HTTP), or 443 (HTTPS) are marked as spam.|`X-CustomSpam: URL redirect to other port`|
76
-
|**Links to .biz or .info websites** (_IncreaseScoreWithBizOrInfoUrls_)|Messages that contain `.biz` or `.info` links in the body of the message are marked as spam.|`X-CustomSpam: URL to .biz or .info websites`|
76
+
|**Links to .biz or .info websites** (_IncreaseScoreWithBizOrInfoUrls_)|Messages that contain `.biz` or `.info` links in the body of the message are marked as spam. <br/><br/> Note that URLs such as `contoso.info.com` (where `.biz` or `.info` is not the top-level domain) will also match. |`X-CustomSpam: URL to .biz or .info websites`|
0 commit comments