mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 10:53:43 +00:00
Merge branch 'master' into dansimp-metadata-biggerfix-ms.prod
This commit is contained in:
Daniel Simpson
GitHub
@ -15,7 +15,7 @@ manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 4/16/2017
|
||||
ms.date: 1/20/2021
|
||||
---
|
||||
|
||||
# Manage Windows Hello for Business in your organization
|
||||
@ -369,9 +369,11 @@ For more information about using the PIN recovery service for PIN reset see [Win
|
||||
|
||||
Windows Hello for Business is designed to be managed by Group Policy or MDM but not a combination of both. If policies are set from both sources it can result in a mixed result of what is actually enforced for a user or device.
|
||||
|
||||
Policies for Windows Hello for Business are enforced using the following hierarchy: User Group Policy > Computer Group Policy > User MDM > Device MDM > Device Lock policy. All PIN complexity policies are grouped together and enforced from a single policy source.
|
||||
Policies for Windows Hello for Business are enforced using the following hierarchy: User Group Policy > Computer Group Policy > User MDM > Device MDM > Device Lock policy.
|
||||
|
||||
Use a hardware security device and RequireSecurityDevice enforcement are also grouped together with PIN complexity policy. Conflict resolution for other Windows Hello for Business policies is enforced on a per policy basis.
|
||||
Feature enablement policy and certificate trust policy are grouped together and enforced from the same source (either GP or MDM), based on the rule above. The Use Passport for Work policy is used to determine the winning policy source.
|
||||
|
||||
All PIN complexity policies, are grouped separately from feature enablement and are enforced from a single policy source. Use a hardware security device and RequireSecurityDevice enforcement are also grouped together with PIN complexity policy. Conflict resolution for other Windows Hello for Business policies are enforced on a per policy basis.
|
||||
|
||||
>[!NOTE]
|
||||
> Windows Hello for Business policy conflict resolution logic does not respect the ControlPolicyConflict/MDMWinsOverGP policy in the Policy CSP.
|
||||
@ -382,8 +384,6 @@ Use a hardware security device and RequireSecurityDevice enforcement are also gr
|
||||
>
|
||||
>- Use Windows Hello for Business - Enabled
|
||||
>- User certificate for on-premises authentication - Enabled
|
||||
>- Require digits - Enabled
|
||||
>- Minimum PIN length - 6
|
||||
>
|
||||
>The following are configured using device MDM Policy:
|
||||
>
|
||||
@ -398,8 +398,10 @@ Use a hardware security device and RequireSecurityDevice enforcement are also gr
|
||||
>
|
||||
>- Use Windows Hello for Business - Enabled
|
||||
>- Use certificate for on-premises authentication - Enabled
|
||||
>- Require digits - Enabled
|
||||
>- Minimum PIN length - 6d
|
||||
>- MinimumPINLength - 8
|
||||
>- Digits - 1
|
||||
>- LowercaseLetters - 1
|
||||
>- SpecialCharacters - 1
|
||||
|
||||
## How to use Windows Hello for Business with Azure Active Directory
|
||||
|
||||
|
||||
@ -39,27 +39,36 @@ The following table summarizes what happens with Microsoft Defender Antivirus wh
|
||||
|
||||
| Windows version | Antimalware protection | Microsoft Defender for Endpoint enrollment | Microsoft Defender Antivirus state |
|
||||
|------|------|-------|-------|
|
||||
| Windows 10 | A third-party product that is not offered or developed by Microsoft | Yes | Passive mode |
|
||||
| Windows 10 | A third-party product that is not offered or developed by Microsoft | No | Automatic disabled mode |
|
||||
| Windows 10 | Microsoft Defender Antivirus | Yes | Active mode |
|
||||
| Windows 10 | Microsoft Defender Antivirus | No | Active mode |
|
||||
| Windows Server 2016 or 2019 | A third-party product that is not offered or developed by Microsoft | Yes | Active mode<sup>[[1](#fn1)]</sup> |
|
||||
| Windows Server 2016 or 2019 | A third-party product that is not offered or developed by Microsoft | No | Active mode<sup>[[1](#fn1)]<sup> |
|
||||
| Windows Server 2016 or 2019 | Microsoft Defender Antivirus | Yes | Active mode |
|
||||
| Windows Server 2016 or 2019 | Microsoft Defender Antivirus | No | Active mode |
|
||||
| Windows 10 | A third-party product that is not offered or developed by Microsoft | Yes | Passive mode |
|
||||
| Windows 10 | A third-party product that is not offered or developed by Microsoft | No | Automatic disabled mode |
|
||||
| Windows 10 | Microsoft Defender Antivirus | Yes | Active mode |
|
||||
| Windows 10 | Microsoft Defender Antivirus | No | Active mode |
|
||||
| Windows Server, version 1803 or newer, or Windows Server 2019 | A third-party product that is not offered or developed by Microsoft | Yes | Active mode<sup>[[1](#fn1)]</sup> |
|
||||
| Windows Server, version 1803 or newer, or Windows Server 2019 | A third-party product that is not offered or developed by Microsoft | No | Must be set to passive mode (manually)<sup>[[1](#fn1)]<sup> |
|
||||
| Windows Server, version 1803 or newer, or Windows Server 2019 | Microsoft Defender Antivirus | Yes | Active mode |
|
||||
| Windows Server, version 1803 or newer, or Windows Server 2019 | Microsoft Defender Antivirus | No | Active mode |
|
||||
| Windows Server 2016 | Microsoft Defender Antivirus | Yes | Active mode |
|
||||
| Windows Server 2016 | Microsoft Defender Antivirus | No | Active mode |
|
||||
| Windows Server 2016 | A third-party product that is not offered or developed by Microsoft | Yes | Must be disabled (manually)<sup>[[2](#fn2)]<sup> |
|
||||
| Windows Server 2016 | A third-party product that is not offered or developed by Microsoft | No | Must be disabled (manually)<sup>[[2](#fn2)]<sup> |
|
||||
|
||||
(<a id="fn1">1</a>) On Windows Server 2016 or 2019, Microsoft Defender Antivirus does not enter passive mode automatically when you install a non-Microsoft antivirus product. In those cases, [set Microsoft Defender Antivirus to passive mode](microsoft-defender-antivirus-on-windows-server-2016.md#need-to-set-microsoft-defender-antivirus-to-passive-mode) to prevent problems caused by having multiple antivirus products installed on a server.
|
||||
(<a id="fn1">1</a>) On Windows Server, version 1803 or newer, or Windows Server 2019, Microsoft Defender Antivirus does not enter passive mode automatically when you install a non-Microsoft antivirus product. In those cases, [set Microsoft Defender Antivirus to passive mode](microsoft-defender-antivirus-on-windows-server-2016.md#need-to-set-microsoft-defender-antivirus-to-passive-mode) to prevent problems caused by having multiple antivirus products installed on a server.
|
||||
|
||||
If you are using Windows Server, version 1803 or Windows Server 2019, you set Microsoft Defender Antivirus to passive mode by setting this registry key:
|
||||
If you are using Windows Server, version 1803 or newer, or Windows Server 2019, you can set Microsoft Defender Antivirus to passive mode by setting the following registry key:
|
||||
- Path: `HKLM\SOFTWARE\Policies\Microsoft\Windows Advanced Threat Protection`
|
||||
- Name: `ForceDefenderPassiveMode`
|
||||
- Type: `REG_DWORD`
|
||||
- Value: `1`
|
||||
|
||||
See [Microsoft Defender Antivirus on Windows Server 2016 and 2019](microsoft-defender-antivirus-on-windows-server-2016.md) for key differences and management options for Windows Server installations.
|
||||
> [!NOTE]
|
||||
> The `ForceDefenderPassiveMode` registry key is not supported on Windows Server 2016.
|
||||
|
||||
(<a id="fn2">2</a>) On Windows Server 2016, Microsoft Defender Antivirus does not enter passive mode automatically when you install a non-Microsoft antivirus product. In addition, Microsoft Defender Antivirus is not supported in passive mode. In those cases, [disable/uninstall Microsoft Defender Antivirus manually](microsoft-defender-antivirus-on-windows-server-2016.md#are-you-using-windows-server-2016) to prevent problems caused by having multiple antivirus products installed on a server.
|
||||
|
||||
See [Microsoft Defender Antivirus on Windows Server](microsoft-defender-antivirus-on-windows-server-2016.md) for key differences and management options for Windows Server installations.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Microsoft Defender Antivirus is only available on endpoints running Windows 10, Windows Server 2016, and Windows Server 2019.
|
||||
> Microsoft Defender Antivirus is only available on devices running Windows 10, Windows Server 2016, Windows Server, version 1803 or later, and Windows Server 2019.
|
||||
>
|
||||
> In Windows 8.1 and Windows Server 2012, enterprise-level endpoint antivirus protection is offered as [System Center Endpoint Protection](https://technet.microsoft.com/library/hh508760.aspx), which is managed through Microsoft Endpoint Configuration Manager.
|
||||
>
|
||||
@ -82,7 +91,7 @@ The table in this section summarizes the functionality and features that are ava
|
||||
- In Active mode, Microsoft Defender Antivirus is used as the antivirus app on the machine. All configuration made with Configuration Manager, Group Policy, Intune, or other management products will apply. Files are scanned and threats remediated, and detection information are reported in your configuration tool (such as Configuration Manager or the Microsoft Defender Antivirus app on the machine itself).
|
||||
- In Passive mode, Microsoft Defender Antivirus is not used as the antivirus app, and threats are not remediated by Microsoft Defender Antivirus. Files are scanned and reports are provided for threat detections that are shared with the Microsoft Defender for Endpoint service. Therefore, you might encounter alerts in the Security Center console with Microsoft Defender Antivirus as a source, even when Microsoft Defender Antivirus is in Passive mode.
|
||||
- When [EDR in block mode](../microsoft-defender-atp/edr-in-block-mode.md) is turned on and Microsoft Defender Antivirus is not the primary antivirus solution, it can still detect and remediate malicious items.
|
||||
- When disabled, Microsoft Defender Antivirus is not used as the antivirus app. Files are not scanned and threats are not remediated. Disabling/uninstalling Microsoft Defender Antivirus is not recommended.
|
||||
- When disabled, Microsoft Defender Antivirus is not used as the antivirus app. Files are not scanned and threats are not remediated. Disabling/uninstalling Microsoft Defender Antivirus is not recommended in general; if possible, keep Microsoft Defender Antivirus in passive mode if you are using a non-Microsoft antimalware/antivirus solution.
|
||||
|
||||
## Keep the following points in mind
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Microsoft Defender Antivirus on Windows Server 2016 and 2019
|
||||
title: Microsoft Defender Antivirus on Windows Server
|
||||
description: Learn how to enable and configure Microsoft Defender Antivirus on Windows Server 2016 and Windows Server 2019.
|
||||
keywords: windows defender, server, scep, system center endpoint protection, server 2016, current branch, server 2012
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
@ -10,13 +10,13 @@ ms.sitesec: library
|
||||
ms.localizationpriority: medium
|
||||
author: denisebmsft
|
||||
ms.author: deniseb
|
||||
ms.date: 01/04/2021
|
||||
ms.date: 01/21/2021
|
||||
ms.reviewer: pahuijbr, shwjha
|
||||
manager: dansimp
|
||||
ms.technology: mde
|
||||
---
|
||||
|
||||
# Microsoft Defender Antivirus on Windows Server 2016 and Windows Server 2019
|
||||
# Microsoft Defender Antivirus on Windows Server
|
||||
|
||||
[!INCLUDE [Microsoft 365 Defender rebranding](../../includes/microsoft-defender.md)]
|
||||
|
||||
@ -24,9 +24,12 @@ ms.technology: mde
|
||||
|
||||
- [Microsoft Defender for Endpoint](https://go.microsoft.com/fwlink/p/?linkid=2146631)
|
||||
|
||||
Microsoft Defender Antivirus is available on Windows Server 2016 and 2019. In some instances, Microsoft Defender Antivirus is referred to as *Endpoint Protection*; however, the protection engine is the same.
|
||||
Microsoft Defender Antivirus is available on the following editions/versions of Windows Server:
|
||||
- Windows Server 2019
|
||||
- Windows Server, version 1803 or later
|
||||
- Windows Server 2016.
|
||||
|
||||
While the functionality, configuration, and management are largely the same for [Microsoft Defender Antivirus on Windows 10](microsoft-defender-antivirus-in-windows-10.md), there are a few key differences on Windows Server 2016 and 2019:
|
||||
In some instances, Microsoft Defender Antivirus is referred to as *Endpoint Protection*; however, the protection engine is the same. Although the functionality, configuration, and management are largely the same for [Microsoft Defender Antivirus on Windows 10](microsoft-defender-antivirus-in-windows-10.md), there are a few key differences on Windows Server:
|
||||
|
||||
- In Windows Server, [automatic exclusions](configure-server-exclusions-microsoft-defender-antivirus.md) are applied based on your defined Server Role.
|
||||
- In Windows Server, Microsoft Defender Antivirus does not automatically disable itself if you are running another antivirus product.
|
||||
@ -35,29 +38,29 @@ While the functionality, configuration, and management are largely the same for
|
||||
|
||||
The process of setting up and running Microsoft Defender Antivirus on a server platform includes several steps:
|
||||
|
||||
1. [Enable the interface](#enable-the-user-interface-on-windows-server-2016-or-2019).
|
||||
2. [Install Microsoft Defender Antivirus](#install-microsoft-defender-antivirus-on-windows-server-2016-or-2019).
|
||||
1. [Enable the interface](#enable-the-user-interface-on-windows-server).
|
||||
2. [Install Microsoft Defender Antivirus](#install-microsoft-defender-antivirus-on-windows-server).
|
||||
3. [Verify Microsoft Defender Antivirus is running](#verify-microsoft-defender-antivirus-is-running).
|
||||
4. [Update your antimalware Security intelligence](#update-antimalware-security-intelligence).
|
||||
5. (As needed) [Submit samples](#submit-samples).
|
||||
6. (As needed) [Configure automatic exclusions](#configure-automatic-exclusions).
|
||||
7. (Only if necessary) [Set Microsoft Defender Antivirus to passive mode](#need-to-set-microsoft-defender-antivirus-to-passive-mode).
|
||||
|
||||
## Enable the user interface on Windows Server 2016 or 2019
|
||||
## Enable the user interface on Windows Server
|
||||
|
||||
By default, Microsoft Defender Antivirus is installed and functional on Windows Server 2016 and 2019. The user interface (GUI) is installed by default on some SKUs, but is not required because you can use PowerShell or other methods to manage Microsoft Defender Antivirus. And if the GUI is not installed on your server, you can add it by using the Add Roles and Features Wizard or by using PowerShell.
|
||||
By default, Microsoft Defender Antivirus is installed and functional on Windows Server. The user interface (GUI) is installed by default on some SKUs, but is not required because you can use PowerShell or other methods to manage Microsoft Defender Antivirus. If the GUI is not installed on your server, you can add it by using the **Add Roles and Features** wizard, or by using PowerShell cmdlets.
|
||||
|
||||
### Turn on the GUI using the Add Roles and Features Wizard
|
||||
|
||||
1. Refer to [this article](https://docs.microsoft.com/windows-server/administration/server-manager/install-or-uninstall-roles-role-services-or-features#install-roles-role-services-and-features-by-using-the-add-roles-and-features-wizard), and use the **Add Roles and Features Wizard**.
|
||||
1. See [Install roles, role services, and features by using the add Roles and Features Wizard](https://docs.microsoft.com/windows-server/administration/server-manager/install-or-uninstall-roles-role-services-or-features#install-roles-role-services-and-features-by-using-the-add-roles-and-features-wizard), and use the **Add Roles and Features Wizard**.
|
||||
|
||||
2. When you get to the **Features** step of the wizard, under **Windows Defender Features**, select the **GUI for Windows Defender** option.
|
||||
|
||||
In Windows Server 2016, the **Add Roles and Features Wizard** looks like this:
|
||||
In Windows Server 2016, the **Add Roles and Features Wizard** looks like this:
|
||||
|
||||
|
||||
|
||||
|
||||
In Windows Server 2019, the **Add Roles and Feature Wizard** looks much the same.
|
||||
In Windows Server 2019, the **Add Roles and Feature Wizard** is similar.
|
||||
|
||||
### Turn on the GUI using PowerShell
|
||||
|
||||
@ -67,7 +70,7 @@ The following PowerShell cmdlet will enable the interface:
|
||||
Install-WindowsFeature -Name Windows-Defender-GUI
|
||||
```
|
||||
|
||||
## Install Microsoft Defender Antivirus on Windows Server 2016 or 2019
|
||||
## Install Microsoft Defender Antivirus on Windows Server
|
||||
|
||||
You can use either the **Add Roles and Features Wizard** or PowerShell to install Microsoft Defender Antivirus.
|
||||
|
||||
@ -112,7 +115,7 @@ The `sc query` command returns information about the Microsoft Defender Antiviru
|
||||
|
||||
## Update antimalware Security intelligence
|
||||
|
||||
In order to get updated antimalware Security intelligence, you must have the Windows Update service running. If you use an update management service, like Windows Server Update Services (WSUS), make sure that updates for Microsoft Defender Antivirus Security intelligence are approved for the computers you manage.
|
||||
To get updated antimalware security intelligence, you must have the Windows Update service running. If you use an update management service, like Windows Server Update Services (WSUS), make sure that updates for Microsoft Defender Antivirus Security intelligence are approved for the computers you manage.
|
||||
|
||||
By default, Windows Update does not download and install updates automatically on Windows Server 2019 or Windows Server 2016. You can change this configuration by using one of the following methods:
|
||||
|
||||
@ -196,10 +199,22 @@ To turn off the Microsoft Defender Antivirus GUI, use the following PowerShell c
|
||||
Uninstall-WindowsFeature -Name Windows-Defender-GUI
|
||||
```
|
||||
|
||||
### Are you using Windows Server 2016?
|
||||
|
||||
If you are using Windows Server 2016 and a third-party antimalware/antivirus product that is not offered or developed by Microsoft, you'll need to disable/uninstall Microsoft Defender Antivirus.
|
||||
|
||||
> [!NOTE]
|
||||
> You can't uninstall the Windows Security app, but you can disable the interface with these instructions.
|
||||
|
||||
The following PowerShell cmdlet uninstalls Microsoft Defender Antivirus on Windows Server 2016:
|
||||
|
||||
```PowerShell
|
||||
Uninstall-WindowsFeature -Name Windows-Defender
|
||||
```
|
||||
|
||||
## See also
|
||||
|
||||
- [Microsoft Defender Antivirus in Windows 10](microsoft-defender-antivirus-in-windows-10.md)
|
||||
|
||||
- [Configure exclusions in Microsoft Defender AV on Windows Server](configure-server-exclusions-microsoft-defender-antivirus.md)
|
||||
- [Microsoft Defender Antivirus compatibility](microsoft-defender-antivirus-compatibility.md)
|
||||
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: denisebmsft
|
||||
ms.author: deniseb
|
||||
ms.date: 11/03/2020
|
||||
ms.date: 01/21/2021
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.custom: asr
|
||||
@ -147,7 +147,7 @@ There is a known issue such that if you change the Exploit Protection settings f
|
||||
|
||||
ICS is enabled by default in Windows, and ICS must be enabled in order for Application Guard to function correctly. We do not recommend disabling ICS; however, you can disable ICS in part by using a Group Policy and editing registry keys.
|
||||
|
||||
1. In the Group Policy setting called, *Prohibit use of Internet Connection Sharing on your DNS domain network*, set it to **Disabled**.
|
||||
1. In the Group Policy setting, **Prohibit use of Internet Connection Sharing on your DNS domain network**, set it to **Disabled**.
|
||||
|
||||
2. Disable IpNat.sys from ICS load as follows: <br/>
|
||||
`System\CurrentControlSet\Services\SharedAccess\Parameters\DisableIpNat = 1`
|
||||
@ -160,6 +160,28 @@ ICS is enabled by default in Windows, and ICS must be enabled in order for Appli
|
||||
|
||||
5. Reboot the device.
|
||||
|
||||
### Why doesn't the container fully load when device control policies are enabled?
|
||||
Allow-listed items must be configured as "allowed" in the Group Policy Object ensure AppGuard works properly.
|
||||
|
||||
Policy: Allow installation of devices that match any of these device IDs
|
||||
- `SCSI\DiskMsft____Virtual_Disk____`
|
||||
- `{8e7bd593-6e6c-4c52-86a6-77175494dd8e}\msvhdhba`
|
||||
- `VMS_VSF`
|
||||
- `root\Vpcivsp`
|
||||
- `root\VMBus`
|
||||
- `vms_mp`
|
||||
- `VMS_VSP`
|
||||
- `ROOT\VKRNLINTVSP`
|
||||
- `ROOT\VID`
|
||||
- `root\storvsp`
|
||||
- `vms_vsmp`
|
||||
- `VMS_PP`
|
||||
|
||||
Policy: Allow installation of devices using drivers that match these device setup classes
|
||||
- `{71a27cdd-812a-11d0-bec7-08002be2092f}`
|
||||
|
||||
|
||||
|
||||
## See also
|
||||
|
||||
[Configure Microsoft Defender Application Guard policy settings](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-application-guard/configure-md-app-guard)
|
||||
@ -14,8 +14,8 @@ ms.author: deniseb
|
||||
ms.reviewer: sugamar, jcedola
|
||||
manager: dansimp
|
||||
ms.custom: asr
|
||||
ms.date: 01/08/2021
|
||||
ms.technology: mde
|
||||
|
||||
---
|
||||
|
||||
# Use attack surface reduction rules to prevent malware infection
|
||||
@ -25,7 +25,7 @@ ms.technology: mde
|
||||
|
||||
**Applies to:**
|
||||
|
||||
* [Microsoft Defender for Endpoint](https://go.microsoft.com/fwlink/p/?linkid=2146631)
|
||||
- [Microsoft Defender for Endpoint](https://go.microsoft.com/fwlink/p/?linkid=2146631)
|
||||
|
||||
## Why attack surface reduction rules are important
|
||||
|
||||
@ -65,7 +65,9 @@ Warn mode is supported on devices running the following versions of Windows:
|
||||
- [Windows 10, version 1809](https://docs.microsoft.com/windows/whats-new/whats-new-windows-10-version-1809) or later
|
||||
- [Windows Server, version 1809](https://docs.microsoft.com/windows-server/get-started/whats-new-in-windows-server-1809) or later
|
||||
|
||||
In addition, make sure [Microsoft Defender Antivirus and antimalware updates](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus#monthly-platform-and-engine-versions) are installed
|
||||
Microsoft Defender Antivirus must be running with real-time protection in [Active mode](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-antivirus/microsoft-defender-antivirus-compatibility#functionality-and-features-available-in-each-state).
|
||||
|
||||
In addition, make sure [Microsoft Defender Antivirus and antimalware updates](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus#monthly-platform-and-engine-versions) are installed.
|
||||
- Minimum platform release requirement: `4.18.2008.9`
|
||||
- Minimum engine release requirement: `1.1.17400.5`
|
||||
|
||||
@ -125,13 +127,9 @@ DeviceEvents
|
||||
You can review the Windows event log to view events generated by attack surface reduction rules:
|
||||
|
||||
1. Download the [Evaluation Package](https://aka.ms/mp7z2w) and extract the file *cfa-events.xml* to an easily accessible location on the device.
|
||||
|
||||
2. Enter the words, *Event Viewer*, into the Start menu to open the Windows Event Viewer.
|
||||
|
||||
3. Under **Actions**, select **Import custom view...**.
|
||||
|
||||
4. Select the file *cfa-events.xml* from where it was extracted. Alternatively, [copy the XML directly](event-views.md).
|
||||
|
||||
5. Select **OK**.
|
||||
|
||||
You can create a custom view that filters events to only show the following events, all of which are related to controlled folder access:
|
||||
@ -464,9 +462,6 @@ GUID: `c1db55ab-c21a-4637-bb3f-a12568109d35`
|
||||
## See also
|
||||
|
||||
- [Attack surface reduction FAQ](attack-surface-reduction-faq.md)
|
||||
|
||||
- [Enable attack surface reduction rules](enable-attack-surface-reduction.md)
|
||||
|
||||
- [Evaluate attack surface reduction rules](evaluate-attack-surface-reduction.md)
|
||||
|
||||
- [Compatibility of Microsoft Defender Antivirus with other antivirus/antimalware solutions](../microsoft-defender-antivirus/microsoft-defender-antivirus-compatibility.md)
|
||||
|
||||
@ -47,13 +47,13 @@ You can also set mitigations to [audit mode](evaluate-exploit-protection.md). Au
|
||||
|
||||
## Windows Security app
|
||||
|
||||
1. Open the Windows Security app by clicking the shield icon in the task bar or searching the start menu for **Security**.
|
||||
1. Open the Windows Security app by selecting the shield icon in the task bar or by searching the start menu for **Security**.
|
||||
|
||||
2. Click the **App & browser control** tile (or the app icon on the left menu bar) and then click **Exploit protection settings**.
|
||||
2. Select the **App & browser control** tile (or the app icon on the left menu bar) and then select **Exploit protection settings**.
|
||||
|
||||
3. Go to **Program settings** and choose the app you want to apply mitigations to. <br/>
|
||||
- If the app you want to configure is already listed, click it and then click **Edit**.
|
||||
- If the app is not listed, at the top of the list click **Add program to customize** and then choose how you want to add the app. <br/>
|
||||
- If the app you want to configure is already listed, select it, and then select **Edit**.
|
||||
- If the app is not listed, at the top of the list select **Add program to customize** and then choose how you want to add the app. <br/>
|
||||
- Use **Add by program name** to have the mitigation applied to any running process with that name. You must specify a file with an extension. You can enter a full path to limit the mitigation to only the app with that name in that location.
|
||||
- Use **Choose exact file path** to use a standard Windows Explorer file picker window to find and select the file you want.
|
||||
|
||||
@ -61,12 +61,12 @@ You can also set mitigations to [audit mode](evaluate-exploit-protection.md). Au
|
||||
|
||||
5. Repeat steps 3-4 for all the apps and mitigations you want to configure.
|
||||
|
||||
6. Under the **System settings** section, find the mitigation you want to configure and select one of the following. Apps that aren't configured individually in the **Program settings** section will use the settings configured here:<br/>
|
||||
6. Under the **System settings** section, find the mitigation you want to configure and then specify one of the following settings. Apps that aren't configured individually in the **Program settings** section use the settings that are configured here.<br/>
|
||||
- **On by default**: The mitigation is *enabled* for apps that don't have this mitigation set in the app-specific **Program settings** section
|
||||
- **Off by default**: The mitigation is *disabled* for apps that don't have this mitigation set in the app-specific **Program settings** section
|
||||
- **Use default**: The mitigation is either enabled or disabled, depending on the default configuration that is set up by Windows 10 installation; the default value (**On** or **Off**) is always specified next to the **Use default** label for each mitigation
|
||||
|
||||
7. Repeat step 6 for all the system-level mitigations you want to configure. Click **Apply** when you're done setting up your configuration.
|
||||
7. Repeat step 6 for all the system-level mitigations you want to configure. Select **Apply** when you're done setting up your configuration.
|
||||
|
||||
If you add an app to the **Program settings** section and configure individual mitigation settings there, they will be honored above the configuration for the same mitigations specified in the **System settings** section. The following matrix and examples help to illustrate how defaults work:
|
||||
|
||||
@ -81,7 +81,7 @@ If you add an app to the **Program settings** section and configure individual m
|
||||
|
||||
Mikael adds the app *test.exe* to the **Program settings** section. In the options for that app, under **Data Execution Prevention (DEP)**, Mikael enables the **Override system settings** option and sets the switch to **On**. There are no other apps listed in the **Program settings** section.
|
||||
|
||||
The result will be that DEP only will be enabled for *test.exe*. All other apps will not have DEP applied.
|
||||
The result is that DEP is enabled only for *test.exe*. All other apps will not have DEP applied.
|
||||
|
||||
### Example 2: Josie configures Data Execution Prevention in system settings to be off by default
|
||||
|
||||
@ -89,66 +89,84 @@ Josie adds the app *test.exe* to the **Program settings** section. In the option
|
||||
|
||||
Josie also adds the app *miles.exe* to the **Program settings** section and configures **Control flow guard (CFG)** to **On**. Josie doesn't enable the **Override system settings** option for DEP or any other mitigations for that app.
|
||||
|
||||
The result will be that DEP will be enabled for *test.exe*. DEP will not be enabled for any other app, including *miles.exe*. CFG will be enabled for *miles.exe*.
|
||||
The result is that DEP is enabled for *test.exe*. DEP will not be enabled for any other app, including *miles.exe*. CFG will be enabled for *miles.exe*.
|
||||
|
||||
1. Open the Windows Security app by clicking the shield icon in the task bar or searching the start menu for **Defender**.
|
||||
1. Open the Windows Security app by selecting the shield icon in the task bar or searching the start menu for **Defender**.
|
||||
|
||||
2. Click the **App & browser control** tile (or the app icon on the left menu bar) and then click **Exploit protection**.
|
||||
2. Select the **App & browser control** tile (or the app icon on the left menu bar) and then select **Exploit protection**.
|
||||
|
||||
3. Go to **Program settings** and choose the app you want to apply mitigations to.<br/>
|
||||
- If the app you want to configure is already listed, click it and then click **Edit**.
|
||||
- If the app is not listed, at the top of the list click **Add program to customize** and then choose how you want to add the app.<br/>
|
||||
- If the app you want to configure is already listed, select it, and then select **Edit**.
|
||||
- If the app is not listed, at the top of the list select **Add program to customize** and then choose how you want to add the app.<br/>
|
||||
- Use **Add by program name** to have the mitigation applied to any running process with that name. You must specify a file with an extension. You can enter a full path to limit the mitigation to only the app with that name in that location.
|
||||
- Use **Choose exact file path** to use a standard Windows Explorer file picker window to find and select the file you want.
|
||||
|
||||
4. After selecting the app, you'll see a list of all the mitigations that can be applied. Choosing **Audit** will apply the mitigation in audit mode only. You will be notified if you need to restart the process or app, or if you need to restart Windows.
|
||||
|
||||
5. Repeat steps 3-4 for all the apps and mitigations you want to configure. Click **Apply** when you're done setting up your configuration.
|
||||
5. Repeat steps 3-4 for all the apps and mitigations you want to configure. Select **Apply** when you're done setting up your configuration.
|
||||
|
||||
## Intune
|
||||
|
||||
1. Sign in to the [Azure portal](https://portal.azure.com) and open Intune.
|
||||
|
||||
2. Click **Device configuration** > **Profiles** > **Create profile**.
|
||||
2. Go to **Device configuration** > **Profiles** > **Create profile**.
|
||||
|
||||
3. Name the profile, choose **Windows 10 and later** and **Endpoint protection**.
|
||||
|
||||
3. Name the profile, choose **Windows 10 and later** and **Endpoint protection**.<br/>
|
||||
<br/>
|
||||
|
||||
4. Click **Configure** > **Windows Defender Exploit Guard** > **Exploit protection**.
|
||||
4. Select **Configure** > **Windows Defender Exploit Guard** > **Exploit protection**.
|
||||
|
||||
5. Upload an [XML file](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-exploitguard) with the exploit protection settings:<br/><br/>
|
||||
5. Upload an [XML file](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-exploitguard) with the exploit protection settings:
|
||||
|
||||
6. Click **OK** to save each open blade and click **Create**.
|
||||
<br/>
|
||||
|
||||
7. Click the profile **Assignments**, assign to **All Users & All Devices**, and click **Save**.
|
||||
6. Select **OK** to save each open blade, and then choose **Create**.
|
||||
|
||||
7. Select the profile **Assignments** tab, assign the policy to **All Users & All Devices**, and then select **Save**.
|
||||
|
||||
## MDM
|
||||
|
||||
Use the [./Vendor/MSFT/Policy/Config/ExploitGuard/ExploitProtectionSettings](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-exploitguard) configuration service provider (CSP) to enable or disable exploit protection mitigations or to use audit mode.
|
||||
|
||||
## Microsoft Endpoint Manager
|
||||
|
||||
1. In Microsoft Endpoint Manager, go to **Endpoint Security** > **Attack surface reduction**.
|
||||
|
||||
2. Select **Create Policy** > **Platform**, and for **Profile**, choose **Exploit Protection**. Then select **Create**.
|
||||
|
||||
3. Specify a name and a description, and then choose **Next**.
|
||||
|
||||
4. Select **Select XML File** and browse to the location of the exploit protection XML file. Select the file, and then choose **Next**.
|
||||
|
||||
5. Configure **Scope tags** and **Assignments** if necessary.
|
||||
|
||||
6. Under **Review + create**, review the configuration and then choose **Create**.
|
||||
|
||||
|
||||
## Microsoft Endpoint Configuration Manager
|
||||
|
||||
1. In Microsoft Endpoint Configuration Manager, click **Assets and Compliance** > **Endpoint Protection** > **Windows Defender Exploit Guard**.
|
||||
1. In Microsoft Endpoint Configuration Manager, go to **Assets and Compliance** > **Endpoint Protection** > **Windows Defender Exploit Guard**.
|
||||
|
||||
2. Click **Home** > **Create Exploit Guard Policy**.
|
||||
2. Select **Home** > **Create Exploit Guard Policy**.
|
||||
|
||||
3. Enter a name and a description, click **Exploit protection**, and click **Next**.
|
||||
3. Specify a name and a description, select **Exploit protection**, and then choose **Next**.
|
||||
|
||||
4. Browse to the location of the exploit protection XML file and click **Next**.
|
||||
4. Browse to the location of the exploit protection XML file and select **Next**.
|
||||
|
||||
5. Review the settings and click **Next** to create the policy.
|
||||
5. Review the settings, and then choose **Next** to create the policy.
|
||||
|
||||
6. After the policy is created, click **Close**.
|
||||
6. After the policy is created, select **Close**.
|
||||
|
||||
## Group Policy
|
||||
|
||||
1. On your Group Policy management device, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**.
|
||||
|
||||
2. In the **Group Policy Management Editor** go to **Computer configuration** and click **Administrative templates**.
|
||||
2. In the **Group Policy Management Editor** go to **Computer configuration** and select **Administrative templates**.
|
||||
|
||||
3. Expand the tree to **Windows components** > **Windows Defender Exploit Guard** > **Exploit Protection** > **Use a common set of exploit protection settings**.
|
||||
|
||||
4. Click **Enabled** and type the location of the [XML file](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-exploitguard) and click **OK**.
|
||||
4. Select **Enabled** and type the location of the [XML file](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-exploitguard), and then choose **OK**.
|
||||
|
||||
## PowerShell
|
||||
|
||||
@ -208,41 +226,41 @@ This table lists the individual **Mitigations** (and **Audits**, when available)
|
||||
|
||||
| Mitigation type | Applies to | Mitigation cmdlet parameter keyword | Audit mode cmdlet parameter |
|
||||
| :-------------- | :--------- | :---------------------------------- | :-------------------------- |
|
||||
| Control flow guard (CFG) | System and app-level | CFG, StrictCFG, SuppressExports | Audit not available |
|
||||
| Data Execution Prevention (DEP) | System and app-level | DEP, EmulateAtlThunks | Audit not available |
|
||||
| Force randomization for images (Mandatory ASLR) | System and app-level | ForceRelocateImages | Audit not available |
|
||||
| Randomize memory allocations (Bottom-Up ASLR) | System and app-level | BottomUp, HighEntropy | Audit not available
|
||||
| Validate exception chains (SEHOP) | System and app-level | SEHOP, SEHOPTelemetry | Audit not available |
|
||||
| Validate heap integrity | System and app-level | TerminateOnError | Audit not available |
|
||||
| Arbitrary code guard (ACG) | App-level only | DynamicCode | AuditDynamicCode |
|
||||
| Block low integrity images | App-level only | BlockLowLabel | AuditImageLoad |
|
||||
| Block remote images | App-level only | BlockRemoteImages | Audit not available |
|
||||
| Block untrusted fonts | App-level only | DisableNonSystemFonts | AuditFont, FontAuditOnly |
|
||||
| Code integrity guard | App-level only | BlockNonMicrosoftSigned, AllowStoreSigned | AuditMicrosoftSigned, AuditStoreSigned |
|
||||
| Disable extension points | App-level only | ExtensionPoint | Audit not available |
|
||||
| Disable Win32k system calls | App-level only | DisableWin32kSystemCalls | AuditSystemCall |
|
||||
| Do not allow child processes | App-level only | DisallowChildProcessCreation | AuditChildProcess |
|
||||
| Export address filtering (EAF) | App-level only | EnableExportAddressFilterPlus, EnableExportAddressFilter <a href="#r1" id="t1">\[1\]</a> | Audit not available<a href="#r2" id="t2">\[2\]</a> |
|
||||
| Import address filtering (IAF) | App-level only | EnableImportAddressFilter | Audit not available<a href="#r2" id="t2">\[2\]</a> |
|
||||
| Simulate execution (SimExec) | App-level only | EnableRopSimExec | Audit not available<a href="#r2" id="t2">\[2\]</a> |
|
||||
| Validate API invocation (CallerCheck) | App-level only | EnableRopCallerCheck | Audit not available<a href="#r2" id="t2">\[2\]</a> |
|
||||
| Validate handle usage | App-level only | StrictHandle | Audit not available |
|
||||
| Validate image dependency integrity | App-level only | EnforceModuleDepencySigning | Audit not available |
|
||||
| Validate stack integrity (StackPivot) | App-level only | EnableRopStackPivot | Audit not available<a href="#r2" id="t2">\[2\]</a> |
|
||||
| Control flow guard (CFG) | System and app-level | `CFG`, `StrictCFG`, `SuppressExports` | Audit not available |
|
||||
| Data Execution Prevention (DEP) | System and app-level | `DEP`, `EmulateAtlThunks` | Audit not available |
|
||||
| Force randomization for images (Mandatory ASLR) | System and app-level | `ForceRelocateImages` | Audit not available |
|
||||
| Randomize memory allocations (Bottom-Up ASLR) | System and app-level | `BottomUp`, `HighEntropy` | Audit not available
|
||||
| Validate exception chains (SEHOP) | System and app-level | `SEHOP`, `SEHOPTelemetry` | Audit not available |
|
||||
| Validate heap integrity | System and app-level | `TerminateOnError` | Audit not available |
|
||||
| Arbitrary code guard (ACG) | App-level only | `DynamicCode` | `AuditDynamicCode` |
|
||||
| Block low integrity images | App-level only | `BlockLowLabel` | `AuditImageLoad` |
|
||||
| Block remote images | App-level only | `BlockRemoteImages` | Audit not available |
|
||||
| Block untrusted fonts | App-level only | `DisableNonSystemFonts` | `AuditFont`, `FontAuditOnly` |
|
||||
| Code integrity guard | App-level only | `BlockNonMicrosoftSigned`, `AllowStoreSigned` | AuditMicrosoftSigned, AuditStoreSigned |
|
||||
| Disable extension points | App-level only | `ExtensionPoint` | Audit not available |
|
||||
| Disable Win32k system calls | App-level only | `DisableWin32kSystemCalls` | `AuditSystemCall` |
|
||||
| Do not allow child processes | App-level only | `DisallowChildProcessCreation` | `AuditChildProcess` |
|
||||
| Export address filtering (EAF) | App-level only | `EnableExportAddressFilterPlus`, `EnableExportAddressFilter` <a href="#r1" id="t1">\[1\]</a> | Audit not available<a href="#r2" id="t2">\[2\]</a> |
|
||||
| Import address filtering (IAF) | App-level only | `EnableImportAddressFilter` | Audit not available<a href="#r2" id="t2">\[2\]</a> |
|
||||
| Simulate execution (SimExec) | App-level only | `EnableRopSimExec` | Audit not available<a href="#r2" id="t2">\[2\]</a> |
|
||||
| Validate API invocation (CallerCheck) | App-level only | `EnableRopCallerCheck` | Audit not available<a href="#r2" id="t2">\[2\]</a> |
|
||||
| Validate handle usage | App-level only | `StrictHandle` | Audit not available |
|
||||
| Validate image dependency integrity | App-level only | `EnforceModuleDepencySigning` | Audit not available |
|
||||
| Validate stack integrity (StackPivot) | App-level only | `EnableRopStackPivot` | Audit not available<a href="#r2" id="t2">\[2\]</a> |
|
||||
|
||||
<a href="#t1" id="r1">\[1\]</a>: Use the following format to enable EAF modules for DLLs for a process:
|
||||
|
||||
```PowerShell
|
||||
Set-ProcessMitigation -Name processName.exe -Enable EnableExportAddressFilterPlus -EAFModules dllName1.dll,dllName2.dll
|
||||
```
|
||||
<a href="#t2" id="r2">\[2\]</a>: Audit for this mitigation is not available via Powershell cmdlets.
|
||||
<a href="#t2" id="r2">\[2\]</a>: Audit for this mitigation is not available via PowerShell cmdlets.
|
||||
|
||||
## Customize the notification
|
||||
|
||||
See the [Windows Security](../windows-defender-security-center/windows-defender-security-center.md#customize-notifications-from-the-windows-defender-security-center) topic for more information about customizing the notification when a rule is triggered and blocks an app or file.
|
||||
See the [Windows Security](../windows-defender-security-center/windows-defender-security-center.md#customize-notifications-from-the-windows-defender-security-center) article for more information about customizing the notification when a rule is triggered and blocks an app or file.
|
||||
|
||||
## See also
|
||||
|
||||
* [Evaluate exploit protection](evaluate-exploit-protection.md)
|
||||
* [Configure and audit exploit protection mitigations](customize-exploit-protection.md)
|
||||
* [Import, export, and deploy exploit protection configurations](import-export-exploit-protection-emet-xml.md)
|
||||
- [Evaluate exploit protection](evaluate-exploit-protection.md)
|
||||
- [Configure and audit exploit protection mitigations](customize-exploit-protection.md)
|
||||
- [Import, export, and deploy exploit protection configurations](import-export-exploit-protection-emet-xml.md)
|
||||
|
||||
@ -158,7 +158,7 @@ $version = undef
|
||||
}
|
||||
|
||||
file { '/etc/opt/microsoft/mdatp/mdatp_onboard.json':
|
||||
source => 'puppet:///modules/mdatp/mdatp_onboard.json',
|
||||
source => 'puppet:///modules/install_mdatp/mdatp_onboard.json',
|
||||
owner => root,
|
||||
group => root,
|
||||
mode => '0600',
|
||||
|
||||
@ -201,7 +201,7 @@ Type of threat for which the behavior is configured.
|
||||
Action to take when coming across a threat of the type specified in the preceding section. Can be:
|
||||
|
||||
- **Audit**: The device is not protected against this type of threat, but an entry about the threat is logged.
|
||||
- **Block**: The device is protected against this type of threat and you are notified in the user interface and the security console.
|
||||
- **Block**: The device is protected against this type of threat and you are notified in the security console.
|
||||
- **Off**: The device is not protected against this type of threat and nothing is logged.
|
||||
|
||||
|||
|
||||
|
||||
Reference in New Issue
Block a user