mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-23 14:23:38 +00:00
Merge branch 'master' of https://cpubwin.visualstudio.com/_git/it-client into vsts17425031
This commit is contained in:
Justin Hall
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: high
|
||||
author: brianlic-msft
|
||||
ms.date: 10/27/2017
|
||||
ms.date: 05/16/2018
|
||||
---
|
||||
|
||||
# TPM recommendations
|
||||
@ -102,7 +102,9 @@ The following table defines which Windows features require TPM support.
|
||||
| Measured Boot | Yes | Yes | Yes | Measured Boot requires TPM 1.2 or 2.0 and UEFI Secure Boot |
|
||||
| BitLocker | Yes | Yes | Yes | TPM 1.2 or 2.0 is required |
|
||||
| Device Encryption | Yes | N/A | Yes | Device Encryption requires Modern Standby/Connected Standby certification, which requires TPM 2.0. |
|
||||
| Device Guard | No | Yes | Yes | |
|
||||
| Windows Defender Application Control (Device Guard) | No | Yes | Yes | |
|
||||
| Windows Defender Exploit Guard | Yes | Yes | Yes | |
|
||||
| Windows Defender System Guard | Yes | Yes | Yes | |
|
||||
| Credential Guard | No | Yes | Yes | Windows 10, version 1507 (End of Life as of May 2017) only supported TPM 2.0 for Credential Guard. Beginning with Windows 10, version 1511, TPM 1.2 and 2.0 are supported. |
|
||||
| Device Health Attestation| Yes | Yes | Yes | |
|
||||
| Windows Hello/Windows Hello for Business| No | Yes | Yes | Azure AD join supports both versions of TPM, but requires TPM with keyed-hash message authentication code (HMAC) and Endorsement Key (EK) certificate for key attestation support. |
|
||||
|
||||
@ -25,7 +25,7 @@ On-premises deployments must use the On-premises Azure MFA Server using the AD F
|
||||
|
||||
## Prerequisites
|
||||
|
||||
The Azure MFA Server and User Portal servers have several perquisites and must have connectivity to the Internet.
|
||||
The Azure MFA Server and User Portal servers have several prerequisites and must have connectivity to the Internet.
|
||||
|
||||
### Primary MFA Server
|
||||
|
||||
@ -540,4 +540,4 @@ The Multi-Factor Authentication server communicates with the Azure MFA cloud ser
|
||||
2. [Validate and Configure Public Key Infrastructure](hello-cert-trust-validate-pki.md)
|
||||
3. [Prepare and Deploy Windows Server 2016 Active Directory Federation Services](hello-cert-trust-adfs.md)
|
||||
4. [Validate and Deploy Multifactor Authentication Services (MFA)](hello-cert-trust-validate-deploy-mfa.md)
|
||||
5. [Configure Windows Hello for Business Policy settings](hello-cert-trust-policy-settings.md)
|
||||
5. [Configure Windows Hello for Business Policy settings](hello-cert-trust-policy-settings.md)
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 81 KiB |
@ -6,9 +6,10 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, networking
|
||||
author: jdeckerms
|
||||
author: shortpatti
|
||||
ms.author: pashort
|
||||
ms.localizationpriority: high
|
||||
ms.date: 07/27/2017
|
||||
ms.date: 05/17/2018
|
||||
---
|
||||
|
||||
# VPN profile options
|
||||
@ -37,10 +38,10 @@ The following table lists the VPN settings and whether the setting can be config
|
||||
| Name resolution: persistent | no |
|
||||
| Auto-trigger: app trigger | yes |
|
||||
| Auto-trigger: name trigger | yes |
|
||||
| Auto-trigger: Always On | no |
|
||||
| Auto-trigger: Always On | yes |
|
||||
| Auto-trigger: trusted network detection | no |
|
||||
| LockDown | no |
|
||||
| Windows Information Protection (WIP) | no |
|
||||
| Windows Information Protection (WIP) | yes |
|
||||
| Traffic filters | yes |
|
||||
|
||||
The ProfileXML node was added to the VPNv2 CSP to allow users to deploy VPN profile as a single blob. This is particularly useful for deploying profiles with features that are not yet supported by MDMs. You can get additional examples in the [ProfileXML XSD](https://msdn.microsoft.com/library/windows/hardware/mt755930.aspx) topic.
|
||||
@ -296,9 +297,30 @@ The following is a sample plug-in VPN profile. This blob would fall under the Pr
|
||||
|
||||
After you configure the settings that you want using ProfileXML, you can apply it using Intune and a **Custom Configuration (Windows 10 Desktop and Mobile and later)** policy.
|
||||
|
||||
The OMS-URI setting to apply ProfileXML is **./user/vendor/MSFT/*VPN profile name*/ProfileXML**.
|
||||
1. Sign into the [Azure portal](https://portal.azure.com).
|
||||
2. Click **Intune** > **Device Configuration** > **Profiles**.
|
||||
3. Click **Create Profile**.
|
||||
4. Enter a name and (optionally) a description.
|
||||
5. Choose **Windows 10 and later** as the platform.
|
||||
6. Choose **Custom** as the profile type.
|
||||
7. Click **Add**.
|
||||
8. Configure the custom setting:
|
||||
|
||||
a. Enter a name and (optionally) a description.
|
||||
|
||||
b. Enter the OMA-URI: **./user/vendor/MSFT/_VPN profile name_/ProfileXML**.
|
||||
|
||||
c. Set Data type to **String (XML file)**.
|
||||
|
||||
d. Upload the file with the profile XML.
|
||||
|
||||
e. Click **OK**.
|
||||
|
||||
|
||||
|
||||
9. Click **OK**, then click **Create**.
|
||||
10. Assign the profile.
|
||||
|
||||
|
||||
|
||||
## Learn more
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 04/30/2018
|
||||
ms.date: 05/17/2018
|
||||
---
|
||||
|
||||
# Configure exclusions in Windows Defender AV on Windows Server
|
||||
@ -55,6 +55,9 @@ In Windows Server 2016 the predefined exclusions delivered by definition updates
|
||||
> [!WARNING]
|
||||
> Opting out of automatic exclusions may adversely impact performance, or result in data corruption. The exclusions that are delivered automatically are optimized for Windows Server 2016 roles.
|
||||
|
||||
> [!NOTE]
|
||||
> This setting is only supported on Windows Server 2016. While this setting exists in Windows 10, it doesn't have an effect on exclusions.
|
||||
|
||||
You can disable the auto-exclusions lists with Group Policy, PowerShell cmdlets, and WMI.
|
||||
|
||||
**Use Group Policy to disable the auto-exclusions list on Windows Server 2016:**
|
||||
@ -89,9 +92,6 @@ See the following for more information and allowed parameters:
|
||||
- [Windows Defender WMIv2 APIs](https://msdn.microsoft.com/en-us/library/dn439477(v=vs.85).aspx)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## List of automatic exclusions
|
||||
The following sections contain the exclusions that are delivered with automatic exclusions file paths and file types.
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 04/30/2018
|
||||
ms.date: 05/17/2018
|
||||
---
|
||||
|
||||
# Deploy, manage, and report on Windows Defender Antivirus
|
||||
@ -47,7 +47,7 @@ PowerShell|Deploy with Group Policy, System Center Configuration Manager, or man
|
||||
Group Policy and Active Directory (domain-joined)|Use a Group Policy Object to deploy configuration changes and ensure Windows Defender Antivirus is enabled.|Use Group Policy Objects (GPOs) to [Configure update options for Windows Defender Antivirus][] and [Configure Windows Defender features][]|Endpoint reporting is not available with Group Policy. You can generate a list of [Group Policies to determine if any settings or policies are not applied][]
|
||||
Microsoft Azure|Deploy Microsoft Antimalware for Azure in the [Azure portal, by using Visual Studio virtual machine configuration, or using Azure PowerShell cmdlets](https://docs.microsoft.com/en-us/azure/security/azure-security-antimalware#antimalware-deployment-scenarios). You can also [Install Endpoint protection in Azure Security Center](https://docs.microsoft.com/en-us/azure/security-center/security-center-install-endpoint-protection)|Configure [Microsoft Antimalware for Virtual Machines and Cloud Services with Azure PowerShell cmdlets](https://docs.microsoft.com/en-us/powershell/servicemanagement/azure.antimalware/v3.4.0/azure.antimalware) or [use code samples](https://gallery.technet.microsoft.com/Antimalware-For-Azure-5ce70efe)|Use [Microsoft Antimalware for Virtual Machines and Cloud Services with Azure PowerShell cmdlets](https://docs.microsoft.com/en-us/powershell/servicemanagement/azure.antimalware/v3.4.0/azure.antimalware) to enable monitoring. You can also review usage reports in Azure Active Directory to determine suspicious activity, including the [Possibly infected devices][] report and configure an SIEM tool to report on [Windows Defender Antivirus events][] and add that tool as an app in AAD.
|
||||
|
||||
1. <span id="fn1" />The availability of some functions and features, especially related to cloud-delivered protection, differ between System Center Configuration Manager, current branch (for example, System Center Configuration Manager 2016) and System Center Configuration Manager 2012. In this library, we've focused on Windows 10, Windows Server 2016, and System Center Configuration Manager, current branch (2016). See the [Utilize Microsoft cloud-provided protection in Windows Defender Antivirus](utilize-microsoft-cloud-protection-windows-defender-antivirus.md) topic for a table that describes the major differences. [(Return to table)](#ref2)
|
||||
1. <span id="fn1" />The availability of some functions and features, especially related to cloud-delivered protection, differ between System Center Configuration Manager 2016 and System Center Configuration Manager 2012. In this library, we've focused on Windows 10, Windows Server 2016, and System Center Configuration Manager 2016. See [Use Microsoft cloud-provided protection in Windows Defender Antivirus](utilize-microsoft-cloud-protection-windows-defender-antivirus.md) for a table that describes the major differences. [(Return to table)](#ref2)
|
||||
|
||||
2. <span id="fn2" />In Windows 10, Windows Defender Antivirus is a component available without installation or deployment of an additional client or service. It will automatically be enabled when third-party antivirus products are either uninstalled or out of date ([except on Windows Server 2016](windows-defender-antivirus-on-windows-server-2016.md)). Traditional deployment therefore is not required. Deployment here refers to ensuring the Windows Defender Antivirus component is available and enabled on endpoints or servers. [(Return to table)](#ref2)
|
||||
|
||||
|
||||
@ -67,8 +67,7 @@ Feature | Windows 8.1 (Group Policy) | Windows 10, version 1607 (Group Policy) |
|
||||
---|---|---|---|---|---|---
|
||||
Cloud-protection service label | Microsoft Advanced Protection Service | Microsoft Advanced Protection Service | Cloud-based Protection | NA | Cloud protection service | Microsoft Advanced Protection Service
|
||||
Reporting level (MAPS membership level) | Basic, Advanced | Advanced | Advanced | Dependent on Windows version | Dependent on Windows version | Dependent on Windows version
|
||||
Block at first sight availability | No | Yes | Yes | Not configurable | Configurable | No
|
||||
Cloud block timeout period | No | No | Configurable | Not configurable | Configurable | No
|
||||
Cloud block timeout period | No | No | Configurable | Not configurable | Configurable | Configurable
|
||||
|
||||
You can also [configure Windows Defender AV to automatically receive new protection updates based on reports from our cloud service](manage-event-based-updates-windows-defender-antivirus.md#cloud-report-updates).
|
||||
|
||||
@ -81,4 +80,4 @@ You can also [configure Windows Defender AV to automatically receive new protect
|
||||
[Specify the cloud-delivered protection level](specify-cloud-protection-level-windows-defender-antivirus.md) | You can specify the level of protection offered by the cloud with Group Policy and System Center Configuration Manager. The protection level will affect the amount of information shared with the cloud and how aggressively new files are blocked.
|
||||
[Configure and validate network connections for Windows Defender Antivirus](configure-network-connections-windows-defender-antivirus.md) | There are certain Microsoft URLs that your network and endpoints must be able to connect to for cloud-delivered protection to work effectively. This topic lists the URLs that should be allowed via firewall or network filtering rules, and instructions for confirming your network is properly enrolled in cloud-delivered protection.
|
||||
[Configure the Block at First Sight feature](configure-block-at-first-sight-windows-defender-antivirus.md) | The Block at First Sight feature can block new malware within seconds, without having to wait hours for a traditional signature. You can enable and configure it with System Center Configuration Manager and Group Policy.
|
||||
[Configure the cloud block timeout period](configure-cloud-block-timeout-period-windows-defender-antivirus.md) | Windows Defender Antivirus can block suspicious files from running while it queries our cloud-delivered protection service. You can configure the amount of time the file will be prevented from running with System Center Configuration Manager and Group Policy.
|
||||
[Configure the cloud block timeout period](configure-cloud-block-timeout-period-windows-defender-antivirus.md) | Windows Defender Antivirus can block suspicious files from running while it queries our cloud-delivered protection service. You can configure the amount of time the file will be prevented from running with System Center Configuration Manager and Group Policy.
|
||||
|
||||
@ -11,14 +11,15 @@
|
||||
|
||||
## [Windows Defender Application Control deployment guide](windows-defender-application-control-deployment-guide.md)
|
||||
### [Types of devices](types-of-devices.md)
|
||||
### [Use WDAC with a managed installer](use-windows-defender-application-control-with-managed-installer.md)
|
||||
###Use WDAC with custom policies
|
||||
#### [Create an initial default policy](create-initial-default-policy.md)
|
||||
#### [Microsoft recommended block rules](microsoft-recommended-block-rules.md)
|
||||
### [Audit WDAC policies](audit-windows-defender-application-control-policies.md)
|
||||
### [Merge WDAC policies](merge-windows-defender-application-control-policies.md)
|
||||
### [Enforce WDAC policies](enforce-windows-defender-application-control-policies.md)
|
||||
### [Deploy WDAC policies](deploy-windows-defender-application-control-policies-using-group-policy.md)
|
||||
### [Deploy WDAC with a managed installer](use-windows-defender-application-control-with-managed-installer.md)
|
||||
### [Deploy WDAC policies using Group Policy](deploy-windows-defender-application-control-policies-using-group-policy.md)
|
||||
### [Deploy WDAC policies using Intune](deploy-windows-defender-application-control-policies-using-intune.md)
|
||||
### [Use code signing to simplify application control for classic Windows applications](use-code-signing-to-simplify-application-control-for-classic-windows-applications.md)
|
||||
#### [Optional: Use the Device Guard Signing Portal in the Microsoft Store for Business](use-device-guard-signing-portal-in-microsoft-store-for-business.md)
|
||||
#### [Optional: Create a code signing cert for WDAC](create-code-signing-cert-for-windows-defender-application-control.md)
|
||||
|
||||
@ -0,0 +1,33 @@
|
||||
---
|
||||
title: Deploy Windows Defender Application Control (WDAC) policies by using Microsoft Intune (Windows 10)
|
||||
description: Windows Defender Application Control restricts which applications users are allowed to run and the code that runs in the system core.
|
||||
ms.assetid: 8d6e0474-c475-411b-b095-1c61adb2bdbb
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: justinha
|
||||
ms.date: 05/17/2018
|
||||
---
|
||||
|
||||
# Deploy Windows Defender Application Control policies by using Microsoft Intune
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows Server 2016
|
||||
|
||||
You can use Microsoft Intune to configure Windows Defender Application Control (WDAC). You can configure Windows 10 client computers to only run Windows components and Microsoft Store apps, or let them also run reputable apps defined by the Intelligent Security Graph.
|
||||
|
||||
1. Open the Microsoft Intune portal and click **Device configuration** > **Profiles** > **Creae profile**.
|
||||
|
||||
3. Type a name for the new profile, select **Windows 10 and later** as the **Platform** and **Endpoint protection** as the **Profile type**.
|
||||
|
||||
|
||||
|
||||
4. Click **Configure** > **Windows Defender Application Control**. for the following settings and then click **OK**:
|
||||
|
||||
- **Application control code intergity policies**: Select **Audit only** to log events but not block any apps from running or select **Enforce** to allow only Windows components and Store apps to run.
|
||||
- **Trust apps with good reputation**: Select **Enable** to allow reputable apps as defined by the Intelligent Security Graph to run in addition to Windows components and Store apps.
|
||||
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 90 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 74 KiB |
@ -79,30 +79,30 @@ Microsoft recommends that you block the following Microsoft-signed applications
|
||||
|
||||
```
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
- <SiPolicy xmlns="urn:schemas-microsoft-com:sipolicy">
|
||||
<SiPolicy xmlns="urn:schemas-microsoft-com:sipolicy">
|
||||
<VersionEx>10.0.0.0</VersionEx>
|
||||
<PolicyTypeID>{A244370E-44C9-4C06-B551-F6016E563076}</PolicyTypeID>
|
||||
<PlatformID>{2E07F7E4-194C-4D20-B7C9-6F44A6C5A234}</PlatformID>
|
||||
- <Rules>
|
||||
- <Rule>
|
||||
<Rules>
|
||||
<Rule>
|
||||
<Option>Enabled:Unsigned System Integrity Policy</Option>
|
||||
</Rule>
|
||||
- <Rule>
|
||||
<Rule>
|
||||
<Option>Enabled:Audit Mode</Option>
|
||||
</Rule>
|
||||
- <Rule>
|
||||
<Rule>
|
||||
<Option>Enabled:Advanced Boot Options Menu</Option>
|
||||
</Rule>
|
||||
- <Rule>
|
||||
<Rule>
|
||||
<Option>Enabled:UMCI</Option>
|
||||
</Rule>
|
||||
</Rules>
|
||||
- <!-- EKUS
|
||||
<!-- EKUS
|
||||
-->
|
||||
<EKUs />
|
||||
- <!-- File Rules
|
||||
<!-- File Rules
|
||||
-->
|
||||
- <FileRules>
|
||||
<FileRules>
|
||||
<Deny ID="ID_DENY_BGINFO" FriendlyName="bginfo.exe" FileName="BGINFO.Exe" MinimumFileVersion="4.21.0.0"/>
|
||||
<Deny ID="ID_DENY_CBD" FriendlyName="cdb.exe" FileName="CDB.Exe" MinimumFileVersion="65535.65535.65535.65535"/>
|
||||
<Deny ID="ID_DENY_KD" FriendlyName="kd.exe" FileName="kd.Exe" MinimumFileVersion="65535.65535.65535.65535"/>
|
||||
@ -159,7 +159,7 @@ Microsoft recommends that you block the following Microsoft-signed applications
|
||||
<Deny ID="ID_DENY_D_24" FriendlyName="Powershell 24" Hash="F16E605B55774CDFFDB0EB99FAFF43A40622ED2AB1C011D1195878F4B20030BC"/>
|
||||
<Deny ID="ID_DENY_D_25" FriendlyName="Powershell 25" Hash="F29A958287788A6EEDE6035D49EF5CB85EEC40D214FDDE5A0C6CAA65AFC00EEC"/>
|
||||
<Deny ID="ID_DENY_D_26" FriendlyName="Powershell 26" Hash="F875E43E12685ECE0BA2D42D55A13798CE9F1FFDE3CAE253D2529F4304811A52"/>
|
||||
- <!-- System.Management.Automation.dll
|
||||
<!-- System.Management.Automation.dll
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_27" FriendlyName="PowerShell 27" Hash="720D826A84284E18E0003526A0CD9B7FF0C4A98A"/>
|
||||
<Deny ID="ID_DENY_D_28" FriendlyName="PowerShell 28" Hash="CB5DF9D0D25571948C3D257882E07C7FA5E768448E0DEBF637E110F9FF575808"/>
|
||||
@ -383,103 +383,103 @@ Microsoft recommends that you block the following Microsoft-signed applications
|
||||
<Deny ID="ID_DENY_D_246" FriendlyName="PowerShell 246" Hash="0C4688AACD02829850DE0F792AC06D3C87895412A910EA76F7F9BF31B3B4A3E9"/>
|
||||
<Deny ID="ID_DENY_D_247" FriendlyName="PowerShell 247" Hash="6DC048AFA50B5B1B0AD7DD3125AC83D46FED730A"/>
|
||||
<Deny ID="ID_DENY_D_248" FriendlyName="PowerShell 248" Hash="432F666CCE8CD222484E263AE02F63E0038143DD6AD07B3EB1633CD3C498C13D"/>
|
||||
- <!-- pubprn.vbs
|
||||
<!-- pubprn.vbs
|
||||
-->
|
||||
- <!-- rs2 x86fre
|
||||
<!-- rs2 x86fre
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_249" FriendlyName="PubPrn 249" Hash="68E96BE23748AA680D5E1E557778901F332ED5D3"/>
|
||||
<Deny ID="ID_DENY_D_250" FriendlyName="PubPrn 250" Hash="8FA30B5931806565C2058E565C06AD5F1C5A48CDBE609975EB31207C25214063"/>
|
||||
- <!-- rs2 amd64fre
|
||||
<!-- rs2 amd64fre
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_251" FriendlyName="PubPrn 251" Hash="32C4B29FE428B1DF473F3F4FECF519D285E93521"/>
|
||||
<Deny ID="ID_DENY_D_252" FriendlyName="PubPrn 252" Hash="D44FB563198D60DFDC91608949FE2FADAD6161854D084EB1968C558AA36513C7"/>
|
||||
- <!-- rs2 amd64chk
|
||||
<!-- rs2 amd64chk
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_253" FriendlyName="PubPrn 253" Hash="9EDBEF086D350863F29175F5AB5178B88B142C75"/>
|
||||
<Deny ID="ID_DENY_D_254" FriendlyName="PubPrn 254" Hash="9B22C98351F2B6DEDDCED0D805C65F5B166FF519A8DF41EB242CB909471892EB"/>
|
||||
- <!-- rs2 x86chk
|
||||
<!-- rs2 x86chk
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_255" FriendlyName="PubPrn 255" Hash="8A3B30F345C43246B3500721CFEEADBAC6B9D9C6"/>
|
||||
<Deny ID="ID_DENY_D_256" FriendlyName="PubPrn 256" Hash="37C20BF20A2BBACE50957F8D0AB3FD16174BC005E79D47E51E899AFD9E4B7724"/>
|
||||
- <!-- rs2 woafre
|
||||
<!-- rs2 woafre
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_257" FriendlyName="PubPrn 257" Hash="C659DAD2B37375781E2D584E16AAE2A10B5A1156"/>
|
||||
<Deny ID="ID_DENY_D_258" FriendlyName="PubPRn 258" Hash="EBDACA86F10AC0446D60CC75628EC7A370B1E2236E6D20F22372F91033B6D429"/>
|
||||
- <!-- rs3 amd64chk
|
||||
<!-- rs3 amd64chk
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_259" FriendlyName="PubPrn 259" Hash="C9D6394BBFF8CD9C6590F08C54EC6AFDEB5CFFB4"/>
|
||||
<Deny ID="ID_DENY_D_260" FriendlyName="PubPrn 260" Hash="518E4EA7A2B70713E1AEC6E7E75A488C39384B625C5F2779073E9294CBF2BD9F"/>
|
||||
- <!-- rs3 amd64fre
|
||||
<!-- rs3 amd64fre
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_261" FriendlyName="PubPrn 261" Hash="C9D6394BBFF8CD9C6590F08C54EC6AFDEB5CFFB4"/>
|
||||
<Deny ID="ID_DENY_D_262" FriendlyName="PubPrn 262" Hash="518E4EA7A2B70713E1AEC6E7E75A488C39384B625C5F2779073E9294CBF2BD9F"/>
|
||||
- <!-- rs3 arm64chk
|
||||
<!-- rs3 arm64chk
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_263" FriendlyName="PubPrn 263" Hash="763A652217A1E30F2D288B7F44E08346949A02CD"/>
|
||||
<Deny ID="ID_DENY_D_264" FriendlyName="PubPrn 264" Hash="FCDDA212B06602F642B29FC05316EF75E4EE9975E6E8A9526E842BE2EA237C5D"/>
|
||||
- <!-- rs3 arm64fre
|
||||
<!-- rs3 arm64fre
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_265" FriendlyName="PubPrn 265" Hash="763A652217A1E30F2D288B7F44E08346949A02CD"/>
|
||||
<Deny ID="ID_DENY_D_266" FriendlyName="PubPrn 266" Hash="FCDDA212B06602F642B29FC05316EF75E4EE9975E6E8A9526E842BE2EA237C5D"/>
|
||||
- <!-- rs3 woachk
|
||||
<!-- rs3 woachk
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_267" FriendlyName="PubPrn 267" Hash="60FD28D770B23A0477679311D247DA4D5C61074C"/>
|
||||
<Deny ID="ID_DENY_D_268" FriendlyName="PubPrn 268" Hash="D09A4B2EA611CDFDC6DCA44314289B622B2A5EDA09716EF4A16B91EC90BFBA8F"/>
|
||||
- <!-- rs3 woafre
|
||||
<!-- rs3 woafre
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_269" FriendlyName="PubPrn 269" Hash="60FD28D770B23A0477679311D247DA4D5C61074C"/>
|
||||
<Deny ID="ID_DENY_D_270" FriendlyName="PubPrn 270" Hash="D09A4B2EA611CDFDC6DCA44314289B622B2A5EDA09716EF4A16B91EC90BFBA8F"/>
|
||||
- <!-- rs3 x86chk
|
||||
<!-- rs3 x86chk
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_271" FriendlyName="PubPrn 271" Hash="47CBE201ED224BF3F5C322F7A49EF64469AF2E1A"/>
|
||||
<Deny ID="ID_DENY_D_272" FriendlyName="PubPrn 272" Hash="24855B9CC420719D5AB93F4F1589CE09E4063E4FC98681BD91A1D18A3C8ACB43"/>
|
||||
- <!-- rs3 x86fre
|
||||
<!-- rs3 x86fre
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_273" FriendlyName="PubPrn 273" Hash="47CBE201ED224BF3F5C322F7A49EF64469AF2E1A"/>
|
||||
<Deny ID="ID_DENY_D_274" FriendlyName="PubPrn 274" Hash="24855B9CC420719D5AB93F4F1589CE09E4063E4FC98681BD91A1D18A3C8ACB43"/>
|
||||
- <!-- rs3 sxs amd64
|
||||
<!-- rs3 sxs amd64
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_275" FriendlyName="PubPrn 275" Hash="663D8E25BAE20510A882F6692BE2620FBABFB94E"/>
|
||||
<Deny ID="ID_DENY_D_276" FriendlyName="PubPrn 276" Hash="649A9E5A4867A28C7D0934793F33B545F9441EA23872715C84826D80CC8EC576"/>
|
||||
- <!-- rs3 sxs arm64
|
||||
<!-- rs3 sxs arm64
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_277" FriendlyName="PubPrn 277" Hash="226ABB2FBAEFC5A7E2A819D9D708F826C00FD215"/>
|
||||
<Deny ID="ID_DENY_D_278" FriendlyName="PubPrn 278" Hash="AC6B35C904D388FD12C07C2F6A1A07F337D31895713BF01DCCE7A7F187D7F4D9"/>
|
||||
- <!-- rs3 sxs woa
|
||||
<!-- rs3 sxs woa
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_279" FriendlyName="PubPrn 279" Hash="071D7849941E43144839988971255FE34690A747"/>
|
||||
<Deny ID="ID_DENY_D_280" FriendlyName="PubPrn 280" Hash="5AF75895BDC11A6B68C816A8677D7CF9692BF25A95C4378A43FBDE740B18EEB1"/>
|
||||
- <!-- rs3 sxs x86
|
||||
<!-- rs3 sxs x86
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_281" FriendlyName="PubPrn 281" Hash="9FBFF074C201BFEBE37710CB453EFF9A14AE3BFF"/>
|
||||
<Deny ID="ID_DENY_D_282" FriendlyName="PubPrn 282" Hash="A0C71A925850D2D481C7E520F5D5A83305EC169EEA4C5B8DC20C8D8AFCD8A512"/>
|
||||
- <!-- psworkflowutility.psm1
|
||||
<!-- psworkflowutility.psm1
|
||||
-->
|
||||
- <!-- th1
|
||||
<!-- th1
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_283" FriendlyName="PSWorkflowUtility 283" Hash="4FBC9A72C5D5246F34994F13076A5AD98A1A844E"/>
|
||||
<Deny ID="ID_DENY_D_284" FriendlyName="PSWorkflowUtility 284" Hash="7BF44433D3A606104778F64B11B92C52FC99C4BA570C50B70438275D0B587B8E"/>
|
||||
- <!-- th2
|
||||
<!-- th2
|
||||
-->
|
||||
<Deny ID="ID_DENY_D_285" FriendlyName="PSWorkflowUtility 285" Hash="99382ED8FA3577DFD903C01478A79D6D90681406"/>
|
||||
<Deny ID="ID_DENY_D_286" FriendlyName="PSWorkflowUtility 286" Hash="C3A5DAB20947CA8FD092E75C25177E7BAE7884CA58710F14827144C09EA1F94B"/>
|
||||
</FileRules>
|
||||
- <!-- Signers
|
||||
<!-- Signers
|
||||
-->
|
||||
<Signers />
|
||||
- <!-- Driver Signing Scenarios
|
||||
<!-- Driver Signing Scenarios
|
||||
-->
|
||||
- <SigningScenarios>
|
||||
- <SigningScenario Value="131" ID="ID_SIGNINGSCENARIO_DRIVERS_1" FriendlyName="Driver Signing Scenarios">
|
||||
- <ProductSigners>
|
||||
- <FileRulesRef>
|
||||
<SigningScenarios>
|
||||
<SigningScenario Value="131" ID="ID_SIGNINGSCENARIO_DRIVERS_1" FriendlyName="Driver Signing Scenarios">
|
||||
<ProductSigners>
|
||||
<FileRulesRef>
|
||||
<FileRuleRef RuleID="ID_DENY_KD_KMCI"/>
|
||||
</FileRulesRef>
|
||||
</ProductSigners>
|
||||
</SigningScenario>
|
||||
- <SigningScenario Value="12" ID="ID_SIGNINGSCENARIO_WINDOWS" FriendlyName="User Mode Signing Scenarios">
|
||||
- <ProductSigners>
|
||||
- <FileRulesRef>
|
||||
<SigningScenario Value="12" ID="ID_SIGNINGSCENARIO_WINDOWS" FriendlyName="User Mode Signing Scenarios">
|
||||
<ProductSigners>
|
||||
<FileRulesRef>
|
||||
<FileRuleRef RuleID="ID_DENY_BGINFO"/>
|
||||
<FileRuleRef RuleID="ID_DENY_CBD"/>
|
||||
<FileRuleRef RuleID="ID_DENY_KD"/>
|
||||
|
||||
@ -6,7 +6,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: high
|
||||
author: jsuther1974
|
||||
ms.date: 05/03/2018
|
||||
ms.date: 05/16/2018
|
||||
---
|
||||
|
||||
# Planning and getting started on the Windows Defender Application Control deployment process
|
||||
@ -60,5 +60,25 @@ This topic provides a roadmap for planning and getting started on the Windows De
|
||||
|
||||
8. Enable desired virtualization-based security (VBS) features. Hardware-based security features—also called virtualization-based security (VBS) features—strengthen the protections offered by Windows Defender Application Control.
|
||||
|
||||
> [!WARNING]
|
||||
> Virtualization-based protection of code integrity may be incompatible with some devices and applications. We strongly recommend testing this configuration in your lab before enabling virtualization-based protection of code integrity on production systems. Failure to do so may result in unexpected failures up to and including data loss or a blue screen error (also called a stop error).
|
||||
## Known issues
|
||||
|
||||
This section covers known issues with WDAC and Device Guard. Virtualization-based protection of code integrity may be incompatible with some devices and applications, which might cause unexpected failures, data loss, or a blue screen error (also called a stop error).
|
||||
Test this configuration in your lab before enabling it in production.
|
||||
|
||||
### MSI Installations are blocked by WDAC
|
||||
|
||||
Installing .msi files directly from the internet to a computer protected by WDAC will fail.
|
||||
For example, this command will not work:
|
||||
|
||||
```code
|
||||
msiexec –i https://download.microsoft.com/download/2/E/3/2E3A1E42-8F50-4396-9E7E-76209EA4F429/Windows10_Version_1511_ADMX.msi
|
||||
```
|
||||
|
||||
As a workaround, download the MSI file and run it locally:
|
||||
|
||||
|
||||
```code
|
||||
msiexec –i c:\temp\Windows10_Version_1511_ADMX.msi
|
||||
```
|
||||
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ Your environment needs the following hardware to run Windows Defender Applicatio
|
||||
|--------|-----------|
|
||||
|64-bit CPU|A 64-bit computer with minimum 4 cores is required for hypervisor and virtualization-based security (VBS). For more info about Hyper-V, see [Hyper-V on Windows Server 2016](https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-on-windows-server) or [Introduction to Hyper-V on Windows 10](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/about/). For more info about hypervisor, see [Hypervisor Specifications](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/tlfs).|
|
||||
|CPU virtualization extensions|Extended page tables, also called _Second Level Address Translation (SLAT)_<br><br>**-AND-**<br><br>One of the following virtualization extensions for VBS:<br><br>VT-x (Intel)<br><br>**-OR-**<br><br>AMD-V|
|
||||
|Hardware memory|Microsoft recommends 8GB RAM for optimal performance|
|
||||
|Hardware memory|Microsoft requires a minimum of 8GB RAM|
|
||||
|Hard disk|5 GB free space, solid state disk (SSD) recommended|
|
||||
|Input/Output Memory Management Unit (IOMMU) support|Not required, but strongly recommended|
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: high
|
||||
ms.date: 04/24/2018
|
||||
ms.date: 05/08/2018
|
||||
---
|
||||
|
||||
# Configure advanced features in Windows Defender ATP
|
||||
@ -87,6 +87,11 @@ When you enable this feature, you'll be able to share Windows Defender ATP devic
|
||||
>You'll need to enable the integration on both Intune and Windows Defender ATP to use this feature.
|
||||
|
||||
|
||||
## Preview features
|
||||
Learn about new features in the Windows Defender ATP preview release and be among the first to try upcoming features by turning on the preview experience.
|
||||
|
||||
You'll have access to upcoming features which you can provide feedback on to help improve the overall experience before features are generally available.
|
||||
|
||||
## Enable advanced features
|
||||
1. In the navigation pane, select **Preferences setup** > **Advanced features**.
|
||||
2. Select the advanced feature you want to configure and toggle the setting between **On** and **Off**.
|
||||
|
||||
@ -10,7 +10,7 @@ ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: high
|
||||
ms.date: 05/03/2018
|
||||
ms.date: 05/08/2018
|
||||
---
|
||||
|
||||
# Use Automated investigations to investigate and remediate threats
|
||||
@ -65,15 +65,24 @@ While an investigation is running, any other alert generated from the machine wi
|
||||
If an incriminated entity is seen in another machine, the Automated investigation will expand the investigation to include that machine and a generic machine playbook will start on that machine. If 10 or more machines are found during this expansion process from the same entity, then that expansion action will require an approval and will be seen in the **Pending actions** view.
|
||||
|
||||
### How threats are remediated
|
||||
Depending on how you set up the machine groups and their level of automation, the Automated investigation will either automatically remediate threats or require user approval (this is the default). For more information, see [Create and manage machine groups](machine-groups-windows-defender-advanced-threat-protection.md).
|
||||
Depending on how you set up the machine groups and their level of automation, the Automated investigation will either require user approval (default) or automatically remediate threats.
|
||||
|
||||
You can configure the following levels of automation:
|
||||
|
||||
Automation level | Description
|
||||
:---|:---
|
||||
Semi - require approval for any remediation | This is the default automation level.<br><br> An approval is needed for any remediation action.
|
||||
Semi - require approval for non-temp folders remediation | An approval is required on files or executables that are not in temporary folders. <br><br> Files or executables in temporary folders, such as the user's download folder or the user's temp folder, will automatically be remediated if needed.
|
||||
Semi - require approval for non-temp folders remediation | An approval is required on files or executables that are in the operating system directories such as Windows folder and Program files folder. <br><br> Files or executables in all other folders will automatically be remediated if needed.
|
||||
Semi - require approval for core folders remediation | An approval is required on files or executables that are in the operating system directories such as Windows folder and Program files folder. <br><br> Files or executables in all other folders will automatically be remediated if needed.
|
||||
Full - remediate threats automatically | All remediation actions will be performed automatically.
|
||||
|
||||
For more information on how to configure these automation levels, see [Create and manage machine groups](machine-groups-windows-defender-advanced-threat-protection.md).
|
||||
|
||||
The default machine group is configured for semi-automatic remediation. This means that any malicious entity that needs to be remediated requires an approval and the investigation is added to the **Pending actions** section, this can be changed to fully automatic so that no user approval is needed.
|
||||
|
||||
When a pending action is approved, the entity is then remediated and this new state is reflected in the **Entities** tab of the investigation.
|
||||
|
||||
### How an Automated investigation is completed
|
||||
When the Automated investigation completes its analysis, and all pending actions are resolved, an investigation is considered complete. It's important to understand that an investigation is only considered complete if there are no pending actions on it.
|
||||
|
||||
|
||||
## Manage Automated investigations
|
||||
By default, the Automated investigations list displays investigations initiated in the last week. You can also choose to select other time ranges from the drop-down menu or specify a custom range.
|
||||
@ -103,19 +112,15 @@ Status | Description
|
||||
| No threats found | No malicious entities found during the investigation.
|
||||
| Failed | A problem has interrupted the investigation, preventing it from completing. |
|
||||
| Partially remediated | A problem prevented the remediation of some malicious entities. |
|
||||
| Action required | Remediation actions require review and approval. |
|
||||
| Pending | Remediation actions require review and approval. |
|
||||
| Waiting for machine | Investigation paused. The investigation will resume as soon as the machine is available. |
|
||||
| Queued | Investigation has been queued and will resume as soon as other remediation activities are completed. |
|
||||
| Running | Investigation ongoing. Malicious entities found will be remediated. |
|
||||
| Remediated | Malicious entities found were successfully remediated. |
|
||||
| Terminated by system | Investigation was stopped due to <reason>. |
|
||||
| Terminated by user | A user stopped the investigation before it could complete. |
|
||||
| Not applicable | Automated investigations do not apply to this alert type. |
|
||||
| Terminated by user | A user stopped the investigation before it could complete.
|
||||
| Partially investigated | Entities directly related to the alert have been investigated. However, a problem stopped the investigation of collateral entities. |
|
||||
| Automated investigation not applicable to alert type | Automated investigation does not apply to this alert type. |
|
||||
| Automated investigation does not support OS | Machine is running an OS that is not supported by Automated investigation. |
|
||||
| Automated investigation unavailable for preexisting alert | Automated investigation does not apply to alerts that were generated before it was deployed. |
|
||||
| Automated investigation unavailable for suppressed alert | Automated investigation does not apply to suppressed alerts. |
|
||||
|
||||
|
||||
|
||||
**Detection source**</br>
|
||||
|
||||
@ -102,7 +102,7 @@ Take the following steps to enable conditional access:
|
||||
|
||||
|
||||
### Step 1: Turn on the Microsoft Intune connection
|
||||
1. In the navigation pane, select **Settings** > **General** > **Advanced features** > **Microsoft Intune connection**.
|
||||
1. In the navigation pane, select **Settings** > **Advanced features** > **Microsoft Intune connection**.
|
||||
2. Toggle the Microsoft Intune setting to **On**.
|
||||
3. Click **Save preferences**.
|
||||
|
||||
|
||||
@ -30,26 +30,29 @@ ms.date: 05/01/2018
|
||||
You can configure Windows Defender ATP to send email notifications to specified recipients for new alerts. This feature enables you to identify a group of individuals who will immediately be informed and can act on alerts based on their severity.
|
||||
|
||||
> [!NOTE]
|
||||
> Only users with full access can configure email notifications.
|
||||
> Only users with 'Manage security settings' permissions can configure email notifications. If you've chosen to use basic permissions management, users with Security Administrator or Global Administrator roles can configure email notifications.
|
||||
|
||||
You can set the alert severity levels that trigger notifications. When you turn enable the email notifications feature, it’s set to high and medium alerts by default.
|
||||
You can set the alert severity levels that trigger notifications. You can also add or remove recipients of the email notification. New recipients get notified about alerts encountered after they are added. For more information about alerts, see [View and organize the Alerts queue](alerts-queue-windows-defender-advanced-threat-protection.md).
|
||||
|
||||
You can also add or remove recipients of the email notification. New recipients get notified about alerts encountered after they are added. For more information about alerts, see [View and organize the Alerts queue](alerts-queue-windows-defender-advanced-threat-protection.md).
|
||||
If you're using role-based access control (RBAC), recipients will only receive notifications based on the machine groups that were configured in the notification rule.
|
||||
Users with the proper permission can only create, edit, or delete notifications that are limited to their machine group management scope.
|
||||
Only users assigned to the Global administrator role can manage notification rules that are configured for all machine groups.
|
||||
|
||||
The email notification includes basic information about the alert and a link to the portal where you can do further investigation.
|
||||
|
||||
|
||||
## Set up email notifications for alerts
|
||||
The email notifications feature is turned off by default. Turn it on to start receiving email notifications.
|
||||
|
||||
1. On the navigation pane, select **Settings** > **Alert notifications**.
|
||||
2. Toggle the setting between **On** and **Off**.
|
||||
3. Select the alert severity level that you’d like your recipients to receive:
|
||||
- **High** – Select this level to send notifications for high-severity alerts.
|
||||
- **Medium** – Select this level to send notifications for medium-severity alerts.
|
||||
3. Select the alert severity level that you<EFBFBD>d like your recipients to receive:
|
||||
- **High** <EFBFBD> Select this level to send notifications for high-severity alerts.
|
||||
- **Medium** <EFBFBD> Select this level to send notifications for medium-severity alerts.
|
||||
- **Low** - Select this level to send notifications for low-severity alerts.
|
||||
- **Informational** - Select this level to send notification for alerts that might not be considered harmful but good to keep track of.
|
||||
4. In **Email recipients to notify on new alerts**, type the email address then select the + sign.
|
||||
5. Click **Save preferences** when you’ve completed adding all the recipients.
|
||||
5. Click **Save preferences** when you<EFBFBD>ve completed adding all the recipients.
|
||||
|
||||
Check that email recipients are able to receive the email notifications by selecting **Send test email**. All recipients in the list will receive the test email.
|
||||
|
||||
@ -59,10 +62,9 @@ Here's an example email notification:
|
||||
|
||||
## Remove email recipients
|
||||
|
||||
1. Select the trash bin icon beside the email address you’d like to remove.
|
||||
1. Select the trash bin icon beside the email address you<EFBFBD>d like to remove.
|
||||
2. Click **Save preferences**.
|
||||
|
||||
|
||||
## Troubleshoot email notifications for alerts
|
||||
This section lists various issues that you may encounter when using email notifications for alerts.
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ ms.date: 04/24/2018
|
||||
## Onboard machines using Group Policy
|
||||
1. Open the GP configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
@ -122,7 +122,7 @@ For security reasons, the package used to Offboard machines will expire 30 days
|
||||
|
||||
1. Get the offboarding package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Offboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Offboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
|
||||
@ -106,7 +106,7 @@ For more information on using Windows Defender ATP CSP see, [WindowsAdvancedThre
|
||||
|
||||
1. Open the Microsoft Intune configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
@ -189,7 +189,7 @@ For security reasons, the package used to Offboard machines will expire 30 days
|
||||
|
||||
1. Get the offboarding package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Offboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Offboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
|
||||
@ -34,7 +34,7 @@ You'll need to take the following steps to onboard non-Windows machines:
|
||||
|
||||
### Turn on third-party integration
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**. Make sure the third-party solution is listed.
|
||||
1. In the navigation pane, select **Settings** > **Onboarding**. Make sure the third-party solution is listed.
|
||||
|
||||
2. Select Mac and Linux as the operating system.
|
||||
|
||||
@ -59,7 +59,7 @@ To effectively offboard the machine from the service, you'll need to disable the
|
||||
|
||||
1. Follow the third-party documentation to opt-out on the third-party service side.
|
||||
|
||||
2. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
2. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
3. Turn off the third-party solution integration.
|
||||
|
||||
|
||||
@ -49,7 +49,7 @@ You can use existing System Center Configuration Manager functionality to create
|
||||
|
||||
1. Open the SCCM configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
@ -127,7 +127,7 @@ For security reasons, the package used to Offboard machines will expire 30 days
|
||||
|
||||
1. Get the offboarding package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Offboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Offboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ You can also manually onboard individual machines to Windows Defender ATP. You m
|
||||
## Onboard machines
|
||||
1. Open the GP configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
@ -94,7 +94,7 @@ For security reasons, the package used to Offboard machines will expire 30 days
|
||||
|
||||
1. Get the offboarding package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Offboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Offboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
|
||||
@ -40,7 +40,7 @@ You can onboard VDI machines using a single entry or multiple entries for each m
|
||||
|
||||
1. Open the VDI configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: mjcaparas
|
||||
localizationpriority: high
|
||||
ms.date: 05/03/2018
|
||||
ms.date: 05/08/2018
|
||||
---
|
||||
|
||||
# Onboard servers to the Windows Defender ATP service
|
||||
@ -71,8 +71,8 @@ Once completed, you should see onboarded servers in the portal within an hour.
|
||||
- Each Windows server must be able to connect to the Internet using HTTPS. This connection can be direct, using a proxy, or through the [OMS Gateway](https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-oms-gateway).
|
||||
- If a proxy or firewall is blocking all traffic by default and allowing only specific domains through or HTTPS scanning (SSL inspection) is enabled, make sure that the following URLs are white-listed to permit communication with Windows Defender ATP service:
|
||||
|
||||
| Agent Resource | Ports |
|
||||
|------------------------------------|-------------|
|
||||
Agent Resource | Ports
|
||||
:---|:---
|
||||
| *.oms.opinsights.azure.com | 443 |
|
||||
| *.blob.core.windows.net | 443 |
|
||||
| *.azure-automation.net | 443 |
|
||||
@ -81,6 +81,10 @@ Once completed, you should see onboarded servers in the portal within an hour.
|
||||
| winatp-gw-eus.microsoft.com | 443 |
|
||||
| winatp-gw-neu.microsoft.com | 443 |
|
||||
| winatp-gw-weu.microsoft.com | 443 |
|
||||
|winatp-gw-uks.microsoft.com | 443 |
|
||||
|winatp-gw-ukw.microsoft.com | 443 |
|
||||
| winatp-gw-aus.microsoft.com | 443|
|
||||
| winatp-gw-aue.microsoft.com |443 |
|
||||
|
||||
## Onboard Windows Server, version 1803
|
||||
You’ll be able to onboard in the same method available for Windows 10 client machines. For more information, see [Onboard Windows 10 machines](configure-endpoints-windows-defender-advanced-threat-protection.md). Support for Windows Server, version 1803 provides deeper insight into activities happening on the server, coverage for kernel and memory attack detection, and enables response actions on Windows Server endpoint as well.
|
||||
@ -111,7 +115,9 @@ You’ll be able to onboard in the same method available for Windows 10 client m
|
||||
If the result is ‘The specified service does not exist as an installed service’, then you'll need to install Windows Defender AV. For more information, see [Windows Defender Antivirus in Windows 10](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10).
|
||||
|
||||
## Offboard servers
|
||||
You have two options to offboard servers from the service:
|
||||
You can offboard Windows Server, version 1803 in the same method available for Windows 10 client machines.
|
||||
|
||||
For other server versions, you have two options to offboard servers from the service:
|
||||
- Uninstall the MMA agent
|
||||
- Remove the Windows Defender ATP workspace configuration
|
||||
|
||||
@ -139,7 +145,7 @@ To offboard the server, you can use either of the following methods:
|
||||
#### Run a PowerShell command to remove the configuration
|
||||
|
||||
1. Get your Workspace ID:
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
b. Select **Windows server 2012, 2012R2 and 2016** as the operating system and get your Workspace ID:
|
||||
|
||||
|
||||
@ -139,6 +139,10 @@ Use the solution explorer to view alerts in Splunk.
|
||||
5. Find the query you saved in the list and click **Run**. The results are displayed based on your query.
|
||||
|
||||
|
||||
>[!TIP]
|
||||
> To mininimize alert duplications, you can use the following query:
|
||||
>```source="rest://windows atp alerts" | spath | dedup _raw | table *```
|
||||
|
||||
## Related topics
|
||||
- [Enable SIEM integration in Windows Defender ATP](enable-siem-integration-windows-defender-advanced-threat-protection.md)
|
||||
- [Configure ArcSight to pull Windows Defender ATP alerts](configure-arcsight-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
@ -28,7 +28,7 @@ ms.date: 04/24/2018
|
||||
|
||||
During the onboarding process, a wizard takes you through the general settings of Windows Defender ATP. After onboarding, you might want to update the data retention settings.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **General** > **Data rention**.
|
||||
1. In the navigation pane, select **Settings** > **Data rention**.
|
||||
|
||||
2. Select the data retention duration from the drop-down list.
|
||||
|
||||
|
||||
@ -29,7 +29,7 @@ ms.date: 04/24/2018
|
||||
|
||||
Before you can create custom threat intelligence (TI) using REST API, you'll need to set up the custom threat intelligence application through the Windows Defender ATP portal.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **APIs** > **Threat intel**.
|
||||
1. In the navigation pane, select **Settings** > **Threat intel**.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ Set the baselines for calculating the score of Windows Defender security control
|
||||
>[!NOTE]
|
||||
>Changes might take up to a few hours to reflect on the dashboard.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **General** > **Secure Score**.
|
||||
1. In the navigation pane, select **Settings** > **Secure Score**.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -29,7 +29,7 @@ ms.date: 04/24/2018
|
||||
|
||||
Enable security information and event management (SIEM) integration so you can pull alerts from the Windows Defender ATP portal using your SIEM solution or by connecting directly to the alerts REST API.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **APIs** > **SIEM**.
|
||||
1. In the navigation pane, select **Settings** > **SIEM**.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: high
|
||||
ms.date: 04/24/2018
|
||||
ms.date: 05/08/2018
|
||||
---
|
||||
|
||||
# Create and manage machine groups in Windows Defender ATP
|
||||
@ -33,61 +33,61 @@ In Windows Defender ATP, you can create machine groups and use them to:
|
||||
- Configure different auto-remediation settings for different sets of machines
|
||||
|
||||
As part of the process of creating a machine group, you'll:
|
||||
- Set the automated remediation level for that group
|
||||
- Define a matching rule based on the machine name, domain, tags, and OS platform to determine which machines belong to the group. If a machine is also matched to other groups, it is added only to the highest ranked machine group.
|
||||
- Determine access to machine group
|
||||
- Rank the machine group relative to other groups after it is created
|
||||
- Set the automated remediation level for that group. For more information on remediation levels, see [Use Automated investigation to investigate and remediate threats](automated-investigations-windows-defender-advanced-threat-protection.md).
|
||||
- Specify the matching rule that determines which machine group belongs to the group based on the machine name, domain, tags, and OS platform. If a machine is also matched to other groups, it is added only to the highest ranked machine group.
|
||||
- Select the Azure AD user group that should have access to the machine group.
|
||||
- Rank the machine group relative to other groups after it is created.
|
||||
|
||||
>[!NOTE]
|
||||
>All machine groups are accessible to all users if you don’t assign any Azure AD groups to them.
|
||||
>A machine group is accessible to all users if you don’t assign any Azure AD groups to it.
|
||||
|
||||
|
||||
## Add a machine group
|
||||
|
||||
1. In the navigation pane, select **Settings > Permissions > Machine groups**.
|
||||
1. In the navigation pane, select **Settings** > **Machine groups**.
|
||||
|
||||
2. Click **Add machine group**.
|
||||
|
||||
3. Set the machine group details, configure an association rule, preview the results, then assign the group to an Azure user group:
|
||||
3. Enter the group name and automation settings and specify the matching rule that determines which machines belong to the group.
|
||||
|
||||
- **Name**
|
||||
|
||||
- **Remediation level for automated investigations**
|
||||
- **No remediation**
|
||||
- **Require approval (all folders)**
|
||||
- **Require approval (non-temp folders)**
|
||||
- **Require approval (core folders)**
|
||||
- **Fully automated**
|
||||
- **Machine group name**
|
||||
- **Automation level**
|
||||
- **Semi - require approval for any remediation**
|
||||
- **Semi - require approval for non-temp folders remediation**
|
||||
- **Semi - require approval for core folders remediation**
|
||||
- **Full - remediate threats automatically**
|
||||
|
||||
>[!NOTE]
|
||||
> For more information on automation levels, see [Understand the Automated investigation flow](automated-investigations-windows-defender-advanced-threat-protection.md#understand-the-automated-investigation-flow).
|
||||
|
||||
- **Description**
|
||||
- **Members**
|
||||
|
||||
- **Matching rule** – you can apply the rule based on machine name, domain, tag, or OS version.
|
||||
>[!TIP]
|
||||
>If you want to group machines by organizational unit, you can configure the registry key for the group affiliation. For more information on device tagging, see [Manage machine group and tags](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-atp/investigate-machines-windows-defender-advanced-threat-protection#manage-machine-group-and-tags).
|
||||
|
||||
>[!TIP]
|
||||
>If you want to group machines by organizational unit, you can configure the registry key for the group affiliation. For more information on device tagging, see [Manage machine group and tags](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-atp/investigate-machines-windows-defender-advanced-threat-protection#manage-machine-group-and-tags).
|
||||
|
||||
4. Review the result of the preview of matched machines. If you are satisfied with the rules, click the **Access** tab.
|
||||
4. Preview several machines that will be matched by this rule. If you are satisfied with the rule, click the **Access** tab.
|
||||
|
||||
5. Assign the user groups that can access the machine group you created.
|
||||
|
||||
>[!NOTE]
|
||||
>You can only grant access to Azure AD user groups that have been assigned to RBAC roles.
|
||||
|
||||
6. Click **Close**.
|
||||
6. Click **Close**. The configuration changes are applied.
|
||||
|
||||
7. Apply the configuration settings.
|
||||
|
||||
## Understand matching and manage groups
|
||||
You can promote the rank of a machine group so that it is given higher priority during matching. When a machine is matched to more than one group, it is added only to the highest ranked group. You can also edit and delete groups.
|
||||
## Manage machine groups
|
||||
You can promote or demote the rank of a machine group so that it is given higher or lower priority during matching. When a machine is matched to more than one group, it is added only to the highest ranked group. You can also edit and delete groups.
|
||||
|
||||
>[!WARNING]
|
||||
>Deleting a machine group may affect email notification rules. If a machine group is configured under an email notification rule, it will be removed from that rule. If the machine group is the only group configured for an email notification, that email notification rule will be deleted along with the machine group.
|
||||
|
||||
By default, machine groups are accessible to all users with portal access. You can change the default behavior by assigning Azure AD user groups to the machine group.
|
||||
|
||||
Machines that are not matched to any groups are added to Ungrouped machines (default) group. You cannot change the rank of this group or delete it. However, you can change the remediation level of this group, and define the Azure AD user groups that can access this group.
|
||||
|
||||
>[!NOTE]
|
||||
>Applying changes to machine group configuration may take up to several minutes.
|
||||
|
||||
|
||||
> - Applying changes to machine group configuration may take up to several minutes.
|
||||
|
||||
|
||||
## Related topic
|
||||
|
||||
@ -110,7 +110,7 @@ Create custom rules to control when alerts are suppressed, or resolved. You can
|
||||
|
||||
### View the list of suppression rules
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Alert suppression**.
|
||||
1. In the navigation pane, select **Settings** > **Alert suppression**.
|
||||
|
||||
2. The list of suppression rules shows all the rules that users in your organization have created.
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ Entities added to the blocked list are considered malicious and will be remediat
|
||||
You can define the conditions for when entities are identified as malicious or safe based on certain attributes such as hash values or certificates.
|
||||
|
||||
## Create an allowed or blocked list
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation allowed/blocked list**.
|
||||
1. In the navigation pane, select **Settings** > **Automation allowed/blocked list**.
|
||||
|
||||
2. Select the type of entity you'd like to create an exclusion for. You can choose any of the following entities:
|
||||
- File hash
|
||||
@ -52,14 +52,14 @@ You can define the conditions for when entities are identified as malicious or s
|
||||
5. Click **Update rule**.
|
||||
|
||||
## Edit a list
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation allowed/blocked list**.
|
||||
1. In the navigation pane, select **Settings** > **Automation allowed/blocked list**.
|
||||
|
||||
2. Select the type of entity you'd like to edit the list from.
|
||||
|
||||
3. Update the details of the rule and click **Update rule**.
|
||||
|
||||
## Delete a list
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation allowed/blocked list**.
|
||||
1. In the navigation pane, select **Settings** > **Automation allowed/blocked list**.
|
||||
|
||||
2. Select the type of entity you'd like to delete the list from.
|
||||
|
||||
|
||||
@ -35,7 +35,7 @@ For example, if you add *exe* and *bat* as file or attachment extension names, t
|
||||
|
||||
## Add file extension names and attachment extension names.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation file uploads**.
|
||||
1. In the navigation pane, select **Settings** > **Automation file uploads**.
|
||||
|
||||
2. Toggle the content analysis setting between **On** and **Off**.
|
||||
|
||||
|
||||
@ -47,7 +47,7 @@ You can specify the file names that you want to be excluded in a specific direct
|
||||
|
||||
|
||||
## Add an automation folder exclusion
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation folder exclusions**.
|
||||
1. In the navigation pane, select **Settings** > **Automation folder exclusions**.
|
||||
|
||||
2. Click **New folder exclusion**.
|
||||
|
||||
@ -62,14 +62,14 @@ You can specify the file names that you want to be excluded in a specific direct
|
||||
4. Click **Save**.
|
||||
|
||||
## Edit an automation folder exclusion
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation folder exclusions**.
|
||||
1. In the navigation pane, select **Settings** > **Automation folder exclusions**.
|
||||
|
||||
2. Click **Edit** on the folder exclusion.
|
||||
|
||||
3. Update the details of the rule and click **Save**.
|
||||
|
||||
## Remove an automation folder exclusion
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation folder exclusions**.
|
||||
1. In the navigation pane, select **Settings** > **Automation folder exclusions**.
|
||||
2. Click **Remove exclusion**.
|
||||
|
||||
|
||||
|
||||
@ -32,7 +32,7 @@ There might be scenarios where you need to suppress alerts from appearing in the
|
||||
You can view a list of all the suppression rules and manage them in one place. You can also turn an alert suppression rule on or off.
|
||||
|
||||
## Turn a suppression rule on or off
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Alert suppression**. The list of suppression rules that users in your organization have created is displayed.
|
||||
1. In the navigation pane, select **Settings** > **Alert suppression**. The list of suppression rules that users in your organization have created is displayed.
|
||||
|
||||
2. Select a rule by clicking on the check-box beside the rule name.
|
||||
|
||||
@ -40,7 +40,7 @@ You can view a list of all the suppression rules and manage them in one place. Y
|
||||
|
||||
## View details of a suppression rule
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Alert suppression**. The list of suppression rules that users in your organization have created is displayed.
|
||||
1. In the navigation pane, select **Settings** > **Alert suppression**. The list of suppression rules that users in your organization have created is displayed.
|
||||
|
||||
2. Click on a rule name. Details of the rule is displayed. You'll see the rule details such as status, scope, action, number of matching alerts, created by, and date when the rule was created. You can also view associated alerts and the rule conditions.
|
||||
|
||||
|
||||
@ -40,7 +40,7 @@ You can access these options from the Windows Defender ATP portal. Both the Powe
|
||||
## Create a Windows Defender ATP dashboard on Power BI service
|
||||
Windows Defender ATP makes it easy to create a Power BI dashboard by providing an option straight from the portal.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **General** > **Power BI reports**.
|
||||
1. In the navigation pane, select **Settings** > **Power BI reports**.
|
||||
|
||||
2. Click **Create dashboard**.
|
||||
|
||||
@ -127,7 +127,7 @@ You can create a custom dashboard in Power BI Desktop to create visualizations t
|
||||
### Before you begin
|
||||
1. Make sure you use Power BI Desktop June 2017 and above. [Download the latest version](https://powerbi.microsoft.com/en-us/desktop/).
|
||||
|
||||
2. In the navigation pane, select **Settings** > **General** > **Power BI reports**.
|
||||
2. In the navigation pane, select **Settings** > **Power BI reports**.
|
||||
|
||||
3. Click **Download connector** to download the WDATPPowerBI.zip file and extract it.
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ ms.date: 04/24/2018
|
||||
|
||||
Turn on the preview experience setting to be among the first to try upcoming features.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Preview experience**.
|
||||
1. In the navigation pane, select **Settings** > **Advanced features**.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ You'll have access to upcoming features which you can provide feedback on to hel
|
||||
|
||||
Turn on the preview experience setting to be among the first to try upcoming features.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **General** > **Advanced features** > **Preview features**.
|
||||
1. In the navigation pane, select **Settings** > **Advanced features** > **Preview features**.
|
||||
|
||||
2. Toggle the setting between **On** and **Off** and select **Save preferences**.
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: high
|
||||
ms.date: 04/24/2018
|
||||
ms.date: 05/08/2018
|
||||
---
|
||||
|
||||
# Manage portal access using role-based access control
|
||||
@ -76,17 +76,18 @@ Someone with a Windows Defender ATP Global administrator role has unrestricted a
|
||||
|
||||
2. Click **Add role**.
|
||||
|
||||
3. Enter the role name, description, and active permissions you’d like to assign to the role.
|
||||
3. Enter the role name, description, and permissions you’d like to assign to the role.
|
||||
|
||||
- **Role name**
|
||||
|
||||
- **Description**
|
||||
|
||||
- **Active permissions**
|
||||
- **Permissions**
|
||||
- **View data** - Users can view information in the portal.
|
||||
- **Investigate alerts** - Users can manage alerts, initiate automated investigations, collect investigation packages, manage machine tags, and export machine timeline.
|
||||
- **Approve or take action** - Users can take response actions and approve or dismiss pending remediation actions.
|
||||
- **Manage system settings** - Users can configure settings, SIEM and threat intel API settings, advanced settings, preview features, and automated file uploads.
|
||||
- **Manage security settings** - Users can configure alert suppression settings, manage allowed/blocked lists for automation, manage folder exclusions for automation, onboard and offboard machines, and manage email notifications.
|
||||
|
||||
4. Click **Next** to assign the role to an Azure AD group.
|
||||
|
||||
@ -102,13 +103,13 @@ Someone with a Windows Defender ATP Global administrator role has unrestricted a
|
||||
|
||||
2. Click **Edit**.
|
||||
|
||||
3. Modify the details or the groups that the role is a part of.
|
||||
3. Modify the details or the groups that are assigned to the role.
|
||||
|
||||
4. Click **Save and close**.
|
||||
|
||||
## Delete roles
|
||||
|
||||
1. Select the role row you'd like to delete.
|
||||
1. Select the role you'd like to delete.
|
||||
|
||||
2. Click the drop-down button and select **Delete role**.
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ms.pagetype: security
|
||||
localizationpriority: medium
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 04/30/2018
|
||||
ms.date: 05/17/2018
|
||||
---
|
||||
|
||||
|
||||
@ -42,7 +42,7 @@ ms.date: 04/30/2018
|
||||
- Configuration service providers for mobile device management
|
||||
|
||||
|
||||
Attack surface reduction helps prevent actions and apps that are typically used by exploit-seeking malware to infect machines.
|
||||
Available in Windows 10 Enterprise E5, Attack surface reduction helps prevent actions and apps that are typically used by exploit-seeking malware to infect machines.
|
||||
|
||||
It is part of [Windows Defender Exploit Guard](windows-defender-exploit-guard.md).
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ms.pagetype: security
|
||||
localizationpriority: medium
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 04/30/2018
|
||||
ms.date: 05/17/2018
|
||||
---
|
||||
|
||||
# Customize Attack surface reduction
|
||||
@ -35,7 +35,7 @@ ms.date: 04/30/2018
|
||||
- Configuration service providers for mobile device management
|
||||
|
||||
|
||||
Attack surface reduction is a feature that is part of Windows Defender Exploit Guard. It helps prevent actions and apps that are typically used by exploit-seeking malware to infect machines.
|
||||
Available in Windows 10 Enterprise E5, Attack surface reduction is a feature that is part of Windows Defender Exploit Guard. It helps prevent actions and apps that are typically used by exploit-seeking malware to infect machines.
|
||||
|
||||
This topic describes how to customize Attack surface reduction by [excluding files and folders](#exclude-files-and-folders) or [adding custom text to the notification](#customize-the-notification) alert that appears on a user's computer.
|
||||
|
||||
@ -48,12 +48,14 @@ You can exclude files and folders from being evaluated by most Attack surface re
|
||||
This could potentially allow unsafe files to run and infect your devices.
|
||||
|
||||
>[!WARNING]
|
||||
>Excluding files or folders can severly reduce the protection provided by Attack surface reduction rules. Files that would have been blocked by a rule will be allowed to run, and there will be no report or event recorded.
|
||||
>Excluding files or folders can severely reduce the protection provided by Attack surface reduction rules. Files that would have been blocked by a rule will be allowed to run, and there will be no report or event recorded.
|
||||
>
|
||||
>If you are encountering problems with rules detecting files that you believe should not be detected, you should [use audit mode first to test the rule](enable-attack-surface-reduction.md#enable-and-audit-attack-surface-reduction-rules).
|
||||
|
||||
You can specify individual files or folders (using folder paths or fully qualified resource names) but you cannot specify if the exclusions should only be applied to individual rules: the exclusions will apply to all rules that are enabled (or placed in audit mode) and that allow exclusions.
|
||||
|
||||
Windows 10, version 1803 supports environment variables and wildcards. For information about using wildcards in Windows Defender Exploit Guard, see [Use wildcards in the file name and folder path or extension exclusion lists](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10).
|
||||
|
||||
Exclusions will only be applied to certain rules. Some rules will not honor the exclusion list. This means that even if you have added a file to the exclusion list, some rules will still evaluate and potentially block that file if the rule determines the file to be unsafe.
|
||||
|
||||
>[!IMPORTANT]
|
||||
|
||||
@ -11,7 +11,7 @@ ms.pagetype: security
|
||||
localizationpriority: medium
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 04/30/2018
|
||||
ms.date: 05/17/2018
|
||||
---
|
||||
|
||||
|
||||
@ -59,7 +59,8 @@ You can add additional folders to be protected, but you cannot remove the defaul
|
||||
|
||||
Adding other folders to Controlled folder access can be useful, for example, if you don't store files in the default Windows libraries or you've changed the location of the libraries away from the defaults.
|
||||
|
||||
You can also enter network shares and mapped drives, but environment variables and wildcards are not supported.
|
||||
You can also enter network shares and mapped drives. Windows 10, version 1803 supports environment variables and wildcards. For information about using wildcards in Windows Defender Exploit Guard, see [Use wildcards in the file name and folder path or extension exclusion lists](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10).
|
||||
|
||||
|
||||
You can use the Windows Defender Security Center app or Group Policy to add and remove additional protected folders.
|
||||
|
||||
@ -86,8 +87,8 @@ You can use the Windows Defender Security Center app or Group Policy to add and
|
||||
|
||||
6. Double-click the **Configured protected folders** setting and set the option to **Enabled**. Click **Show** and enter each folder.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Environment variables and wildcards are not supported.
|
||||
> [!NOTE]
|
||||
> Windows 10, version 1803 supports environment variables and wildcards. For information about using wildcards in Windows Defender Exploit Guard, see [Use wildcards in the file name and folder path or extension exclusion lists](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10).
|
||||
|
||||
|
||||
### Use PowerShell to protect additional folders
|
||||
|
||||
@ -11,7 +11,7 @@ ms.pagetype: security
|
||||
localizationpriority: medium
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 04/30/2018
|
||||
ms.date: 05/17/2018
|
||||
---
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ ms.date: 04/30/2018
|
||||
- Configuration service providers for mobile device management
|
||||
|
||||
|
||||
Attack surface reduction is a feature that is part of Windows Defender Exploit Guard. It helps prevent actions and apps that are typically used by exploit-seeking malware to infect machines.
|
||||
Available in Windows 10 Enterprise E5, Attack surface reduction is a feature that is part of Windows Defender Exploit Guard. It helps prevent actions and apps that are typically used by exploit-seeking malware to infect machines.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ms.pagetype: security
|
||||
localizationpriority: medium
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 04/30/2018
|
||||
ms.date: 05/17/2018
|
||||
---
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ ms.date: 04/30/2018
|
||||
- Configuration service providers for mobile device management
|
||||
|
||||
|
||||
Network protection is a feature that is part of [Windows Defender Exploit Guard](windows-defender-exploit-guard.md). It helps to prevent employees from using any application to access dangerous domains that may host phishing scams, exploits, and other malicious content on the Internet.
|
||||
Available in Windows 10 Enterprise, Network protection is a feature that is part of [Windows Defender Exploit Guard](windows-defender-exploit-guard.md). It helps to prevent employees from using any application to access dangerous domains that may host phishing scams, exploits, and other malicious content on the Internet.
|
||||
|
||||
This topic describes how to enable Network protection with Group Policy, PowerShell cmdlets, and configuration service providers (CSPs) for mobile device management (MDM).
|
||||
|
||||
|
||||
@ -37,7 +37,7 @@ ms.date: 04/30/2018
|
||||
|
||||
|
||||
|
||||
Attack surface reduction is a feature that is part of Windows Defender Exploit Guard [that helps prevent actions and apps that are typically used by exploit-seeking malware to infect machines](attack-surface-reduction-exploit-guard.md).
|
||||
Available in Windows 10 Enterprise E5, Attack surface reduction is a feature that is part of Windows Defender Exploit Guard [that helps prevent actions and apps that are typically used by exploit-seeking malware to infect machines](attack-surface-reduction-exploit-guard.md).
|
||||
|
||||
This topic helps you evaluate Attack surface reduction. It explains how to demo the feature using a specialized tool, and how to enable audit mode so you can test the feature directly in your organization.
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ms.pagetype: security
|
||||
localizationpriority: medium
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 04/30/2018
|
||||
ms.date: 05/17/2018
|
||||
---
|
||||
|
||||
# Evaluate Network protection
|
||||
@ -36,7 +36,7 @@ ms.date: 04/30/2018
|
||||
|
||||
|
||||
|
||||
Network protection is a feature that is part of [Windows Defender Exploit Guard](windows-defender-exploit-guard.md).
|
||||
Available in Windows 10 Enterprise, Network protection is a feature that is part of [Windows Defender Exploit Guard](windows-defender-exploit-guard.md).
|
||||
|
||||
It helps to prevent employees from using any application to access dangerous domains that may host phishing scams, exploits, and other malicious content on the Internet.
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ms.pagetype: security
|
||||
localizationpriority: medium
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 04/30/2018
|
||||
ms.date: 05/17/2018
|
||||
---
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ ms.date: 04/30/2018
|
||||
- Configuration service providers for mobile device management
|
||||
|
||||
|
||||
Network protection helps reduce the attack surface of your devices from Internet-based events. It prevents employees from using any application to access dangerous domains that may host phishing scams, exploits, and other malicious content on the Internet.
|
||||
Available in Windows 10 Enterprise, Network protection helps reduce the attack surface of your devices from Internet-based events. It prevents employees from using any application to access dangerous domains that may host phishing scams, exploits, and other malicious content on the Internet.
|
||||
|
||||
It expands the scope of [Windows Defender SmartScreen](../windows-defender-smartscreen/windows-defender-smartscreen-overview.md) to block all outbound HTTP(s) traffic that attempts to connect to low-reputation sources (based on the domain or hostname).
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 04/30/2018
|
||||
ms.date: 05/17/2018
|
||||
---
|
||||
|
||||
# Troubleshoot Attack surface reduction rules
|
||||
@ -45,7 +45,7 @@ There are four steps to troubleshooting these problems:
|
||||
Attack surface reduction (ASR) will only work on devices with the following conditions:
|
||||
|
||||
>[!div class="checklist"]
|
||||
> - Endpoints are running Windows 10 Enterprise edition, version 1709 (also known as the Fall Creators Update).
|
||||
> - Endpoints are running Windows 10 Enterprise E5, version 1709 (also known as the Fall Creators Update).
|
||||
> - Endpoints are using Windows Defender Antivirus as the sole antivirus protection app. [Using any other antivirus app will cause Windows Defender AV to disable itself](../windows-defender-antivirus/windows-defender-antivirus-compatibility.md).
|
||||
> - [Real-time protection](../windows-defender-antivirus/configure-real-time-protection-windows-defender-antivirus.md) is enabled.
|
||||
> - Audit mode is not enabled. Use Group Policy to set the rule to **Disabled** (value: **0**) as described in the [Enable ASR topic](enable-attack-surface-reduction.md#use-group-policy-to-enable-or-audit-attack-surface-reduction-rules).
|
||||
|
||||
@ -11,7 +11,7 @@ ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 12/12/2017
|
||||
ms.date: 05/17/2018
|
||||
---
|
||||
|
||||
# Troubleshoot Network protection
|
||||
|
||||
Reference in New Issue
Block a user