mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 22:07:22 +00:00
edits
This commit is contained in:
parent
63a6304b41
commit
a52a78eda2
@ -151,8 +151,11 @@ It's important to understand the following prerequisites prior to creating indic
|
|||||||
|
|
||||||
You can create indicators for certificates. Some common use cases include:
|
You can create indicators for certificates. Some common use cases include:
|
||||||
|
|
||||||
- Deploying blocking technologies, such as [attack surface reduction rules](attack-surface-reduction.md) but allow behaviors from signed applications using certificate whitelisting.
|
- 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 using the adding the certificate in the allow list.
|
||||||
- Blocking the use of a specific signed application across your organization. Using the certificate 'block' indicator, Windows Defender AV will prevent file executions (block and remediate) and the Automated Investigation and Remediation behave the same.
|
- 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.
|
||||||
|
-
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Before you begin
|
### Before you begin
|
||||||
|
|
||||||
@ -160,9 +163,8 @@ It's important to understand the following requirements prior to creating indica
|
|||||||
|
|
||||||
- This feature is available if your organization uses Windows Defender Antivirus and Cloud–based protection is enabled. For more information, see [Manage cloud–based protection](../windows-defender-antivirus/deploy-manage-report-windows-defender-antivirus.md).
|
- This feature is available if your organization uses Windows Defender Antivirus and Cloud–based protection is enabled. For more information, see [Manage cloud–based protection](../windows-defender-antivirus/deploy-manage-report-windows-defender-antivirus.md).
|
||||||
- Supported on machines on Windows 10, version 1703 or later.
|
- Supported on machines on Windows 10, version 1703 or later.
|
||||||
- The Antimalware client version must be or later.
|
- The Antimalware client version must be 4.18.1901.x or later.
|
||||||
- The Engine version must be x or later.
|
- The virus and threat protection definitions must be up-to-date.
|
||||||
- This feature currently supports entering … or …
|
|
||||||
|
|
||||||
>[!IMPORTANT]
|
>[!IMPORTANT]
|
||||||
> - 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').
|
> - 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').
|
||||||
|
Loading…
x
Reference in New Issue
Block a user