Merge pull request #18 from MicrosoftDocs/master
Pull in official repo updates 4.29.20
@ -45,7 +45,7 @@ The statement "PIN is stronger than Password" is not directed at the strength of
|
||||
The **Key Admins** and **Enterprise Key Admins** groups are created when you install the first Windows Server 2016 domain controller into a domain. Domain controllers running previous versions of Windows Server cannot translate the security identifier (SID) to a name. To resolve this, transfer the PDC emulator domain role to a domain controller running Windows Server 2016.
|
||||
|
||||
## Can I use a convenience PIN with Azure AD?
|
||||
It is currently possible to set a convenience PIN on Azure Active Directory Joined or Hybrid Active Directory Joined devices. Convenience PIN is not supported for Azure Active Directory user accounts. It is only supported for on-premises only Domain Joined users and local account users.
|
||||
It is currently possible to set a convenience PIN on Azure Active Directory Joined or Hybrid Active Directory Joined devices. Convenience PIN is not supported for Azure Active Directory user accounts. It is only supported for on-premises Domain Joined users and local account users.
|
||||
|
||||
## Can I use an external camera when my laptop is closed or docked?
|
||||
No. Windows 10 currently only supports one Windows Hello for Business camera and does not fluidly switch to an external camera when the computer is docked with the lid closed. The product group is aware of this and is investigating this topic further.
|
||||
@ -64,11 +64,11 @@ The user experience for Windows Hello for Business occurs after user sign-in, af
|
||||
[Windows Hello for Business user enrollment experience](hello-videos.md#windows-hello-for-business-user-enrollment-experience)
|
||||
|
||||
## What happens when my user forgets their PIN?
|
||||
If the user can sign-in with a password, they can reset their PIN by clicking the "I forgot my PIN" link in settings. Beginning with the Fall Creators Update, users can reset their PIN above the lock screen by clicking the "I forgot my PIN" link on the PIN credential provider.
|
||||
If the user can sign-in with a password, they can reset their PIN by clicking the "I forgot my PIN" link in settings. Beginning with Windows 10 1709, users can reset their PIN above the lock screen by clicking the "I forgot my PIN" link on the PIN credential provider.
|
||||
|
||||
[Windows Hello for Business forgotten PIN user experience](hello-videos.md#windows-hello-for-business-forgotten-pin-user-experience)
|
||||
|
||||
For on-premises deployments, devices must be well connected to their on-premises network (domain controllers and/or certificate authority) to reset their PINs. Hybrid customers can on-board their Azure tenant to use the Windows Hello for Business PIN reset service to reset their PINs without access to their corporate network.
|
||||
For on-premises deployments, devices must be well-connected to their on-premises network (domain controllers and/or certificate authority) to reset their PINs. Hybrid customers can on-board their Azure tenant to use the Windows Hello for Business PIN reset service to reset their PINs without access to their corporate network.
|
||||
|
||||
## What URLs do I need to allow for a hybrid deployment?
|
||||
Communicating with Azure Active Directory uses the following URLs:
|
||||
@ -88,11 +88,12 @@ Windows Hello for Business has two types of PIN reset: non-destructive and destr
|
||||
Organizations that have the on-premises deployment of Windows Hello for Business, or those not using Windows 10 Enterprise can use destructive PIN reset. with destructive PIN reset, users that have forgotten their PIN can authenticate using their password, perform a second factor of authentication to re-provision their Windows Hello for Business credential. Re-provisioning deletes the old credential and requests a new credential and certificate. On-premises deployments need network connectivity to their domain controllers, Active Directory Federation Services, and their issuing certificate authority to perform a destructive PIN reset. Also, for hybrid deployments, destructive PIN reset is only supported with the certificate trust model and the latest updates to Active Directory Federation Services.
|
||||
|
||||
## Which is better or more secure: Key trust or Certificate trust?
|
||||
The trust models of your deployment determine how you authenticate to Active Directory (on-premises). Both key trust and certificate trust use the same hardware backed, two-factor credential. The difference between the two trust types are:
|
||||
The trust models of your deployment determine how you authenticate to Active Directory (on-premises). Both key trust and certificate trust use the same hardware-backed, two-factor credential. The difference between the two trust types are:
|
||||
- Required domain controllers
|
||||
- Issuing end entity certificates
|
||||
|
||||
The **key trust** model authenticates to Active Directory using a raw key. Windows Server 2016 domain controllers enables this authentication. Key trust authenticate does not require an enterprise issued certificate, therefore you do not need to issue certificates to your end users (domain controller certificates are still needed).
|
||||
|
||||
The **certificate trust** model authenticates to Active Directory using a certificate. Because this authentication uses a certificate, domain controllers running previous versions of Windows Server can authenticate the user. Therefore, you need to issue certificates to your end users, but you do not need Windows Server 2016 domain controllers. The certificate used in certificate trust uses the TPM protected private key to request a certificate from your enterprise's issuing certificate authority.
|
||||
|
||||
## Do I need Windows Server 2016 domain controllers?
|
||||
@ -102,7 +103,7 @@ There are many deployment options from which to choose. Some of those options re
|
||||
Review [Azure AD Connect sync: Attributes synchronized to Azure Active Directory](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnectsync-attributes-synchronized) for a list of attributes that are sync based on scenarios. The base scenarios that include Windows Hello for Business are [Windows 10](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnectsync-attributes-synchronized#windows-10) scenario and the [Device writeback](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnectsync-attributes-synchronized#device-writeback) scenario. Your environment may include additional attributes.
|
||||
|
||||
## Is Windows Hello for Business multifactor authentication?
|
||||
Windows Hello for Business is two-factor authentication based the observed authentication factors of: something you have, something you know, and something part of you. Windows Hello for Business incorporates two of these factors: something you have (the user's private key protected by the device's security module) and something you know (your PIN). With the proper hardware, you can enhance the user experience by introducing biometrics. Using biometrics, you can replace the "something you know" authentication factor with the "something that is part of you" factor, with the assurances that users can fall back to the "something you know factor".
|
||||
Windows Hello for Business is two-factor authentication based on the observed authentication factors of: something you have, something you know, and something part of you. Windows Hello for Business incorporates two of these factors: something you have (the user's private key protected by the device's security module) and something you know (your PIN). With the proper hardware, you can enhance the user experience by introducing biometrics. Using biometrics, you can replace the "something you know" authentication factor with the "something that is part of you" factor, with the assurances that users can fall back to the "something you know factor".
|
||||
|
||||
## What are the biometric requirements for Windows Hello for Business?
|
||||
Read [Windows Hello biometric requirements](https://docs.microsoft.com/windows-hardware/design/device-experiences/windows-hello-biometric-requirements) for more information.
|
||||
|
@ -43,18 +43,20 @@ Before you can remotely reset PINs, you must on-board the Microsoft PIN reset se
|
||||
|
||||
### Connect Azure Active Directory with the PIN reset service
|
||||
|
||||
1. Go to the [Microsoft PIN Reset Service Production website](https://login.windows.net/common/oauth2/authorize?response_type=code&client_id=b8456c59-1230-44c7-a4a2-99b085333e84&resource=https%3A%2F%2Fgraph.windows.net&redirect_uri=https%3A%2F%2Fcred.microsoft.com&state=e9191523-6c2f-4f1d-a4f9-c36f26f89df0&prompt=admin_consent), and sign in using the tenant administrator account you use to manage your Azure Active Directory tenant.
|
||||
2. After you log in, click **Accept** to give consent for the PIN reset service to access your account.
|
||||
1. Go to the [Microsoft PIN Reset Service Production website](https://login.windows.net/common/oauth2/authorize?response_type=code&client_id=b8456c59-1230-44c7-a4a2-99b085333e84&resource=https%3A%2F%2Fgraph.windows.net&redirect_uri=https%3A%2F%2Fcred.microsoft.com&state=e9191523-6c2f-4f1d-a4f9-c36f26f89df0&prompt=admin_consent), and sign in using the Global administrator account you use to manage your Azure Active Directory tenant.
|
||||
2. After you have logged in, choose **Accept** to give consent for the PIN reset service to access your account.
|
||||

|
||||
3. Go to the [Microsoft PIN Reset Client Production website](https://login.windows.net/common/oauth2/authorize?response_type=code&client_id=9115dd05-fad5-4f9c-acc7-305d08b1b04e&resource=https%3A%2F%2Fcred.microsoft.com%2F&redirect_uri=ms-appx-web%3A%2F%2FMicrosoft.AAD.BrokerPlugin%2F9115dd05-fad5-4f9c-acc7-305d08b1b04e&state=6765f8c5-f4a7-4029-b667-46a6776ad611&prompt=admin_consent), and sign in using the tenant administrator account you use to manage your Azure Active Directory tenant.
|
||||
4. After you log in, click **Accept** to give consent for the PIN reset client to access your account.
|
||||
3. Go to the [Microsoft PIN Reset Client Production website](https://login.windows.net/common/oauth2/authorize?response_type=code&client_id=9115dd05-fad5-4f9c-acc7-305d08b1b04e&resource=https%3A%2F%2Fcred.microsoft.com%2F&redirect_uri=ms-appx-web%3A%2F%2FMicrosoft.AAD.BrokerPlugin%2F9115dd05-fad5-4f9c-acc7-305d08b1b04e&state=6765f8c5-f4a7-4029-b667-46a6776ad611&prompt=admin_consent), and sign in using the Global administrator account you use to manage your Azure Active Directory tenant.
|
||||
4. After you have logged in, choose **Accept** to give consent for the PIN reset client to access your account.
|
||||
|
||||
> [!NOTE]
|
||||
> After you have accepted the PIN reset service and client requests, you will land on a page that states "You do not have permission to view this directory or page." This behavior is expected. Be sure to confirm that the two PIN reset applications are listed for your tenant.
|
||||
|
||||

|
||||
|
||||
5. In the [Azure portal](https://portal.azure.com), verify that the Microsoft PIN Reset Service and Microsoft PIN Reset Client are integrated from the **Enterprise applications** blade. Filter to application status "Enabled" and both Microsoft Pin Reset Service Production and Microsoft Pin Reset Client Production will show up in your tenant.
|
||||

|
||||
|
||||
>[!NOTE]
|
||||
>After you Accept the PIN reset service and client requests, you will land on a page that states "You do not have permission to view this directory or page." This behavior is expected. Be sure to confirm that the two PIN Reset applications are listed for your tenant.
|
||||
|
||||
### Configure Windows devices to use PIN reset using Group Policy
|
||||
|
||||
You configure Windows 10 to use the Microsoft PIN Reset service using the computer configuration portion of a Group Policy object.
|
||||
@ -70,8 +72,8 @@ To configure PIN reset on Windows devices you manage, use an [Intune Windows 10
|
||||
|
||||
#### Create a PIN Reset Device configuration profile using Microsoft Intune
|
||||
|
||||
1. Sign-in to [Azure Portal](https://portal.azure.com) using a tenant administrator account.
|
||||
2. You need your tenant ID to complete the following task. You can discovery your tenant ID viewing the **Properties** of your Azure Active Directory from the Azure Portal. It will be listed under Directory ID. You can also use the following command in a command Window on any Azure AD joined or hybrid Azure AD joined computer.</br>
|
||||
1. Sign-in to [Azure Portal](https://portal.azure.com) using a Global administrator account.
|
||||
2. You need your tenant ID to complete the following task. You can discover your tenant ID by viewing the **Properties** of your Azure Active Directory from the Azure Portal. It will be listed under Directory ID. You can also use the following command in a Command window on any Azure AD-joined or hybrid Azure AD-joined computer.</br>
|
||||
|
||||
```
|
||||
dsregcmd /status | findstr -snip "tenantid"
|
||||
@ -86,9 +88,9 @@ To configure PIN reset on Windows devices you manage, use an [Intune Windows 10
|
||||
|
||||
#### Assign the PIN Reset Device configuration profile using Microsoft Intune
|
||||
|
||||
1. Sign-in to [Azure Portal](https://portal.azure.com) using a tenant administrator account.
|
||||
2. Navigate to the Microsoft Intune blade. Click **Device configuration**. Click **Profiles**. From the list of device configuration profiles, click the profile that contains the PIN reset configuration.
|
||||
3. In the device configuration profile, click **Assignments**.
|
||||
1. Sign in to the [Azure Portal](https://portal.azure.com) using a Global administrator account.
|
||||
2. Navigate to the Microsoft Intune blade. Choose **Device configuration** > **Profiles**. From the list of device configuration profiles, choose the profile that contains the PIN reset configuration.
|
||||
3. In the device configuration profile, select **Assignments**.
|
||||
4. Use the **Include** and/or **Exclude** tabs to target the device configuration profile to select groups.
|
||||
|
||||
## On-premises Deployments
|
||||
|
@ -644,28 +644,28 @@ Sign-in a workstation with access equivalent to a _domain user_.
|
||||
3. Select **Device Configuration**, and then click **Profiles**.
|
||||
4. Select **Create Profile**.
|
||||

|
||||
5. Next to **Name**, type **WHFB Certificate Enrollment**.
|
||||
6. Next to **Description**, provide a description meaningful for your environment.
|
||||
7. Select **Windows 10 and later** from the **Platform** list.
|
||||
8. Select **SCEP certificate** from the **Profile** list.
|
||||

|
||||
9. The **SCEP Certificate** blade should open. Configure **Certificate validity period** to match your organization.
|
||||
5. Select **Windows 10 and later** from the **Platform** list.
|
||||
6. Choose **SCEP certificate** from the **Profile** list, and select **Create**.
|
||||
7. The **SCEP Certificate** wizard should open. Next to **Name**, type **WHFB Certificate Enrollment**.
|
||||
8. Next to **Description**, provide a description meaningful for your environment, then select **Next**.
|
||||
9. Select **User** as a certificate type.
|
||||
10. Configure **Certificate validity period** to match your organization.
|
||||
> [!IMPORTANT]
|
||||
> Remember that you need to configure your certificate authority to allow Microsoft Intune to configure certificate validity.
|
||||
> Remember that you need to configure your certificate authority to allow Microsoft Intune to configure certificate validity.
|
||||
|
||||
10. Select **Enroll to Windows Hello for Business, otherwise fail (Windows 10 and later)** from the **Key storage provider (KSP)** list.
|
||||
11. Select **Custom** from the **Subject name format** list.
|
||||
12. Next to **Custom**, type **CN={{OnPrem_Distinguished_Name}}** to make the on-premises distinguished name the subject of the issued certificate.
|
||||
13. Specify **User Principal Name (UPN)** as a **Subject Alternative Name** value.
|
||||
14. Refer to the "Configure Certificate Templates on NDES" task for how you configured the **AADJ WHFB Authentication** certificate template in the registry. Select the appropriate combination of key usages from the **Key Usages** list that map to configured NDES template in the registry. In this example, the **AADJ WHFB Authentication** certificate template was added to the **SignatureTemplate** registry value name. The **Key usage** that maps to that registry value name is **Digital Signature**.
|
||||
15. Select a previously configured **Trusted certificate** profile that matches the root certificate of the issuing certificate authority.
|
||||
11. Select **Enroll to Windows Hello for Business, otherwise fail (Windows 10 and later)** from the **Key storage provider (KSP)** list.
|
||||
12. Select **Custom** from the **Subject name format** list.
|
||||
13. Next to **Custom**, type **CN={{OnPrem_Distinguished_Name}}** to make the on-premises distinguished name the subject of the issued certificate.
|
||||
14. Specify **User Principal Name (UPN)** as a **Subject Alternative Name** value.
|
||||
15. Refer to the "Configure Certificate Templates on NDES" task for how you configured the **AADJ WHFB Authentication** certificate template in the registry. Select the appropriate combination of key usages from the **Key Usages** list that map to configured NDES template in the registry. In this example, the **AADJ WHFB Authentication** certificate template was added to the **SignatureTemplate** registry value name. The **Key usage** that maps to that registry value name is **Digital Signature**.
|
||||
16. Select a previously configured **Trusted certificate** profile that matches the root certificate of the issuing certificate authority.
|
||||

|
||||
16. Under **Extended key usage**, type **Smart Card Logon** under **Name**. Type **1.3.6.1.4.1.311.20.2.2** under **Object identifier**. Click **Add**.
|
||||
17. Type a percentage (without the percent sign) next to **Renewal Threshold** to determine when the certificate should attempt to renew. The recommended value is **20**.
|
||||
17. Under **Extended key usage**, type **Smart Card Logon** under **Name**. Type **1.3.6.1.4.1.311.20.2.2** under **Object identifier**. Click **Add**.
|
||||
18. Type a percentage (without the percent sign) next to **Renewal Threshold** to determine when the certificate should attempt to renew. The recommended value is **20**.
|
||||

|
||||
18. Under **SCEP Server URLs**, type the fully qualified external name of the Azure AD Application proxy you configured. Append to the name **/certsrv/mscep/mscep.dll**. For example, https://ndes-mtephendemo.msappproxy.net/certsrv/mscep/mscep.dll. Click **Add**. Repeat this step for each additional NDES Azure AD Application Proxy you configured to issue Windows Hello for Business certificates. Microsoft Intune round-robin load balances requests among the URLs listed in the SCEP certificate profile.
|
||||
19. Click **OK**.
|
||||
20. Click **Create**.
|
||||
19. Under **SCEP Server URLs**, type the fully qualified external name of the Azure AD Application proxy you configured. Append to the name **/certsrv/mscep/mscep.dll**. For example, https://ndes-mtephendemo.msappproxy.net/certsrv/mscep/mscep.dll. Click **Add**. Repeat this step for each additional NDES Azure AD Application Proxy you configured to issue Windows Hello for Business certificates. Microsoft Intune round-robin load balances requests among the URLs listed in the SCEP certificate profile.
|
||||
20. Click **Next**.
|
||||
21. Click **Next** two more times to skip the **Scope tags** and **Assignments** steps of the wizard and click **Create**.
|
||||
|
||||
### Assign Group to the WHFB Certificate Enrollment Certificate Profile
|
||||
Sign-in a workstation with access equivalent to a _domain user_.
|
||||
|
@ -15,40 +15,42 @@ manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 10/18/2017
|
||||
ms.date: 4/16/2017
|
||||
---
|
||||
|
||||
# Manage Windows Hello for Business in your organization
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 10
|
||||
|
||||
You can create a Group Policy or mobile device management (MDM) policy that will implement Windows Hello on devices running Windows 10.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>The Group Policy setting **Turn on PIN sign-in** does not apply to Windows Hello for Business. It still prevents or enables the creation of a convenience PIN for Windows 10, version 1507 and 1511.
|
||||
>The Group Policy setting **Turn on PIN sign-in** does not apply to Windows Hello for Business. It still prevents or enables the creation of a convenience PIN for Windows 10, version 1507 and 1511.
|
||||
>
|
||||
>Beginning in version 1607, Windows Hello as a convenience PIN is disabled by default on all domain-joined computers. To enable a convenience PIN for Windows 10, version 1607, enable the Group Policy setting **Turn on convenience PIN sign-in**.
|
||||
>Beginning in version 1607, Windows Hello as a convenience PIN is disabled by default on all domain-joined computers. To enable a convenience PIN for Windows 10, version 1607, enable the Group Policy setting **Turn on convenience PIN sign-in**.
|
||||
>
|
||||
>Use **PIN Complexity** policy settings to manage PINs for Windows Hello for Business.
|
||||
|
||||
|
||||
## Group Policy settings for Windows Hello for Business
|
||||
|
||||
The following table lists the Group Policy settings that you can configure for Windows Hello use in your workplace. These policy settings are available in both **User configuration** and **Computer Configuration** under **Policies** > **Administrative Templates** > **Windows Components** > **Windows Hello for Business**.
|
||||
The following table lists the Group Policy settings that you can configure for Windows Hello use in your workplace. These policy settings are available in **User configuration** and **Computer Configuration** under **Policies** > **Administrative Templates** > **Windows Components** > **Windows Hello for Business**.
|
||||
|
||||
> [!NOTE]
|
||||
> Starting with Windows 10, version 1709, the location of the PIN complexity section of the Group Policy is: **Computer Configuration** > **Administrative Templates** > **System** > **PIN Complexity**.
|
||||
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<th colspan="2">Policy</th>
|
||||
<th>Scope</th>
|
||||
<th>Options</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Use Windows Hello for Business</td>
|
||||
<td></td>
|
||||
<td>Computer or user</td>
|
||||
<td>
|
||||
<p><b>Not configured</b>: Users can provision Windows Hello for Business, which encrypts their domain password.</p>
|
||||
<p><b>Not configured</b>: Device does not provision Windows Hello for Business for any user.</p>
|
||||
<p><b>Enabled</b>: Device provisions Windows Hello for Business using keys or certificates for all users.</p>
|
||||
<p><b>Disabled</b>: Device does not provision Windows Hello for Business for any user.</p>
|
||||
</td>
|
||||
@ -56,15 +58,41 @@ The following table lists the Group Policy settings that you can configure for W
|
||||
<tr>
|
||||
<td>Use a hardware security device</td>
|
||||
<td></td>
|
||||
<td>Computer</td>
|
||||
<td>
|
||||
<p><b>Not configured</b>: Windows Hello for Business will be provisioned using TPM if available, and will be provisioned using software if TPM is not available.</p>
|
||||
<p><b>Enabled</b>: Windows Hello for Business will only be provisioned using TPM.</p>
|
||||
<p><b>Enabled</b>: Windows Hello for Business will only be provisioned using TPM. This feature will provision Windows Hello for Business using TPM 1.2 unless the option to exclude them is explicitly set.</p>
|
||||
<p><b>Disabled</b>: Windows Hello for Business will be provisioned using TPM if available, and will be provisioned using software if TPM is not available.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Use certificate for on-premises authentication</td>
|
||||
<td></td>
|
||||
<td>Computer or user</td>
|
||||
<td>
|
||||
<p><b>Not configured</b>: Windows Hello for Business enrolls a key that is used for on-premises authentication.</p>
|
||||
<p><b>Enabled</b>: Windows Hello for Business enrolls a sign-in certificate using ADFS that is used for on-premises authentication.</p>
|
||||
<p><b>Disabled</b>: Windows Hello for Business enrolls a key that is used for on-premises authentication.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<td>Use PIN recovery</td>
|
||||
<td></td>
|
||||
<td>Computer</td>
|
||||
<td>
|
||||
<p>Added in Windows 10, version 1703</p>
|
||||
<p><b>Not configured</b>: Windows Hello for Business does not create or store a PIN recovery secret. PIN reset does not use the Azure-based PIN recovery service.</p>
|
||||
<p><b>Enabled</b>: Windows Hello for Business uses the Azure-based PIN recovery service for PIN reset.</p>
|
||||
<p><b>Disabled</b>: Windows Hello for Business does not create or store a PIN recovery secret. PIN reset does not use the Azure-based PIN recovery service.</p>
|
||||
<p>
|
||||
|
||||
For more information about using the PIN recovery service for PIN reset see [Windows Hello for Business PIN Reset](hello-feature-pin-reset.md).
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Use biometrics</td>
|
||||
<td></td>
|
||||
<td>Computer</td>
|
||||
<td>
|
||||
<p><b>Not configured</b>: Biometrics can be used as a gesture in place of a PIN.</p>
|
||||
<p><b>Enabled</b>: Biometrics can be used as a gesture in place of a PIN.</p>
|
||||
@ -74,6 +102,7 @@ The following table lists the Group Policy settings that you can configure for W
|
||||
<tr>
|
||||
<td rowspan="8">PIN Complexity</td>
|
||||
<td>Require digits</td>
|
||||
<td>Computer</td>
|
||||
<td>
|
||||
<p><b>Not configured</b>: Users must include a digit in their PIN.</p>
|
||||
<p><b>Enabled</b>: Users must include a digit in their PIN.</p>
|
||||
@ -82,6 +111,7 @@ The following table lists the Group Policy settings that you can configure for W
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Require lowercase letters</td>
|
||||
<td>Computer</td>
|
||||
<td>
|
||||
<p><b>Not configured</b>: Users cannot use lowercase letters in their PIN.</p>
|
||||
<p><b>Enabled</b>: Users must include at least one lowercase letter in their PIN.</p>
|
||||
@ -90,6 +120,7 @@ The following table lists the Group Policy settings that you can configure for W
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Maximum PIN length</td>
|
||||
<td>Computer</td>
|
||||
<td>
|
||||
<p><b>Not configured</b>: PIN length must be less than or equal to 127.</p>
|
||||
<p><b>Enabled</b>: PIN length must be less than or equal to the number you specify.</p>
|
||||
@ -98,6 +129,7 @@ The following table lists the Group Policy settings that you can configure for W
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Minimum PIN length</td>
|
||||
<td>Computer</td>
|
||||
<td>
|
||||
<p><b>Not configured</b>: PIN length must be greater than or equal to 4.</p>
|
||||
<p><b>Enabled</b>: PIN length must be greater than or equal to the number you specify.</p>
|
||||
@ -106,6 +138,7 @@ The following table lists the Group Policy settings that you can configure for W
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Expiration</td>
|
||||
<td>Computer</td>
|
||||
<td>
|
||||
<p><b>Not configured</b>: PIN does not expire.</p>
|
||||
<p><b>Enabled</b>: PIN can be set to expire after any number of days between 1 and 730, or PIN can be set to never expire by setting policy to 0.</p>
|
||||
@ -114,6 +147,7 @@ The following table lists the Group Policy settings that you can configure for W
|
||||
</tr>
|
||||
<tr>
|
||||
<td>History</td>
|
||||
<td>Computer</td>
|
||||
<td>
|
||||
<p><b>Not configured</b>: Previous PINs are not stored.</p>
|
||||
<p><b>Enabled</b>: Specify the number of previous PINs that can be associated to a user account that can't be reused.</p>
|
||||
@ -124,6 +158,7 @@ The following table lists the Group Policy settings that you can configure for W
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Require special characters</td>
|
||||
<td>Computer</td>
|
||||
<td>
|
||||
<p><b>Not configured</b>: Users cannot include a special character in their PIN.</p>
|
||||
<p><b>Enabled</b>: Users must include at least one special character in their PIN.</p>
|
||||
@ -132,6 +167,7 @@ The following table lists the Group Policy settings that you can configure for W
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Require uppercase letters</td>
|
||||
<td>Computer</td>
|
||||
<td>
|
||||
<p><b>Not configured</b>: Users cannot include an uppercase letter in their PIN.</p>
|
||||
<p><b>Enabled</b>: Users must include at least one uppercase letter in their PIN.</p>
|
||||
@ -139,9 +175,9 @@ The following table lists the Group Policy settings that you can configure for W
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>>Phone Sign-in</td>
|
||||
<td>
|
||||
<p>Use Phone Sign-in</p>
|
||||
<td>Phone Sign-in</td>
|
||||
<td>Use Phone Sign-in</td>
|
||||
<td>Computer</td>
|
||||
</td>
|
||||
<td>
|
||||
<p>Not currently supported.</p>
|
||||
@ -154,7 +190,7 @@ The following table lists the Group Policy settings that you can configure for W
|
||||
The following table lists the MDM policy settings that you can configure for Windows Hello for Business use in your workplace. These MDM policy settings use the [PassportForWork configuration service provider (CSP)](https://go.microsoft.com/fwlink/p/?LinkId=692070).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Starting in Windows 10, version 1607, all devices only have one PIN associated with Windows Hello for Business. This means that any PIN on a device will be subject to the policies specified in the PassportForWork CSP. The values specified take precedence over any complexity rules set via Exchange ActiveSync (EAS) or the DeviceLock CSP.
|
||||
>Starting in Windows 10, version 1607, all devices only have one PIN associated with Windows Hello for Business. This means that any PIN on a device will be subject to the policies specified in the PassportForWork CSP. The values specified take precedence over any complexity rules set via Exchange ActiveSync (EAS) or the DeviceLock CSP.
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
@ -166,7 +202,7 @@ The following table lists the MDM policy settings that you can configure for Win
|
||||
<tr>
|
||||
<td>UsePassportForWork</td>
|
||||
<td></td>
|
||||
<td>Device</td>
|
||||
<td>Device or user</td>
|
||||
<td>True</td>
|
||||
<td>
|
||||
<p>True: Windows Hello for Business will be provisioned for all users on the device.</p>
|
||||
@ -178,7 +214,7 @@ The following table lists the MDM policy settings that you can configure for Win
|
||||
<tr>
|
||||
<td>RequireSecurityDevice</td>
|
||||
<td></td>
|
||||
<td>Device</td>
|
||||
<td>Device or user</td>
|
||||
<td>False</td>
|
||||
<td>
|
||||
<p>True: Windows Hello for Business will only be provisioned using TPM.</p>
|
||||
@ -186,6 +222,32 @@ The following table lists the MDM policy settings that you can configure for Win
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>ExcludeSecurityDevice</td>
|
||||
<td>TPM12</td>
|
||||
<td>Device</td>
|
||||
<td>False</td>
|
||||
<td>
|
||||
<p>Added in Windows 10, version 1703</p>
|
||||
<p>True: TPM revision 1.2 modules will be disallowed from being used with Windows Hello for Business.</p>
|
||||
<p>False: TPM revision 1.2 modules will be allowed to be used with Windows Hello for Business.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>EnablePinRecovery</td>
|
||||
<td></td>
|
||||
<td>Device or user</td>
|
||||
<td>False</td>
|
||||
<td>
|
||||
<p>Added in Windows 10, version 1703</p>
|
||||
<p>True: Windows Hello for Business uses the Azure-based PIN recovery service for PIN reset.</p>
|
||||
<p>False: Windows Hello for Business does not create or store a PIN recovery secret. PIN reset does not use the Azure-based PIN recovery service.</p>
|
||||
<p>
|
||||
|
||||
For more information about using the PIN recovery service for PIN reset see [Windows Hello for Business PIN Reset](hello-feature-pin-reset.md).
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td rowspan="2">Biometrics</td>
|
||||
<td>
|
||||
<p>UseBiometrics</p>
|
||||
@ -216,19 +278,41 @@ The following table lists the MDM policy settings that you can configure for Win
|
||||
<tr>
|
||||
<td>Digits </td>
|
||||
<td>Device or user</td>
|
||||
<td>2 </td>
|
||||
<td>1 </td>
|
||||
<td>
|
||||
<p>1: Numbers are not allowed. </p>
|
||||
<p>2: At least one number is required.</p>
|
||||
<p>0: Digits are allowed. </p>
|
||||
<p>1: At least one digit is required.</p>
|
||||
<p>2: Digits are not allowed. </p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Lowercase letters </td>
|
||||
<td>Device or user</td>
|
||||
<td>1 </td>
|
||||
<td>2</td>
|
||||
<td>
|
||||
<p>1: Lowercase letters are not allowed. </p>
|
||||
<p>2: At least one lowercase letter is required.</p>
|
||||
<p>0: Lowercase letters are allowed. </p>
|
||||
<p>1: At least one lowercase letter is required.</p>
|
||||
<p>2: Lowercase letters are not allowed. </p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Special characters</td>
|
||||
<td>Device or user</td>
|
||||
<td>2</td>
|
||||
<td>
|
||||
<p>0: Special characters are allowed. </p>
|
||||
<p>1: At least one special character is required. </p>
|
||||
<p>2: Special characters are not allowed.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Uppercase letters</td>
|
||||
<td>Device or user</td>
|
||||
<td>2</td>
|
||||
<td>
|
||||
<p>0: Uppercase letters are allowed. </p>
|
||||
<p>1: At least one uppercase letter is required.</p>
|
||||
<p>2: Uppercase letters are not allowed. </p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -252,7 +336,7 @@ The following table lists the MDM policy settings that you can configure for Win
|
||||
<td>Device or user</td>
|
||||
<td>0</td>
|
||||
<td>
|
||||
<p>Integer value specifies the period of time (in days) that a PIN can be used before the system requires the user to change it. The largest number you can configure for this policy setting is 730. The lowest number you can configure for this policy setting is 0. If this policy is set to 0, then the user’s PIN will never expire.
|
||||
<p>Integer value specifies the period of time (in days) that a PIN can be used before the system requires the user to change it. The largest number you can configure for this policy setting is 730. The lowest number you can configure for this policy setting is 0. If this policy is set to 0, then the user's PIN will never expire.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
@ -261,29 +345,11 @@ The following table lists the MDM policy settings that you can configure for Win
|
||||
<td>Device or user</td>
|
||||
<td>0</td>
|
||||
<td>
|
||||
<p>Integer value that specifies the number of past PINs that can be associated to a user account that can’t be reused. The largest number you can configure for this policy setting is 50. The lowest number you can configure for this policy setting is 0. If this policy is set to 0, then storage of previous PINs is not required.
|
||||
<p>Integer value that specifies the number of past PINs that can be associated to a user account that can't be reused. The largest number you can configure for this policy setting is 50. The lowest number you can configure for this policy setting is 0. If this policy is set to 0, then storage of previous PINs is not required.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Special characters</td>
|
||||
<td>Device or user</td>
|
||||
<td>1</td>
|
||||
<td>
|
||||
<p>1: Special characters are not allowed. </p>
|
||||
<p>2: At least one special character is required.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Uppercase letters</td>
|
||||
<td>Device or user</td>
|
||||
<td>1</td>
|
||||
<td>
|
||||
<p>1: Uppercase letters are not allowed </p>
|
||||
<p>2: At least one uppercase letter is required</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Remote</td>
|
||||
<td>
|
||||
<p>UseRemotePassport</p>
|
||||
@ -297,20 +363,53 @@ The following table lists the MDM policy settings that you can configure for Win
|
||||
</table>
|
||||
|
||||
>[!NOTE]
|
||||
> If policy is not configured to explicitly require letters or special characters, users will be restricted to creating a numeric PIN.
|
||||
|
||||
> In Windows 10, version 1709 and later, if policy is not configured to explicitly require letters or special characters, users can optionally set an alphanumeric PIN. Prior to version 1709 the user is required to set a numeric PIN.
|
||||
|
||||
## Policy conflicts from multiple policy sources
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
>[!NOTE]
|
||||
> Windows Hello for Business policy conflict resolution logic does not respect the ControlPolicyConflict/MDMWinsOverGP policy in the Policy CSP.
|
||||
|
||||
><b>Examples</b>
|
||||
>
|
||||
>The following are configured using computer Group Policy:
|
||||
>
|
||||
>- 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:
|
||||
>
|
||||
>- UsePassportForWork - Disabled
|
||||
>- UseCertificateForOnPremAuth - Disabled
|
||||
>- MinimumPINLength - 8
|
||||
>- Digits - 1
|
||||
>- LowercaseLetters - 1
|
||||
>- SpecialCharacters - 1
|
||||
>
|
||||
>Enforced policy set:
|
||||
>
|
||||
>- Use Windows Hello for Business - Enabled
|
||||
>- Use certificate for on-premises authentication - Enabled
|
||||
>- Require digits - Enabled
|
||||
>- Minimum PIN length - 6d
|
||||
|
||||
## How to use Windows Hello for Business with Azure Active Directory
|
||||
|
||||
There are three scenarios for using Windows Hello for Business in Azure AD–only organizations:
|
||||
There are three scenarios for using Windows Hello for Business in Azure AD–only organizations:
|
||||
|
||||
- **Organizations that use the version of Azure AD included with Office 365**. For these organizations, no additional work is necessary. When Windows 10 was released to general availability, Microsoft changed the behavior of the Office 365 Azure AD stack. When a user selects the option to join a work or school network, the device is automatically joined to the Office 365 tenant’s directory partition, a certificate is issued for the device, and it becomes eligible for Office 365 MDM if the tenant has subscribed to that feature. In addition, the user will be prompted to log on and, if MFA is enabled, to enter an MFA proof that Azure AD sends to his or her phone.
|
||||
- **Organizations that use the free tier of Azure AD**. For these organizations, Microsoft has not enabled automatic domain join to Azure AD. Organizations that have signed up for the free tier have the option to enable or disable this feature, so automatic domain join won’t be enabled unless and until the organization’s administrators decide to enable it. When that feature is enabled, devices that join the Azure AD domain by using the Connect to work or school dialog box will be automatically registered with Windows Hello for Business support, but previously joined devices will not be registered.
|
||||
- **Organizations that use the version of Azure AD included with Office 365**. For these organizations, no additional work is necessary. When Windows 10 was released to general availability, Microsoft changed the behavior of the Office 365 Azure AD stack. When a user selects the option to join a work or school network, the device is automatically joined to the Office 365 tenant's directory partition, a certificate is issued for the device, and it becomes eligible for Office 365 MDM if the tenant has subscribed to that feature. In addition, the user will be prompted to log on and, if MFA is enabled, to enter an MFA proof that Azure AD sends to his or her phone.
|
||||
- **Organizations that use the free tier of Azure AD**. For these organizations, Microsoft has not enabled automatic domain join to Azure AD. Organizations that have signed up for the free tier have the option to enable or disable this feature, so automatic domain join won't be enabled unless and until the organization's administrators decide to enable it. When that feature is enabled, devices that join the Azure AD domain by using the Connect to work or school dialog box will be automatically registered with Windows Hello for Business support, but previously joined devices will not be registered.
|
||||
- **Organizations that have subscribed to Azure AD Premium** have access to the full set of Azure AD MDM features. These features include controls to manage Windows Hello for Business. You can set policies to disable or force the use of Windows Hello for Business, require the use of a TPM, and control the length and strength of PINs set on the device.
|
||||
|
||||
If you want to use Windows Hello for Business with certificates, you’ll need a device registration system. That means that you set up Configuration Manager, Microsoft Intune, or a compatible non-Microsoft MDM system and enable it to enroll devices. This is a prerequisite step to use Windows Hello for Business with certificates, no matter the IDP, because the enrollment system is responsible for provisioning the devices with the necessary certificates.
|
||||
|
||||
|
||||
If you want to use Windows Hello for Business with certificates, you'll need a device registration system. That means that you set up Configuration Manager, Microsoft Intune, or a compatible non-Microsoft MDM system and enable it to enroll devices. This is a prerequisite step to use Windows Hello for Business with certificates, no matter the IDP, because the enrollment system is responsible for provisioning the devices with the necessary certificates.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
@ -16,8 +16,8 @@ ms.author: dansimp
|
||||
# VPN security features
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
|
||||
|
||||
## LockDown VPN
|
||||
@ -29,53 +29,52 @@ A VPN profile configured with LockDown secures the device to only allow network
|
||||
- The user cannot delete or modify the VPN profile.
|
||||
- The VPN LockDown profile uses forced tunnel connection.
|
||||
- If the VPN connection is not available, outbound network traffic is blocked.
|
||||
- Only one VPN LockDown profile is allowed on a device.
|
||||
- Only one VPN LockDown profile is allowed on a device.
|
||||
|
||||
>[!NOTE]
|
||||
>For built-in VPN, Lockdown VPN is only available for the Internet Key Exchange version 2 (IKEv2) connection type.
|
||||
|
||||
Deploy this feature with caution as the resultant connection will not be able to send or receive any network traffic without the VPN being connected.
|
||||
> [!NOTE]
|
||||
> For built-in VPN, LockDown VPN is only available for the Internet Key Exchange version 2 (IKEv2) connection type.
|
||||
|
||||
Deploy this feature with caution, as the resultant connection will not be able to send or receive any network traffic without the VPN being connected.
|
||||
|
||||
|
||||
## Windows Information Protection (WIP) integration with VPN
|
||||
|
||||
Windows Information Protection provides capabilities allowing the separation and protection of enterprise data against disclosure across both company and personally owned devices without requiring additional changes to the environments or the apps themselves. Additionally, when used with Rights Management Services (RMS), WIP can help to protect enterprise data locally.
|
||||
Windows Information Protection provides capabilities allowing the separation and protection of enterprise data against disclosure across both company and personally owned devices, without requiring additional changes to the environments or the apps themselves. Additionally, when used with Rights Management Services (RMS), WIP can help to protect enterprise data locally.
|
||||
|
||||
The **EdpModeId** node in the [VPNv2 Configuration Service Provider (CSP)](https://msdn.microsoft.com/library/windows/hardware/dn914776.aspx) allows a Windows 10 VPN client to integrate with WIP, extending its functionality to remote devices. Use case scenarios for WIP include:
|
||||
The **EdpModeId** node in the [VPNv2 Configuration Service Provider (CSP)](https://docs.microsoft.com/windows/client-management/mdm/vpnv2-csp) allows a Windows 10 VPN client to integrate with WIP, extending its functionality to remote devices. Use case scenarios for WIP include:
|
||||
|
||||
- Core functionality: File encryption and file access blocking
|
||||
- UX policy enforcement: Restricting copy/paste, drag/drop, and sharing operations
|
||||
- WIP network policy enforcement: Protecting intranet resources over the corporate network and VPN
|
||||
- Network policy enforcement: Protecting SMB and Internet cloud resources over the corporate network and VPN
|
||||
|
||||
The value of the **EdpModeId** is an Enterprise ID. The networking stack will look for this ID in the app token to determine whether VPN should be triggered for that particular app.
|
||||
The value of the **EdpModeId** is an Enterprise ID. The networking stack will look for this ID in the app token to determine whether VPN should be triggered for that particular app.
|
||||
|
||||
Additionally, when connecting with WIP, the admin does not have to specify AppTriggerList and TrafficFilterList rules separately in this profile (unless more advanced configuration is needed) because the WIP policies and App lists automatically take effect.
|
||||
|
||||
[Learn more about Windows Information Protection](/windows/threat-protection/windows-information-protection/protect-enterprise-data-using-wip)
|
||||
|
||||
|
||||
## Traffic filters
|
||||
## Traffic Filters
|
||||
|
||||
Traffic Filters give enterprises the ability to decide what traffic is allowed into the corporate network based on policy. Network admins to effectively add interface specific firewall rules on the VPN Interface.There are two types of Traffic Filter rules:
|
||||
Traffic Filters give enterprises the ability to decide what traffic is allowed into the corporate network based on policy. Network admins can use Traffic Filters to effectively add interface specific firewall rules on the VPN Interface. There are two types of Traffic Filter rules:
|
||||
|
||||
- App-based rules. With app-based rules, a list of applications can be marked such that only traffic originating from these apps is allowed to go over the VPN interface.
|
||||
- Traffic-based rules. Traffic-based rules are 5-tuple policies (ports, addresses, protocol) that can be specified such that only traffic matching these rules is allowed to go over the VPN interface.
|
||||
- App-based rules. With app-based rules, a list of applications can be marked to allow only traffic originating from these apps to go over the VPN interface.
|
||||
- Traffic-based rules. Traffic-based rules are 5-tuple policies (ports, addresses, protocol) that can be specified to allow only traffic matching these rules to go over the VPN interface.
|
||||
|
||||
There can be many sets of rules which are linked by OR. Within each set, there can be app-based rules and traffic-based rules; all the properties within the set will be linked by AND. In addition, these rules can be applied at a per-app level or a per-device level.
|
||||
There can be many sets of rules which are linked by OR. Within each set, there can be app-based rules and traffic-based rules; all the properties within the set will be linked by AND. In addition, these rules can be applied at a per-app level or a per-device level.
|
||||
|
||||
For example, an admin could define rules that specify:
|
||||
For example, an admin could define rules that specify:
|
||||
|
||||
- The Contoso HR App must be allowed to go through the VPN and only access port 4545.
|
||||
- The Contoso finance apps is allowed to go over the VPN and only access the Remote IP ranges of 10.10.0.40 - 10.10.0.201 on port 5889.
|
||||
- All other apps on the device should be able to access only ports 80 or 443.
|
||||
- The Contoso HR App must be allowed to go through the VPN and only access port 4545.
|
||||
- The Contoso finance apps are allowed to go over the VPN and only access the Remote IP ranges of 10.10.0.40 - 10.10.0.201 on port 5889.
|
||||
- All other apps on the device should be able to access only ports 80 or 443.
|
||||
|
||||
## Configure traffic filters
|
||||
|
||||
See [VPN profile options](vpn-profile-options.md) and [VPNv2 CSP](https://msdn.microsoft.com/library/windows/hardware/dn914776.aspx) for XML configuration.
|
||||
See [VPN profile options](vpn-profile-options.md) and [VPNv2 CSP](https://docs.microsoft.com/windows/client-management/mdm/vpnv2-csp) for XML configuration.
|
||||
|
||||
The following image shows the interface to configure traffic rules in a VPN Profile configuration policy using Microsoft Intune.
|
||||
The following image shows the interface to configure traffic rules in a VPN Profile configuration policy, using Microsoft Intune.
|
||||
|
||||

|
||||
|
||||
|
@ -53,7 +53,7 @@ Microsoft has made a concerted effort to enlighten several of our more popular a
|
||||
|
||||
- Mobile Office apps, including Word, Excel, PowerPoint, OneNote, and Outlook Mail and Calendar
|
||||
|
||||
- Office 365 ProPlus apps, including Word, Excel, PowerPoint, OneNote, and Outlook
|
||||
- Microsoft 365 Apps for enterprise apps, including Word, Excel, PowerPoint, OneNote, and Outlook
|
||||
|
||||
- OneDrive app
|
||||
|
||||
@ -99,7 +99,7 @@ You can add any or all of the enlightened Microsoft apps to your allowed apps li
|
||||
| PowerPoint Mobile | **Publisher:** `CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US`<br>**Product Name:** Microsoft.Office.PowerPoint<br>**App Type:** Universal app |
|
||||
| OneNote | **Publisher:** `CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US`<br>**Product Name:** Microsoft.Office.OneNote<br>**App Type:** Universal app |
|
||||
| Outlook Mail and Calendar | **Publisher:** `CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US`<br>**Product Name:** microsoft.windowscommunicationsapps<br>**App Type:** Universal app |
|
||||
| Office 365 ProPlus and Office 2019 Professional Plus | Office 365 ProPlus and Office 2019 Professional Plus apps are set up as a suite. You must use the [O365 ProPlus - Allow and Exempt AppLocker policy files (.zip files)](https://download.microsoft.com/download/7/0/D/70D72459-D72D-4673-B309-F480E3BEBCC9/O365%20ProPlus%20-%20WIP%20Enterprise%20AppLocker%20Policy%20Files.zip) to turn the suite on for WIP.<br>We don't recommend setting up Office by using individual paths or publisher rules. |
|
||||
| Microsoft 365 Apps for enterprise and Office 2019 Professional Plus | Microsoft 365 Apps for enterprise and Office 2019 Professional Plus apps are set up as a suite. You must use the [O365 ProPlus - Allow and Exempt AppLocker policy files (.zip files)](https://download.microsoft.com/download/7/0/D/70D72459-D72D-4673-B309-F480E3BEBCC9/O365%20ProPlus%20-%20WIP%20Enterprise%20AppLocker%20Policy%20Files.zip) to turn the suite on for WIP.<br>We don't recommend setting up Office by using individual paths or publisher rules. |
|
||||
| Microsoft Photos | **Publisher:** `CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US`<br>**Product Name:** Microsoft.Windows.Photos<br>**App Type:** Universal app |
|
||||
| Groove Music | **Publisher:** `CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US`<br>**Product Name:** Microsoft.ZuneMusic<br>**App Type:** Universal app |
|
||||
| Microsoft Movies & TV | **Publisher:** `CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US`<br>**Product Name:** Microsoft.ZuneVideo<br>**App Type:** Universal app |
|
||||
|
@ -1,122 +0,0 @@
|
||||
---
|
||||
title: How Windows Information Protection (WIP) protects files with a sensitivity label (Windows 10)
|
||||
description: Explains how Windows Information Protection works with other Microsoft information protection technologies to protect files that have a sensitivity label.
|
||||
keywords: sensitivity, labels, WIP, Windows Information Protection, EDP, Enterprise Data Protection
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: dulcemontemayor
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/30/2019
|
||||
ms.reviewer:
|
||||
---
|
||||
|
||||
# How Windows Information Protection (WIP) protects a file that has a sensitivity label
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Windows Defender Advanced Threat Protection (Windows Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
- Windows 10, version 1903
|
||||
- Windows 10, version 1809
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
|
||||
|
||||
This topic explains how Windows Information Protection works with other Microsoft information protection technologies to protect files that have a sensitivity label.
|
||||
Microsoft information protection technologies work together as an integrated solution to help enterprises:
|
||||
|
||||
- Discover corporate data on endpoint devices
|
||||
- Classify and label information based on its content and context
|
||||
- Protect corporate data from unintentionally leaving to non-business environments
|
||||
- Enable audit reports of user interactions with corporate data on endpoint devices
|
||||
|
||||
Microsoft information protection technologies include:
|
||||
|
||||
- [Windows Information Protection (WIP)](protect-enterprise-data-using-wip.md) is built in to Windows 10 and protects local data at rest on endpoint devices, and manages apps to protect local data in use. Data that leaves the endpoint device, such as email attachment, is not protected by WIP.
|
||||
|
||||
- [Azure Information Protection](https://docs.microsoft.com/azure/information-protection/what-is-information-protection) is a cloud-based solution that can be purchased either standalone or as part of Microsoft 365 Enterprise. It helps an organization classify and protect its documents and emails by applying labels. Azure Information Protection is applied directly to content, and roams with the content as it's moved between locations and cloud services.
|
||||
|
||||
- [Microsoft Cloud App Security](https://docs.microsoft.com/cloud-app-security/what-is-cloud-app-security) is a cloud access security broker (CASB) solution that allows you to discover, classify, protect, and monitor user data in first-party and third-party Software-as-a-Service (SaaS) apps used by your organization.
|
||||
|
||||
## How WIP protects sensitivity labels with endpoint data loss prevention
|
||||
|
||||
You can create and manage [sensitivity labels](https://docs.microsoft.com/office365/securitycompliance/labels) in the Microsoft 365 compliance center.
|
||||
When you [create a sensitivity label](https://docs.microsoft.com/microsoft-365/compliance/create-sensitivity-labels), you can specify that endpoint data loss prevention applies to content with that label.
|
||||
|
||||

|
||||
|
||||
Office app users can choose a sensitivity label from a menu and apply it to a file.
|
||||
|
||||

|
||||
|
||||
WIP enforces default endpoint protection as follows:
|
||||
|
||||
- If endpoint data loss prevention is enabled, the device enforces work protection for any file with the label
|
||||
- If endpoint data loss prevention is not enabled:
|
||||
- The device enforces work protection to a file downloaded from a work site
|
||||
- The device does not enforce work protection to a file downloaded from a personal site
|
||||
|
||||
Here's an example where a file remains protected without any work context beyond the sensitivity label:
|
||||
|
||||
1. Sara creates a PDF file on a Mac and labels it as **Confidential**.
|
||||
1. She emails the PDF from her Gmail account to Laura.
|
||||
1. Laura opens the PDF file on her Windows 10 device.
|
||||
1. Windows Defender Advanced Threat Protection (Windows Defender ATP) scans Windows 10 for any file that gets modified or created, including files that were created on a personal site.
|
||||
1. Windows Defender ATP triggers WIP policy.
|
||||
1. WIP policy protects the file even though it came from a personal site.
|
||||
|
||||
## How WIP protects automatically classified files
|
||||
|
||||
The next sections cover how Windows Defender ATP extends discovery and protection of sensitive information with improvements in Windows 10 version 1903.
|
||||
|
||||
### Discovery
|
||||
|
||||
Windows Defender ATP can extract the content of the file itself and evaluate whether it contains sensitive information types such as credit card numbers or employee ID numbers.
|
||||
When you create a sensitivity label, you can specify that the label be added to any file that contains a sensitive information type.
|
||||
|
||||

|
||||
|
||||
A default set of [sensitive information types](https://docs.microsoft.com/office365/securitycompliance/what-the-sensitive-information-types-look-for) in Microsoft 365 compliance center includes credit card numbers, phone numbers, driver's license numbers, and so on.
|
||||
You can also [create a custom sensitive information type](https://docs.microsoft.com/office365/securitycompliance/create-a-custom-sensitive-information-type), which can include any keyword or expression that you want to evaluate.
|
||||
|
||||
### Protection
|
||||
|
||||
When a file is created or edited on a Windows 10 endpoint, Windows Defender ATP extracts the content and evaluates if it contains any default or custom sensitive information types that have been defined.
|
||||
If the file has a match, Windows Defender ATP applies endpoint data loss prevention even if the file had no label previously.
|
||||
|
||||
Windows Defender ATP is integrated with Azure Information Protection for data discovery and reports sensitive information types that were discovered.
|
||||
Azure Information Protection aggregates the files with sensitivity labels and the sensitive information types they contain across the enterprise.
|
||||
|
||||

|
||||
|
||||
You can see sensitive information types in Microsoft 365 compliance under **Classifications**. Default sensitive information types have Microsoft as the publisher. The publisher for custom types is the tenant name.
|
||||
|
||||

|
||||
|
||||
>[!NOTE]
|
||||
>Automatic classification does not change the file itself, but it applies protection based on the label.
|
||||
>WIP protects a file that contains a sensitive information type as a work file.
|
||||
>Azure Information Protection works differently in that it extends a file with a new attribute so the protection persists if the file is copied.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- Endpoint data loss prevention requires Windows 10, version 1809
|
||||
- Auto labelling requires Windows 10, version 1903
|
||||
- Devices need to be onboarded to [Windows Defender ATP](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/windows-defender-advanced-threat-protection), which scans content for a label and applies WIP policy
|
||||
- [Sensitivity labels](https://docs.microsoft.com/office365/securitycompliance/labels) need to be configured in Microsoft 365 compliance center
|
||||
- WIP policy needs to be applied to endpoint devices by using [Intune](create-wip-policy-using-intune-azure.md) or [Microsoft Endpoint Configuration Manager](overview-create-wip-policy-configmgr.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -82,7 +82,7 @@
|
||||
#### [Network protection]()
|
||||
##### [Protect your network](microsoft-defender-atp/network-protection.md)
|
||||
##### [Network protection evaluation](microsoft-defender-atp/evaluate-network-protection.md)
|
||||
|
||||
##### [Enable network protection](microsoft-defender-atp/enable-network-protection.md)
|
||||
|
||||
#### [Web protection]()
|
||||
##### [Web protection overview](microsoft-defender-atp/web-protection-overview.md)
|
||||
@ -356,7 +356,7 @@
|
||||
##### [DeviceInfo](microsoft-defender-atp/advanced-hunting-deviceinfo-table.md)
|
||||
##### [DeviceNetworkInfo](microsoft-defender-atp/advanced-hunting-devicenetworkinfo-table.md)
|
||||
##### [DeviceEvents](microsoft-defender-atp/advanced-hunting-deviceevents-table.md)
|
||||
##### [DeviceFileCertificateInfoBeta](microsoft-defender-atp/advanced-hunting-devicefilecertificateinfobeta-table.md)
|
||||
##### [DeviceFileCertificateInfo](microsoft-defender-atp/advanced-hunting-devicefilecertificateinfo-table.md)
|
||||
##### [DeviceNetworkEvents](microsoft-defender-atp/advanced-hunting-devicenetworkevents-table.md)
|
||||
##### [DeviceProcessEvents](microsoft-defender-atp/advanced-hunting-deviceprocessevents-table.md)
|
||||
##### [DeviceRegistryEvents](microsoft-defender-atp/advanced-hunting-deviceregistryevents-table.md)
|
||||
@ -413,7 +413,7 @@
|
||||
### [Configure portal settings]()
|
||||
#### [Set up preferences](microsoft-defender-atp/preferences-setup.md)
|
||||
#### [General]()
|
||||
##### [Update data retention settings](microsoft-defender-atp/data-retention-settings.md)
|
||||
##### [Verify data storage location and update data retention settings](microsoft-defender-atp/data-retention-settings.md)
|
||||
##### [Configure alert notifications](microsoft-defender-atp/configure-email-notifications.md)
|
||||
##### [Enable and create Power BI reports using Windows Defender Security center data](microsoft-defender-atp/powerbi-reports.md)
|
||||
##### [Enable Secure score security controls](microsoft-defender-atp/enable-secure-score.md)
|
||||
@ -700,9 +700,10 @@
|
||||
#### [Family options](windows-defender-security-center/wdsc-family-options.md)
|
||||
|
||||
|
||||
### [Windows Defender SmartScreen](windows-defender-smartscreen/windows-defender-smartscreen-overview.md)
|
||||
#### [Windows Defender SmartScreen Group Policy and mobile device management (MDM) settings](windows-defender-smartscreen/windows-defender-smartscreen-available-settings.md)
|
||||
#### [Set up and use Windows Defender SmartScreen on individual devices](windows-defender-smartscreen/windows-defender-smartscreen-set-individual-device.md)
|
||||
### [Microsoft Defender SmartScreen](microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md)
|
||||
#### [Microsoft Defender SmartScreen Group Policy and mobile device management (MDM) settings](microsoft-defender-smartscreen/microsoft-defender-smartscreen-available-settings.md)
|
||||
#### [Set up and use Microsft Defender SmartScreen on individual devices](microsoft-defender-smartscreen/microsoft-defender-smartscreen-set-individual-device.md)
|
||||
|
||||
|
||||
### [Windows Sandbox](windows-sandbox/windows-sandbox-overview.md)
|
||||
#### [Windows Sandbox architecture](windows-sandbox/windows-sandbox-architecture.md)
|
||||
|
@ -2,7 +2,7 @@
|
||||
title: Audit Other Privilege Use Events (Windows 10)
|
||||
description: This security policy setting is not used.
|
||||
ms.assetid: 5f7f5b25-42a6-499f-8aa2-01ac79a2a63c
|
||||
ms.reviewer:
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
ms.pagetype: security
|
||||
@ -17,8 +17,8 @@ ms.date: 04/19/2017
|
||||
# Audit Other Privilege Use Events
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows Server 2016
|
||||
- Windows 10
|
||||
- Windows Server 2016
|
||||
|
||||
|
||||
This auditing subcategory should not have any events in it, but for some reason Success auditing will enable generation of event 4985(S): The state of a transaction has changed.
|
||||
@ -31,7 +31,7 @@ This auditing subcategory should not have any events in it, but for some reason
|
||||
|
||||
**Events List:**
|
||||
|
||||
- [4985](event-4674.md)(S): The state of a transaction has changed.
|
||||
- [4985](event-4985.md)(S): The state of a transaction has changed.
|
||||
|
||||
|
||||
|
||||
|
@ -14,7 +14,7 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/19/2017
|
||||
ms.date:
|
||||
---
|
||||
|
||||
# Monitor the use of removable storage devices
|
||||
@ -28,7 +28,10 @@ If you configure this policy setting, an audit event is generated each time a us
|
||||
|
||||
Use the following procedures to monitor the use of removable storage devices and to verify that the devices are being monitored.
|
||||
|
||||
>**Note:** Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings.
|
||||
Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings.
|
||||
|
||||
> [!NOTE]
|
||||
> When a policy to audit removable storage is pushed to a computer, a new [Security Descriptor](https://docs.microsoft.com/windows/win32/secauthz/audit-generation) needs to be applied to all removable storage devices with the audit settings. The [security descriptor for a device](https://docs.microsoft.com/windows-hardware/drivers/kernel/controlling-device-access) can be set up either when the device is installed, or by setting up the [device properties in the registry](https://docs.microsoft.com/windows-hardware/drivers/kernel/setting-device-object-registry-properties-after-installation), which is done by calling a [device installation function](https://docs.microsoft.com/previous-versions/ff541299). This may require the device to restart to apply the new security descriptor.
|
||||
|
||||
**To configure settings to monitor removable storage devices**
|
||||
|
||||
@ -46,7 +49,8 @@ After you configure the settings to monitor removable storage devices, use the f
|
||||
|
||||
1. Sign in to the computer that hosts the resources that you want to monitor. Press the Windows key + R, and then type **cmd** to open a Command Prompt window.
|
||||
|
||||
>**Note:** If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click **Yes**.
|
||||
> [!NOTE]
|
||||
> If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click **Yes**.
|
||||
|
||||
2. Type **gpupdate /force**, and press ENTER.
|
||||
3. Connect a removable storage device to the targeted computer and attempt to copy a file that is protected with the Removable Storage Audit policy.
|
||||
@ -56,7 +60,8 @@ After you configure the settings to monitor removable storage devices, use the f
|
||||
|
||||
Key information to look for includes the name and account domain of the user who attempted to access the file, the object that the user is attempting to access, resource attributes of the resource, and the type of access that was attempted.
|
||||
|
||||
>**Note:** We do not recommend that you enable this category on a file server that hosts file shares on a removable storage device. When Removable Storage Auditing is configured, any attempt to access the removable storage device will generate an audit event.
|
||||
> [!NOTE]
|
||||
> We do not recommend that you enable this category on a file server that hosts file shares on a removable storage device. When Removable Storage Auditing is configured, any attempt to access the removable storage device will generate an audit event.
|
||||
|
||||
### Related resource
|
||||
|
||||
|
@ -7,8 +7,8 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dansimp
|
||||
author: DulceMontemayor
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
@ -19,6 +19,9 @@ ms.topic: conceptual
|
||||
# Threat Protection
|
||||
[Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559) is a unified platform for preventative protection, post-breach detection, automated investigation, and response. Microsoft Defender ATP protects endpoints from cyber threats; detects advanced attacks and data breaches, automates security incidents and improves security posture.
|
||||
|
||||
>[!TIP]
|
||||
> Enable your users to access cloud services and on-premises applications with ease and enable modern management capabilities for all devices. For more information, see [Secure your remote workforce](https://docs.microsoft.com/enterprise-mobility-security/remote-work/).
|
||||
|
||||
<center><h2>Microsoft Defender ATP</center></h2>
|
||||
<table>
|
||||
<tr>
|
||||
|
@ -16,7 +16,7 @@ manager: dansimp
|
||||
|
||||
Microsoft Baseline Security Analyzer (MBSA) is used to verify patch compliance. MBSA also performed several other security checks for Windows, IIS, and SQL Server. Unfortunately, the logic behind these additional checks had not been actively maintained since Windows XP and Windows Server 2003. Changes in the products since then rendered many of these security checks obsolete and some of their recommendations counterproductive.
|
||||
|
||||
MBSA was largely used in situations where neither Microsoft Update nor a local WSUS/SCCM server was available, or as a compliance tool to ensure that all security updates were deployed to a managed environment. While MBSA version 2.3 introduced support for Windows Server 2012 R2 and Windows 8.1, it has since been deprecated and no longer developed. MBSA 2.3 is not updated to fully support Windows 10 and Windows Server 2016.
|
||||
MBSA was largely used in situations where neither Microsoft Update nor a local WSUS or Configuration Manager server was available, or as a compliance tool to ensure that all security updates were deployed to a managed environment. While MBSA version 2.3 introduced support for Windows Server 2012 R2 and Windows 8.1, it has since been deprecated and no longer developed. MBSA 2.3 is not updated to fully support Windows 10 and Windows Server 2016.
|
||||
|
||||
## The Solution
|
||||
A script can help you with an alternative to MBSA’s patch-compliance checking:
|
||||
|
@ -20,6 +20,7 @@ ms.topic: article
|
||||
# Configure advanced features in Microsoft Defender ATP
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-advancedfeats-abovefoldlink)
|
||||
@ -30,32 +31,36 @@ Use the following advanced features to get better protected from potentially mal
|
||||
|
||||
## Automated investigation
|
||||
|
||||
When you enable this feature, you'll be able to take advantage of the automated investigation and remediation features of the service. For more information, see [Automated investigation](automated-investigations.md).
|
||||
Turn on this feature to take advantage of the automated investigation and remediation features of the service. For more information, see [Automated investigation](automated-investigations.md).
|
||||
|
||||
## Live response
|
||||
|
||||
When you enable this feature, users with the appropriate permissions can initiate a live response session on machines.
|
||||
Turn on this feature so that users with the appropriate permissions can start a live response session on machines.
|
||||
|
||||
For more information on role assignments see, [Create and manage roles](user-roles.md).
|
||||
For more information about role assignments, see [Create and manage roles](user-roles.md).
|
||||
|
||||
## Live response unsigned script execution
|
||||
|
||||
Enabling this feature allows you to run unsigned scripts in a live response session.
|
||||
|
||||
## Auto-resolve remediated alerts
|
||||
## Autoresolve remediated alerts
|
||||
|
||||
For tenants created on or after Windows 10, version 1809 the automated investigation and remediation capability is configured by default to resolve alerts where the automated analysis result status is "No threats found" or "Remediated". If you don’t want to have alerts auto-resolved, you’ll need to manually turn off the feature.
|
||||
For tenants created on or after Windows 10, version 1809 the automated investigation and remediation capability is configured by default to resolve alerts where the automated analysis result status is "No threats found" or "Remediated". If you don't want to have alerts auto-resolved, you'll need to manually turn off the feature.
|
||||
|
||||
>[!TIP]
|
||||
>For tenants created prior that version, you'll need to manually turn this feature on from the [Advanced features](https://securitycenter.windows.com/preferences2/integration) page.
|
||||
|
||||
>[!NOTE]
|
||||
> - The result of the auto-resolve action may influence the Machine risk level calculation which is based on the active alerts found on a machine.
|
||||
>
|
||||
>- The result of the auto-resolve action may influence the Machine risk level calculation which is based on the active alerts found on a machine.
|
||||
>- If a security operations analyst manually sets the status of an alert to "In progress" or "Resolved" the auto-resolve capability will not overwrite it.
|
||||
|
||||
## Allow or block file
|
||||
|
||||
Blocking is only available if your organization uses Windows Defender Antivirus as the active antimalware solution, and if the cloud-based protection feature is enabled.
|
||||
Blocking is only available if your organization fulfills these requirements:
|
||||
|
||||
- Uses Windows Defender Antivirus as the active antimalware solution and,
|
||||
- The cloud-based protection feature is enabled
|
||||
|
||||
This feature enables you to block potentially malicious files in your network. Blocking a file will prevent it from being read, written, or executed on machines in your organization.
|
||||
|
||||
@ -69,24 +74,22 @@ To turn **Allow or block** files on:
|
||||
|
||||
1. Select **Save preferences** at the bottom of the page.
|
||||
|
||||
Once you have enabled this feature, you can [block files](respond-file-alerts.md#allow-or-block-file) via the **Add Indicator** tab on a file's profile page.
|
||||
|
||||
After turning on this feature, you can [block files](respond-file-alerts.md#allow-or-block-file) via the **Add Indicator** tab on a file's profile page.
|
||||
|
||||
## Custom network indicators
|
||||
|
||||
Enabling this feature allows you to create indicators for IP addresses, domains, or URLs which determine whether they will be allowed or blocked based on your custom indicator list.
|
||||
Turning on this feature allows you to create indicators for IP addresses, domains, or URLs, which determine whether they will be allowed or blocked based on your custom indicator list.
|
||||
|
||||
To use this feature, machines must be running Windows 10 version 1709 or later. They should also have network protection in block mode and version 4.18.1906.3 or later of the antimalware platform [see KB 4052623](https://go.microsoft.com/fwlink/?linkid=2099834).
|
||||
To use this feature, machines must be running Windows 10 version 1709 or later. They should also have network protection in block mode and version 4.18.1906.3 or later of the antimalware platform [see KB 4052623](https://go.microsoft.com/fwlink/?linkid=2099834).
|
||||
|
||||
For more information, see [Manage indicators](manage-indicators.md).
|
||||
|
||||
>[!NOTE]
|
||||
>Network protection leverages reputation services that process requests in locations that might be outside of the location you have selected for your Microsoft Defender ATP data.
|
||||
|
||||
|
||||
## Show user details
|
||||
|
||||
When you enable this feature, you'll be able to see user details stored in Azure Active Directory including a user's picture, name, title, and department information when investigating user account entities. You can find user account information in the following views:
|
||||
Turn on this feature so that you can see user details stored in Azure Active Directory. Details include a user's picture, name, title, and department information when investigating user account entities. You can find user account information in the following views:
|
||||
|
||||
- Security operations dashboard
|
||||
- Alert queue
|
||||
@ -110,25 +113,25 @@ The integration with Azure Advanced Threat Protection allows you to pivot direct
|
||||
|
||||
## Microsoft Secure Score
|
||||
|
||||
Forwards Microsoft Defender ATP signals to Microsoft Secure Score in the Microsoft 365 security center. Turning this feature on gives Microsoft Secure Score visibility into the devices security posture. Forwarded data is stored and processed in the same location as the your Microsoft Secure Score data.
|
||||
Forwards Microsoft Defender ATP signals to Microsoft Secure Score in the Microsoft 365 security center. Turning on this feature gives Microsoft Secure Score visibility into the devices security posture. Forwarded data is stored and processed in the same location as the your Microsoft Secure Score data.
|
||||
|
||||
### Enable the Microsoft Defender ATP integration from the Azure ATP portal
|
||||
|
||||
To receive contextual machine integration in Azure ATP, you'll also need to enable the feature in the Azure ATP portal.
|
||||
|
||||
1. Login to the [Azure portal](https://portal.atp.azure.com/) with a Global Administrator or Security Administrator role.
|
||||
1. Log in to the [Azure portal](https://portal.atp.azure.com/) with a Global Administrator or Security Administrator role.
|
||||
|
||||
2. Click **Create your instance**.
|
||||
|
||||
3. Toggle the Integration setting to **On** and click **Save**.
|
||||
|
||||
When you complete the integration steps on both portals, you'll be able to see relevant alerts in the machine details or user details page.
|
||||
After completing the integration steps on both portals, you'll be able to see relevant alerts in the machine details or user details page.
|
||||
|
||||
## Office 365 Threat Intelligence connection
|
||||
|
||||
This feature is only available if you have an active Office 365 E5 or the Threat Intelligence add-on. For more information, see the Office 365 Enterprise E5 product page.
|
||||
|
||||
When you enable this feature, you'll be able to incorporate data from Office 365 Advanced Threat Protection into Microsoft Defender Security Center to conduct a holistic security investigation across Office 365 mailboxes and Windows machines.
|
||||
When you turn this feature on, you'll be able to incorporate data from Office 365 Advanced Threat Protection into Microsoft Defender Security Center to conduct a comprehensive security investigation across Office 365 mailboxes and Windows machines.
|
||||
|
||||
>[!NOTE]
|
||||
>You'll need to have the appropriate license to enable this feature.
|
||||
@ -137,7 +140,7 @@ To receive contextual machine integration in Office 365 Threat Intelligence, you
|
||||
|
||||
## Microsoft Threat Experts
|
||||
|
||||
Out of the two Microsoft Threat Expert components, targeted attack notification is in general availability, while experts-on-demand capability is still in preview. You can only use the experts-on-demand capability if you have applied for preview and your application has been approved. You can receive targeted attack notifications from Microsoft Threat Experts through your Microsoft Defender ATP portal's alerts dashboard and via email if you configure it.
|
||||
Out of the two Microsoft Threat Expert components, targeted attack notification is in general availability. Experts-on-demand capability is still in preview. You can only use the experts-on-demand capability if you have applied for preview and your application has been approved. You can receive targeted attack notifications from Microsoft Threat Experts through your Microsoft Defender ATP portal's alerts dashboard and via email if you configure it.
|
||||
|
||||
>[!NOTE]
|
||||
>The Microsoft Threat Experts capability in Microsoft Defender ATP is available with an E5 license for [Enterprise Mobility + Security](https://www.microsoft.com/cloud-platform/enterprise-mobility-security).
|
||||
@ -151,11 +154,11 @@ Enabling this setting forwards Microsoft Defender ATP signals to Microsoft Cloud
|
||||
|
||||
## Azure Information Protection
|
||||
|
||||
Turning this setting on forwards signals to Azure Information Protection, giving data owners and administrators visibility into protected data on onboarded machines and machine risk ratings.
|
||||
Turning on this setting allows signals to be forwarded to Azure Information Protection. It gives data owners and administrators visibility into protected data on onboarded machines and machine risk ratings.
|
||||
|
||||
## Microsoft Intune connection
|
||||
|
||||
Microsoft Defender ATP can be integrated with [Microsoft Intune](https://docs.microsoft.com/intune/what-is-intune) to [enable device risk-based conditional access](https://docs.microsoft.com/intune/advanced-threat-protection#enable-windows-defender-atp-in-intune). When you [enable this feature](configure-conditional-access.md), you'll be able to share Microsoft Defender ATP device information with Intune, enhancing policy enforcement.
|
||||
Microsoft Defender ATP can be integrated with [Microsoft Intune](https://docs.microsoft.com/intune/what-is-intune) to [enable device risk-based conditional access](https://docs.microsoft.com/intune/advanced-threat-protection#enable-windows-defender-atp-in-intune). When you [turn on this feature](configure-conditional-access.md), you'll be able to share Microsoft Defender ATP device information with Intune, enhancing policy enforcement.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>You'll need to enable the integration on both Intune and Microsoft Defender ATP to use this feature. For more information on specific steps, see [Configure Conditional Access in Microsoft Defender ATP](configure-conditional-access.md).
|
||||
@ -176,7 +179,7 @@ When you enable Intune integration, Intune will automatically create a classic C
|
||||
|
||||
Learn about new features in the Microsoft 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.
|
||||
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,7 +1,7 @@
|
||||
---
|
||||
title: DeviceFileCertificateInfoBeta table in the advanced hunting schema
|
||||
description: Learn about file signing information in the DeviceFileCertificateInfoBeta table of the advanced hunting schema
|
||||
keywords: advanced hunting, threat hunting, cyber threat hunting, mdatp, windows defender atp, wdatp search, query, telemetry, schema reference, kusto, table, column, data type, description, digital signature, certificate, file signing, DeviceFileCertificateInfoBeta
|
||||
title: DeviceFileCertificateInfo table in the advanced hunting schema
|
||||
description: Learn about file signing information in the DeviceFileCertificateInfo table of the advanced hunting schema
|
||||
keywords: advanced hunting, threat hunting, cyber threat hunting, mdatp, windows defender atp, wdatp search, query, telemetry, schema reference, kusto, table, column, data type, description, digital signature, certificate, file signing, DeviceFileCertificateInfo
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
@ -18,7 +18,7 @@ ms.topic: article
|
||||
ms.date: 01/14/2020
|
||||
---
|
||||
|
||||
# DeviceFileCertificateInfoBeta
|
||||
# DeviceFileCertificateInfo
|
||||
|
||||
**Applies to:**
|
||||
|
||||
@ -26,9 +26,7 @@ ms.date: 01/14/2020
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-advancedhuntingref-abovefoldlink)
|
||||
|
||||
[!include[Prerelease information](../../includes/prerelease.md)]
|
||||
|
||||
The `DeviceFileCertificateInfoBeta` table in the [advanced hunting](advanced-hunting-overview.md) schema contains information about file signing certificates. This table uses data obtained from certificate verification activities regularly performed on files on endpoints.
|
||||
The `DeviceFileCertificateInfo` table in the [advanced hunting](advanced-hunting-overview.md) schema contains information about file signing certificates. This table uses data obtained from certificate verification activities regularly performed on files on endpoints.
|
||||
|
||||
For information on other tables in the advanced hunting schema, see [the advanced hunting schema reference](advanced-hunting-schema-reference.md).
|
||||
|
@ -47,7 +47,7 @@ Table and column names are also listed within the Microsoft Defender Security Ce
|
||||
| **[DeviceLogonEvents](advanced-hunting-devicelogonevents-table.md)** | Sign-ins and other authentication events |
|
||||
| **[DeviceImageLoadEvents](advanced-hunting-deviceimageloadevents-table.md)** | DLL loading events |
|
||||
| **[DeviceEvents](advanced-hunting-deviceevents-table.md)** | Multiple event types, including events triggered by security controls such as Windows Defender Antivirus and exploit protection |
|
||||
| **[DeviceFileCertificateInfoBeta](advanced-hunting-devicefilecertificateinfobeta-table.md)** | Certificate information of signed files obtained from certificate verification events on endpoints |
|
||||
| **[DeviceFileCertificateInfo](advanced-hunting-devicefilecertificateinfo-table.md)** | Certificate information of signed files obtained from certificate verification events on endpoints |
|
||||
| **[DeviceTvmSoftwareInventoryVulnerabilities](advanced-hunting-tvm-softwareinventory-table.md)** | Inventory of software on devices as well as any known vulnerabilities in these software products |
|
||||
| **[DeviceTvmSoftwareVulnerabilitiesKB ](advanced-hunting-tvm-softwarevulnerability-table.md)** | Knowledge base of publicly disclosed vulnerabilities, including whether exploit code is publicly available |
|
||||
| **[DeviceTvmSecureConfigurationAssessment](advanced-hunting-tvm-configassessment-table.md)** | Threat & Vulnerability Management assessment events, indicating the status of various security configurations on devices |
|
||||
|
@ -52,6 +52,9 @@ You can save a new or existing query so that it is only accessible to you or sha
|
||||
|
||||
2. Select **Delete** and confirm deletion. Or select **Rename** and provide a new name for the query.
|
||||
|
||||
## Create a direct link to a query
|
||||
To generate a link that opens your query directly in the advanced hunting query editor, finalize your query and select **Share link**.
|
||||
|
||||
## Access queries in the GitHub repository
|
||||
Microsoft security researchers regularly share advanced hunting queries in a [designated public repository on GitHub](https://github.com/Microsoft/WindowsDefenderATP-Hunting-Queries). This repository is open to contributions. To contribute, [join GitHub for free](https://github.com/).
|
||||
|
||||
|
@ -21,11 +21,12 @@ ms.date: 03/27/2020
|
||||
# View and organize the Microsoft Defender Advanced Threat Protection Alerts queue
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-alertsq-abovefoldlink)
|
||||
|
||||
The **Alerts queue** shows a list of alerts that were flagged from machines in your network. By default, the queue displays alerts seen in the last 30 days in a grouped view, with the most recent alerts showing at the top of the list, helping you see the most recent alerts first.
|
||||
The **Alerts queue** shows a list of alerts that were flagged from machines in your network. By default, the queue displays alerts seen in the last 30 days in a grouped view. The most recent alerts are showed at the top of the list helping you see the most recent alerts first.
|
||||
|
||||
>[!NOTE]
|
||||
>The alerts queue is significantly reduced with automated investigation and remediation, allowing security operations experts to focus on more sophisticated threats and other high value initiatives. When an alert contains a supported entity for automated investigation (for example, a file) in a machine that has a supported operating system for it, an automated investigation and remediation can start. For more information on automated investigations, see [Overview of Automated investigations](automated-investigations.md).
|
||||
@ -33,6 +34,7 @@ The **Alerts queue** shows a list of alerts that were flagged from machines in y
|
||||
There are several options you can choose from to customize the alerts queue view.
|
||||
|
||||
On the top navigation you can:
|
||||
|
||||
- Select grouped view or list view
|
||||
- Customize columns to add or remove columns
|
||||
- Select the items to show per page
|
||||
@ -42,32 +44,36 @@ On the top navigation you can:
|
||||

|
||||
|
||||
## Sort, filter, and group the alerts queue
|
||||
|
||||
You can apply the following filters to limit the list of alerts and get a more focused view the alerts.
|
||||
|
||||
### Severity
|
||||
|
||||
Alert severity | Description
|
||||
:---|:---
|
||||
High </br>(Red) | Alerts commonly seen associated with advanced persistent threats (APT). These alerts indicate a high risk due to the severity of damage they can inflict on machines. Some examples of these are credential theft tools activities, ransomware activities not associated with any group, tampering with security sensors, or any malicious activities indicative of a human adversary.
|
||||
High </br>(Red) | Alerts commonly seen associated with advanced persistent threats (APT). These alerts indicate a high risk because of the severity of damage they can inflict on machines. Some examples are: credential theft tools activities, ransomware activities not associated with any group, tampering with security sensors, or any malicious activities indicative of a human adversary.
|
||||
Medium </br>(Orange) | Alerts from endpoint detection and response post-breach behaviors that might be a part of an advanced persistent threat (APT). This includes observed behaviors typical of attack stages, anomalous registry change, execution of suspicious files, and so forth. Although some might be part of internal security testing, it requires investigation as it might also be a part of an advanced attack.
|
||||
Low </br>(Yellow) | Alerts on threats associated with prevalent malware, hack-tools, non-malware hack tools, such as running exploration commands, clearing logs, etc., that often do not indicate an advanced threat targeting the organization. It could also come from an isolated security tool testing by a user in your organization.
|
||||
Low </br>(Yellow) | Alerts on threats associated with prevalent malware. For example, hack-tools, non-malware hack tools, such as running exploration commands, clearing logs, etc., that often do not indicate an advanced threat targeting the organization. It could also come from an isolated security tool testing by a user in your organization.
|
||||
Informational </br>(Grey) | Alerts that might not be considered harmful to the network but can drive organizational security awareness on potential security issues.
|
||||
|
||||
#### Understanding alert severity
|
||||
It is important to understand that the Windows Defender Antivirus (Windows Defender AV) and Microsoft Defender ATP alert severities are different because they represent different scopes.
|
||||
|
||||
Windows Defender Antivirus (Windows Defender AV) and Microsoft Defender ATP alert severities are different because they represent different scopes.
|
||||
|
||||
The Windows Defender AV threat severity represents the absolute severity of the detected threat (malware), and is assigned based on the potential risk to the individual machine, if infected.
|
||||
|
||||
The Microsoft Defender ATP alert severity represents the severity of the detected behavior, the actual risk to the machine but more importantly the potential risk to the organization.
|
||||
|
||||
So, for example:
|
||||
- The severity of a Microsoft Defender ATP alert about a Windows Defender AV detected threat that was completely prevented and did not infect the machine is categorized as "Informational" because there was no actual damage incurred.
|
||||
|
||||
- The severity of a Microsoft Defender ATP alert about a Windows Defender AV detected threat that was completely prevented and did not infect the machine is categorized as "Informational" because there was no actual damage.
|
||||
- An alert about a commercial malware was detected while executing, but blocked and remediated by Windows Defender AV, is categorized as "Low" because it may have caused some damage to the individual machine but poses no organizational threat.
|
||||
- An alert about malware detected while executing which can pose a threat not only to the individual machine but to the organization, regardless if it was eventually blocked, may be ranked as "Medium" or "High".
|
||||
- Suspicious behavioral alerts which were not blocked or remediated will be ranked "Low", "Medium" or "High" following the same organizational threat considerations.
|
||||
- Suspicious behavioral alerts, which weren't blocked or remediated will be ranked "Low", "Medium" or "High" following the same organizational threat considerations.
|
||||
|
||||
#### Understanding alert categories
|
||||
We've redefined the alert categories to align to the [enterprise attack tactics](https://attack.mitre.org/tactics/enterprise/) in the [MITRE ATT&CK matrix](https://attack.mitre.org/). New category names apply to all new alerts. Existing alerts will retain the previous category names.
|
||||
|
||||
We've redefined the alert categories to align to the [enterprise attack tactics](https://attack.mitre.org/tactics/enterprise/) in the [MITRE ATT&CK matrix](https://attack.mitre.org/). New category names apply to all new alerts. Existing alerts will keep the previous category names.
|
||||
|
||||
The table below lists the current categories and how they generally map to previous categories.
|
||||
|
||||
@ -92,39 +98,43 @@ The table below lists the current categories and how they generally map to previ
|
||||
|
||||
|
||||
### Status
|
||||
|
||||
You can choose to limit the list of alerts based on their status.
|
||||
|
||||
### Investigation state
|
||||
|
||||
Corresponds to the automated investigation state.
|
||||
|
||||
### Category
|
||||
|
||||
You can choose to filter the queue to display specific types of malicious activity.
|
||||
|
||||
### Assigned to
|
||||
|
||||
You can choose between showing alerts that are assigned to you or automation.
|
||||
|
||||
### Detection source
|
||||
Select the source that triggered the alert detection. Microsoft Threat Experts preview participants can now filter and see detections from the new threat experts managed hunting service.
|
||||
|
||||
Select the source that triggered the alert detection. Microsoft Threat Experts preview participants can now filter and see detections from the new threat experts-managed hunting service.
|
||||
|
||||
>[!NOTE]
|
||||
>The Windows Defender Antivirus filter will only appear if machines are using Windows Defender Antivirus as the default real-time protection antimalware product.
|
||||
|
||||
|
||||
### OS platform
|
||||
|
||||
Limit the alerts queue view by selecting the OS platform that you're interested in investigating.
|
||||
|
||||
### Machine group
|
||||
If you have specific machine groups that you're interested in checking the alerts on, you can select the groups to limit the alerts queue view to display just those machine groups.
|
||||
|
||||
If you have specific machine groups that you're interested in checking, you can select the groups to limit the alerts queue view.
|
||||
|
||||
### Associated threat
|
||||
|
||||
Use this filter to focus on alerts that are related to high profile threats. You can see the full list of high-profile threats in [Threat analytics](threat-analytics.md).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Manage Microsoft Defender Advanced Threat Protection alerts](manage-alerts.md)
|
||||
- [Investigate Microsoft Defender Advanced Threat Protection alerts](investigate-alerts.md)
|
||||
- [Investigate a file associated with a Microsoft Defender ATP alert](investigate-files.md)
|
||||
|
@ -12,7 +12,7 @@ author: mjcaparas
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -20,9 +20,10 @@ ms.topic: article
|
||||
|
||||
**Applies to:** [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
- Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-exposedapis-abovefoldlink)
|
||||
- Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-exposedapis-abovefoldlink)
|
||||
|
||||
## Methods
|
||||
|
||||
Method |Return Type |Description
|
||||
:---|:---|:---
|
||||
[Get alert](get-alert-info-by-id.md) | [Alert](alerts.md) | Get a single [alert](alerts.md) object.
|
||||
@ -37,7 +38,8 @@ Method |Return Type |Description
|
||||
|
||||
|
||||
## Properties
|
||||
Property | Type | Description
|
||||
|
||||
Property | Type | Description
|
||||
:---|:---|:---
|
||||
id | String | Alert ID.
|
||||
title | String | Alert title.
|
||||
@ -45,15 +47,15 @@ description | String | Alert description.
|
||||
alertCreationTime | Nullable DateTimeOffset | The date and time (in UTC) the alert was created.
|
||||
lastEventTime | Nullable DateTimeOffset | The last occurrence of the event that triggered the alert on the same machine.
|
||||
firstEventTime | Nullable DateTimeOffset | The first occurrence of the event that triggered the alert on that machine.
|
||||
lastUpdateTime | Nullable DateTimeOffset | The first occurrence of the event that triggered the alert on that machine.
|
||||
lastUpdateTime | Nullable DateTimeOffset | The date and time (in UTC) the alert was last updated.
|
||||
resolvedTime | Nullable DateTimeOffset | The date and time in which the status of the alert was changed to 'Resolved'.
|
||||
incidentId | Nullable Long | The [Incident](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/view-incidents-queue) ID of the Alert.
|
||||
investigationId | Nullable Long | The [Investigation](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/automated-investigations) ID related to the Alert.
|
||||
incidentId | Nullable Long | The [Incident](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/view-incidents-queue) ID of the Alert.
|
||||
investigationId | Nullable Long | The [Investigation](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/automated-investigations) ID related to the Alert.
|
||||
investigationState | Nullable Enum | The current state of the [Investigation](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/automated-investigations). Possible values are: 'Unknown', 'Terminated', 'SuccessfullyRemediated', 'Benign', 'Failed', 'PartiallyRemediated', 'Running', 'PendingApproval', 'PendingResource', 'PartiallyInvestigated', 'TerminatedByUser', 'TerminatedBySystem', 'Queued', 'InnerFailure', 'PreexistingAlert', 'UnsupportedOs', 'UnsupportedAlertType', 'SuppressedAlert'.
|
||||
assignedTo | String | Owner of the alert.
|
||||
severity | Enum | Severity of the alert. Possible values are: 'UnSpecified', 'Informational', 'Low', 'Medium' and 'High'.
|
||||
status | Enum | Specifies the current status of the alert. Possible values are: 'Unknown', 'New', 'InProgress' and 'Resolved'.
|
||||
classification | Nullable Enum | Specification of the alert. Possible values are: 'Unknown', 'FalsePositive', 'TruePositive'.
|
||||
classification | Nullable Enum | Specification of the alert. Possible values are: 'Unknown', 'FalsePositive', 'TruePositive'.
|
||||
determination | Nullable Enum | Specifies the determination of the alert. Possible values are: 'NotAvailable', 'Apt', 'Malware', 'SecurityPersonnel', 'SecurityTesting', 'UnwantedSoftware', 'Other'.
|
||||
category| String | Category of the alert.
|
||||
detectionSource | String | Detection source.
|
||||
@ -61,7 +63,6 @@ threatFamilyName | String | Threat family.
|
||||
machineId | String | ID of a [machine](machine.md) entity that is associated with the alert.
|
||||
comments | List of Alert comments | Alert Comment is an object that contains: comment string, createdBy string and createTime date time.
|
||||
|
||||
|
||||
### Response example for getting single alert:
|
||||
|
||||
```
|
||||
@ -73,7 +74,7 @@ GET https://api.securitycenter.windows.com/api/alerts/da637084217856368682_-2929
|
||||
"id": "da637084217856368682_-292920499",
|
||||
"incidentId": 66860,
|
||||
"investigationId": 4416234,
|
||||
"investigationState": "Running",
|
||||
"investigationState": "Running",
|
||||
"assignedTo": "secop@contoso.com",
|
||||
"severity": "Low",
|
||||
"status": "New",
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: API Explorer in Microsoft Defender ATP
|
||||
ms.reviewer:
|
||||
description: Use the API Explorer to construct and perform API queries, test and send requests for any available API
|
||||
description: Use the API Explorer to construct and do API queries, test, and send requests for any available API
|
||||
keywords: api, explorer, send, request, get, post,
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
@ -19,14 +19,16 @@ ms.topic: conceptual
|
||||
---
|
||||
|
||||
# API Explorer
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Windows Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
The Microsoft Defender ATP API Explorer is a tool that helps you explore various Microsoft Defender ATP APIs interactively.
|
||||
|
||||
The API Explorer makes it easy to construct and perform API queries, test and send requests for any available Microsoft Defender ATP API endpoint. You can also use the API Explorer to perform actions or find data that might not yet be available through the user interface.
|
||||
The API Explorer makes it easy to construct and do API queries, test, and send requests for any available Microsoft Defender ATP API endpoint. Use the API Explorer to take actions or find data that might not yet be available through the user interface.
|
||||
|
||||
The tool is useful during app development because it allows you to perform API queries that respect your user access settings, reducing the need to generate access tokens.
|
||||
The tool is useful during app development. It allows you to perform API queries that respect your user access settings, reducing the need to generate access tokens.
|
||||
|
||||
You can also use the tool to explore the gallery of sample queries, copy result code samples, and generate debug information.
|
||||
|
||||
@ -34,26 +36,30 @@ With the API Explorer, you can:
|
||||
|
||||
- Run requests for any method and see responses in real-time
|
||||
- Quickly browse through the API samples and learn what parameters they support
|
||||
- Make API calls with ease; no need to authenticate beyond the management portal sign-in
|
||||
- Make API calls with ease; no need to authenticate beyond the management portal sign in
|
||||
|
||||
## Access API Explorer
|
||||
|
||||
From the left navigation menu, select **Partners & APIs** > **API Explorer**.
|
||||
|
||||
## Supported APIs
|
||||
## Supported APIs
|
||||
|
||||
API Explorer supports all the APIs offered by Microsoft Defender ATP.
|
||||
|
||||
The list of supported APIs is available in the [APIs documentation](apis-intro.md).
|
||||
|
||||
## Get started with the API Explorer
|
||||
|
||||
1. In the left pane, there is a list of sample requests that you can use.
|
||||
2. Follow the links and click **Run query**.
|
||||
|
||||
Some of the samples may require specifying a parameter in the URL, for example, {machine- id}.
|
||||
Some of the samples may require specifying a parameter in the URL, for example, {machine- ID}.
|
||||
|
||||
## FAQ
|
||||
|
||||
**Do I need to have an API token to use the API Explorer?** <br>
|
||||
Credentials to access an API are not needed since the API Explorer uses the Microsoft Defender ATP management portal token whenever it makes a request.
|
||||
Credentials to access an API aren't needed. The API Explorer uses the Microsoft Defender ATP management portal token whenever it makes a request.
|
||||
|
||||
The logged-in user authentication credential is used to verify that the API Explorer is authorized to access data on your behalf.
|
||||
|
||||
Specific API requests are limited based on your RBAC privileges; for example, a request to "Submit indicator" is limited to the security admin role.
|
||||
Specific API requests are limited based on your RBAC privileges. For example, a request to "Submit indicator" is limited to the security admin role.
|
||||
|
@ -18,7 +18,9 @@ ms.topic: article
|
||||
|
||||
# View details and results of automated investigations
|
||||
|
||||
Pending and completed [remediation actions](manage-auto-investigation.md#remediation-actions) are listed in the **Action center** ([https://securitycenter.windows.com/action-center](https://securitycenter.windows.com/action-center)) and the **Investigations** page ([https://securitycenter.windows.com/investigations](https://securitycenter.windows.com/investigations)).
|
||||
During and after an automated investigation, certain remediation actions can be identified. Depending on the threat and how [Microsoft Defender Advanced Threat Protection](https://docs.microsoft.com/windows/security/threat-protection) (Microsoft Defender ATP) is configured for your organization, some remediation actions are taken automatically.
|
||||
|
||||
If you're part of your organization's security operations team, you can view pending and completed [remediation actions](manage-auto-investigation.md#remediation-actions) in the **Action center** ([https://securitycenter.windows.com/action-center](https://securitycenter.windows.com/action-center)). You can also use the **Investigations** page ([https://securitycenter.windows.com/investigations](https://securitycenter.windows.com/investigations)) to view details about an investigation.
|
||||
|
||||
>[!NOTE]
|
||||
>If your organization has implemented role-based access to manage portal access, only authorized users or user groups who have permission to view the machine or machine group will be able to view the entire investigation.
|
||||
@ -27,12 +29,13 @@ Pending and completed [remediation actions](manage-auto-investigation.md#remedia
|
||||
|
||||

|
||||
|
||||
The action center consists of two main tabs, as described in the following table.
|
||||
|
||||
|Tab |Description |
|
||||
|---------|---------|
|
||||
|Pending actions |Displays a list of ongoing investigations that require attention. Recommended actions are presented that your security operations team can approve or reject. <br/><br/>**NOTE**: The Pending tab appears only if there are pending actions to be approved (or rejected). |
|
||||
|History |Acts as an audit log for all of the following: <br/>- All actions taken by automated investigation and remediation in Microsoft Defender ATP <br/>Actions that were approved by your security operations team (some actions, such as sending a file to quarantine, can be undone) <br/>- All commands ran and remediation actions that were applied in Live Response sessions (some actions can be undone) <br/>- Remediation actions that were applied by Windows Defender Antivirus (some actions can be undone) |
|
||||
The action center consists of two main tabs: **Pending actions** and **History**.
|
||||
- **Pending actions** Displays a list of ongoing investigations that require attention. Recommended actions are presented that your security operations team can approve or reject. The Pending tab appears only if there are pending actions to be approved (or rejected).
|
||||
- **History** Acts as an audit log for all of the following items: <br/>
|
||||
- Remediation actions that were taken as a result of an automated investigation
|
||||
- Remediation actions that were approved by your security operations team (some actions, such as sending a file to quarantine, can be undone)
|
||||
- Commands that were run and remediation actions that were applied in Live Response sessions (some actions can be undone)
|
||||
- Remediation actions that were applied by Windows Defender Antivirus (some actions can be undone)
|
||||
|
||||
Use the **Customize columns** menu to select columns that you'd like to show or hide.
|
||||
|
||||
@ -58,29 +61,30 @@ On the **Investigations** page, you can view details and use filters to focus on
|
||||
|---------|---------|
|
||||
|**Status** |(See [Automated investigation status](#automated-investigation-status)) |
|
||||
|**Triggering alert** | The alert that initiated the automated investigation |
|
||||
|**Detection source** |The source of the alert that initiated the automated investigation. |
|
||||
|**Entities** | These can include device or machines, and machine groups. You can filter the automated investigations list to zone in a specific machine to see other investigations related to the machine, or to see specific machine groups that you might have created. |
|
||||
|**Threat** |The category of threat detected during the automated investigation. |
|
||||
|**Tags** |Filter using manually added tags that capture the context of an automated investigation.|
|
||||
|**Comments** |Select between filtering the list between automated investigations that have comments and those that don't.|
|
||||
|**Detection source** |The source of the alert that initiated the automated investigation |
|
||||
|**Entities** | Entities can include device or machines, and machine groups. You can filter the automated investigations list to zone in a specific machine to see other investigations related to the machine, or to see specific machine groups that were created. |
|
||||
|**Threat** |The category of threat detected during the automated investigation |
|
||||
|**Tags** |Filter using manually added tags that capture the context of an automated investigation|
|
||||
|**Comments** |Select between filtering the list between automated investigations that have comments and those that don't|
|
||||
|
||||
## Automated investigation status
|
||||
|
||||
An automated investigation can be have one of the following status values:
|
||||
An automated investigation can have one of the following status values:
|
||||
|
||||
|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. |
|
||||
| Pending action | Remediation actions require review and approval. |
|
||||
| Running | The investigation process has started and is underway. Malicious artifacts that are found are remediated. |
|
||||
| Partially investigated | Entities directly related to the alert have been investigated. However, a problem stopped the investigation of collateral entities. Check the investigation log ([https://securitycenter.windows.com/investigations](https://securitycenter.windows.com/investigations)) for specific details. |
|
||||
| No threats found | The investigation has finished and no threats were identified. <br/>If you suspect something was missed (such as a false negative), you can use [advanced hunting](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-overview). |
|
||||
| Pending action | The investigation has found a threat, and an action to remediate that threat is awaiting approval. The Pending Action state is triggered when any threat with a corresponding action is found. However, the list of pending actions can increase as an investigation runs. Check the investigation log ([https://securitycenter.windows.com/investigations](https://securitycenter.windows.com/investigations)) to see if other items are still pending completion. |
|
||||
| Remediated | The investigation finished and all actions were approved (fully remediated). |
|
||||
| Partially remediated | The investigation resulted in remediation actions, and some were approved and completed. Other actions are still pending. |
|
||||
| Terminated by system | The investigation stopped. An investigation can stop for several reasons:<br/>- The investigation's pending actions expired. Pending actions can time out after awaiting approval for an extended period of time. <br/>- There are too many actions in the list.<br/>Visit the Action center ([https://securitycenter.windows.com/action-center](https://securitycenter.windows.com/action-center)) to view and approve any pending actions. |
|
||||
| Failed | At least one investigation analyzer ran into a problem where it could not complete properly. <br/><br/>If an investigation fails after remediation actions were approved, the remediation actions might still have succeeded. Check the investigation log ([https://securitycenter.windows.com/investigations](https://securitycenter.windows.com/investigations)) for detailed results. |
|
||||
| Queued | An investigation is being held in a queue. When other investigations complete, queued investigations begin. |
|
||||
| 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 by the system. |
|
||||
| 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. |
|
||||
|
||||
|
||||
## View details about an automated investigation
|
||||
|
||||
@ -92,7 +96,7 @@ In this view, you'll see the name of the investigation, when it started and ende
|
||||
|
||||
### Investigation graph
|
||||
|
||||
The investigation graph provides a graphical representation of an automated investigation. All investigation related information is simplified and arranged in specific sections. Clicking on any of the icons brings you the relevant section where you can view more information.
|
||||
The investigation graph provides a graphical representation of an automated investigation. All investigation-related information is simplified and arranged in specific sections. Clicking on any of the icons brings you the relevant section where you can view more information.
|
||||
|
||||
A progress ring shows two status indicators:
|
||||
- Orange ring - shows the pending portion of the investigation
|
||||
@ -108,7 +112,7 @@ From this view, you can also view and add comments and tags about the investigat
|
||||
|
||||
### Alerts
|
||||
|
||||
The **Alerts** tab for an automated investigation shows details such as a short description of the alert that initiated the automated investigation, severity, category, the machine associated with the alert, user, time in queue, status, investigation state, and who the investigation is assigned to.
|
||||
The **Alerts** tab for an automated investigation shows details such as a short description of the alert that initiated the automated investigation, severity, category, the machine associated with the alert, user, time in queue, status, investigation state, and to whom the investigation is assigned.
|
||||
|
||||
Additional alerts seen on a machine can be added to an automated investigation as long as the investigation is ongoing.
|
||||
|
||||
@ -124,7 +128,7 @@ Machines that show the same threat can be added to an ongoing investigation and
|
||||
|
||||
Selecting a machine using the checkbox brings up the machine details pane where you can see more information such as machine details and logged-on users.
|
||||
|
||||
Clicking on an machine name brings you the machine page.
|
||||
Clicking on a machine name brings you the machine page.
|
||||
|
||||
### Evidence
|
||||
|
||||
@ -146,7 +150,7 @@ You can also click on an action to bring up the details pane where you'll see in
|
||||
|
||||
### Pending actions
|
||||
|
||||
If there are pending actions on an automated investigation, you'll see a pop up similar to the following image.
|
||||
If there are pending actions on an automated investigation, you'll see a pop-up similar to the following image.
|
||||
|
||||

|
||||
|
||||
|
@ -15,7 +15,7 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 04/24/2018
|
||||
ms.date: 04/16/2020
|
||||
---
|
||||
|
||||
# Onboard non-persistent virtual desktop infrastructure (VDI) machines
|
||||
@ -81,26 +81,62 @@ The following steps will guide you through onboarding VDI machines and will high
|
||||
|
||||
6. Test your solution:
|
||||
|
||||
a. Create a pool with one machine.
|
||||
a. Create a pool with one machine.
|
||||
|
||||
b. Logon to machine.
|
||||
b. Logon to machine.
|
||||
|
||||
c. Logoff from machine.
|
||||
c. Logoff from machine.
|
||||
|
||||
d. Logon to machine with another user.
|
||||
d. Logon to machine with another user.
|
||||
|
||||
e. **For single entry for each machine**: Check only one entry in Microsoft Defender Security Center.<br>
|
||||
e. **For single entry for each machine**: Check only one entry in Microsoft Defender Security Center.<br>
|
||||
**For multiple entries for each machine**: Check multiple entries in Microsoft Defender Security Center.
|
||||
|
||||
7. Click **Machines list** on the Navigation pane.
|
||||
|
||||
8. Use the search function by entering the machine name and select **Machine** as search type.
|
||||
|
||||
## Updating non-persistent virtual desktop infrastructure (VDI) images
|
||||
As a best practice, we recommend using offline servicing tools to patch golden/master images.<br>
|
||||
For example, you can use the below commands to install an update while the image remains offline:
|
||||
|
||||
```
|
||||
DISM /Mount-image /ImageFile:"D:\Win10-1909.vhdx" /index:1 /MountDir:"C:\Temp\OfflineServicing"
|
||||
DISM /Image:"C:\Temp\OfflineServicing" /Add-Package /Packagepath:"C:\temp\patch\windows10.0-kb4541338-x64.msu"
|
||||
DISM /Unmount-Image /MountDir:"C:\Temp\OfflineServicing" /commit
|
||||
```
|
||||
|
||||
For more information on DISM commands and offline servicing, please refer to the articles below:
|
||||
- [Modify a Windows image using DISM](https://docs.microsoft.com/windows-hardware/manufacture/desktop/mount-and-modify-a-windows-image-using-dism)
|
||||
- [DISM Image Management Command-Line Options](https://docs.microsoft.com/windows-hardware/manufacture/desktop/dism-image-management-command-line-options-s14)
|
||||
- [Reduce the Size of the Component Store in an Offline Windows Image](https://docs.microsoft.com/windows-hardware/manufacture/desktop/reduce-the-size-of-the-component-store-in-an-offline-windows-image)
|
||||
|
||||
If offline servicing is not a viable option for your non-persistent VDI environment, the following steps should be taken to ensure consistency and sensor health:
|
||||
|
||||
1. After booting the master image for online servicing or patching, run an offboarding script to turn off the Microsoft Defender ATP sensor. For more information, see [Offboard machines using a local script](configure-endpoints-script.md#offboard-machines-using-a-local-script).
|
||||
|
||||
2. Ensure the sensor is stopped by running the command below in a CMD window:
|
||||
|
||||
```
|
||||
sc query sense
|
||||
```
|
||||
|
||||
3. Service the image as needed.
|
||||
|
||||
4. Run the below commands using PsExec.exe (which can be downloaded from https://download.sysinternals.com/files/PSTools.zip) to cleanup the cyber folder contents that the sensor may have accumulated since boot:
|
||||
|
||||
```
|
||||
PsExec.exe -s cmd.exe
|
||||
cd "C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Cyber"
|
||||
del *.* /f /s /q
|
||||
exit
|
||||
```
|
||||
|
||||
5. Re-seal the golden/master image as you normally would.
|
||||
|
||||
## Related topics
|
||||
- [Onboard Windows 10 machines using Group Policy](configure-endpoints-gp.md)
|
||||
- [Onboard Windows 10 machines using Microsoft Endpoint Configuration Manager](configure-endpoints-sccm.md)
|
||||
- [Onboard Windows 10 machines using Mobile Device Management tools](configure-endpoints-mdm.md)
|
||||
- [Onboard Windows 10 machines using a local script](configure-endpoints-script.md)
|
||||
- [Troubleshoot Microsoft Defender Advanced Threat Protection onboarding issues](troubleshoot-onboarding.md)
|
||||
|
||||
|
||||
|
@ -43,26 +43,19 @@ The service supports the onboarding of the following servers:
|
||||
|
||||
For a practical guidance on what needs to be in place for licensing and infrastructure, see [Protecting Windows Servers with Microsoft Defender ATP](https://techcommunity.microsoft.com/t5/What-s-New/Protecting-Windows-Server-with-Windows-Defender-ATP/m-p/267114#M128).
|
||||
|
||||
> [!NOTE]
|
||||
> An Azure Security Center Standard license is required, per node, to enroll Microsoft Defender ATP on a supported Windows Server platform, see [Supported features available in Azure Security Center](https://docs.microsoft.com/azure/security-center/security-center-services)
|
||||
|
||||
## Windows Server 2008 R2 SP1, Windows Server 2012 R2, and Windows Server 2016
|
||||
|
||||
There are two options to onboard Windows Server 2008 R2 SP1, Windows Server 2012 R2 and Windows Server 2016 to Microsoft Defender ATP:
|
||||
|
||||
- **Option 1**: Onboard through Azure Security Center
|
||||
- **Option 2**: Onboard through Microsoft Defender Security Center
|
||||
- **Option 1**: Onboard through Microsoft Defender Security Center
|
||||
- **Option 2**: Onboard through Azure Security Center
|
||||
|
||||
### Option 1: Onboard servers through Azure Security Center
|
||||
1. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
> [!NOTE]
|
||||
> Microsoft defender ATP standalone server license is required, per node, in order to onboard the server through Microsoft Defender Security Center (Option 1), or an Azure Security Center Standard license is required, per node, in order to onboard a server through Azure Security Center (Option 2), see [Supported features available in Azure Security Center](https://docs.microsoft.com/azure/security-center/security-center-services).
|
||||
|
||||
2. Select Windows Server 2008 R2 SP1, 2012 R2 and 2016 as the operating system.
|
||||
|
||||
3. Click **Onboard Servers in Azure Security Center**.
|
||||
|
||||
4. Follow the onboarding instructions in [Microsoft Defender Advanced Threat Protection with Azure Security Center](https://docs.microsoft.com/azure/security-center/security-center-wdatp).
|
||||
|
||||
### Option 2: Onboard servers through Microsoft Defender Security Center
|
||||
### Option 1: Onboard servers through Microsoft Defender Security Center
|
||||
You'll need to take the following steps if you choose to onboard servers through Microsoft Defender Security Center.
|
||||
|
||||
- For Windows Server 2008 R2 SP1, ensure that you fulfill the following requirements:
|
||||
@ -84,8 +77,6 @@ You'll need to take the following steps if you choose to onboard servers through
|
||||
> After onboarding the machine, you can choose to run a detection test to verify that it is properly onboarded to the service. For more information, see [Run a detection test on a newly onboarded Microsoft Defender ATP endpoint](run-detection-test.md).
|
||||
|
||||
### Configure and update System Center Endpoint Protection clients
|
||||
> [!IMPORTANT]
|
||||
> This step is required only if your organization uses System Center Endpoint Protection (SCEP) and you're onboarding Windows Server 2012 R2.
|
||||
|
||||
Microsoft Defender ATP integrates with System Center Endpoint Protection. The integration provides visibility to malware detections and to stop propagation of an attack in your organization by banning potentially malicious files or suspected malware.
|
||||
|
||||
@ -125,6 +116,18 @@ Once completed, you should see onboarded servers in the portal within an hour.
|
||||
- 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 you [enable access to Microsoft Defender ATP service URLs](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-proxy-internet#enable-access-to-microsoft-defender-atp-service-urls-in-the-proxy-server).
|
||||
|
||||
|
||||
|
||||
### Option 2: Onboard servers through Azure Security Center
|
||||
1. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
|
||||
2. Select Windows Server 2008 R2 SP1, 2012 R2 and 2016 as the operating system.
|
||||
|
||||
3. Click **Onboard Servers in Azure Security Center**.
|
||||
|
||||
4. Follow the onboarding instructions in [Microsoft Defender Advanced Threat Protection with Azure Security Center](https://docs.microsoft.com/azure/security-center/security-center-wdatp).
|
||||
|
||||
|
||||
|
||||
## Windows Server, version 1803 and Windows Server 2019
|
||||
To onboard Windows Server, version 1803 or Windows Server 2019, refer to the supported methods and versions below.
|
||||
|
||||
@ -169,7 +172,7 @@ Support for Windows Server, provide deeper insight into activities happening on
|
||||
|
||||
|
||||
## Integration with Azure Security Center
|
||||
Microsoft Defender ATP integrates with Azure Security Center to provide a comprehensive server protection solution. With this integration, Azure Security Center can leverage the power of Microsoft Defender ATP to provide improved threat detection for Windows Servers.
|
||||
Microsoft Defender ATP can integrate with Azure Security Center to provide a comprehensive server protection solution. With this integration, Azure Security Center can leverage the power of Microsoft Defender ATP to provide improved threat detection for Windows Servers.
|
||||
|
||||
The following capabilities are included in this integration:
|
||||
- Automated onboarding - Microsoft Defender ATP sensor is automatically enabled on Windows Servers that are onboarded to Azure Security Center. For more information on Azure Security Center onboarding, see [Onboarding to Azure Security Center Standard for enhanced security](https://docs.microsoft.com/azure/security-center/security-center-onboarding).
|
||||
|
@ -89,7 +89,7 @@ Validate stack integrity (StackPivot) | Ensures that the stack has not been redi
|
||||
>
|
||||
> Mikael then adds the app *test.exe* to the **Program settings** section. In the options for that app, under **Data Execution Prevention (DEP)**, he 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 will be that DEP only will be enabled for *test.exe*. All other apps will not have DEP applied.
|
||||
>
|
||||
>
|
||||
> * **Example 2**
|
||||
@ -100,8 +100,7 @@ Validate stack integrity (StackPivot) | Ensures that the stack has not been redi
|
||||
>
|
||||
> Josie also adds the app *miles.exe* to the **Program settings** section and configures **Control flow guard (CFG)** to **On**. She 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 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*.
|
||||
|
||||
> [!NOTE]
|
||||
> If you have found any issues in this article, you can report it directly to a Windows Server/Windows Client partner or use the Microsoft technical support numbers for your country.
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Update how long data is stored by MDATP
|
||||
description: Update data retention settings for Microsoft Defender Advanced Threat Protection (MDATP) by selecting between 30 days to 180 days.
|
||||
title: Verify data storage location and update data retention settings
|
||||
description: Verify data storage location and update data retention settings for Microsoft Defender Advanced Threat Protection
|
||||
keywords: data, storage, settings, retention, update
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
@ -15,9 +15,8 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/24/2018
|
||||
---
|
||||
# Update data retention settings for Microsoft Defender ATP
|
||||
# Verify data storage location and update data retention settings for Microsoft Defender ATP
|
||||
|
||||
**Applies to:**
|
||||
|
||||
@ -25,10 +24,18 @@ ms.date: 04/24/2018
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-gensettings-abovefoldlink)
|
||||
|
||||
During the onboarding process, a wizard takes you through the general settings of Microsoft Defender ATP. After onboarding, you might want to update the data retention settings.
|
||||
During the onboarding process, a wizard takes you through the data storage and retention settings of Microsoft Defender ATP.
|
||||
|
||||
After completing the onboarding, you can verify your selection in the data retention settings page.
|
||||
|
||||
## Verify data storage location
|
||||
During the [Set up phase](production-deployment.md), you would have selected the location to store your data.
|
||||
|
||||
You can verify the data location by navigating to **Settings** > **Data retention**.
|
||||
|
||||
## Update data retention settings
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Data retention**.
|
||||
|
||||
|
@ -28,11 +28,31 @@ You can [audit network protection](evaluate-network-protection.md) in a test env
|
||||
|
||||
You can enable network protection by using any of these methods:
|
||||
|
||||
* [PowerShell](#powershell)
|
||||
* [Microsoft Intune](#intune)
|
||||
* [Mobile Device Management (MDM)](#mdm)
|
||||
* [Microsoft Endpoint Configuration Manager](#microsoft-endpoint-configuration-manager)
|
||||
* [Group Policy](#group-policy)
|
||||
* [PowerShell](#powershell)
|
||||
|
||||
## PowerShell
|
||||
|
||||
1. Type **powershell** in the Start menu, right-click **Windows PowerShell** and click **Run as administrator**
|
||||
2. Enter the following cmdlet:
|
||||
|
||||
```PowerShell
|
||||
Set-MpPreference -EnableNetworkProtection Enabled
|
||||
```
|
||||
|
||||
You can enable the feature in audit mode using the following cmdlet:
|
||||
|
||||
```PowerShell
|
||||
Set-MpPreference -EnableNetworkProtection AuditMode
|
||||
```
|
||||
|
||||
Use `Disabled` instead of `AuditMode` or `Enabled` to turn the feature off.
|
||||
|
||||
|
||||
|
||||
|
||||
## Intune
|
||||
|
||||
@ -89,22 +109,6 @@ You can confirm network protection is enabled on a local computer by using Regis
|
||||
* 1=On
|
||||
* 2=Audit
|
||||
|
||||
## PowerShell
|
||||
|
||||
1. Type **powershell** in the Start menu, right-click **Windows PowerShell** and click **Run as administrator**
|
||||
2. Enter the following cmdlet:
|
||||
|
||||
```PowerShell
|
||||
Set-MpPreference -EnableNetworkProtection Enabled
|
||||
```
|
||||
|
||||
You can enable the feature in audit mode using the following cmdlet:
|
||||
|
||||
```PowerShell
|
||||
Set-MpPreference -EnableNetworkProtection AuditMode
|
||||
```
|
||||
|
||||
Use `Disabled` instead of `AuditMode` or `Enabled` to turn the feature off.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
Before Width: | Height: | Size: 53 KiB After Width: | Height: | Size: 46 KiB |
@ -21,11 +21,11 @@ manager: dansimp
|
||||
|
||||
**Applies to:**
|
||||
|
||||
* [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
* [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](microsoft-defender-advanced-threat-protection.md)
|
||||
|
||||
Exploit protection applies helps protect devices from malware that use exploits to spread and infect. It consists of a number of mitigations that can be applied at either the operating system level, or at the individual app level.
|
||||
|
||||
Many of the features that are part of the [Enhanced Mitigation Experience Toolkit (EMET)](https://technet.microsoft.com/security/jj653751) are now included in exploit protection.
|
||||
Many of the features that are part of the [Enhanced Mitigation Experience Toolkit (EMET)](https://support.microsoft.com/help/2458544/) are now included in exploit protection.
|
||||
|
||||
You use the Windows Security app or PowerShell to create a set of mitigations (known as a configuration). You can then export this configuration as an XML file and share it with multiple machines on your network so they all have the same set of mitigation settings.
|
||||
|
||||
@ -33,7 +33,7 @@ You can also convert and import an existing EMET configuration XML file into an
|
||||
|
||||
This topic describes how to create a configuration file and deploy it across your network, and how to convert an EMET configuration.
|
||||
|
||||
The [Evaluation Package](https://aka.ms/mp7z2w) contains a sample configuration file (name *ProcessMitigation-Selfhost-v4.xml* that you can use to see how the XML structure looks. The sample file also contains settings that have been converted from an EMET configuration. You can open the file in a text editor (such as Notepad) or import it directly into exploit protection and then review the settings in the Windows Security app, as described further in this topic.
|
||||
The [Evaluation Package](https://demo.wd.microsoft.com/Page/EP) contains a sample configuration file (name *ProcessMitigation.xml* (Selfhost v4) that you can use to see how the XML structure looks. The sample file also contains settings that have been converted from an EMET configuration. You can open the file in a text editor (such as Notepad) or import it directly into exploit protection and then review the settings in the Windows Security app, as described further in this topic.
|
||||
|
||||
## Create and export a configuration file
|
||||
|
||||
@ -53,27 +53,28 @@ When you have configured exploit protection to your desired state (including bot
|
||||
|
||||
3. At the bottom of the **Exploit protection** section, click **Export settings** and then choose the location and name of the XML file where you want the configuration to be saved.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you want to use Default configuration, use the settings "On by default" instead of "Use Default (On)" to get the settings exported correctly on the XML file.
|
||||
> [!IMPORTANT]
|
||||
> If you want to use Default configuration, use the settings "On by default" instead of "Use Default (On)" to get the settings exported correctly on the XML file.
|
||||
|
||||

|
||||

|
||||
|
||||
> [!NOTE]
|
||||
> When you export the settings, all settings for both app-level and system-level mitigations are saved. This means you don't need to export a file from both the **System settings** and **Program settings** sections - either section will export all settings.
|
||||
> [!NOTE]
|
||||
> When you export the settings, all settings for both app-level and system-level mitigations are saved. This means you don't need to export a file from both the **System settings** and **Program settings** sections—either section will export all settings.
|
||||
|
||||
### Use PowerShell to export a configuration file
|
||||
|
||||
1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator**
|
||||
1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator**.
|
||||
2. Enter the following cmdlet:
|
||||
|
||||
```PowerShell
|
||||
Get-ProcessMitigation -RegistryConfigFilePath filename.xml
|
||||
```
|
||||
|
||||
Change `filename` to any name or location of your choosing.
|
||||
Change `filename` to any name or location of your choosing.
|
||||
|
||||
Example command
|
||||
**Get-ProcessMitigation -RegistryConfigFilePath C:\ExploitConfigfile.xml**
|
||||
Example command:
|
||||
|
||||
**Get-ProcessMitigation -RegistryConfigFilePath C:\ExploitConfigfile.xml**
|
||||
|
||||
> [!IMPORTANT]
|
||||
> When you deploy the configuration using Group Policy, all machines that will use the configuration must be able to access the configuration file. Ensure you place the file in a shared location.
|
||||
@ -86,17 +87,18 @@ After importing, the settings will be instantly applied and can be reviewed in t
|
||||
|
||||
### Use PowerShell to import a configuration file
|
||||
|
||||
1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator**
|
||||
1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator**.
|
||||
2. Enter the following cmdlet:
|
||||
|
||||
```PowerShell
|
||||
Set-ProcessMitigation -PolicyFilePath filename.xml
|
||||
```
|
||||
|
||||
Change `filename` to the location and name of the exploit protection XML file.
|
||||
Change `filename` to the location and name of the exploit protection XML file.
|
||||
|
||||
Example command
|
||||
**Set-ProcessMitigation -PolicyFilePath C:\ExploitConfigfile.xml**
|
||||
Example command:
|
||||
|
||||
**Set-ProcessMitigation -PolicyFilePath C:\ExploitConfigfile.xml**
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
@ -116,14 +118,14 @@ You can only do this conversion in PowerShell.
|
||||
>
|
||||
> You can then convert that file using the PowerShell cmdlet described here before importing the settings into Exploit protection.
|
||||
|
||||
1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator**
|
||||
1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator**.
|
||||
2. Enter the following cmdlet:
|
||||
|
||||
```PowerShell
|
||||
ConvertTo-ProcessMitigationPolicy -EMETFilePath emetFile.xml -OutputFilePath filename.xml
|
||||
```
|
||||
|
||||
Change `emetFile` to the name and location of the EMET configuration file, and change `filename` to whichever location and file name you want to use.
|
||||
Change `emetFile` to the name and location of the EMET configuration file, and change `filename` to whichever location and file name you want to use.
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
@ -141,7 +143,7 @@ You can use Group Policy to deploy the configuration you've created to multiple
|
||||
|
||||
### Use Group Policy to distribute the configuration
|
||||
|
||||
1. On your Group Policy management machine, 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**.
|
||||
1. On your Group Policy management machine, open the [Group Policy Management Console](https://docs.microsoft.com/previous-versions/windows/desktop/gpmc/group-policy-management-console-portal), 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**.
|
||||
|
||||
@ -151,14 +153,14 @@ You can use Group Policy to deploy the configuration you've created to multiple
|
||||
|
||||
4. Double-click the **Use a common set of Exploit protection settings** setting and set the option to **Enabled**.
|
||||
|
||||
5. In the **Options::** section, enter the location and filename of the Exploit protection configuration file that you want to use, such as in the following examples:
|
||||
5. In the **Options::** section, enter the location and file name of the Exploit protection configuration file that you want to use, such as in the following examples:
|
||||
|
||||
* C:\MitigationSettings\Config.XML
|
||||
* \\\Server\Share\Config.xml
|
||||
* https://localhost:8080/Config.xml
|
||||
* C:\ExploitConfigfile.xml
|
||||
|
||||
6. Click **OK** and [Deploy the updated GPO as you normally do](https://msdn.microsoft.com/library/ee663280(v=vs.85).aspx).
|
||||
6. Click **OK** and [Deploy the updated GPO as you normally do](https://docs.microsoft.com/windows/win32/srvnodes/group-policy).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
@ -2,7 +2,7 @@
|
||||
title: Information protection in Windows overview
|
||||
ms.reviewer:
|
||||
description: Learn about how information protection works in Windows to identify and protect sensitive information
|
||||
keywords: information, protection, dlp, wip, data, loss, prevention, protect
|
||||
keywords: information, protection, dlp, data, loss, prevention, protect
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -35,7 +35,7 @@ Microsoft Defender ATP applies the following methods to discover, classify, and
|
||||
|
||||
- **Data discovery** - Identify sensitive data on Windows devices at risk
|
||||
- **Data classification** - Automatically classify data based on common Microsoft Information Protection (MIP) policies managed in Office 365 Security & Compliance Center. Auto-classification allows you to protect sensitive data even if the end user hasn’t manually classified it.
|
||||
- **Data protection** - Windows Information Protection (WIP) as outcome of Azure Information Protection label
|
||||
|
||||
|
||||
## Data discovery and data classification
|
||||
|
||||
@ -95,6 +95,4 @@ InformationProtectionLogs_CL
|
||||
- Go to **Settings** in Microsoft Defender Security Center, click on **Advanced Settings** under **General**.
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
- [How Windows Information Protection protects files with a sensitivity label](https://docs.microsoft.com/windows/security/information-protection/windows-information-protection/how-wip-works-with-labels)
|
||||
|
@ -64,6 +64,9 @@ $ curl -x http://proxy_address:port -w ' %{url_effective}\n' 'https://x.cp.wd.mi
|
||||
|
||||
Ensure that you use the same proxy address and port as configured in the `/lib/system/system/mdatp.service` file. Check your proxy configuration if there are errors from the above commands.
|
||||
|
||||
> [!WARNING]
|
||||
> The static proxy cannot be configured through a system-wide `HTTPS_PROXY` environment variable. Instead, ensure that `HTTPS_PROXY` is properly set in the `/lib/system/system/mdatp.service` file.
|
||||
|
||||
To use a static proxy, the `mdatp.service` file must be modified. Ensure the leading `#` is removed to uncomment the following line from `/lib/systemd/system/mdatp.service`:
|
||||
|
||||
```bash
|
||||
|
@ -23,24 +23,24 @@ ms.topic: article
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
|
||||
Live response is a capability that gives your security operations team instantaneous access to a device (also referred to as a machine) using a remote shell connection. This gives you the power to do in-depth investigative work and take immediate response actions to promptly contain identified threats –- in real time.
|
||||
Live response is a capability that gives your security operations team instantaneous access to a device (also referred to as a machine) using a remote shell connection. This gives you the power to do in-depth investigative work and take immediate response actions to promptly contain identified threats — in real time.
|
||||
|
||||
Live response is designed to enhance investigations by enabling your security operations team to collect forensic data, run scripts, send suspicious entities for analysis, remediate threats, and proactively hunt for emerging threats.
|
||||
|
||||
> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4qLUW]
|
||||
|
||||
With live response, analysts can do all of the following tasks:
|
||||
- Run basic and advanced commands to do investigative work on a device
|
||||
- Download files such as malware samples and outcomes of PowerShell scripts
|
||||
- Download files in the background (new!)
|
||||
- Upload a PowerShell script or executable to the library and run it on a device from a tenant level
|
||||
- Take or undo remediation actions
|
||||
- Run basic and advanced commands to do investigative work on a device.
|
||||
- Download files such as malware samples and outcomes of PowerShell scripts.
|
||||
- Download files in the background (new!).
|
||||
- Upload a PowerShell script or executable to the library and run it on a device from a tenant level.
|
||||
- Take or undo remediation actions.
|
||||
|
||||
## Before you begin
|
||||
|
||||
Before you can initiate a session on a device, make sure you fulfill the following requirements:
|
||||
|
||||
- **Verify that you're running a supported version of Windows 10** <br/>
|
||||
- **Verify that you're running a supported version of Windows 10**. <br/>
|
||||
Devices must be running one of the following versions of Windows 10:
|
||||
- [1909](https://docs.microsoft.com/windows/whats-new/whats-new-windows-10-version-1909) or later
|
||||
- [1903](https://docs.microsoft.com/windows/whats-new/whats-new-windows-10-version-1903)
|
||||
@ -48,29 +48,29 @@ Devices must be running one of the following versions of Windows 10:
|
||||
- [1803](https://docs.microsoft.com/windows/whats-new/whats-new-windows-10-version-1803)
|
||||
- [1709](https://docs.microsoft.com/windows/whats-new/whats-new-windows-10-version-1709)
|
||||
|
||||
- **Make sure to install appropriate security updates**<br/>
|
||||
- **Make sure to install appropriate security updates**.<br/>
|
||||
- 1903: [KB4515384](https://support.microsoft.com/help/4515384/windows-10-update-kb4515384)
|
||||
- 1809 (RS5): [KB4537818](https://support.microsoft.com/help/4537818/windows-10-update-kb4537818)
|
||||
- 1803 (RS4): [KB4537795](https://support.microsoft.com/help/4537795/windows-10-update-kb4537795)
|
||||
- 1709 (RS3): [KB4537816](https://support.microsoft.com/help/4537816/windows-10-update-kb4537816)
|
||||
|
||||
- **Enable live response from the settings page**<br>
|
||||
- **Enable live response from the settings page**.<br>
|
||||
You'll need to enable the live response capability in the [Advanced features settings](advanced-features.md) page.
|
||||
|
||||
>[!NOTE]
|
||||
>Only users with manage security or global admin roles can edit these settings.
|
||||
|
||||
- **Ensure that the machine has an Automation Remediation level assigned to it**<br>
|
||||
You'll need to enable, at least, the minimum Remdiation Level for a given Machine Group. Otherwise you won't be able to establish a Live Response session to a member of that group.
|
||||
- **Ensure that the machine has an Automation Remediation level assigned to it**.<br>
|
||||
You'll need to enable, at least, the minimum Remediation Level for a given Machine Group. Otherwise you won't be able to establish a Live Response session to a member of that group.
|
||||
|
||||
- **Enable live response unsigned script execution** (optional) <br>
|
||||
- **Enable live response unsigned script execution** (optional). <br>
|
||||
|
||||
>[!WARNING]
|
||||
>Allowing the use of unsigned scripts may increase your exposure to threats.
|
||||
|
||||
Running unsigned scripts is not recommended as it can increase your exposure to threats. If you must use them however, you'll need to enable the setting in the [Advanced features settings](advanced-features.md) page.
|
||||
|
||||
- **Ensure that you have the appropriate permissions**<br>
|
||||
- **Ensure that you have the appropriate permissions**.<br>
|
||||
Only users who have been provisioned with the appropriate permissions can initiate a session. For more information on role assignments, see [Create and manage roles](user-roles.md).
|
||||
|
||||
> [!IMPORTANT]
|
||||
@ -133,7 +133,7 @@ drivers | Shows all drivers installed on the device. |
|
||||
|`trace` | Sets the terminal's logging mode to debug. |
|
||||
|
||||
### Advanced commands
|
||||
The following commands are available for user roles that are granted the ability to run **advanced** live response commands. For more information on role assignments see, [Create and manage roles](user-roles.md).
|
||||
The following commands are available for user roles that are granted the ability to run **advanced** live response commands. For more information on role assignments see [Create and manage roles](user-roles.md).
|
||||
|
||||
| Command | Description |
|
||||
|---|---|
|
||||
@ -157,15 +157,18 @@ The advanced commands offer a more robust set of actions that allow you to take
|
||||
For scenarios when you'd like get a file from a device you're investigating, you can use the `getfile` command. This allows you to save the file from the device for further investigation.
|
||||
|
||||
>[!NOTE]
|
||||
>There is a file size limit of 750mb.
|
||||
>The following file size limits apply:
|
||||
>- `getfile` limit: 3 GB
|
||||
>- `fileinfo` limit: 10 GB
|
||||
>- `library` limit: 250 MB
|
||||
|
||||
### Download a file in the background
|
||||
|
||||
To enable your security operations team to continue investigating an impacted device, files can now be downloaded in the background.
|
||||
|
||||
- To download a file in the background, in the live response command console, type `download <file_path> &`
|
||||
- To download a file in the background, in the live response command console, type `download <file_path> &`.
|
||||
- If you are waiting for a file to be downloaded, you can move it to the background by using Ctrl + Z.
|
||||
- To bring a file download to the foreground, in the live response command console, type `fg <command_id>`
|
||||
- To bring a file download to the foreground, in the live response command console, type `fg <command_id>`.
|
||||
|
||||
Here are some examples:
|
||||
|
||||
@ -173,7 +176,7 @@ Here are some examples:
|
||||
|Command |What it does |
|
||||
|---------|---------|
|
||||
|`"C:\windows\some_file.exe" &` |Starts downloading a file named *some_file.exe* in the background. |
|
||||
|`fg 1234` |Returns a download with command ID *1234* to the foreground |
|
||||
|`fg 1234` |Returns a download with command ID *1234* to the foreground. |
|
||||
|
||||
|
||||
### Put a file in the library
|
||||
@ -277,11 +280,14 @@ Each command is tracked with full details such as:
|
||||
|
||||
## Limitations
|
||||
|
||||
- Live response sessions are limited to 10 live response sessions at a time
|
||||
- Large scale command execution is not supported
|
||||
- A user can only initiate one session at a time
|
||||
- A device can only be in one session at a time
|
||||
- There is a file size limit of 750mb when downloading files from a device
|
||||
- Live response sessions are limited to 10 live response sessions at a time.
|
||||
- Large scale command execution is not supported.
|
||||
- A user can only initiate one session at a time.
|
||||
- A device can only be in one session at a time.
|
||||
- The following file size limits apply:
|
||||
- `getfile` limit: 3 GB
|
||||
- `fileinfo` limit: 10 GB
|
||||
- `library` limit: 250 MB
|
||||
|
||||
## Related article
|
||||
- [Live response command examples](live-response-command-examples.md)
|
||||
|
@ -19,6 +19,12 @@ ms.topic: conceptual
|
||||
|
||||
# Intune-based deployment for Microsoft Defender ATP for Mac
|
||||
|
||||
> [!NOTE]
|
||||
> This documentation explains the legacy method for deploying and configuring Microsoft Defender ATP on macOS devices. The native experience is now available in the MEM console. The release of the native UI in the MEM console provide admins with a much simpler way to configure and dfeploy the application and send it down to macOS devices.
|
||||
> This blog post explains the new features: https://techcommunity.microsoft.com/t5/microsoft-endpoint-manager-blog/microsoft-endpoint-manager-simplifies-deployment-of-microsoft/ba-p/1322995
|
||||
> To configure the app go here: https://docs.microsoft.com/mem/intune/protect/antivirus-microsoft-defender-settings-macos
|
||||
> To deploy the app go here: https://docs.microsoft.com/mem/intune/apps/apps-advanced-threat-protection-macos
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP) for Mac](microsoft-defender-atp-mac.md)
|
||||
|
@ -71,12 +71,13 @@ Filter by the following machine health states:
|
||||
|
||||
For more information on how to address issues on misconfigured machines see, [Fix unhealthy sensors](fix-unhealthy-sensors.md).
|
||||
|
||||
### Security state
|
||||
### Antivirus status
|
||||
|
||||
Filter by machines that are well configured or require attention based on the security controls that are enabled in your organization. Applies to active Windows 10 machines only.
|
||||
Filter machines by antivirus status. Applies to active Windows 10 machines only.
|
||||
|
||||
- **Well configured** - Machines have the security controls well configured.
|
||||
- **Requires attention** - Machines where improvements can be made to increase the overall security posture of your organization.
|
||||
- **Disabled** - Virus & threat protection is turned off.
|
||||
- **Not reporting** - Virus & threat protection is not reporting.
|
||||
- **Not updated** - Virus & threat protection is not up to date.
|
||||
|
||||
For more information, see [View the Threat & Vulnerability Management dashboard](tvm-dashboard-insights.md).
|
||||
|
||||
|
@ -21,39 +21,39 @@ ms.topic: conceptual
|
||||
|
||||
## Remediation actions
|
||||
|
||||
When an automated investigation runs, a verdict is generated for each piece of evidence investigated. Verdicts can be *Malicious*, *Suspicious*, or *Clean*. Depending on the type of threat and resulting verdict, remediation actions occur automatically or upon approval by your organization’s security operations team. For example, some actions, such as removing malware, are taken automatically. Other actions require review and approval to proceed.
|
||||
When an automated investigation runs, a verdict is generated for each piece of evidence investigated. Verdicts can be *Malicious*, *Suspicious*, or *No threats found*. Depending on the type of threat and resulting verdict, remediation actions occur automatically or upon approval by your organization’s security operations team. For example, some actions, such as removing malware, are taken automatically. Other actions require review and approval to proceed.
|
||||
|
||||
When a verdict of *Malicious* is reached for a piece of evidence, Microsoft Defender Advanced Threat Protection takes one of the following remediation actions automatically:
|
||||
- Quarantine file
|
||||
- Remove registry key
|
||||
- Kill process
|
||||
- Stop service
|
||||
- Remove registry key
|
||||
- Disable driver
|
||||
- Remove scheduled task
|
||||
- Quarantine a file
|
||||
- Remove a registry key
|
||||
- Kill a process
|
||||
- Stop a service
|
||||
- Remove a registry key
|
||||
- Disable a driver
|
||||
- Remove a scheduled task
|
||||
|
||||
Evidence determined as *Suspicious* results in pending actions that require approval. As a best practice, make sure to [approve (or reject) pending actions](#review-pending-actions) as soon as possible. This helps your automated investigations complete in a timely manner.
|
||||
Evidence determined as *Suspicious* results in pending actions that require approval. As a best practice, make sure to [approve (or reject) pending actions](#review-pending-actions) as soon as possible so that you automated investigations complete in a timely manner.
|
||||
|
||||
No actions are taken when evidence is determined to be *Clean*.
|
||||
No actions are taken when a verdict of *No threats found* is reached for a piece of evidence.
|
||||
|
||||
In Microsoft Defender Advanced Threat Protection, all verdicts are [tracked and viewable in the Microsoft Defender Security Center](#review-completed-actions).
|
||||
|
||||
## Review pending actions
|
||||
|
||||
1. Go to the Microsoft Defender Security Center ([https://securitycenter.windows.com](https://securitycenter.windows.com)) and sign in. This takes you to your Security dashboard.
|
||||
1. Go to the Microsoft Defender Security Center ([https://securitycenter.windows.com](https://securitycenter.windows.com)) and sign in. You'll see the Security dashboard.
|
||||
|
||||
2. On the Security dashboard, in the navigation pane on the left, choose **Automated investigations** > **Action center**.
|
||||
|
||||
3. Review any items on the **Pending** tab.
|
||||
|
||||
Selecting an investigation from any of the categories opens a panel where you can approve or reject the remediation. Other details such as file or service details, investigation details, and alert details are displayed. From the panel, you can click on the **Open investigation page** link to see the investigation details.
|
||||
Select an investigation from any of the categories to open a panel where you can approve or reject remediation actions. Other details such as file or service details, investigation details, and alert details are displayed. From the panel, you can click on the **Open investigation page** link to see the investigation details.
|
||||
|
||||
You can also select multiple investigations to approve or reject actions on multiple investigations.
|
||||
|
||||
|
||||
## Review completed actions
|
||||
|
||||
1. Go to the Microsoft Defender Security Center ([https://securitycenter.windows.com](https://securitycenter.windows.com)) and sign in. This takes you to your Security dashboard.
|
||||
1. Go to the Microsoft Defender Security Center ([https://securitycenter.windows.com](https://securitycenter.windows.com)) and sign in. You'll see the Security dashboard.
|
||||
|
||||
2. On the Security dashboard, in the navigation pane on the left, choose **Automated investigations** > **Action center**.
|
||||
|
||||
@ -61,6 +61,12 @@ In Microsoft Defender Advanced Threat Protection, all verdicts are [tracked and
|
||||
|
||||
4. Select an item to view more details about that remediation action.
|
||||
|
||||
## Next steps
|
||||
|
||||
- [View details and results of automated investigations](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center)
|
||||
|
||||
- [Get an overview of live response](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/live-response)
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Automated investigation and response in Office 365 Advanced Threat Protection](https://docs.microsoft.com/microsoft-365/security/office-365-security/office-365-air)
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Manage indicators
|
||||
ms.reviewer:
|
||||
description: Create indicators for a file hash, IP address, URLs or domains that define the detection, prevention, and exclusion of entities.
|
||||
description: Create indicators for a file hash, IP address, URLs, or domains that define the detection, prevention, and exclusion of entities.
|
||||
keywords: manage, allowed, blocked, whitelist, blacklist, block, clean, malicious, file hash, ip address, urls, domain
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
@ -26,7 +26,7 @@ ms.topic: article
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-automationexclusionlist-abovefoldlink)
|
||||
|
||||
Indicator of compromise (IoCs) matching is an essential feature in every endpoint protection solution. This capability is available in Microsoft Defender ATP and gives SecOps the ability to set a list of indicators for detection and for blocking (prevention and response).
|
||||
Indicator of compromise (IoCs) matching is an essential feature in every endpoint protection solution. This capability gives SecOps the ability to set a list of indicators for detection and for blocking (prevention and response).
|
||||
|
||||
Create indicators that define the detection, prevention, and exclusion of entities. You can define the action to be taken as well as the duration for when to apply the action as well as the scope of the machine group to apply it to.
|
||||
|
||||
@ -54,7 +54,7 @@ You can create an indicator for:
|
||||
- URLs/domains
|
||||
|
||||
>[!NOTE]
|
||||
>There is a limit of 5000 indicators per tenant.
|
||||
>There is a limit of 15,000 indicators per tenant.
|
||||
|
||||
|
||||

|
||||
@ -69,6 +69,7 @@ There are two ways you can create indicators for files:
|
||||
|
||||
### Before you begin
|
||||
It's important to understand the following prerequisites prior to creating indicators for files:
|
||||
|
||||
- This feature is available if your organization uses Windows Defender Antivirus and Cloud–based protection is enabled. For more information, see [Manage cloud–based protection](../windows-defender-antivirus/deploy-manage-report-windows-defender-antivirus.md).
|
||||
- The Antimalware client version must be 4.18.1901.x or later.
|
||||
- Supported on machines on Windows 10, version 1703 or later.
|
||||
@ -103,18 +104,18 @@ One of the options when taking [response actions on a file](respond-file-alerts.
|
||||
|
||||
When you add an indicator hash for a file, you can choose to raise an alert and block the file whenever a machine in your organization attempts to run it.
|
||||
|
||||
Files automatically blocked by an indicator won't show up in the files's Action center, but the alerts will still be visible in the Alerts queue.
|
||||
Files automatically blocked by an indicator won't show up in the file's Action center, but the alerts will still be visible in the Alerts queue.
|
||||
|
||||
## Create indicators for IPs and URLs/domains (preview)
|
||||
## Create indicators for IPs and URLs/domains
|
||||
Microsoft Defender ATP can block what Microsoft deems as malicious IPs/URLs, through Windows Defender SmartScreen for Microsoft browsers, and through Network Protection for non-Microsoft browsers or calls made outside of a browser.
|
||||
|
||||
The threat intelligence data set for this has been managed by Microsoft.
|
||||
|
||||
By creating indicators for IPs and URLs or domains, you can now allow or block IPs, URLs or domains based on your own threat intelligence. You can do this through the settings page or by machine groups if you deem certain groups to be more or less at risk than others.
|
||||
By creating indicators for IPs and URLs or domains, you can now allow or block IPs, URLs, or domains based on your own threat intelligence. You can do this through the settings page or by machine groups if you deem certain groups to be more or less at risk than others.
|
||||
|
||||
### Before you begin
|
||||
It's important to understand the following prerequisites prior to creating indicators for IPS, URLs or domains:
|
||||
- URL/IP allow and block relies on the Microsoft Defender ATP component Network Protection to be enabled in block mode. For more information on Network Protection and configuration instructions, see [Protect your network](network-protection.md).
|
||||
It's important to understand the following prerequisites prior to creating indicators for IPS, URLs, or domains:
|
||||
- URL/IP allow and block relies on the Microsoft Defender ATP component Network Protection to be enabled in block mode. For more information on Network Protection and configuration instructions, see [Enable network protection](enable-network-protection.md).
|
||||
- The Antimalware client version must be 4.18.1906.x or later.
|
||||
- Supported on machines on Windows 10, version 1709 or later.
|
||||
- Ensure that **Custom network indicators** is enabled in **Microsoft Defender Security Center > Settings > Advanced features**. For more information, see [Advanced features](advanced-features.md).
|
||||
@ -132,7 +133,7 @@ It's important to understand the following prerequisites prior to creating indic
|
||||
>[!NOTE]
|
||||
>There may be up to 2 hours latency (usually less) between the time the action is taken, and the URL and IP being blocked.
|
||||
|
||||
### Create an indicator for IPs, URLs or domains from the settings page
|
||||
### Create an indicator for IPs, URLs, or domains from the settings page
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Indicators**.
|
||||
|
||||
@ -147,6 +148,46 @@ It's important to understand the following prerequisites prior to creating indic
|
||||
|
||||
5. Review the details in the Summary tab, then click **Save**.
|
||||
|
||||
## Create indicators for certificates (preview)
|
||||
|
||||
You can create indicators for certificates. Some common use cases include:
|
||||
|
||||
- Scenarios when you need to deploy blocking technologies, such as [attack surface reduction rules](attack-surface-reduction.md) and [controlled folder access](controlled-folders.md) but need to allow behaviors from signed applications by adding the certificate in the allow list.
|
||||
- Blocking the use of a specific signed application across your organization. By creating an indicator to block the certificate of the application, Windows Defender AV will prevent file executions (block and remediate) and the Automated Investigation and Remediation behave the same.
|
||||
|
||||
|
||||
### Before you begin
|
||||
|
||||
It's important to understand the following requirements prior to creating indicators for certificates:
|
||||
|
||||
- This feature is available if your organization uses Windows Defender Antivirus and Cloud–based protection is enabled. For more information, see [Manage cloud–based protection](../windows-defender-antivirus/deploy-manage-report-windows-defender-antivirus.md).
|
||||
- The Antimalware client version must be 4.18.1901.x or later.
|
||||
- Supported on machines on Windows 10, version 1703 or later.
|
||||
- The virus and threat protection definitions must be up-to-date.
|
||||
- This feature currently supports entering .CER or .PEM file extensions.
|
||||
|
||||
>[!IMPORTANT]
|
||||
> - A valid leaf certificate is a signing certificate that has a valid certification path and must be chained to the Root Certificate Authority (CA) trusted by Microsoft. Alternatively, a custom (self-signed) certificate can be used as long as it’s trusted by the client (Root CA certificate is installed under the Local Machine 'Trusted Root Certification Authorities').
|
||||
>- The children or parent of the allow/block certificate IOCs are not included in the allow/block IoC functionality – only leaf certificates are supported.
|
||||
>- Microsoft signed certificates cannot be blocked.
|
||||
|
||||
#### Create an indicator for certificates from the settings page:
|
||||
|
||||
>[!IMPORTANT]
|
||||
> It can take up to 3 hours to create and remove a certificate IoC.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Indicators**.
|
||||
|
||||
2. Select the **Certificate** tab.
|
||||
|
||||
3. Select **Add indicator**.
|
||||
|
||||
4. Specify the following details:
|
||||
- Indicator - Specify the entity details and define the expiration of the indicator.
|
||||
- Action - Specify the action to be taken and provide a description.
|
||||
- Scope - Define the scope of the machine group.
|
||||
|
||||
5. Review the details in the Summary tab, then click **Save**.
|
||||
|
||||
|
||||
## Manage indicators
|
||||
@ -163,8 +204,33 @@ You can also choose to upload a CSV file that defines the attributes of indicato
|
||||
|
||||
Download the sample CSV to know the supported column attributes.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Indicators**.
|
||||
|
||||
2. Select the tab of the entity type you'd like to import indicators for.
|
||||
|
||||
3. Select **Import** > **Choose file**.
|
||||
|
||||
4. Select **Import**. Do this for all the files you'd like to import.
|
||||
|
||||
5. Select **Done**.
|
||||
|
||||
The following table shows the supported parameters.
|
||||
|
||||
Parameter | Type | Description
|
||||
:---|:---|:---
|
||||
indicatorType | Enum | Type of the indicator. Possible values are: "FileSha1", "FileSha256", "IpAddress", "DomainName" and "Url". **Required**
|
||||
indicatorValue | String | Identity of the [Indicator](ti-indicator.md) entity. **Required**
|
||||
action | Enum | The action that will be taken if the indicator will be discovered in the organization. Possible values are: "Alert", "AlertAndBlock", and "Allowed". **Required**
|
||||
title | String | Indicator alert title. **Required**
|
||||
description | String | Description of the indicator. **Required**
|
||||
expirationTime | DateTimeOffset | The expiration time of the indicator in the following format YYYY-MM-DDTHH:MM:SS.0Z. **Optional**
|
||||
severity | Enum | The severity of the indicator. Possible values are: "Informational", "Low", "Medium" and "High". **Optional**
|
||||
recommendedActions | String | TI indicator alert recommended actions. **Optional**
|
||||
rbacGroupNames | String | Comma-separated list of RBAC group names the indicator would be applied to. **Optional**
|
||||
|
||||
|
||||
|
||||
## Related topic
|
||||
- [Create contextual IoC](respond-file-alerts.md#add-indicator-to-block-or-allow-a-file)
|
||||
- [Use the Microsoft Defender ATP indicators API](ti-indicator.md)
|
||||
- [Use partner integrated solutions](partner-applications.md)
|
||||
|
||||
|
@ -74,9 +74,9 @@ The following table lists the services and their associated URLs that your netwo
|
||||
| Service location | DNS record |
|
||||
| ---------------------------------------- | ----------------------- |
|
||||
| Common URLs for all locations | x.cp.wd.microsoft.com <br/> cdn.x.cp.wd.microsoft.com <br/> eu-cdn.x.cp.wd.microsoft.com <br/> wu-cdn.x.cp.wd.microsoft.com <br/> officecdn-microsoft-com.akamaized.net <br/> crl.microsoft.com <br/> events.data.microsoft.com |
|
||||
| European Union | europe.x.cp.wd.microsoft.com <br/> eu-v20.events.data.microsoft.com <br/> usseu1northprod.blob.core.windows.net <br/> usseu1westprod.blob.core.windows.net |
|
||||
| United Kingdom | unitedkingdom.x.cp.wd.microsoft.com <br/> uk-v20.events.data.microsoft.com <br/> ussuk1southprod.blob.core.windows.net <br/> ussuk1westprod.blob.core.windows.net |
|
||||
| United States | unitedstates.x.cp.wd.microsoft.com <br/> us-v20.events.data.microsoft.com <br/> ussus1eastprod.blob.core.windows.net <br/> ussus1westprod.blob.core.windows.net |
|
||||
| European Union | europe.x.cp.wd.microsoft.com <br/> eu-v20.events.data.microsoft.com <br/> usseu1northprod.blob.core.windows.net <br/> usseu1westprod.blob.core.windows.net <br/> winatp-gw-weu.microsoft.com <br/> winatp-gw-neu.microsoft.com |
|
||||
| United Kingdom | unitedkingdom.x.cp.wd.microsoft.com <br/> uk-v20.events.data.microsoft.com <br/> ussuk1southprod.blob.core.windows.net <br/> ussuk1westprod.blob.core.windows.net <br/> winatp-gw-ukw.microsoft.com <br/> winatp-gw-uks.microsoft.com |
|
||||
| United States | unitedstates.x.cp.wd.microsoft.com <br/> us-v20.events.data.microsoft.com <br/> ussus1eastprod.blob.core.windows.net <br/> ussus1westprod.blob.core.windows.net <br/> winatp-gw-cus.microsoft.com <br/> winatp-gw-eus.microsoft.com |
|
||||
|
||||
Microsoft Defender ATP can discover a proxy server by using the following discovery methods:
|
||||
- Proxy auto-config (PAC)
|
||||
|
@ -27,7 +27,7 @@ ms.custom: asr
|
||||
|
||||
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.
|
||||
|
||||
Network protection 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).
|
||||
Network protection expands the scope of [Microsoft Defender SmartScreen](../microsoft-defender-smartscreen/microsoft-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).
|
||||
|
||||
Network protection is supported beginning with Windows 10, version 1709.
|
||||
|
||||
|
@ -71,6 +71,7 @@ description | String | Description of the indicator. **Required**
|
||||
expirationTime | DateTimeOffset | The expiration time of the indicator. **Optional**
|
||||
severity | Enum | The severity of the indicator. possible values are: "Informational", "Low", "Medium" and "High". **Optional**
|
||||
recommendedActions | String | TI indicator alert recommended actions. **Optional**
|
||||
rbacGroupNames | String | Comma-separated list of RBAC group names the indicator would be applied to. **Optional**
|
||||
|
||||
|
||||
## Response
|
||||
@ -87,16 +88,18 @@ Here is an example of the request.
|
||||
POST https://api.securitycenter.windows.com/api/indicators
|
||||
Content-type: application/json
|
||||
{
|
||||
"indicatorValue": "220e7d15b011d7fac48f2bd61114db1022197f7f",
|
||||
"indicatorType": "FileSha1",
|
||||
"title": "test",
|
||||
"application": "demo-test",
|
||||
"expirationTime": "2020-12-12T00:00:00Z",
|
||||
"action": "AlertAndBlock",
|
||||
"severity": "Informational",
|
||||
"description": "test",
|
||||
"recommendedActions": "nothing"
|
||||
"indicatorValue": "220e7d15b011d7fac48f2bd61114db1022197f7f",
|
||||
"indicatorType": "FileSha1",
|
||||
"title": "test",
|
||||
"application": "demo-test",
|
||||
"expirationTime": "2020-12-12T00:00:00Z",
|
||||
"action": "AlertAndBlock",
|
||||
"severity": "Informational",
|
||||
"description": "test",
|
||||
"recommendedActions": "nothing",
|
||||
"rbacGroupNames": ["group1", "group2"]
|
||||
}
|
||||
```
|
||||
|
||||
## Related topic
|
||||
- [Manage indicators](manage-indicators.md)
|
@ -44,6 +44,8 @@ Turn on the preview experience setting to be among the first to try upcoming fea
|
||||
## Preview features
|
||||
|
||||
The following features are included in the preview release:
|
||||
- [Create indicators for certificates](manage-indicators.md) <br> Create indicators to allow or block certificates.
|
||||
|
||||
- [Microsoft Defender ATP for Linux](microsoft-defender-atp-linux.md) <br> Microsoft Defender ATP now adds support for Linux. Learn how to install, configure, update, and use Microsoft Defender ATP for Linux.
|
||||
|
||||
- [Threat & Vulnerability supported operating systems and platforms](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/tvm-supported-os) <BR> Ensure that you meet the operating system or platform requisites for Threat & Vulnerability Management so the activities in your devices are properly accounted for. Threat & Vulnerability Management supports Windows 7, Windows 10 1607-1703, Windows 10 1709+, Windows Server 2008R2, Windows Server 2012R2, Windows Server 2016, Windows Server 2019. <BR> <BR> Secure Configuration Assessment (SCA) supports Windows 10 1709+, Windows Server 2008R2, Windows Server 2012R2, Windows Server 2016, and Windows Server 2019. See [Secure Configuration Assessment (SCA) for Windows Server now in public preview](https://techcommunity.microsoft.com/t5/microsoft-defender-atp/secure-configuration-assessment-sca-for-windows-server-now-in/ba-p/1243885) and [Reducing risk with new Threat & Vulnerability Management capabilities](https://techcommunity.microsoft.com/t5/microsoft-defender-atp/reducing-risk-with-new-threat-amp-vulnerability-management/ba-p/978145) blogs for more information.
|
||||
|
After Width: | Height: | Size: 151 KiB |
Before Width: | Height: | Size: 106 KiB After Width: | Height: | Size: 106 KiB |
Before Width: | Height: | Size: 39 KiB After Width: | Height: | Size: 39 KiB |
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 40 KiB |
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Available Windows Defender SmartScreen Group Policy and mobile device management (MDM) settings (Windows 10)
|
||||
description: A list of all available settings for Windows Defender SmartScreen using Group Policy and mobile device management (MDM) settings.
|
||||
keywords: SmartScreen Filter, Windows SmartScreen, Windows Defender SmartScreen
|
||||
title: Available Microsoft Defender SmartScreen Group Policy and mobile device management (MDM) settings (Windows 10)
|
||||
description: A list of all available settings for Microsoft Defender SmartScreen using Group Policy and mobile device management (MDM) settings.
|
||||
keywords: SmartScreen Filter, Windows SmartScreen, Microsoft Defender SmartScreen
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
@ -13,13 +13,13 @@ ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
---
|
||||
# Available Windows Defender SmartScreen Group Policy and mobile device management (MDM) settings
|
||||
# Available Microsoft Defender SmartScreen Group Policy and mobile device management (MDM) settings
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
|
||||
Windows Defender SmartScreen works with Intune, Group Policy, and mobile device management (MDM) settings to help you manage your organization's computer settings. Based on how you set up Windows Defender SmartScreen, you can show employees a warning page and let them continue to the site, or you can block the site entirely.
|
||||
Microsoft Defender SmartScreen works with Intune, Group Policy, and mobile device management (MDM) settings to help you manage your organization's computer settings. Based on how you set up Microsoft Defender SmartScreen, you can show employees a warning page and let them continue to the site, or you can block the site entirely.
|
||||
|
||||
See [Windows 10 (and later) settings to protect devices using Intune](https://docs.microsoft.com/intune/endpoint-protection-windows-10#windows-defender-smartscreen-settings) for the controls you can use in Intune.
|
||||
|
||||
@ -35,7 +35,7 @@ SmartScreen uses registry-based Administrative Template policy settings. For mor
|
||||
<tr>
|
||||
<td><strong>Windows 10, version 1703:</strong><br>Administrative Templates\Windows Components\Windows Defender SmartScreen\Explorer\Configure Windows Defender SmartScreen<p><strong>Windows 10, Version 1607 and earlier:</strong><br>Administrative Templates\Windows Components\File Explorer\Configure Windows SmartScreen</td>
|
||||
<td>At least Windows Server 2012, Windows 8 or Windows RT</td>
|
||||
<td>This policy setting turns on Windows Defender SmartScreen.<p>If you enable this setting, it turns on Windows Defender SmartScreen and your employees are unable to turn it off. Additionally, when enabling this feature, you must also pick whether Windows Defender SmartScreen should Warn your employees or Warn and prevent bypassing the message (effectively blocking the employee from the site).<p>If you disable this setting, it turns off Windows Defender SmartScreen and your employees are unable to turn it on.<p>If you don't configure this setting, your employees can decide whether to use Windows Defender SmartScreen.</td>
|
||||
<td>This policy setting turns on Microsoft Defender SmartScreen.<p>If you enable this setting, it turns on Microsoft Defender SmartScreen and your employees are unable to turn it off. Additionally, when enabling this feature, you must also pick whether Microsoft Defender SmartScreen should Warn your employees or Warn and prevent bypassing the message (effectively blocking the employee from the site).<p>If you disable this setting, it turns off Microsoft Defender SmartScreen and your employees are unable to turn it on.<p>If you don't configure this setting, your employees can decide whether to use Microsoft Defender SmartScreen.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Administrative Templates\Windows Components\Windows Defender SmartScreen\Explorer\Configure App Install Control</td>
|
||||
@ -45,38 +45,38 @@ SmartScreen uses registry-based Administrative Template policy settings. For mor
|
||||
<tr>
|
||||
<td><strong>Windows 10, version 1703:</strong><br>Administrative Templates\Windows Components\Windows Defender SmartScreen\Microsoft Edge\Configure Windows Defender SmartScreen<p><strong>Windows 10, Version 1607 and earlier:</strong><br>Administrative Templates\Windows Components\Microsoft Edge\Configure Windows SmartScreen</td>
|
||||
<td>Microsoft Edge on Windows 10 or later</td>
|
||||
<td>This policy setting turns on Windows Defender SmartScreen.<p>If you enable this setting, it turns on Windows Defender SmartScreen and your employees are unable to turn it off.<p>If you disable this setting, it turns off Windows Defender SmartScreen and your employees are unable to turn it on.<p>If you don't configure this setting, your employees can decide whether to use Windows Defender SmartScreen.</td>
|
||||
<td>This policy setting turns on Microsoft Defender SmartScreen.<p>If you enable this setting, it turns on Microsoft Defender SmartScreen and your employees are unable to turn it off.<p>If you disable this setting, it turns off Microsoft Defender SmartScreen and your employees are unable to turn it on.<p>If you don't configure this setting, your employees can decide whether to use Microsoft Defender SmartScreen.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Windows 10, version 1703:</strong><br>Administrative Templates\Windows Components\Windows Defender SmartScreen\Microsoft Edge\Prevent bypassing Windows Defender SmartScreen prompts for files<p><strong>Windows 10, Version 1511 and 1607:</strong><br>Administrative Templates\Windows Components\Microsoft Edge\Prevent bypassing Windows SmartScreen prompts for files</td>
|
||||
<td>Microsoft Edge on Windows 10, version 1511 or later</td>
|
||||
<td>This policy setting stops employees from bypassing the Windows Defender SmartScreen warnings about potentially malicious files.<p>If you enable this setting, it stops employees from bypassing the warning, stopping the file download.<p>If you disable or don't configure this setting, your employees can bypass the warnings and continue to download potentially malicious files.</td>
|
||||
<td>This policy setting stops employees from bypassing the Microsoft Defender SmartScreen warnings about potentially malicious files.<p>If you enable this setting, it stops employees from bypassing the warning, stopping the file download.<p>If you disable or don't configure this setting, your employees can bypass the warnings and continue to download potentially malicious files.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Windows 10, version 1703:</strong><br>Administrative Templates\Windows Components\Windows Defender SmartScreen\Microsoft Edge\Prevent bypassing Windows Defender SmartScreen prompts for sites<p><strong>Windows 10, Version 1511 and 1607:</strong><br>Administrative Templates\Windows Components\Microsoft Edge\Prevent bypassing Windows SmartScreen prompts for sites</td>
|
||||
<td>Microsoft Edge on Windows 10, version 1511 or later</td>
|
||||
<td>This policy setting stops employees from bypassing the Windows Defender SmartScreen warnings about potentially malicious sites.<p>If you enable this setting, it stops employees from bypassing the warning, stopping them from going to the site.<p>If you disable or don't configure this setting, your employees can bypass the warnings and continue to visit a potentially malicious site.</td>
|
||||
<td>This policy setting stops employees from bypassing the Microsoft Defender SmartScreen warnings about potentially malicious sites.<p>If you enable this setting, it stops employees from bypassing the warning, stopping them from going to the site.<p>If you disable or don't configure this setting, your employees can bypass the warnings and continue to visit a potentially malicious site.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Administrative Templates\Windows Components\Internet Explorer\Prevent managing SmartScreen Filter</td>
|
||||
<td>Internet Explorer 9 or later</td>
|
||||
<td>This policy setting prevents the employee from managing Windows Defender SmartScreen.<p>If you enable this policy setting, the employee isn't prompted to turn on Windows Defender SmartScreen. All website addresses that are not on the filter's allow list are sent automatically to Microsoft without prompting the employee.<p>If you disable or don't configure this policy setting, the employee is prompted to decide whether to turn on Windows Defender SmartScreen during the first-run experience.</td>
|
||||
<td>This policy setting prevents the employee from managing Microsoft Defender SmartScreen.<p>If you enable this policy setting, the employee isn't prompted to turn on Microsoft Defender SmartScreen. All website addresses that are not on the filter's allow list are sent automatically to Microsoft without prompting the employee.<p>If you disable or don't configure this policy setting, the employee is prompted to decide whether to turn on Microsoft Defender SmartScreen during the first-run experience.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Administrative Templates\Windows Components\Internet Explorer\Prevent bypassing SmartScreen Filter warnings</td>
|
||||
<td>Internet Explorer 8 or later</td>
|
||||
<td>This policy setting determines whether an employee can bypass warnings from Windows Defender SmartScreen.<p>If you enable this policy setting, Windows Defender SmartScreen warnings block the employee.<p>If you disable or don't configure this policy setting, the employee can bypass Windows Defender SmartScreen warnings.</td>
|
||||
<td>This policy setting determines whether an employee can bypass warnings from Microsoft Defender SmartScreen.<p>If you enable this policy setting, Microsoft Defender SmartScreen warnings block the employee.<p>If you disable or don't configure this policy setting, the employee can bypass Microsoft Defender SmartScreen warnings.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Administrative Templates\Windows Components\Internet Explorer\Prevent bypassing SmartScreen Filter warnings about files that are not commonly downloaded from the Internet</td>
|
||||
<td>Internet Explorer 9 or later</td>
|
||||
<td>This policy setting determines whether the employee can bypass warnings from Windows Defender SmartScreen. Windows Defender SmartScreen warns the employee about executable files that Internet Explorer users do not commonly download from the Internet.<p>If you enable this policy setting, Windows Defender SmartScreen warnings block the employee.<p>If you disable or don't configure this policy setting, the employee can bypass Windows Defender SmartScreen warnings.</td>
|
||||
<td>This policy setting determines whether the employee can bypass warnings from Microsoft Defender SmartScreen. Microsoft Defender SmartScreen warns the employee about executable files that Internet Explorer users do not commonly download from the Internet.<p>If you enable this policy setting, Microsoft Defender SmartScreen warnings block the employee.<p>If you disable or don't configure this policy setting, the employee can bypass Microsoft Defender SmartScreen warnings.</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
## MDM settings
|
||||
If you manage your policies using Microsoft Intune, you'll want to use these MDM policy settings. All settings support both desktop computers (running Windows 10 Pro or Windows 10 Enterprise, enrolled with Microsoft Intune) and Windows 10 Mobile devices. <br><br>
|
||||
For Windows Defender SmartScreen Internet Explorer MDM policies, see [Policy CSP - InternetExplorer](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-internetexplorer).
|
||||
For Microsoft Defender SmartScreen Internet Explorer MDM policies, see [Policy CSP - InternetExplorer](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-internetexplorer).
|
||||
<table>
|
||||
<tr>
|
||||
<th align="left">Setting</th>
|
||||
@ -91,8 +91,8 @@ For Windows Defender SmartScreen Internet Explorer MDM policies, see [Policy CSP
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/Policy/Config/Browser/AllowSmartScreen</li>
|
||||
<li><strong>Data type.</strong> Integer</li>
|
||||
<li><strong>Allowed values:</strong><ul>
|
||||
<li><strong>0 .</strong> Turns off Windows Defender SmartScreen in Edge.</li>
|
||||
<li><strong>1.</strong> Turns on Windows Defender SmartScreen in Edge.</li></ul></li></ul>
|
||||
<li><strong>0 .</strong> Turns off Microsoft Defender SmartScreen in Edge.</li>
|
||||
<li><strong>1.</strong> Turns on Microsoft Defender SmartScreen in Edge.</li></ul></li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -115,8 +115,8 @@ For Windows Defender SmartScreen Internet Explorer MDM policies, see [Policy CSP
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/Policy/Config/SmartScreen/EnableSmartScreenInShell</li>
|
||||
<li><strong>Data type.</strong> Integer</li>
|
||||
<li><strong>Allowed values:</strong><ul>
|
||||
<li><strong>0 .</strong> Turns off Windows Defender SmartScreen in Windows for app and file execution.</li>
|
||||
<li><strong>1.</strong> Turns on Windows Defender SmartScreen in Windows for app and file execution.</li></ul></li></ul>
|
||||
<li><strong>0 .</strong> Turns off Microsoft Defender SmartScreen in Windows for app and file execution.</li>
|
||||
<li><strong>1.</strong> Turns on Microsoft Defender SmartScreen in Windows for app and file execution.</li></ul></li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -127,8 +127,8 @@ For Windows Defender SmartScreen Internet Explorer MDM policies, see [Policy CSP
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/Policy/Config/SmartScreen/PreventOverrideForFilesInShell</li>
|
||||
<li><strong>Data type.</strong> Integer</li>
|
||||
<li><strong>Allowed values:</strong><ul>
|
||||
<li><strong>0 .</strong> Employees can ignore Windows Defender SmartScreen warnings and run malicious files.</li>
|
||||
<li><strong>1.</strong> Employees can't ignore Windows Defender SmartScreen warnings and run malicious files.</li></ul></li></ul>
|
||||
<li><strong>0 .</strong> Employees can ignore Microsoft Defender SmartScreen warnings and run malicious files.</li>
|
||||
<li><strong>1.</strong> Employees can't ignore Microsoft Defender SmartScreen warnings and run malicious files.</li></ul></li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -139,8 +139,8 @@ For Windows Defender SmartScreen Internet Explorer MDM policies, see [Policy CSP
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/Policy/Config/Browser/PreventSmartscreenPromptOverride</li>
|
||||
<li><strong>Data type.</strong> Integer</li>
|
||||
<li><strong>Allowed values:</strong><ul>
|
||||
<li><strong>0 .</strong> Employees can ignore Windows Defender SmartScreen warnings.</li>
|
||||
<li><strong>1.</strong> Employees can't ignore Windows Defender SmartScreen warnings.</li></ul></li></ul>
|
||||
<li><strong>0 .</strong> Employees can ignore Microsoft Defender SmartScreen warnings.</li>
|
||||
<li><strong>1.</strong> Employees can't ignore Microsoft Defender SmartScreen warnings.</li></ul></li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -151,16 +151,16 @@ For Windows Defender SmartScreen Internet Explorer MDM policies, see [Policy CSP
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/Policy/Config/Browser/PreventSmartScreenPromptOverrideForFiles</li>
|
||||
<li><strong>Data type.</strong> Integer</li>
|
||||
<li><strong>Allowed values:</strong><ul>
|
||||
<li><strong>0 .</strong> Employees can ignore Windows Defender SmartScreen warnings for files.</li>
|
||||
<li><strong>1.</strong> Employees can't ignore Windows Defender SmartScreen warnings for files.</li></ul></li></ul>
|
||||
<li><strong>0 .</strong> Employees can ignore Microsoft Defender SmartScreen warnings for files.</li>
|
||||
<li><strong>1.</strong> Employees can't ignore Microsoft Defender SmartScreen warnings for files.</li></ul></li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
## Recommended Group Policy and MDM settings for your organization
|
||||
By default, Windows Defender SmartScreen lets employees bypass warnings. Unfortunately, this can let employees continue to an unsafe site or to continue to download an unsafe file, even after being warned. Because of this possibility, we strongly recommend that you set up Windows Defender SmartScreen to block high-risk interactions instead of providing just a warning.
|
||||
By default, Microsoft Defender SmartScreen lets employees bypass warnings. Unfortunately, this can let employees continue to an unsafe site or to continue to download an unsafe file, even after being warned. Because of this possibility, we strongly recommend that you set up Microsoft Defender SmartScreen to block high-risk interactions instead of providing just a warning.
|
||||
|
||||
To better help you protect your organization, we recommend turning on and using these specific Windows Defender SmartScreen Group Policy and MDM settings.
|
||||
To better help you protect your organization, we recommend turning on and using these specific Microsoft Defender SmartScreen Group Policy and MDM settings.
|
||||
<table>
|
||||
<tr>
|
||||
<th align="left">Group Policy setting</th>
|
||||
@ -168,7 +168,7 @@ To better help you protect your organization, we recommend turning on and using
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Administrative Templates\Windows Components\Microsoft Edge\Configure Windows Defender SmartScreen</td>
|
||||
<td><strong>Enable.</strong> Turns on Windows Defender SmartScreen.</td>
|
||||
<td><strong>Enable.</strong> Turns on Microsoft Defender SmartScreen.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Administrative Templates\Windows Components\Microsoft Edge\Prevent bypassing Windows Defender SmartScreen prompts for sites</td>
|
||||
@ -191,7 +191,7 @@ To better help you protect your organization, we recommend turning on and using
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Browser/AllowSmartScreen</td>
|
||||
<td><strong>1.</strong> Turns on Windows Defender SmartScreen.</td>
|
||||
<td><strong>1.</strong> Turns on Microsoft Defender SmartScreen.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Browser/PreventSmartScreenPromptOverride</td>
|
||||
@ -203,7 +203,7 @@ To better help you protect your organization, we recommend turning on and using
|
||||
</tr>
|
||||
<tr>
|
||||
<td>SmartScreen/EnableSmartScreenInShell</td>
|
||||
<td><strong>1.</strong> Turns on Windows Defender SmartScreen in Windows.<p>Requires at least Windows 10, version 1703.</td>
|
||||
<td><strong>1.</strong> Turns on Microsoft Defender SmartScreen in Windows.<p>Requires at least Windows 10, version 1703.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>SmartScreen/PreventOverrideForFilesInShell</td>
|
||||
@ -214,7 +214,7 @@ To better help you protect your organization, we recommend turning on and using
|
||||
## Related topics
|
||||
- [Threat protection](../index.md)
|
||||
|
||||
- [Windows Defender SmartScreen overview](windows-defender-smartscreen-overview.md)
|
||||
- [Microsoft Defender SmartScreen overview](microsoft-defender-smartscreen-overview.md)
|
||||
|
||||
- [Available Group Policy and Mobile Device Management (MDM) settings for Microsoft Edge](/microsoft-edge/deploy/available-policies)
|
||||
|
@ -0,0 +1,93 @@
|
||||
---
|
||||
title: Microsoft Defender SmartScreen overview (Windows 10)
|
||||
description: Conceptual info about Microsoft Defender SmartScreen.
|
||||
keywords: SmartScreen Filter, Windows SmartScreen, Microsoft Defender SmartScreen
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: mjcaparas
|
||||
ms.author: macapara
|
||||
audience: ITPro
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/27/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
---
|
||||
|
||||
# Microsoft Defender SmartScreen
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
- Microsoft Edge
|
||||
|
||||
Microsoft Defender SmartScreen protects against phishing or malware websites and applications, and the downloading of potentially malicious files.
|
||||
|
||||
**Microsoft Defender SmartScreen determines whether a site is potentially malicious by:**
|
||||
|
||||
- Analyzing visited webpages looking for indications of suspicious behavior. If Microsoft Defender SmartScreen determines that a page is suspicious, it will show a warning page to advise caution.
|
||||
|
||||
- Checking the visited sites against a dynamic list of reported phishing sites and malicious software sites. If it finds a match, Microsoft Defender SmartScreen shows a warning to let the user know that the site might be malicious.
|
||||
|
||||
**Microsoft Defender SmartScreen determines whether a downloaded app or app installer is potentially malicious by:**
|
||||
|
||||
- Checking downloaded files against a list of reported malicious software sites and programs known to be unsafe. If it finds a match, Microsoft Defender SmartScreen shows a warning to let the user know that the site might be malicious.
|
||||
|
||||
- Checking downloaded files against a list of files that are well known and downloaded by many Windows users. If the file isn't on that list, Microsoft Defender SmartScreen shows a warning, advising caution.
|
||||
|
||||
## Benefits of Microsoft Defender SmartScreen
|
||||
|
||||
Microsoft Defender SmartScreen provide an early warning system against websites that might engage in phishing attacks or attempt to distribute malware through a socially-engineered attack. The primary benefits are:
|
||||
|
||||
- **Anti-phishing and anti-malware support.** Microsoft Defender SmartScreen helps to protect users from sites that are reported to host phishing attacks or attempt to distribute malicious software. It can also help protect against deceptive advertisements, scam sites, and drive-by attacks. Drive-by attacks are web-based attacks that tend to start on a trusted site, targeting security vulnerabilities in commonly used software. Because drive-by attacks can happen even if the user does not click or download anything on the page, the danger often goes unnoticed. For more info about drive-by attacks, see [Evolving Microsoft Defender SmartScreen to protect you from drive-by attacks](https://blogs.windows.com/msedgedev/2015/12/16/SmartScreen-drive-by-improvements/#3B7Bb8bzeAPq8hXE.97)
|
||||
|
||||
- **Reputation-based URL and app protection.** Microsoft Defender SmartScreen evaluates a website's URLs to determine if they're known to distribute or host unsafe content. It also provides reputation checks for apps, checking downloaded programs and the digital signature used to sign a file. If a URL, a file, an app, or a certificate has an established reputation, users won't see any warnings. If, however, there's no reputation, the item is marked as a higher risk and presents a warning to the user.
|
||||
|
||||
- **Operating system integration.** Microsoft Defender SmartScreen is integrated into the Windows 10 operating system, meaning that it checks any files an app (including 3rd-party browsers and email clients) attempts to download and run.
|
||||
|
||||
- **Improved heuristics and diagnostic data.** Microsoft Defender SmartScreen is constantly learning and endeavoring to stay up-to-date, so it can help to protect you against potentially malicious sites and files.
|
||||
|
||||
- **Management through Group Policy and Microsoft Intune.** Microsoft Defender SmartScreen supports using both Group Policy and Microsoft Intune settings. For more info about all available settings, see [Available Microsoft Defender SmartScreen Group Policy and mobile device management (MDM) settings](microsoft-defender-smartscreen-available-settings.md).
|
||||
|
||||
- **Blocking URLs associated with potentially unwanted applications.** In Microsoft Edge (based on Chromium), SmartScreen blocks URLs associated with potentially unwanted applications, or PUAs. For more information on blocking URLs associated with PUAs, see [Detect and block potentially unwanted applications](../windows-defender-antivirus/detect-block-potentially-unwanted-apps-windows-defender-antivirus.md).
|
||||
|
||||
> [!IMPORTANT]
|
||||
> SmartScreen protects against malicious files from the internet. It does not protect against malicious files on internal locations or network shares, such as shared folders with UNC paths or SMB/CIFS shares.
|
||||
|
||||
## Submit files to Microsoft Defender SmartScreen for review
|
||||
|
||||
If you believe a warning or block was incorrectly shown for a file or application, or if you believe an undetected file is malware, you can [submit a file](https://www.microsoft.com/wdsi/filesubmission/) to Microsoft for review. For more info, see [Submit files for analysis](https://docs.microsoft.com/windows/security/threat-protection/intelligence/submission-guide).
|
||||
|
||||
When submitting Microsoft Defender Smartscreen products, make sure to select **Microsoft Defender SmartScreen** from the product menu.
|
||||
|
||||

|
||||
|
||||
## Viewing Microsoft Defender SmartScreen anti-phishing events
|
||||
|
||||
When Microsoft Defender SmartScreen warns or blocks a user from a website, it's logged as [Event 1035 - Anti-Phishing](https://technet.microsoft.com/scriptcenter/dd565657(v=msdn.10).aspx).
|
||||
|
||||
## Viewing Windows event logs for Microsoft Defender SmartScreen
|
||||
Microsoft Defender SmartScreen events appear in the Microsoft-Windows-SmartScreen/Debug log in Event Viewer.
|
||||
|
||||
Windows event log for SmartScreen is disabled by default, users can use Event Viewer UI to enable the log or use the command line to enable it:
|
||||
|
||||
```
|
||||
wevtutil sl Microsoft-Windows-SmartScreen/Debug /e:true
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
> For information on how to use the Event Viewer, see [Windows Event Viewer](https://docs.microsoft.com/host-integration-server/core/windows-event-viewer1).
|
||||
|
||||
|
||||
EventID | Description
|
||||
-|-
|
||||
1000 | Application Windows Defender SmartScreen Event
|
||||
1001 | Uri Windows Defender SmartScreen Event
|
||||
1002 | User Decision Windows Defender SmartScreen Event
|
||||
|
||||
## Related topics
|
||||
- [SmartScreen Frequently Asked Questions](https://fb.smartscreen.microsoft.com/smartscreenfaq.aspx)
|
||||
- [Threat protection](../index.md)
|
||||
- [Available Microsoft Defender SmartScreen Group Policy and mobile device management (MDM) settings](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-available-settings)
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Set up and use Windows Defender SmartScreen on individual devices (Windows 10)
|
||||
description: Learn how employees can use Windows Security to set up Windows Defender SmartScreen. Windows Defender SmartScreen protects users from running malicious apps.
|
||||
keywords: SmartScreen Filter, Windows SmartScreen, Windows Defender SmartScreen
|
||||
title: Set up and use Microsoft Defender SmartScreen on individual devices (Windows 10)
|
||||
description: Learn how employees can use Windows Security to set up Microsoft Defender SmartScreen. Microsoft Defender SmartScreen protects users from running malicious apps.
|
||||
keywords: SmartScreen Filter, Windows SmartScreen, Microsoft Defender SmartScreen
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
@ -14,22 +14,22 @@ manager: dansimp
|
||||
ms.author: macapara
|
||||
---
|
||||
|
||||
# Set up and use Windows Defender SmartScreen on individual devices
|
||||
# Set up and use Microsoft Defender SmartScreen on individual devices
|
||||
|
||||
**Applies to:**
|
||||
- Windows 10, version 1703
|
||||
- Windows 10 Mobile
|
||||
- Microsoft Edge
|
||||
|
||||
Windows Defender SmartScreen helps to protect users if they try to visit sites previously reported as phishing or malware websites, or if a user tries to download potentially malicious files.
|
||||
Microsoft Defender SmartScreen helps to protect users if they try to visit sites previously reported as phishing or malware websites, or if a user tries to download potentially malicious files.
|
||||
|
||||
## How users can use Windows Security to set up Windows Defender SmartScreen
|
||||
Starting with Windows 10, version 1703, users can use Windows Security to set up Windows Defender SmartScreen for an individual device; unless and administrator has used Group Policy or Microsoft Intune to prevent it.
|
||||
## How users can use Windows Security to set up Microsoft Defender SmartScreen
|
||||
Starting with Windows 10, version 1703, users can use Windows Security to set up Microsoft Defender SmartScreen for an individual device; unless an administrator has used Group Policy or Microsoft Intune to prevent it.
|
||||
|
||||
>[!NOTE]
|
||||
>If any of the following settings are managed through Group Policy or mobile device management (MDM) settings, it appears as unavailable to the employee.
|
||||
|
||||
**To use Windows Security to set up Windows Defender SmartScreen on a device**
|
||||
**To use Windows Security to set up Microsoft Defender SmartScreen on a device**
|
||||
1. Open the Windows Security app, and then select **App & browser control** > **Reputation-based protection settings**.
|
||||
|
||||
2. In the **Reputation-based protection** screen, choose from the following options:
|
||||
@ -38,13 +38,13 @@ Starting with Windows 10, version 1703, users can use Windows Security to set up
|
||||
|
||||
- **On.** Warns users that the apps and files being downloaded from the web are potentially dangerous but allows the action to continue.
|
||||
|
||||
- **Off.** Turns off Windows Defender SmartScreen, so a user isn't alerted or stopped from downloading potentially malicious apps and files.
|
||||
- **Off.** Turns off Microsoft Defender SmartScreen, so a user isn't alerted or stopped from downloading potentially malicious apps and files.
|
||||
|
||||
- In the **Windows Defender SmartScreen for Microsoft Edge** area:
|
||||
- In the **Microsoft Defender SmartScreen for Microsoft Edge** area:
|
||||
|
||||
- **On.** Warns users that sites and downloads are potentially dangerous but allows the action to continue while running in Microsoft Edge.
|
||||
|
||||
- **Off.** Turns off Windows Defender SmartScreen, so a user isn't alerted or stopped from downloading potentially malicious apps and files.
|
||||
- **Off.** Turns off Microsoft Defender SmartScreen, so a user isn't alerted or stopped from downloading potentially malicious apps and files.
|
||||
- In the **Potentially unwanted app blocking** area:
|
||||
|
||||
- **On.** Turns on both the 'Block apps' and 'Block downloads settings. To learn more, see [How Microsoft identifies malware and potentially unwanted applications](https://docs.microsoft.com/windows/security/threat-protection/intelligence/criteria#potentially-unwanted-application-pua).
|
||||
@ -54,21 +54,21 @@ Starting with Windows 10, version 1703, users can use Windows Security to set up
|
||||
|
||||
- **Off.** Turns off Potentially unwanted app blocking, so a user isn't alerted or stopped from downloading or installing potentially unwanted apps.
|
||||
|
||||
- In the **Windows Defender SmartScreen from Microsoft Store apps** area:
|
||||
- In the **Microsoft Defender SmartScreen from Microsoft Store apps** area:
|
||||
|
||||
- **On.** Warns users that the sites and downloads used by Microsoft Store apps are potentially dangerous but allows the action to continue.
|
||||
|
||||
- **Off.** Turns off Windows Defender SmartScreen, so a user isn't alerted or stopped from visiting sites or from downloading potentially malicious apps and files.
|
||||
- **Off.** Turns off Microsoft Defender SmartScreen, so a user isn't alerted or stopped from visiting sites or from downloading potentially malicious apps and files.
|
||||
|
||||

|
||||

|
||||
|
||||
## How Windows Defender SmartScreen works when a user tries to run an app
|
||||
Windows Defender SmartScreen checks the reputation of any web-based app the first time it's run from the Internet, checking digital signatures and other factors against a Microsoft-maintained service. If an app has no reputation or is known to be malicious, Windows Defender SmartScreen can warn the user or block the app from running entirely, depending on how you've configured the feature to run in your organization.
|
||||
## How Microsoft Defender SmartScreen works when a user tries to run an app
|
||||
Microsoft Defender SmartScreen checks the reputation of any web-based app the first time it's run from the Internet, checking digital signatures and other factors against a Microsoft-maintained service. If an app has no reputation or is known to be malicious, Microsoft Defender SmartScreen can warn the user or block the app from running entirely, depending on how you've configured the feature to run in your organization.
|
||||
|
||||
By default, users can bypass Windows Defender SmartScreen protection, letting them run legitimate apps after accepting a warning message prompt. You can also use Group Policy or Microsoft Intune to block your employees from using unrecognized apps, or to entirely turn off Windows Defender SmartScreen (not recommended).
|
||||
By default, users can bypass Microsoft Defender SmartScreen protection, letting them run legitimate apps after accepting a warning message prompt. You can also use Group Policy or Microsoft Intune to block your employees from using unrecognized apps, or to entirely turn off Microsoft Defender SmartScreen (not recommended).
|
||||
|
||||
## How users can report websites as safe or unsafe
|
||||
Windows Defender SmartScreen can be configured to warn users from going to a potentially dangerous site. Users can then choose to report a website as safe from the warning message or as unsafe from within Microsoft Edge and Internet Explorer 11.
|
||||
Microsoft Defender SmartScreen can be configured to warn users from going to a potentially dangerous site. Users can then choose to report a website as safe from the warning message or as unsafe from within Microsoft Edge and Internet Explorer 11.
|
||||
|
||||
**To report a website as safe from the warning message**
|
||||
- On the warning screen for the site, click **More Information**, and then click **Report that this site does not contain threats**. The site info is sent to the Microsoft feedback site, which provides further instructions.
|
||||
@ -82,7 +82,7 @@ Windows Defender SmartScreen can be configured to warn users from going to a pot
|
||||
## Related topics
|
||||
- [Threat protection](../index.md)
|
||||
|
||||
- [Windows Defender SmartScreen overview](windows-defender-smartscreen-overview.md)
|
||||
- [Microsoft Defender SmartScreen overview](microsoft-defender-smartscreen-overview.md)
|
||||
|
||||
>[!NOTE]
|
||||
>Help to make this topic better by providing us with edits, additions, and feedback. For info about how to contribute to this topic, see [Contributing to TechNet content](https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md).
|
@ -86,7 +86,7 @@ Windows Defender SmartScreen notifies users if they click on reported phishing a
|
||||
|
||||
For Windows 10, Microsoft improved SmartScreen (now called Windows Defender SmartScreen) protection capability by integrating its app reputation abilities into the operating system itself, which allows Windows Defender SmartScreen to check the reputation of files downloaded from the Internet and warn users when they’re about to run a high-risk downloaded file. The first time a user runs an app that originates from the Internet, Windows Defender SmartScreen checks the reputation of the application by using digital signatures and other factors against a service that Microsoft maintains. If the app lacks a reputation or is known to be malicious, Windows Defender SmartScreen warns the user or blocks execution entirely, depending on how the administrator has configured Microsoft Intune or Group Policy settings.
|
||||
|
||||
For more information, see [Windows Defender SmartScreen overview](windows-defender-smartscreen/windows-defender-smartscreen-overview.md).
|
||||
For more information, see [Microsoft Defender SmartScreen overview](microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md).
|
||||
|
||||
### Windows Defender Antivirus
|
||||
|
||||
|
@ -41,7 +41,7 @@ The Security Compliance Toolkit consists of:
|
||||
- Windows Server 2012 R2
|
||||
|
||||
- Microsoft Office security baseline
|
||||
- Office 365 ProPlus (Sept 2019)
|
||||
- Microsoft 365 Apps for enterprise (Sept 2019)
|
||||
|
||||
- Microsoft Edge security baseline
|
||||
- Version 80
|
||||
|
@ -2,7 +2,7 @@
|
||||
title: Interactive logon Don't display username at sign-in (Windows 10)
|
||||
description: Describes the best practices, location, values, and security considerations for the Interactive logon Don't display username at sign-in security policy setting.
|
||||
ms.assetid: 98b24b03-95fe-4edc-8e97-cbdaa8e314fd
|
||||
ms.reviewer:
|
||||
ms.reviewer:
|
||||
ms.author: dansimp
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -20,9 +20,9 @@ ms.date: 04/19/2017
|
||||
# Interactive logon: Don't display username at sign-in
|
||||
|
||||
**Applies to**
|
||||
- Windows Server 2003, Windows Vista, Windows XP, Windows Server 2008, Windows 7, Windows 8.1, Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2012, Windows 8, Windows 10
|
||||
- Windows 10, Windows Server 2019
|
||||
|
||||
Describes the best practices, location, values, and security considerations for the **Interactive logon: Don't display username at sign-in** security policy setting.
|
||||
Describes the best practices, location, values, and security considerations for the **Interactive logon: Don't display username at sign-in** security policy setting.
|
||||
|
||||
## Reference
|
||||
|
||||
@ -56,7 +56,7 @@ Computer Configuration\\Windows Settings\\Security Settings\\Local Policies\\Sec
|
||||
| Domain controller effective default settings | Not defined|
|
||||
| Member server effective default settings | Not defined|
|
||||
| Effective GPO default settings on client computers | Not defined|
|
||||
|
||||
|
||||
## Policy management
|
||||
|
||||
This section describes features and tools that are available to help you manage this policy.
|
||||
|
@ -41,7 +41,7 @@ Potentially unwanted applications can increase the risk of your network being in
|
||||
|
||||
### Microsoft Edge
|
||||
|
||||
The next major version of Microsoft Edge, which is Chromium-based, blocks potentially unwanted application downloads and associated resource URLs. This feature is provided via [Windows Defender SmartScreen](../windows-defender-smartscreen/windows-defender-smartscreen-overview.md).
|
||||
The next major version of Microsoft Edge, which is Chromium-based, blocks potentially unwanted application downloads and associated resource URLs. This feature is provided via [Microsoft Defender SmartScreen](../microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md).
|
||||
|
||||
#### Enable PUA protection in Chromium-based Microsoft Edge
|
||||
|
||||
@ -62,7 +62,7 @@ Admins can [configure](https://docs.microsoft.com/DeployEdge/configure-microsoft
|
||||
Defender SmartScreen available, including [one for blocking PUA](https://docs.microsoft.com/DeployEdge/microsoft-edge-policies#smartscreenpuaenabled). In addition, admins can
|
||||
[configure Windows Defender SmartScreen](https://docs.microsoft.com/microsoft-edge/deploy/available-policies?source=docs#configure-windows-defender-smartscreen) as a whole, using group policy settings to turn Windows Defender SmartScreen on or off.
|
||||
|
||||
Although Microsoft Defender ATP has its own block list, based upon a data set managed by Microsoft, you can customize this list based on your own threat intelligence. If you [create and manage indicators](../microsoft-defender-atp/manage-indicators.md#create-indicators-for-ips-and-urlsdomains-preview) in the Microsoft Defender ATP portal, Windows Defender SmartScreen will respect the new settings.
|
||||
Although Microsoft Defender ATP has its own block list, based upon a data set managed by Microsoft, you can customize this list based on your own threat intelligence. If you [create and manage indicators](../microsoft-defender-atp/manage-indicators.md) in the Microsoft Defender ATP portal, Windows Defender SmartScreen will respect the new settings.
|
||||
|
||||
### Windows Defender Antivirus
|
||||
|
||||
|
@ -50,7 +50,8 @@ Only the main version is listed in the following table as reference information:
|
||||
|
||||
Month | Platform/Client | Engine
|
||||
---|---|---
|
||||
Mar-2020 | 4.18.2003.x| 1.1.16900.x
|
||||
Apr-2020 | 4.18.2004.x | 1.1.17000.x
|
||||
Mar-2020 | 4.18.2003.x | 1.1.16900.x
|
||||
Feb-2020 | - | 1.1.16800.x
|
||||
Jan-2020 | 4.18.2001.x | 1.1.16700.x
|
||||
Dec-2019 | - | - |
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Shadow protection in next-generation protection
|
||||
description: Learn about shadow protection in next-generation protection
|
||||
title: Shadow protection
|
||||
description: Learn about shadow protection
|
||||
keywords: Windows Defender Antivirus, shadow protection, passive mode
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
ms.pagetype: security
|
||||
@ -16,7 +16,7 @@ ms.custom: next-gen
|
||||
ms.collection:
|
||||
---
|
||||
|
||||
# Shadow protection in next-generation protection
|
||||
# Shadow protection
|
||||
|
||||
**Applies to:**
|
||||
|
||||
@ -67,7 +67,7 @@ The following images shows an instance of unwanted software that was detected an
|
||||
|Windows Defender Antivirus engine |To make sure your engine is up to date, using PowerShell, run the [Get-MpComputerStatus](https://docs.microsoft.com/powershell/module/defender/get-mpcomputerstatus?view=win10-ps) cmdlet as an administrator. In the **AMEngineVersion** line, you should see **1.1.16700.2** or above. |
|
||||
|
||||
> [!IMPORTANT]
|
||||
> To get the best protection value, make sure Windows Defender Antivirus is configured to receive regular updates and other essential features, such as behavioral monitoring, IOfficeAV, tamper protection, and more. See [Protect security settings with tamper protection](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/prevent-changes-to-security-settings-with-tamper-protection)
|
||||
> To get the best protection value, make sure Windows Defender Antivirus is configured to receive regular updates and other essential features, such as behavioral monitoring, IOfficeAV, tamper protection, and more. See [Protect security settings with tamper protection](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/prevent-changes-to-security-settings-with-tamper-protection).
|
||||
|
||||
|
||||
## Frequently asked questions
|
||||
@ -78,7 +78,7 @@ No. Shadow protection does not affect third-party antivirus protection running o
|
||||
|
||||
### Why do I need to keep Windows Defender Antivirus up to date?
|
||||
|
||||
The [Microsoft Defender ATP](https://docs.microsoft.com/windows/security/threat-protection) stack works in integration, and to get best protection value, you should keep Windows Defender Antivirus up to date.
|
||||
Because Windows Defender Antivirus detects and remediates malicious items, it’s important to keep it up to date to leverage the latest machine learning models, behavioral detections, and heuristics for best results. The [Microsoft Defender ATP](https://docs.microsoft.com/windows/security/threat-protection) stack of capabilities work in an integrated manner, and to get best protection value, you should keep Windows Defender Antivirus up to date.
|
||||
|
||||
### Why do we need cloud protection on?
|
||||
|
||||
|
@ -129,9 +129,9 @@ Wildcards can be used at the beginning or end of a path rule; only one wildcard
|
||||
|
||||
## Windows Defender Application Control filename rules
|
||||
|
||||
File name rule levels provide administrators to specify the file attributes off which to base a file name rule. File name rules do not provide the same security guarantees that explicit signer rules do, as they are based on mutable access permissions. Specification of the file name level occurs when creating new policy rules. In addition, to combine file name levels found in multiple policies, you can merge multiple policies.
|
||||
File name rule levels provide administrators to specify the file attributes off which to base a file name rule. File name rules provide the same security guarantees that explicit signer rules do, as they are based on non-mutable file attributes. Specification of the file name level occurs when creating new policy rules. In addition, to combine file name levels found in multiple policies, you can merge multiple policies.
|
||||
|
||||
Use Table 3 to select the appropriate file name level for your available administrative resources and Windows Defender Application Control deployment scenario.
|
||||
Use Table 3 to select the appropriate file name level for your available administrative resources and Windows Defender Application Control deployment scenario. For instance, an LOB or production application and its binaries (eg. DLLs) may all share the same product name. This allows users to easily create targeted policies based on the Product Name filename rule level.
|
||||
|
||||
**Table 3. Windows Defender Application Control policy - filename levels**
|
||||
|
||||
|
@ -42,4 +42,3 @@ Your environment needs the following software to run Windows Defender Applicatio
|
||||
|Operating system|Windows 10 Enterprise edition, version 1709 or higher<br>Windows 10 Professional edition, version 1803 or higher<br>Windows 10 Professional for Workstations edition, version 1803 or higher<br>Windows 10 Professional Education edition version 1803 or higher<br>Windows 10 Education edition, version 1903 or higher<br>Professional editions are only supported for non-managed devices; Intune or any other 3rd party mobile device management (MDM) solutions are not supported with WDAG for Professional editions. |
|
||||
|Browser|Microsoft Edge and Internet Explorer|
|
||||
|Management system<br> (only for managed devices)|[Microsoft Intune](https://docs.microsoft.com/intune/)<br><br>**-OR-**<br><br>[Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/configmgr/)<br><br>**-OR-**<br><br>[Group Policy](https://technet.microsoft.com/library/cc753298(v=ws.11).aspx)<br><br>**-OR-**<br><br>Your current company-wide 3rd party mobile device management (MDM) solution. For info about 3rd party MDM solutions, see the documentation that came with your product.|
|
||||
|Windows Defender Exploit Protection settings|The following settings should be configured or verified in the **Windows Security** app under **App & browser control** > **Exploit protection** > **Exploit protection settings** > **System Settings**.<br><br>**Control flow guard (CFG)** must be set to **Use default (On)** or **Off by default**. If set to **On by default**, [Windows Defender Application Guard](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-guard) will not launch.<br><br>**Randomize memory allocations (Bottom-up ASLR)** must be set to **Use default (On)** or **Off by default**. If set to "On by default", the `Vmmem` process will have high CPU utilization while a Windows Defender Application Guard window is open.|
|
||||
|
@ -1,84 +0,0 @@
|
||||
---
|
||||
title: Windows Defender SmartScreen overview (Windows 10)
|
||||
description: Conceptual info about Windows Defender SmartScreen.
|
||||
keywords: SmartScreen Filter, Windows SmartScreen, Windows Defender SmartScreen
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: mjcaparas
|
||||
ms.author: macapara
|
||||
audience: ITPro
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/27/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
---
|
||||
|
||||
# Windows Defender SmartScreen
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
- Microsoft Edge
|
||||
|
||||
Windows Defender SmartScreen protects against phishing or malware websites and applications, and the downloading of potentially malicious files.
|
||||
|
||||
**Windows Defender SmartScreen determines whether a site is potentially malicious by:**
|
||||
|
||||
- Analyzing visited webpages looking for indications of suspicious behavior. If Windows Defender SmartScreen determines that a page is suspicious, it will show a warning page to advise caution.
|
||||
|
||||
- Checking the visited sites against a dynamic list of reported phishing sites and malicious software sites. If it finds a match, Windows Defender SmartScreen shows a warning to let the user know that the site might be malicious.
|
||||
|
||||
**Windows Defender SmartScreen determines whether a downloaded app or app installer is potentially malicious by:**
|
||||
|
||||
- Checking downloaded files against a list of reported malicious software sites and programs known to be unsafe. If it finds a match, Windows Defender SmartScreen shows a warning to let the user know that the site might be malicious.
|
||||
|
||||
- Checking downloaded files against a list of files that are well known and downloaded by many Windows users. If the file isn't on that list, Windows Defender SmartScreen shows a warning, advising caution.
|
||||
|
||||
## Benefits of Windows Defender SmartScreen
|
||||
|
||||
Windows Defender SmartScreen provide an early warning system against websites that might engage in phishing attacks or attempt to distribute malware through a socially-engineered attack. The primary benefits are:
|
||||
|
||||
- **Anti-phishing and anti-malware support.** Windows Defender SmartScreen helps to protect users from sites that are reported to host phishing attacks or attempt to distribute malicious software. It can also help protect against deceptive advertisements, scam sites, and drive-by attacks. Drive-by attacks are web-based attacks that tend to start on a trusted site, targeting security vulnerabilities in commonly used software. Because drive-by attacks can happen even if the user does not click or download anything on the page, the danger often goes unnoticed. For more info about drive-by attacks, see [Evolving Windows Defender SmartScreen to protect you from drive-by attacks](https://blogs.windows.com/msedgedev/2015/12/16/SmartScreen-drive-by-improvements/#3B7Bb8bzeAPq8hXE.97)
|
||||
|
||||
- **Reputation-based URL and app protection.** Windows Defender SmartScreen evaluates a website's URLs to determine if they're known to distribute or host unsafe content. It also provides reputation checks for apps, checking downloaded programs and the digital signature used to sign a file. If a URL, a file, an app, or a certificate has an established reputation, users won't see any warnings. If, however, there's no reputation, the item is marked as a higher risk and presents a warning to the user.
|
||||
|
||||
- **Operating system integration.** Windows Defender SmartScreen is integrated into the Windows 10 operating system, meaning that it checks any files an app (including 3rd-party browsers and email clients) attempts to download and run.
|
||||
|
||||
- **Improved heuristics and diagnostic data.** Windows Defender SmartScreen is constantly learning and endeavoring to stay up-to-date, so it can help to protect you against potentially malicious sites and files.
|
||||
|
||||
- **Management through Group Policy and Microsoft Intune.** Windows Defender SmartScreen supports using both Group Policy and Microsoft Intune settings. For more info about all available settings, see [Available Windows Defender SmartScreen Group Policy and mobile device management (MDM) settings](windows-defender-smartscreen-available-settings.md).
|
||||
|
||||
- **Blocking URLs associated with potentially unwanted applications.** In Microsoft Edge (based on Chromium), SmartScreen blocks URLs associated with potentially unwanted applications, or PUAs. For more information on blocking URLs associated with PUAs, see [Detect and block potentially unwanted applications](../windows-defender-antivirus/detect-block-potentially-unwanted-apps-windows-defender-antivirus.md).
|
||||
|
||||
> [!IMPORTANT]
|
||||
> SmartScreen protects against malicious files from the internet. It does not protect against malicious files on internal locations or network shares, such as shared folders with UNC paths or SMB/CIFS shares.
|
||||
|
||||
## Viewing Windows Defender SmartScreen anti-phishing events
|
||||
|
||||
When Windows Defender SmartScreen warns or blocks a user from a website, it's logged as [Event 1035 - Anti-Phishing](https://technet.microsoft.com/scriptcenter/dd565657(v=msdn.10).aspx).
|
||||
|
||||
## Viewing Windows event logs for Windows Defender SmartScreen
|
||||
Windows Defender SmartScreen events appear in the Microsoft-Windows-SmartScreen/Debug log in Event Viewer.
|
||||
|
||||
Windows event log for SmartScreen is disabled by default, users can use Event Viewer UI to enable the log or use the command line to enable it:
|
||||
|
||||
```
|
||||
wevtutil sl Microsoft-Windows-SmartScreen/Debug /e:true
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
> For information on how to use the Event Viewer, see [Windows Event Viewer](https://docs.microsoft.com/host-integration-server/core/windows-event-viewer1).
|
||||
|
||||
|
||||
EventID | Description
|
||||
-|-
|
||||
1000 | Application Windows Defender SmartScreen Event
|
||||
1001 | Uri Windows Defender SmartScreen Event
|
||||
1002 | User Decision Windows Defender SmartScreen Event
|
||||
|
||||
## Related topics
|
||||
- [Threat protection](../index.md)
|
||||
- [Available Windows Defender SmartScreen Group Policy and mobile device management (MDM) settings](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-available-settings)
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows security baselines
|
||||
description: Learn how to use Windows security baselines in your organization. Specific to Windows 10, Windows Server, and Office 365 ProPlus.
|
||||
description: Learn how to use Windows security baselines in your organization. Specific to Windows 10, Windows Server, and Microsoft 365 Apps for enterprise.
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -21,7 +21,7 @@ ms.reviewer:
|
||||
|
||||
- Windows 10
|
||||
- Windows Server
|
||||
- Office 365 ProPlus
|
||||
- Microsoft 365 Apps for enterprise
|
||||
|
||||
## Using security baselines in your organization
|
||||
|
||||
@ -64,7 +64,7 @@ The security baselines are included in the [Security Compliance Toolkit (SCT)](s
|
||||
|
||||
## Community
|
||||
|
||||
[](https://blogs.technet.microsoft.com/secguide/)
|
||||
[](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/bd-p/Security-Baselines)
|
||||
|
||||
## Related Videos
|
||||
|
||||
@ -73,9 +73,9 @@ You may also be interested in this msdn channel 9 video:
|
||||
|
||||
## See Also
|
||||
|
||||
- [Microsoft Endpoint Configuration Manager](https://www.microsoft.com/cloud-platform/system-center-configuration-manager)
|
||||
- [Operations Management Suite](https://www.microsoft.com/cloud-platform/operations-management-suite)
|
||||
- [Configuration Management for Nano Server](https://blogs.technet.microsoft.com/grouppolicy/2016/05/09/configuration-management-on-servers/)
|
||||
- [Microsoft Security Guidance Blog](https://blogs.technet.microsoft.com/secguide/)
|
||||
- [Microsoft Security Compliance Toolkit Download](https://www.microsoft.com/download/details.aspx?id=55319)
|
||||
- [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=55319)
|
||||
- [Microsoft Endpoint Configuration Manager](https://www.microsoft.com/cloud-platform/system-center-configuration-manager)
|
||||
- [Operations Management Suite](https://www.microsoft.com/cloud-platform/operations-management-suite)
|
||||
- [Configuration Management for Nano Server](https://docs.microsoft.com/archive/blogs/grouppolicy/configuration-management-on-servers/)
|
||||
- [Microsoft Security Guidance Blog](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/bg-p/Microsoft-Security-Baselines)
|
||||
- [Microsoft Security Compliance Toolkit Download](https://www.microsoft.com/download/details.aspx?id=55319)
|
||||
- [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=55319)
|
||||
|