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/defender-endpoint-false-positives-negatives.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -212,9 +212,11 @@ To define exclusions across Microsoft Defender for Endpoint, perform the followi
212
212
213
213
- [Create "allow" indicators for Microsoft Defender for Endpoint](#indicators-for-defender-for-endpoint)
214
214
- [Define exclusions for Microsoft Defender Antivirus](#exclusions-for-microsoft-defender-antivirus)
215
+
- For Attack Surface Reduction Rule exclusions [Configure attack surface reduction per-rule exclusions](/defender-endpoint/attack-surface-reduction-rules-deployment-test#configure-attack-surface-reduction-per-rule-exclusions) or you can leverage [ASR rule only exclusions](/defender-endpoint/enable-attack-surface-reduction#exclude-files-and-folders-from-attack-surface-reduction-rules)
215
216
216
217
> [!NOTE]
217
218
> Microsoft Defender Antivirus exclusions apply only to antivirus protection, not across other Microsoft Defender for Endpoint capabilities. To exclude files broadly, use [custom indicators](indicators-overview.md) for Microsoft Defender for Endpoint and exclusions for Microsoft Defender Antivirus.
219
+
> ASR Rules can leverage ASR Rule Exclusions - where the exclusions apply to all ASR Rules; ASR per Rule Exclusions; Defender AV exclusions; as well as allow indicators defined in Custom Indicators.
218
220
219
221
The procedures in this section describe how to define indicators and exclusions.
Copy file name to clipboardExpand all lines: defender-endpoint/evaluate-mdav-using-gp.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -180,13 +180,13 @@ Disable local administrator AV settings such as exclusions, and enforce the poli
180
180
| --- | --- |
181
181
| Prevent users and apps from accessing dangerous websites | Enabled, Block |
182
182
| This settings controls whether Network Protection is allowed to be configured into block or audit mode on Windows Server | Enabled |
183
-
| Allow Network Protection Down Level | Network protection is enabled downlevel |
184
-
| Allow Datagram Processing On Win Server | Datagram processing on Windows Server is enabled |
185
-
| Disable DNS over TCP parsing | DNS over TCP parsing is enabled |
186
-
|Disable HTTP parsing | HTTP parsing is enabled|
187
-
|Disable SSH parsing | SSH parsing is enabled|
188
-
|Disable TLS parsing | TLS parsing is enabled|
189
-
|Enable DNS Sinkhole | DNS Sinkhole is enabled |
183
+
184
+
To enable Network Protection for Windows Servers, for now, please use Powershell:
185
+
186
+
|OS | Powershell cmdlet|
187
+
|--- | ---|
188
+
|Windows Server 2012 R2Windows Server 2022 and later | set-MpPreference -AllowNetworkProtectionOnWinServer $true|
189
+
| Windows Server 2016 and Windows Server 2012 R2 [unified MDE client](/defender-endpoint/update-agent-mma-windows#upgrade-to-the-new-unified-agent-for-defender-for-endpoint) | set-MpPreference -AllowNetworkProtectionOnWinServer $true and set-MpPreference -AllowNetworkProtectionDownLevel $true
190
190
191
191
## Attack Surface Reduction Rules
192
192
@@ -207,7 +207,7 @@ Disable local administrator AV settings such as exclusions, and enforce the poli
207
207
| c0033c00-d16d-4114-a5a0-dc9b3a7d2ceb<br><br>**Note:** ( \[PREVIEW\] Block use of copied or impersonated system tools) | 1 (Block) |
208
208
| d3e037e1-3eb8-44c8-a917-57927947596d<br><br>**Note:** (Block JavaScript or VBScript from launching downloaded executable content) | 1 (Block) |
209
209
| 9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2<br><br>**Note:** (Block credential stealing from the Windows local security authority subsystem) | 1 (Block) |
Copy file name to clipboardExpand all lines: defender-endpoint/indicator-certificates.md
+15-13Lines changed: 15 additions & 13 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: asr
17
17
search.appverid: met150
18
-
ms.date: 07/31/2024
18
+
ms.date: 01/23/2025
19
19
---
20
20
21
21
# Create indicators based on certificates
@@ -33,28 +33,28 @@ ms.date: 07/31/2024
33
33
34
34
You can create indicators for certificates. Some common use cases include:
35
35
36
-
- Scenarios when you need to deploy blocking technologies, such as [attack surface reduction rules](attack-surface-reduction.md) but need to allow behaviors from signed applications by adding the certificate in the allow list.
37
-
- Blocking the use of a specific signed application across your organization. By creating an indicator to block the certificate of the application, Windows Defender AV will prevent file executions (block and remediate) and the Automated Investigation and Remediation behave the same.
36
+
- Scenarios when you need to deploy blocking technologies, such as [attack surface reduction rules](attack-surface-reduction.md) but need to allow behaviors from signed applications by adding the certificate in the allowlist.
37
+
- Blocking the use of a specific signed application across your organization. By creating an indicator to block the certificate of the application, Microsoft Defender Antivirus prevents file executions (block and remediate), and automated investigation and remediation behaves the same.
38
38
39
39
## Before you begin
40
40
41
-
It's important to understand the following requirements prior to creating indicators for certificates:
41
+
It's important to understand the following requirements before creating indicators for certificates:
42
42
43
-
- This feature is available if your organization uses Microsoft Defender Antivirus and Cloud-based protection is enabled. For more information, see [Manage cloud-based protection](/windows/security/threat-protection/microsoft-defender-antivirus/deploy-manage-report-microsoft-defender-antivirus).
44
-
- The Antimalware client version must be 4.18.1901.x or later.
43
+
- This feature is available if your organization uses Microsoft Defender Antivirus (in active mode) and cloud-based protection is enabled. For more information, see [Manage cloud-based protection](/windows/security/threat-protection/microsoft-defender-antivirus/deploy-manage-report-microsoft-defender-antivirus).
44
+
- The anti-malware client version must be `4.18.1901.x` or later.
45
45
- Supported on machines on Windows 10, version 1703 or later, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, and Windows Server 2022.
46
46
47
47
> [!NOTE]
48
-
> Windows Server 2016 and Windows Server 2012 R2 will need to be onboarded using the instructions in [Onboard Windows servers](configure-server-endpoints.md#windows-server-2016-and-windows-server-2012-r2) for this feature to work.
48
+
> 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) for this feature to work.
49
49
50
50
- The virus and threat protection definitions must be up to date.
51
51
- This feature currently supports entering .CER or .PEM file extensions.
52
52
53
53
> [!IMPORTANT]
54
54
>
55
55
> - A valid leaf certificate is a signing certificate that has a valid certification path and must be chained to the Root Certificate Authority (CA) trusted by Microsoft. Alternatively, a custom (self-signed) certificate can be used as long as it's trusted by the client (Root CA certificate is installed under the Local Machine 'Trusted Root Certification Authorities').
56
-
> - The children or parent of the allow/block certificate IOCs are not included in the allow/block IoC functionality, only leaf certificates are supported.
57
-
> - Microsoft signed certificates cannot be blocked.
56
+
> - The children or parent of the allow/block certificate IOCs aren't included in the allow/block IoC functionality, only leaf certificates are supported.
57
+
> - Microsoft signed certificates can't be blocked.
58
58
59
59
## Create an indicator for certificates from the settings page:
60
60
@@ -66,11 +66,12 @@ It's important to understand the following requirements prior to creating indica
66
66
2. Select **Add indicator**.
67
67
68
68
3. Specify the following details:
69
-
- Indicator - Specify the entity details and define the expiration of the indicator.
70
-
- Action - Specify the action to be taken and provide a description.
71
-
- Scope - Define the scope of the machine group.
72
69
73
-
4. Review the details in the Summary tab, then click **Save**.
70
+
-**Indicator**: Specify the entity details and define the expiration of the indicator.
71
+
-**Action**: Specify the action to be taken and provide a description.
72
+
-**Scope**: Define the scope of the machine group.
73
+
74
+
4. Review the details on the **Summary** tab, and then select **Save**.
74
75
75
76
## Related articles
76
77
@@ -79,4 +80,5 @@ It's important to understand the following requirements prior to creating indica
79
80
-[Create indicators for IPs and URLs/domains](indicator-ip-domain.md)
80
81
-[Manage indicators](indicator-manage.md)
81
82
-[Exclusions for Microsoft Defender for Endpoint and Microsoft Defender Antivirus](defender-endpoint-antivirus-exclusions.md)
83
+
82
84
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]
0 commit comments