Merge branch 'master' into wcf
@ -86,6 +86,8 @@ You can do this by using either the Control Panel or the Deployment Image Servic
|
||||
```
|
||||
dism /image:<WIM file name> /Enable-Feature /FeatureName:IsolatedUserMode
|
||||
```
|
||||
> [!NOTE]
|
||||
> In Windows 10, version 1607 and later, the Isolated User Mode feature has been integrated into the core operating system. Running the command in step 3 above is therefore no longer required.
|
||||
|
||||
> [!NOTE]
|
||||
> You can also add these features to an online image by using either DISM or Configuration Manager.
|
||||
|
@ -68,3 +68,5 @@ Following are the various deployment guides and models included in this topic:
|
||||
|
||||
Windows Hello for Business provisioning begins immediately after the user has signed in, after the user profile is loaded, but before the user receives their desktop. Windows only launches the provisioning experience if all the prerequisite checks pass. You can determine the status of the prerequisite checks by viewing the **User Device Registration** in the **Event Viewer** under **Applications and Services Logs\Microsoft\Windows**.
|
||||
|
||||
> [!NOTE]
|
||||
> You need to allow access to the URL account.microsoft.com to initiate Windows Hello for Business provisioning. This URL launches the subsequent steps in the provisioning process and is required to successfully complete Windows Hello for Business provisioning. This URL does not require any authentication and as such, does not collect any user data.
|
||||
|
@ -58,6 +58,9 @@ To resolve this issue, the CRL distribution point must be a location that is acc
|
||||
|
||||
If your CRL distribution point does not list an HTTP distribution point, then you need to reconfigure the issuing certificate authority to include an HTTP CRL distribution point, preferably first in the list of distribution points.
|
||||
|
||||
> [!NOTE]
|
||||
> If your CA has published both the Base and the Delta CRL, please make sure you have included publishing the Delta CRL in the HTTP path. Include web server to fetch the Delta CRL by allowing double escaping in the (IIS) web server.
|
||||
|
||||
### Windows Server 2016 Domain Controllers
|
||||
If you are interested in configuring your environment to use the Windows Hello for Business key rather than a certificate, then your environment must have an adequate number of Windows Server 2016 domain controllers. Only Windows Server 2016 domain controllers are capable of authenticating user with a Windows Hello for Business key. What do we mean by adequate? We are glad you asked. Read [Planning an adequate number of Windows Server 2016 Domain Controllers for Windows Hello for Business deployments](hello-adequate-domain-controllers.md) to learn more.
|
||||
|
||||
@ -335,6 +338,3 @@ Sign-in a workstation with access equivalent to a _domain user_.
|
||||
|
||||
If you plan on using certificates for on-premises single-sign on, perform the additional steps in [Using Certificates for On-premises Single-sign On](hello-hybrid-aadj-sso-cert.md).
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -118,6 +118,11 @@ Hybrid certificate trust deployments need the device write back feature. Authen
|
||||
> [!NOTE]
|
||||
> Windows Hello for Business is tied between a user and a device. Both the user and device need to be synchronized between Azure Active Directory and Active Directory, and therefore the device writeback is used to update the msDS-KeyCredentialLink on the computer object.
|
||||
|
||||
## Provisioning
|
||||
|
||||
You need to allow access to the URL account.microsoft.com to initiate Windows Hello for Business provisioning. This URL launches the subsequent steps in the provisioning process and is required to successfully complete Windows Hello for Business provisioning. This URL does not require any authentication and as such, does not collect any user data.
|
||||
|
||||
|
||||
### Section Checklist ###
|
||||
> [!div class="checklist"]
|
||||
> * Azure Active Directory Device writeback
|
||||
|
@ -31,7 +31,7 @@ In hybrid deployments, users register the public portion of their Windows Hello
|
||||
The key-trust model needs Windows Server 2016 domain controllers, which configures the key registration permissions automatically; however, the certificate-trust model does not and requires you to add the permissions manually.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you already have a Windows Server 2016 domain controller in your domain, you can skip **Configure Permissions for Key Synchronization**.
|
||||
> If you already have a Windows Server 2016 domain controller in your domain, you can skip **Configure Permissions for Key Synchronization**. In this case, you should use the pre-created group KeyAdmins in step 3 of the "Group Memberships for the Azure AD Connect Service Account" section of this article.
|
||||
|
||||
### Configure Permissions for Key Synchronization
|
||||
|
||||
@ -56,9 +56,6 @@ Sign-in a domain controller or management workstation with _Domain Admin_ equiva
|
||||
|
||||
1. Open **Active Directory Users and Computers**.
|
||||
2. Click the **Users** container in the navigation pane.
|
||||
>[!IMPORTANT]
|
||||
> If you already have a Windows Server 2016 domain controller in your domain, use the Keyadmins group in the next step, otherwise use the KeyCredential admins group you previously created.
|
||||
|
||||
3. Right-click either the **KeyAdmins** or **KeyCredential Admins** in the details pane and click **Properties**.
|
||||
4. Click the **Members** tab and click **Add**
|
||||
5. In the **Enter the object names to select** text box, type the name of the Azure AD Connect service account. Click **OK**.
|
||||
|
@ -40,7 +40,7 @@ Hybrid Windows Hello for Business needs two directories: on-premises Active Dire
|
||||
|
||||
A hybrid Windows Hello for Business deployment needs an Azure Active Directory subscription. The hybrid key trust deployment, does not need a premium Azure Active Directory subscription.
|
||||
|
||||
You can deploy Windows Hello for Business in any environment with Windows Server 2008 R2 or later domain controllers. However, the key trust deployment needs an ***adequate*** number of Windows Server 2016 domain controllers at each site where users authenticate using Windows Hello for Business. Read the [Planning an adequate number of Windows Server 2016 Domain Controllers for Windows Hello for Business deployments](hello-adequate-domain-controllers.md) to learn more.
|
||||
You can deploy Windows Hello for Business in any environment with Windows Server 2008 R2 or later domain controllers. However, the key trust deployment needs an ***adequate*** number of Windows Server 2016 or later domain controllers at each site where users authenticate using Windows Hello for Business. Read the [Planning an adequate number of Windows Server 2016 or later Domain Controllers for Windows Hello for Business deployments](hello-adequate-domain-controllers.md) to learn more.
|
||||
|
||||
Review these requirements and those from the Windows Hello for Business planning guide and worksheet. Based on your deployment decisions you may need to upgrade your on-premises Active Directory or your Azure Active Directory subscription to meet your needs.
|
||||
|
||||
@ -125,7 +125,11 @@ Hybrid Windows Hello for Business deployments can use Azure’s Multifactor Auth
|
||||
## Device Registration
|
||||
|
||||
Organizations wanting to deploy hybrid key trust need their domain joined devices to register to Azure Active Directory. Just as a computer has an identity in Active Directory, that same computer has an identity in the cloud. This ensures that only approved computers are used with that Azure Active Directory. Each computer registers its identity in Azure Active Directory.
|
||||
|
||||
|
||||
## Provisioning
|
||||
|
||||
You need to allow access to the URL account.microsoft.com to initiate Windows Hello for Business provisioning. This URL launches the subsequent steps in the provisioning process and is required to successfully complete Windows Hello for Business provisioning. This URL does not require any authentication and as such, does not collect any user data.
|
||||
|
||||
|
||||
### Section Checklist
|
||||
|
||||
|
@ -36,18 +36,6 @@ Windows Hello addresses the following problems with passwords:
|
||||
|
||||
## Prerequisites
|
||||
|
||||
> [!Important]
|
||||
> 1. Hybrid deployments support non-destructive PIN reset that only works with the certificate trust model.</br>.
|
||||
> **Requirements:**</br>
|
||||
> Microsoft PIN Reset Service - Windows 10, versions 1709 to 1809, Enterprise Edition. There is no licensing requirement for this service since version 1903</br>
|
||||
> Reset above lock screen (_I forgot my PIN_ link) - Windows 10, version 1903
|
||||
>
|
||||
> 2. On-premises deployments support destructive PIN reset that works with both the certificate trust and the key trust models.</br>
|
||||
> **Requirements:**</br>
|
||||
> Reset from settings - Windows 10, version 1703, Professional</br>
|
||||
> Reset above lock screen - Windows 10, version 1709, Professional</br>
|
||||
> Reset above lock screen (_I forgot my PIN_ link) - Windows 10, version 1903
|
||||
|
||||
### Cloud Only Deployment
|
||||
|
||||
* Windows 10, version 1511 or later
|
||||
@ -75,6 +63,18 @@ The table shows the minimum requirements for each deployment. For key trust in a
|
||||
| Azure AD Connect | Azure AD Connect | Azure AD Connect | Azure AD Connect |
|
||||
| Azure AD Premium, optional | Azure AD Premium, needed for device write-back | Azure AD Premium, optional for automatic MDM enrollment | Azure AD Premium, optional for automatic MDM enrollment |
|
||||
|
||||
> [!Important]
|
||||
> 1. Hybrid deployments support non-destructive PIN reset that works with both the certificate trust and key trust models. </br>
|
||||
> **Requirements:**</br>
|
||||
> Microsoft PIN Reset Service - Windows 10, versions 1709 to 1809, Enterprise Edition. There is no licensing requirement for this service since version 1903</br>
|
||||
> Reset above lock screen (_I forgot my PIN_ link) - Windows 10, version 1903
|
||||
>
|
||||
> 2. On-premises deployments support destructive PIN reset that works with both the certificate trust and the key trust models.</br>
|
||||
> **Requirements:**</br>
|
||||
> Reset from settings - Windows 10, version 1703, Professional</br>
|
||||
> Reset above lock screen - Windows 10, version 1709, Professional</br>
|
||||
> Reset above lock screen (_I forgot my PIN_ link) - Windows 10, version 1903
|
||||
|
||||
### On-premises Deployments
|
||||
|
||||
The table shows the minimum requirements for each deployment.
|
||||
|
@ -196,7 +196,7 @@ Alternatively, you can forcefully trigger automatic certificate enrollment using
|
||||
Use the event logs to monitor certificate enrollment and archive. Review the configuration, such as publishing certificate templates to issuing certificate authority and the allow auto enrollment permissions.
|
||||
|
||||
|
||||
## Follow the Windows Hello for Business on premises certificate trust deployment guide
|
||||
## Follow the Windows Hello for Business on premises key trust deployment guide
|
||||
1. [Validate Active Directory prerequisites](hello-key-trust-validate-ad-prereq.md)
|
||||
2. Validate and Configure Public Key Infrastructure (*You are here*)
|
||||
3. [Prepare and Deploy Windows Server 2016 Active Directory Federation Services](hello-key-trust-adfs.md)
|
||||
|
@ -1,9 +1,9 @@
|
||||
---
|
||||
title: Create and deploy a Windows Information Protection (WIP) policy using System Center Configuration Manager (Windows 10)
|
||||
title: Create and deploy a Windows Information Protection (WIP) policy using Microsoft Endpoint Configuration Manager (Windows 10)
|
||||
description: Use Configuration Manager to make & deploy a Windows Information Protection (WIP) policy. Choose protected apps, WIP-protection level, and find enterprise data.
|
||||
ms.assetid: 85b99c20-1319-4aa3-8635-c1a87b244529
|
||||
ms.reviewer:
|
||||
keywords: WIP, Windows Information Protection, EDP, Enterprise Data Protection, SCCM, System Center Configuration Manager, Configuration Manager
|
||||
keywords: WIP, Windows Information Protection, EDP, Enterprise Data Protection, SCCM, System Center Configuration Manager, Configuration Manager, MEMCM, Microsoft Endpoint Configuration Manager
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
@ -15,26 +15,29 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 05/13/2019
|
||||
ms.date: 01/09/2020
|
||||
---
|
||||
|
||||
# Create and deploy a Windows Information Protection (WIP) policy using System Center Configuration Manager
|
||||
# Create and deploy a Windows Information Protection (WIP) policy using Microsoft Endpoint Configuration Manager
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10, version 1607 and later
|
||||
- Windows 10 Mobile, version 1607 and later
|
||||
- System Center Configuration Manager
|
||||
- Microsoft Endpoint Configuration Manager
|
||||
|
||||
System Center Configuration Manager helps you create and deploy your Windows Information Protection (WIP) policy, including letting you choose your protected apps, your WIP-protection mode, and how to find enterprise data on the network.
|
||||
Configuration Manager helps you create and deploy your Windows Information Protection (WIP) policy, including letting you choose your protected apps, your WIP-protection mode, and how to find enterprise data on the network.
|
||||
|
||||
## Add a WIP policy
|
||||
After you’ve installed and set up System Center Configuration Manager for your organization, you must create a configuration item for WIP, which in turn becomes your WIP policy.
|
||||
After you’ve installed and set up Configuration Manager for your organization, you must create a configuration item for WIP, which in turn becomes your WIP policy.
|
||||
|
||||
>[!TIP]
|
||||
> Review the [Limitations while using Windows Information Protection (WIP)](limitations-with-wip.md) article before creating a new configuration item to avoid common issues.
|
||||
|
||||
**To create a configuration item for WIP**
|
||||
|
||||
1. Open the System Center Configuration Manager console, click the **Assets and Compliance** node, expand the **Overview** node, expand the **Compliance Settings** node, and then expand the **Configuration Items** node.
|
||||
1. Open the Configuration Manager console, click the **Assets and Compliance** node, expand the **Overview** node, expand the **Compliance Settings** node, and then expand the **Configuration Items** node.
|
||||
|
||||

|
||||

|
||||
|
||||
2. Click the **Create Configuration Item** button.<p>
|
||||
The **Create Configuration Item Wizard** starts.
|
||||
@ -43,7 +46,7 @@ The **Create Configuration Item Wizard** starts.
|
||||
|
||||
3. On the **General Information screen**, type a name (required) and an optional description for your policy into the **Name** and **Description** boxes.
|
||||
|
||||
4. In the **Specify the type of configuration item you want to create** area, pick the option that represents whether you use System Center Configuration Manager for device management, and then click **Next**.
|
||||
4. In the **Specify the type of configuration item you want to create** area, pick the option that represents whether you use Configuration Manager for device management, and then click **Next**.
|
||||
|
||||
- **Settings for devices managed with the Configuration Manager client:** Windows 10
|
||||
|
||||
@ -62,7 +65,7 @@ The **Create Configuration Item Wizard** starts.
|
||||
The **Configure Windows Information Protection settings** page appears, where you'll configure your policy for your organization.
|
||||
|
||||
## Add app rules to your policy
|
||||
During the policy-creation process in System Center Configuration Manager, you can choose the apps you want to give access to your enterprise data through WIP. Apps included in this list can protect data on behalf of the enterprise and are restricted from copying or moving enterprise data to unprotected apps.
|
||||
During the policy-creation process in Configuration Manager, you can choose the apps you want to give access to your enterprise data through WIP. Apps included in this list can protect data on behalf of the enterprise and are restricted from copying or moving enterprise data to unprotected apps.
|
||||
|
||||
The steps to add your app rules are based on the type of rule template being applied. You can add a store app (also known as a Universal Windows Platform (UWP) app), a signed Windows desktop app, or an AppLocker policy file.
|
||||
|
||||
@ -295,9 +298,9 @@ For this example, we’re going to add an AppLocker XML file to the **App Rules*
|
||||
</RuleCollection>
|
||||
</AppLockerPolicy>
|
||||
```
|
||||
12. After you’ve created your XML file, you need to import it by using System Center Configuration Manager.
|
||||
12. After you’ve created your XML file, you need to import it by using Configuration Manager.
|
||||
|
||||
**To import your Applocker policy file app rule using System Center Configuration Manager**
|
||||
**To import your Applocker policy file app rule using Configuration Manager**
|
||||
1. From the **App rules** area, click **Add**.
|
||||
|
||||
The **Add app rule** box appears.
|
||||
@ -506,3 +509,5 @@ After you’ve created your WIP policy, you'll need to deploy it to your organiz
|
||||
- [How to collect Windows Information Protection (WIP) audit event logs](collect-wip-audit-event-logs.md)
|
||||
|
||||
- [General guidance and best practices for Windows Information Protection (WIP)](guidance-and-best-practices-wip.md)
|
||||
|
||||
- [Limitations while using Windows Information Protection (WIP)](limitations-with-wip.md)
|
||||
|
@ -117,13 +117,14 @@
|
||||
#### [Use shared queries](microsoft-defender-atp/advanced-hunting-shared-queries.md)
|
||||
#### [Advanced hunting schema reference]()
|
||||
##### [Understand the schema](microsoft-defender-atp/advanced-hunting-schema-reference.md)
|
||||
##### [AlertEvents](microsoft-defender-atp/advanced-hunting-alertevents-table.md)
|
||||
##### [DeviceAlertEvents](microsoft-defender-atp/advanced-hunting-devicealertevents-table.md)
|
||||
##### [DeviceFileEvents](microsoft-defender-atp/advanced-hunting-devicefileevents-table.md)
|
||||
##### [DeviceImageLoadEvents](microsoft-defender-atp/advanced-hunting-deviceimageloadevents-table.md)
|
||||
##### [DeviceLogonEvents](microsoft-defender-atp/advanced-hunting-devicelogonevents-table.md)
|
||||
##### [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)
|
||||
##### [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)
|
||||
@ -155,6 +156,15 @@
|
||||
### [Portal overview](microsoft-defender-atp/portal-overview.md)
|
||||
### [Microsoft Defender ATP for US Government Community Cloud High customers](microsoft-defender-atp/commercial-gov.md)
|
||||
|
||||
|
||||
## [Deployment guide]()
|
||||
### [Product brief](microsoft-defender-atp/product-brief.md)
|
||||
### [Prepare deployment](microsoft-defender-atp/prepare-deployment.md)
|
||||
### [Evaluate capabilities](microsoft-defender-atp/evaluation-lab.md)
|
||||
### [Production deployment](microsoft-defender-atp/production-deployment.md)
|
||||
### [Helpful resources](microsoft-defender-atp/helpful-resources.md)
|
||||
|
||||
|
||||
## [Get started]()
|
||||
### [What's new in Microsoft Defender ATP](microsoft-defender-atp/whats-new-in-microsoft-defender-atp.md)
|
||||
### [Minimum requirements](microsoft-defender-atp/minimum-requirements.md)
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: AlertEvents table in the advanced hunting schema
|
||||
description: Learn about alert generation events in the AlertEvents 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, alertevents, alert, severity, category
|
||||
title: DeviceAlertEvents table in the advanced hunting schema
|
||||
description: Learn about alert generation events in the DeviceAlertEvents 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, DeviceAlertEvents, alert, severity, category
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
@ -15,10 +15,10 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 10/08/2019
|
||||
ms.date: 01/22/2020
|
||||
---
|
||||
|
||||
# AlertEvents
|
||||
# DeviceAlertEvents
|
||||
|
||||
**Applies to:**
|
||||
|
||||
@ -26,7 +26,7 @@ ms.date: 10/08/2019
|
||||
|
||||
>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)
|
||||
|
||||
The `AlertEvents` table in the [advanced hunting](advanced-hunting-overview.md) schema contains information about alerts on Microsoft Defender Security Center. Use this reference to construct queries that return information from the table.
|
||||
The `DeviceAlertEvents` table in the [advanced hunting](advanced-hunting-overview.md) schema contains information about alerts in Microsoft Defender Security Center. Use this reference to construct queries that return information from the table.
|
||||
|
||||
For information on other tables in the advanced hunting schema, see [the advanced hunting schema reference](advanced-hunting-schema-reference.md).
|
||||
|
@ -0,0 +1,60 @@
|
||||
---
|
||||
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
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: lomayor
|
||||
author: lomayor
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 01/14/2020
|
||||
---
|
||||
|
||||
# DeviceFileCertificateInfoBeta
|
||||
|
||||
**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-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.
|
||||
|
||||
For information on other tables in the advanced hunting schema, see [the advanced hunting schema reference](advanced-hunting-schema-reference.md).
|
||||
|
||||
| Column name | Data type | Description |
|
||||
|-------------|-----------|-------------|
|
||||
| `Timestamp` | datetime | Date and time when the event was recorded |
|
||||
| `DeviceId` | string | Unique identifier for the machine in the service |
|
||||
| `DeviceName` | string | Fully qualified domain name (FQDN) of the machine |
|
||||
| `SHA1` | string | SHA-1 of the file that the recorded action was applied to |
|
||||
| `IsSigned` | boolean | Indicates whether the file is signed |
|
||||
| `SignatureType` | string | Indicates whether signature information was read as embedded content in the file itself or read from an external catalog file |
|
||||
| `Signer` | string | Information about the signer of the file |
|
||||
| `SignerHash` | string | Unique hash value identifying the signer |
|
||||
| `Issuer` | string | Information about the issuing certificate authority (CA) |
|
||||
| `IssuerHash` | string | Unique hash value identifying issuing certificate authority (CA) |
|
||||
| `CertificateSerialNumber` | string | Identifier for the certificate that is unique to the issuing certificate authority (CA) |
|
||||
| `CrlDistributionPointUrls` | string | JSON array listing the URLs of network shares that contain certificates and certificate revocation lists (CRLs) |
|
||||
| `CertificateCreationTime` | datetime | Date and time the certificate was created |
|
||||
| `CertificateExpirationTime` | datetime | Date and time the certificate is set to expire |
|
||||
| `CertificateCountersignatureTime` | datetime | Date and time the certificate was countersigned |
|
||||
| `IsTrusted` | boolean | Indicates whether the file is trusted based on the results of the WinVerifyTrust function, which checks for unknown root certificate information, invalid signatures, revoked certificates, and other questionable attributes |
|
||||
| `IsRootSignerMicrosoft` | boolean | Indicates whether the signer of the root certificate is Microsoft |
|
||||
| `ReportId` | long | Event identifier based on a repeating counter. To identify unique events, this column must be used in conjunction with the DeviceName and Timestamp columns. |
|
||||
|
||||
|
||||
## Related topics
|
||||
- [Advanced hunting overview](advanced-hunting-overview.md)
|
||||
- [Learn the query language](advanced-hunting-query-language.md)
|
||||
- [Understand the schema](advanced-hunting-schema-reference.md)
|
@ -26,7 +26,7 @@ ms.date: 10/08/2019
|
||||
|
||||
>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)
|
||||
|
||||
The `DeviceImageLoadEvents table` in the [advanced hunting](advanced-hunting-overview.md) schema contains information about DLL loading events. Use this reference to construct queries that return information from the table.
|
||||
The `DeviceImageLoadEvents` table in the [advanced hunting](advanced-hunting-overview.md) schema contains information about DLL loading events. Use this reference to construct queries that return information from the table.
|
||||
|
||||
For information on other tables in the advanced hunting schema, see [the advanced hunting schema reference](advanced-hunting-schema-reference.md).
|
||||
|
||||
|
@ -23,8 +23,7 @@ ms.date: 10/08/2019
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
> [!TIP]
|
||||
> 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-advancedhunting-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-advancedhunting-abovefoldlink)
|
||||
|
||||
Advanced hunting is based on the [Kusto query language](https://docs.microsoft.com/azure/kusto/query/). You can use Kusto syntax and operators to construct queries that locate information in the [schema](advanced-hunting-schema-reference.md) specifically structured for advanced hunting. To understand these concepts better, run your first query.
|
||||
|
||||
@ -141,5 +140,4 @@ For detailed information about the query language, see [Kusto query language doc
|
||||
- [Understand the schema](advanced-hunting-schema-reference.md)
|
||||
- [Apply query best practices](advanced-hunting-best-practices.md)
|
||||
|
||||
> [!TIP]
|
||||
> 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-advancedhunting-belowfoldlink)
|
||||
>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-advancedhunting-belowfoldlink)
|
||||
|
@ -15,7 +15,7 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 10/08/2019
|
||||
ms.date: 01/14/2020
|
||||
---
|
||||
|
||||
# Understand the advanced hunting schema
|
||||
@ -37,7 +37,7 @@ Table and column names are also listed within the Microsoft Defender Security Ce
|
||||
|
||||
| Table name | Description |
|
||||
|------------|-------------|
|
||||
| **[AlertEvents](advanced-hunting-alertevents-table.md)** | Alerts on Microsoft Defender Security Center |
|
||||
| **[DeviceAlertEvents](advanced-hunting-devicealertevents-table.md)** | Alerts on Microsoft Defender Security Center |
|
||||
| **[DeviceInfo](advanced-hunting-deviceinfo-table.md)** | Machine information, including OS information |
|
||||
| **[DeviceNetworkInfo](advanced-hunting-devicenetworkinfo-table.md)** | Network properties of machines, including adapters, IP and MAC addresses, as well as connected networks and domains |
|
||||
| **[DeviceProcessEvents](advanced-hunting-deviceprocessevents-table.md)** | Process creation and related events |
|
||||
@ -47,6 +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 |
|
||||
| **[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 |
|
||||
|
@ -28,7 +28,7 @@ ms.date: 11/12/2019
|
||||
|
||||
[!include[Prerelease information](../../includes/prerelease.md)]
|
||||
|
||||
The `DeviceTvmSoftwareInventoryVulnerabilities` table in the advanced hunting schema contains the list of vulnerabilities [Threat & Vulnerability Management](next-gen-threat-and-vuln-mgt.md) assesses devices for. Use this reference to construct queries that return information from the table.
|
||||
The `DeviceTvmSoftwareVulnerabilitiesKB` table in the advanced hunting schema contains the list of vulnerabilities [Threat & Vulnerability Management](next-gen-threat-and-vuln-mgt.md) assesses devices for. Use this reference to construct queries that return information from the table.
|
||||
|
||||
For information on other tables in the advanced hunting schema, see [the advanced hunting reference](advanced-hunting-reference.md).
|
||||
|
||||
|
@ -118,7 +118,7 @@ If a proxy or firewall is blocking anonymous traffic, as Microsoft Defender ATP
|
||||
|
||||
## Microsoft Defender ATP service backend IP range
|
||||
|
||||
If you network devices don't support the URLs white-listed in the prior section, you can use the following information.
|
||||
If your network devices don't support the URLs white-listed in the prior section, you can use the following information.
|
||||
|
||||
Microsoft Defender ATP is built on Azure cloud, deployed in the following regions:
|
||||
|
||||
|
@ -0,0 +1,60 @@
|
||||
---
|
||||
title: Helpful Microsoft Defender Advanced Threat Protection resources
|
||||
description: Access helpful resources such as links to blogs and other resources related to Microsoft Defender Advanced Threat Protection
|
||||
keywords: Microsoft Defender Security Center, product brief, brief, capabilities, licensing
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
---
|
||||
|
||||
# Helpful Microsoft Defender Advanced Threat Protection resources
|
||||
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
Access helpful resources such as links to blogs and other resources related to Microsoft Defender Advanced Threat Protection.
|
||||
|
||||
## Endpoint protection platform
|
||||
- [Top scoring in industry
|
||||
tests](https://docs.microsoft.com/windows/security/threat-protection/intelligence/top-scoring-industry-antivirus-tests)
|
||||
|
||||
- [Inside out: Get to know the advanced technologies at the core of Microsoft
|
||||
Defender ATP next generation
|
||||
protection](https://www.microsoft.com/security/blog/2019/06/24/inside-out-get-to-know-the-advanced-technologies-at-the-core-of-microsoft-defender-atp-next-generation-protection/)
|
||||
|
||||
- [Protecting disconnected devices with Microsoft Defender
|
||||
ATP](https://techcommunity.microsoft.com/t5/Microsoft-Defender-ATP/Protecting-disconnected-devices-with-Microsoft-Defender-ATP/ba-p/500341)
|
||||
|
||||
- [Tamper protection in Microsoft Defender
|
||||
ATP](https://techcommunity.microsoft.com/t5/Microsoft-Defender-ATP/Tamper-protection-in-Microsoft-Defender-ATP/ba-p/389571)
|
||||
|
||||
## Endpoint Detection Response
|
||||
|
||||
- [Incident response at your fingertips with Microsoft Defender ATP live
|
||||
response](https://techcommunity.microsoft.com/t5/Microsoft-Defender-ATP/Incident-response-at-your-fingertips-with-Microsoft-Defender-ATP/ba-p/614894)
|
||||
|
||||
## Threat Vulnerability Management
|
||||
|
||||
- [Microsoft Defender ATP Threat & Vulnerability Management now publicly
|
||||
available!](https://techcommunity.microsoft.com/t5/Microsoft-Defender-ATP/MDATP-Threat-amp-Vulnerability-Management-now-publicly-available/ba-p/460977)
|
||||
|
||||
## Operational
|
||||
|
||||
- [The Golden Hour remake - Defining metrics for a successful security
|
||||
operations](https://techcommunity.microsoft.com/t5/Microsoft-Defender-ATP/The-Golden-Hour-remake-Defining-metrics-for-a-successful/ba-p/782014)
|
||||
|
||||
- [Microsoft Defender ATP Evaluation lab is now available in public preview
|
||||
](https://techcommunity.microsoft.com/t5/Microsoft-Defender-ATP/Microsoft-Defender-ATP-Evaluation-lab-is-now-available-in-public/ba-p/770271)
|
||||
|
||||
- [How automation brings value to your security
|
||||
teams](https://techcommunity.microsoft.com/t5/Microsoft-Defender-ATP/How-automation-brings-value-to-your-security-teams/ba-p/729297)
|
After Width: | Height: | Size: 9.3 KiB |
After Width: | Height: | Size: 90 KiB |
After Width: | Height: | Size: 122 KiB |
After Width: | Height: | Size: 44 KiB |
After Width: | Height: | Size: 45 KiB |
After Width: | Height: | Size: 373 KiB |
After Width: | Height: | Size: 37 KiB |
After Width: | Height: | Size: 58 KiB |
After Width: | Height: | Size: 110 KiB |
After Width: | Height: | Size: 365 KiB |
After Width: | Height: | Size: 5.0 KiB |
After Width: | Height: | Size: 24 KiB |
After Width: | Height: | Size: 10 KiB |
After Width: | Height: | Size: 121 KiB |
After Width: | Height: | Size: 10 KiB |
After Width: | Height: | Size: 464 KiB |
After Width: | Height: | Size: 289 KiB |
After Width: | Height: | Size: 483 KiB |
After Width: | Height: | Size: 34 KiB |
After Width: | Height: | Size: 44 KiB |
After Width: | Height: | Size: 263 KiB |
After Width: | Height: | Size: 30 KiB |
After Width: | Height: | Size: 261 KiB |
After Width: | Height: | Size: 54 KiB |
After Width: | Height: | Size: 37 KiB |
After Width: | Height: | Size: 588 KiB |
After Width: | Height: | Size: 205 KiB |
After Width: | Height: | Size: 376 KiB |
After Width: | Height: | Size: 72 KiB |
After Width: | Height: | Size: 343 KiB |
After Width: | Height: | Size: 266 KiB |
After Width: | Height: | Size: 297 KiB |
After Width: | Height: | Size: 9.3 KiB |
After Width: | Height: | Size: 374 KiB |
After Width: | Height: | Size: 303 KiB |
After Width: | Height: | Size: 19 KiB |
After Width: | Height: | Size: 54 KiB |
After Width: | Height: | Size: 102 KiB |
After Width: | Height: | Size: 307 KiB |
After Width: | Height: | Size: 127 KiB |
After Width: | Height: | Size: 433 KiB |
After Width: | Height: | Size: 7.3 KiB |
After Width: | Height: | Size: 463 KiB |
After Width: | Height: | Size: 40 KiB |
After Width: | Height: | Size: 52 KiB |
After Width: | Height: | Size: 48 KiB |
After Width: | Height: | Size: 185 KiB |
After Width: | Height: | Size: 72 KiB |
Before Width: | Height: | Size: 69 KiB After Width: | Height: | Size: 72 KiB |
After Width: | Height: | Size: 83 KiB |
After Width: | Height: | Size: 24 KiB |
After Width: | Height: | Size: 80 KiB |
After Width: | Height: | Size: 51 KiB |
After Width: | Height: | Size: 52 KiB |
After Width: | Height: | Size: 96 KiB |
After Width: | Height: | Size: 61 KiB |
After Width: | Height: | Size: 53 KiB |
After Width: | Height: | Size: 83 KiB |
After Width: | Height: | Size: 42 KiB |
After Width: | Height: | Size: 83 KiB |
After Width: | Height: | Size: 52 KiB |
After Width: | Height: | Size: 64 KiB |
Before Width: | Height: | Size: 62 KiB After Width: | Height: | Size: 64 KiB |
After Width: | Height: | Size: 121 KiB |
After Width: | Height: | Size: 24 KiB |
After Width: | Height: | Size: 7.8 KiB |
After Width: | Height: | Size: 47 KiB |
After Width: | Height: | Size: 47 KiB |
@ -68,7 +68,7 @@ The **Alert process tree** takes alert triage and investigation to the next leve
|
||||
The **Alert process tree** expands to display the execution path of the alert and related evidence that occurred around the same period. Items marked with a thunderbolt icon should be given priority during investigation.
|
||||
|
||||
>[!NOTE]
|
||||
>The alert process tree might not be available in some alerts.
|
||||
>The alert process tree might not show for some alerts, including alerts not triggered directly by process activity.
|
||||
|
||||
Clicking in the circle immediately to the left of the indicator displays its details.
|
||||
|
||||
|
@ -44,7 +44,7 @@ If you turn network protection off, users or apps will not be blocked from conne
|
||||
|
||||
If you do not configure it, network blocking will be turned off by default.
|
||||
|
||||
For more information, see [Enable network protection](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-exploit-guard/enable-network-protection).
|
||||
For more information, see [Enable network protection](enable-network-protection.md).
|
||||
|
||||
## Investigation impact
|
||||
When network protection is turned on, you'll see that on a machine's timeline the IP address will keep representing the proxy, while the real target address shows up.
|
||||
@ -86,4 +86,3 @@ DeviceNetworkEvents
|
||||
|
||||
## Related topics
|
||||
- [Applying network protection with GP - policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-defender#defender-enablenetworkprotection)
|
||||
- [Protect your network](https://docs.microsoft.comwindows/security/threat-protection/windows-defender-exploit-guard/network-protection-exploit-guard)
|
@ -123,6 +123,11 @@ It's important to understand the following prerequisites prior to creating indic
|
||||
|
||||
>[!IMPORTANT]
|
||||
> Only external IPs can be added to the indicator list. Indicators cannot be created for internal IPs.
|
||||
> For web protection scenarios, we recommend using the built-in capabilities in Microsoft Edge. Microsoft Edge leverages Network Protection (link) to inspect network traffic and allows blocks for TCP, HTTP, and HTTPS (TLS): <br>
|
||||
> NOTE:
|
||||
>- IP is supported for all three protocols
|
||||
>- Encrypted URLs can only be blocked on first party browsers
|
||||
>- Full URL path blocks can be applied on the domain level and all unencrypted URLs
|
||||
|
||||
>[!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.
|
||||
|
@ -63,7 +63,7 @@ The three most recent major releases of macOS are supported.
|
||||
- 10.15 (Catalina), 10.14 (Mojave), 10.13 (High Sierra)
|
||||
- Disk space: 650 MB
|
||||
|
||||
Beta versions of macOS are not supported. macOS Sierra (10.12) support will end on January 1, 2020.
|
||||
Beta versions of macOS are not supported. macOS Sierra (10.12) support ended on January 1, 2020.
|
||||
|
||||
After you've enabled the service, you may need to configure your network or firewall to allow outbound connections between it and your endpoints.
|
||||
|
||||
|
@ -0,0 +1,162 @@
|
||||
---
|
||||
title: Prepare Microsoft Defender ATP deployment
|
||||
description: Prepare stakeholder sign-off, timelines, environment considerations, and adoption order when deploying Microsoft Defender ATP
|
||||
keywords: deploy, prepare, stakeholder, timeline, environment, endpoint, server, management, adoption
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Prepare Microsoft Defender ATP deployment
|
||||
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
## Stakeholders and Sign-off
|
||||
The following section serves to identify all the stakeholders that are involved
|
||||
in this project and need to sign-off, review, or stay informed. Add stakeholders
|
||||
to the table below as appropriate for your organization.
|
||||
|
||||
- SO = Sign-off on this project
|
||||
|
||||
- R = Review this project and provide input
|
||||
|
||||
- I = Informed of this project
|
||||
|
||||
| Name | Role | Action |
|
||||
|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|
|
||||
| Enter name and email | **Chief Information Security Officer (CISO)** *An executive representative who serves as sponsor inside the organization for the new technology deployment.* | SO |
|
||||
| Enter name and email | **Head of Cyber Defense Operations Center (CDOC)** *A representative from the CDOC team in charge of defining how this change is aligned with the processes in the customers security operations team.* | SO |
|
||||
| Enter name and email | **Security Architect** *A representative from the Security team in charge of defining how this change is aligned with the core Security architecture in the organization.* | R |
|
||||
| Enter name and email | **Workplace Architect** *A representative from the IT team in charge of defining how this change is aligned with the core workplace architecture in the organization.* | R |
|
||||
| Enter name and email | **Security Analyst** *A representative from the CDOC team who can provide input on the detection capabilities, user experience and overall usefulness of this change from a security operations perspective.* | I |
|
||||
|
||||
## Project Management
|
||||
|
||||
### In Scope
|
||||
|
||||
The following is in scope for this project:
|
||||
|
||||
- Enabling Microsoft Defender ATP endpoint protection platform (EPP)
|
||||
capabilities
|
||||
|
||||
- Next Generation Protection
|
||||
|
||||
- Attack Surface Reduction
|
||||
|
||||
- Enabling Microsoft Defender ATP endpoint detection and response (EDR)
|
||||
capabilities including automatic investigation and remediation
|
||||
|
||||
- Enabling Microsoft Defender ATP threat and vulnerability management (TVM)
|
||||
- Use of System Center Configuration Manager to onboard endpoints into the service.
|
||||
|
||||
### Out of scope
|
||||
|
||||
The following are out of scope of this project:
|
||||
|
||||
- Configuration of third-party solutions that might integrate with Microsoft
|
||||
Defender ATP.
|
||||
|
||||
- Penetration testing in production environment.
|
||||
|
||||
## Environment
|
||||
|
||||
|
||||
This section is used to ensure your environment is deeply understood by the
|
||||
stakeholders which will help identify potential dependencies and/or changes
|
||||
required in technologies or processes.
|
||||
|
||||
| What | Description |
|
||||
|---------------------------------------|-------------|
|
||||
| Endpoint count | |
|
||||
| Server count | |
|
||||
| Management engine | |
|
||||
| CDOC distribution | |
|
||||
| Security information and event (SIEM) | |
|
||||
|
||||
|
||||
## Role-based access control
|
||||
|
||||
Microsoft recommends using the concept of least privileges. Microsoft Defender
|
||||
ATP leverages built-in roles within Azure Active Directory. Microsoft recommend
|
||||
[review the different roles that are
|
||||
available](https://docs.microsoft.com/azure/active-directory/active-directory-assign-admin-roles-azure-portal)
|
||||
and choose the right one to solve your needs for each persona for this
|
||||
application. Some roles may need to be applied temporarily and removed after the
|
||||
deployment has been completed.
|
||||
|
||||
| Personas | Roles | Azure AD Role (if required) | Assign to |
|
||||
|------------------------------|-------|-----------------------------|-----------|
|
||||
| Security Administrator | | | |
|
||||
| Security Analyst | | | |
|
||||
| Endpoint Administrator | | | |
|
||||
| Infrastructure Administrator | | | |
|
||||
| Business Owner/Stakeholder | | | |
|
||||
|
||||
Microsoft recommends using [Privileged Identity
|
||||
Management](https://docs.microsoft.com/azure/active-directory/active-directory-privileged-identity-management-configure)
|
||||
to manage your roles to provide additional auditing, control, and access review
|
||||
for users with directory permissions.
|
||||
|
||||
Microsoft Defender ATP supports two ways to manage permissions:
|
||||
|
||||
- **Basic permissions management**: Set permissions to either full access or
|
||||
read-only. In the case of basic permissions management users with Global
|
||||
Administrator or Security Administrator role in Azure Active Directory have
|
||||
full access while the Security reader role has read-only access.
|
||||
|
||||
- **Role-based access control (RBAC)**: Set granular permissions by defining
|
||||
roles, assigning Azure AD user groups to the roles, and granting the user
|
||||
groups access to machine groups. For more information. see [Manage portal access using role-based access control](rbac.md).
|
||||
|
||||
Microsoft recommends leveraging RBAC to ensure that only users that have a
|
||||
business justification can access Microsoft Defender ATP.
|
||||
|
||||
You can find details on permission guidelines
|
||||
[here](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/user-roles#create-roles-and-assign-the-role-to-an-azure-active-directory-group).
|
||||
|
||||
The following example table serves to identify the Cyber Defense Operations
|
||||
Center structure in your environment that will help you determine the RBAC
|
||||
structure required for your environment.
|
||||
|
||||
| Tier | Description | Permission Required |
|
||||
|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|
|
||||
| Tier 1 | **Local security operations team / IT team**<br>This team usually triages and investigates alerts contained within their geolocation and escalates to Tier 2 in cases where an active remediation is required. | |
|
||||
| Tier 2 | **Regional security operations team**<br>This team can see all the machines for their region and perform remediation actions. | View data |
|
||||
| Tier 3 | **Global security operations team**<br>This team consists of security experts and are authorized to see and perform all actions from the portal. | View data <br> Alerts investigation Active remediation actions <br> Alerts investigation Active remediation actions <br> Manage portal system settings <br> Manage security settings |
|
||||
|
||||
|
||||
|
||||
## Adoption Order
|
||||
In many cases organizations will have existing endpoint security products in
|
||||
place. The bare minimum every organization should have is an antivirus solution. But in some cases an organization might also already implanted an EDR solution.
|
||||
Historically, replacing any security solution was time intensive and difficult
|
||||
to achieve due to the tight hooks into the application layer and infrastructure
|
||||
dependencies. However, because Microsoft Defender ATP is built into the
|
||||
operating system, replacing third-party solutions is easy to achieve.
|
||||
|
||||
Choose which component of Microsoft Defender ATP to be used and remove the ones
|
||||
that do not apply. The table below indicates the Microsoft recommendation on the
|
||||
order on how the endpoint security suite should be enabled.
|
||||
|
||||
| Component | Description | Adoption Order Rank |
|
||||
|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|
|
||||
| Endpoint Detection & Response (EDR) | Microsoft Defender ATP endpoint detection and response capabilities provide advanced attack detections that are near real-time and actionable. Security analysts can prioritize alerts effectively, gain visibility into the full scope of a breach, and take response actions to remediate threats. [Learn more.](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/overview-endpoint-detection-response) | 1 |
|
||||
| Next Generation Protection (NGP) | Microsoft Defender Antivirus is a built-in antimalware solution that provides next generation protection for desktops, portable computers, and servers. Windows Defender Antivirus includes: | 2 |
|
||||
| Attack Surface Reduction (ASR) | Attack surface reduction capabilities in Microsoft Defender ATP helps protect the devices and applications in the organization from new and emerging threats. [Learn more.](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/overview-attack-surface-reduction) | 3 |
|
||||
| Threat & Vulnerability Management (TVM) | Threat & Vulnerability Management is a component of Microsoft Defender ATP, and provides both security administrators and security operations teams with unique value, including: | 4 |
|
||||
| Auto Investigation & Remediation (AIR) | Microsoft Defender ATP uses Automated investigations to significantly reduce the volume of alerts that need to be investigated individually. The Automated investigation feature leverages various inspection algorithms, and processes used by analysts (such as playbooks) to examine alerts and take immediate remediation action to resolve breaches. This significantly reduces alert volume, allowing security operations experts to focus on more sophisticated threats and other high value initiatives. [Learn more.](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/automated-investigations-windows-defender-advanced-threat-protection) | Not applicable |
|
||||
| Microsoft Threat Experts (MTE) | Microsoft Threat Experts is a managed hunting service that provides Security Operation Centers (SOCs) with expert level monitoring and analysis to help them ensure that critical threats in their unique environments don't get missed. [Learn more.](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/microsoft-threat-experts) | Not applicable |
|
||||
|
||||
## Related topic
|
||||
- [Production deployment](production-deployment.md)
|
@ -0,0 +1,74 @@
|
||||
---
|
||||
title: Microsoft Defender Advanced Threat Protection product brief
|
||||
description: Learn about the Microsoft Defender Advanced Threat Protection capabilities and licensing requirements
|
||||
keywords: Microsoft Defender Security Center, product brief, brief, capabilities, licensing
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
---
|
||||
|
||||
# Microsoft Defender Advanced Threat Protection product brief
|
||||
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
|
||||
Microsoft Defender ATP is a platform designed to
|
||||
help enterprise networks prevent, detect, investigate, and respond to advanced
|
||||
threats.
|
||||
|
||||

|
||||
|
||||
## Platform capabilities
|
||||
|
||||
Capability | Description
|
||||
:---|:---
|
||||
**Threat and Vulnerability Management** | This built-in capability uses a game-changing risk-based approach to the discovery, prioritization, and remediation of endpoint vulnerabilities and misconfigurations.
|
||||
**Attack Surface Reduction** | The attack surface reduction set of capabilities provide the first line of defense in the stack. By ensuring configuration settings are properly set and exploit mitigation techniques are applied, these set of capabilities resist attacks and exploitations.
|
||||
**Next Generation Protection** | To further reinforce the security perimeter of the organizations network, Microsoft Defender ATP uses next generation protection designed to catch all types of emerging threats.
|
||||
**Endpoint Detection & Response** | Endpoint detection and response capabilities are put in place to detect, investigate, and respond to advanced threats that may have made it past the first two security pillars.
|
||||
**Auto Investigation & Remediation** | In conjunction with being able to quickly respond to advanced attacks, Microsoft Defender ATP offers automatic investigation and remediation capabilities that help reduce the volume of alerts in minutes at scale.
|
||||
**Microsoft Threat Experts** | Microsoft Defender ATP's new managed threat hunting service provides proactive hunting, prioritization, and additional context and insights that further empower Security operation centers (SOCs) to identify and respond to threats quickly and accurately.
|
||||
**Secure Score** | Microsoft Defender ATP includes a secure score to help dynamically assess the security state of the enterprise network, identify unprotected systems, and take recommended actions to improve the overall security of the organization.
|
||||
**Advance Hunting** | Create custom threat intelligence and use a powerful search and query tool to hunt for possible threats in the organization.
|
||||
**Management and API** | Integrate Microsoft Defender Advanced Threat Protection into existing workflows.
|
||||
**Microsoft Threat Protection** | Microsoft Defender ATP is part of the Microsoft Threat Protection solution that helps implement end-to-end security across possible attack surfaces in the modern workplace. Bring the power of Microsoft threat protection to the organization. | |
|
||||
|
||||
Microsoft Defender ATP uses the following combination of technology built into Windows 10 and Microsoft's robust cloud service:
|
||||
|
||||
- **Endpoint behavioral sensors**: Embedded in Windows 10, these sensors
|
||||
collect and process behavioral signals from the operating system and sends this sensor data to your private, isolated, cloud instance of Microsoft Defender ATP.
|
||||
|
||||
|
||||
- **Cloud security analytics**: Leveraging big-data, machine-learning, and
|
||||
unique Microsoft optics across the Windows ecosystem,
|
||||
enterprise cloud products (such as Office 365), and online assets, behavioral signals
|
||||
are translated into insights, detections, and recommended responses
|
||||
to advanced threats.
|
||||
|
||||
- **Threat intelligence**: Generated by Microsoft hunters, security teams,
|
||||
and augmented by threat intelligence provided by partners, threat
|
||||
intelligence enables Microsoft Defender ATP to identify attacker
|
||||
tools, techniques, and procedures, and generate alerts when these
|
||||
are observed in collected sensor data.
|
||||
|
||||
## Licensing requirements
|
||||
Microsoft Defender Advanced Threat Protection requires one of the following Microsoft Volume Licensing offers:
|
||||
|
||||
- Windows 10 Enterprise E5
|
||||
- Windows 10 Education A5
|
||||
- Microsoft 365 E5 (M365 E5) which includes Windows 10 Enterprise E5
|
||||
- Microsoft 365 A5 (M365 A5)
|
||||
|
||||
## Related topic
|
||||
- [Prepare deployment](prepare-deployment.md)
|
@ -0,0 +1,602 @@
|
||||
---
|
||||
title: Microsoft Defender ATP production deployment
|
||||
description:
|
||||
keywords:
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Microsoft Defender ATP production deployment
|
||||
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
Proper planning is the foundation of a successful deployment. In this deployment scenario, you'll be guided through the steps on:
|
||||
- Tenant configuration
|
||||
- Network configuration
|
||||
- Onboarding using System Center Configuration Manager
|
||||
- Endpoint detection and response
|
||||
- Next generation protection
|
||||
- Attack surface reduction
|
||||
|
||||
>[!NOTE]
|
||||
>For the purpose of guiding you through a typical deployment, this scenario will only cover the use of System Center Configuration Manager. Microsoft Defnder ATP supports the use of other onboarding tools but will not cover those scenarios in the deployment guide. For more information, see [Onboard machines to Microsoft Defender ATP](onboard-configure.md).
|
||||
|
||||
## Tenant Configuration
|
||||
|
||||
When accessing [Microsoft Defender Security Center](https://securitycenter.windows.com/) for the first time there will be a setup wizard that will guide you through some initial steps. At the end of the setup wizard there will be a dedicated cloud instance of Microsoft Defender ATP created. The easiest method is to perform these steps from a Windows 10 client machine.
|
||||
|
||||
1. From a web browser, navigate to <https://securitycenter.windows.com>.
|
||||
|
||||

|
||||
|
||||
2. If going through a TRIAL license, go to the link (<https://signup.microsoft.com/Signup?OfferId=6033e4b5-c320-4008-a936-909c2825d83c&dl=WIN_DEF_ATP&pc=xxxxxxx-xxxxxx-xxx-x>)
|
||||
|
||||
Once the authorization step is completed, the **Welcome** screen will be displayed.
|
||||
3. Go through the authorization steps.
|
||||
|
||||

|
||||
|
||||
4. Set up preferences.
|
||||
|
||||
**Data storage location** - It's important to set this up correctly. Determine where the customer wants to be primarily hosted: US, EU or UK. You cannot change the location after this setup and Microsoft will not transfer the data from the specified geolocation.
|
||||
|
||||
**Data retention** - The default is 6 months.
|
||||
|
||||
**Enable preview features** - The default is on, can be changed later.
|
||||
|
||||

|
||||
|
||||
5. Select **Next**.
|
||||
|
||||

|
||||
|
||||
6. Select **Continue**.
|
||||
|
||||
|
||||
## Network configuration
|
||||
If the organization does not require the endpoints to use a Proxy to access the
|
||||
Internet, skip this section.
|
||||
|
||||
The Microsoft Defender ATP sensor requires Microsoft Windows HTTP (WinHTTP) to
|
||||
report sensor data and communicate with the Microsoft Defender ATP service. The
|
||||
embedded Microsoft Defender ATP sensor runs in the system context using the
|
||||
LocalSystem account. The sensor uses Microsoft Windows HTTP Services (WinHTTP)
|
||||
to enable communication with the Microsoft Defender ATP cloud service. The
|
||||
WinHTTP configuration setting is independent of the Windows Internet (WinINet)
|
||||
internet browsing proxy settings and can only discover a proxy server by using
|
||||
the following discovery methods:
|
||||
|
||||
**Auto-discovery methods:**
|
||||
|
||||
- Transparent proxy
|
||||
|
||||
- Web Proxy Auto-discovery Protocol (WPAD)
|
||||
|
||||
If a Transparent proxy or WPAD has been implemented in the network topology,
|
||||
there is no need for special configuration settings. For more information on
|
||||
Microsoft Defender ATP URL exclusions in the proxy, see the
|
||||
Appendix section in this document for the URLs Whitelisting or on
|
||||
[Microsoft
|
||||
Docs](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection#enable-access-to-windows-defender-atp-service-urls-in-the-proxy-server).
|
||||
|
||||
**Manual static proxy configuration:**
|
||||
|
||||
- Registry based configuration
|
||||
|
||||
- WinHTTP configured using netsh command <br> Suitable only for desktops in a
|
||||
stable topology (for example: a desktop in a corporate network behind the
|
||||
same proxy)
|
||||
|
||||
### Configure the proxy server manually using a registry-based static proxy
|
||||
|
||||
Configure a registry-based static proxy to allow only Microsoft Defender ATP
|
||||
sensor to report diagnostic data and communicate with Microsoft Defender ATP
|
||||
services if a computer is not permitted to connect to the Internet. The static
|
||||
proxy is configurable through Group Policy (GP). The group policy can be found
|
||||
under:
|
||||
|
||||
- Administrative Templates \> Windows Components \> Data Collection and
|
||||
Preview Builds \> Configure Authenticated Proxy usage for the Connected User
|
||||
Experience and Telemetry Service
|
||||
|
||||
- Set it to **Enabled** and select<63>**Disable Authenticated Proxy usage**
|
||||
|
||||
1. Open the Group Policy Management Console.
|
||||
2. Create a policy or edit an existing policy based off the organizational practices.
|
||||
3. Edit the Group Policy and navigate to **Administrative Templates \> Windows Components \> Data Collection and Preview Builds \> Configure Authenticated Proxy usage for the Connected User Experience and Telemetry Service**.
|
||||

|
||||
|
||||
4. Select **Enabled**.
|
||||
5. Select **Disable Authenticated Proxy usage**.
|
||||
|
||||
6. Navigate to **Administrative Templates \> Windows Components \> Data Collection and Preview Builds \> Configure connected user experiences and telemetry**.
|
||||

|
||||
7. Select **Enabled**.
|
||||
8. Enter the **Proxy Server Name**.
|
||||
|
||||
The policy sets two registry values `TelemetryProxyServer` as REG_SZ and `DisableEnterpriseAuthProxy` as REG_DWORD under the registry key `HKLM\Software\Policies\Microsoft\Windows\DataCollection`.
|
||||
|
||||
The registry value `TelemetryProxyServer` takes the following string format:
|
||||
|
||||
```text
|
||||
<server name or ip>:<port>
|
||||
```
|
||||
|
||||
For example: 10.0.0.6:8080
|
||||
|
||||
The registry value `DisableEnterpriseAuthProxy` should be set to 1.
|
||||
|
||||
### Configure the proxy server manually using netsh command
|
||||
|
||||
Use netsh to configure a system-wide static proxy.
|
||||
|
||||
> [!NOTE]
|
||||
> - This will affect all applications including Windows services which use WinHTTP with default proxy.</br>
|
||||
> - Laptops that are changing topology (for example: from office to home) will malfunction with netsh. Use the registry-based static proxy configuration.
|
||||
|
||||
1. Open an elevated command-line:
|
||||
|
||||
a. Go to **Start** and type **cmd**.
|
||||
|
||||
b. Right-click **Command prompt** and select **Run as administrator**.
|
||||
|
||||
2. Enter the following command and press **Enter**:
|
||||
|
||||
```PowerShell
|
||||
netsh winhttp set proxy <proxy>:<port>
|
||||
```
|
||||
|
||||
For example: netsh winhttp set proxy 10.0.0.6:8080
|
||||
|
||||
|
||||
### Proxy Configuration for down-level machines
|
||||
|
||||
Down-Level machines include Windows 7 SP1 and Windows 8.1 workstations as well
|
||||
as Windows Server 2008 R2, Windows Sever 2012, Windows Server 2012 R2, and
|
||||
versions of Windows Server 2016 prior to Windows Server CB 1803. These operating
|
||||
systems will have the proxy configured as part of the Microsoft Management Agent
|
||||
to handle communication from the endpoint to Azure. Refer to the
|
||||
Microsoft Management Agent Fast Deployment Guide for information on how a proxy
|
||||
is configured on these machines.
|
||||
|
||||
### Proxy Service URLs
|
||||
URLs that include v20 in them are only needed if you have Windows 10, version
|
||||
1803 or later machines. For example, ```us-v20.events.data.microsoft.com``` is only
|
||||
needed if the machine is on Windows 10, version 1803 or later.
|
||||
|
||||
Service location | Microsoft.com DNS record
|
||||
-|-
|
||||
Common URLs for all locations | ```crl.microsoft.com```<br> ```ctldl.windowsupdate.com``` <br>```events.data.microsoft.com```<br>```notify.windows.com```<br> ```settings-win.data.microsoft.com```
|
||||
European Union | ```eu.vortex-win.data.microsoft.com``` <br> ```eu-v20.events.data.microsoft.com``` <br> ```usseu1northprod.blob.core.windows.net``` <br>```usseu1westprod.blob.core.windows.net``` <br> ```winatp-gw-neu.microsoft.com``` <br> ```winatp-gw-weu.microsoft.com``` <br>```wseu1northprod.blob.core.windows.net``` <br>```wseu1westprod.blob.core.windows.net```
|
||||
United Kingdom | ```uk.vortex-win.data.microsoft.com``` <br>```uk-v20.events.data.microsoft.com``` <br>```ussuk1southprod.blob.core.windows.net``` <br>```ussuk1westprod.blob.core.windows.net``` <br>```winatp-gw-uks.microsoft.com``` <br>```winatp-gw-ukw.microsoft.com``` <br>```wsuk1southprod.blob.core.windows.net``` <br>```wsuk1westprod.blob.core.windows.net```
|
||||
United States | ```us.vortex-win.data.microsoft.com``` <br> ```ussus1eastprod.blob.core.windows.net``` <br> ```ussus1westprod.blob.core.windows.net``` <br> ```ussus2eastprod.blob.core.windows.net``` <br> ```ussus2westprod.blob.core.windows.net``` <br> ```ussus3eastprod.blob.core.windows.net``` <br> ```ussus3westprod.blob.core.windows.net``` <br> ```ussus4eastprod.blob.core.windows.net``` <br> ```ussus4westprod.blob.core.windows.net``` <br> ```us-v20.events.data.microsoft.com``` <br> ```winatp-gw-cus.microsoft.com``` <br> ```winatp-gw-eus.microsoft.com``` <br> ```wsus1eastprod.blob.core.windows.net``` <br> ```wsus1westprod.blob.core.windows.net``` <br> ```wsus2eastprod.blob.core.windows.net``` <br> ```wsus2westprod.blob.core.windows.net```
|
||||
|
||||
|
||||
If a proxy or firewall is blocking anonymous traffic, as Microsoft Defender ATP sensor is connecting from system context, make sure anonymous traffic is permitted in the previously listed URLs.
|
||||
|
||||
### Microsoft Defender ATP service backend IP range
|
||||
|
||||
If you network devices don't support the URLs white-listed in the prior section, you can use the following information.
|
||||
|
||||
Microsoft Defender ATP is built on Azure cloud, deployed in the following regions:
|
||||
|
||||
- \+\<Region Name="uswestcentral">
|
||||
- \+\<Region Name="useast2">
|
||||
- \+\<Region Name="useast">
|
||||
- \+\<Region Name="europenorth">
|
||||
- \+\<Region Name="europewest">
|
||||
- \+\<Region Name="uksouth">
|
||||
- \+\<Region Name="ukwest">
|
||||
|
||||
You can find the Azure IP range on [Microsoft Azure Datacenter IP Ranges](https://www.microsoft.com/en-us/download/details.aspx?id=41653).
|
||||
|
||||
> [!NOTE]
|
||||
> As a cloud-based solution, the IP range can change. It's recommended you move to DNS resolving setting.
|
||||
|
||||
## Onboarding using System Center Configuration Manager
|
||||
### Collection creation
|
||||
To onboard Windows 10 devices with System Center Configuration Manager, the
|
||||
deployment can target either and existing collection or a new collection can be
|
||||
created for testing. The onboarding like group policy or manual method does
|
||||
not install any agent on the system. Within the Configuration Manager console
|
||||
the onboarding process will be configured as part of the compliance settings
|
||||
within the console. Any system that receives this required configuration will
|
||||
maintain that configuration for as long as the Configuration Manager client
|
||||
continues to receive this policy from the management point. Follow the steps
|
||||
below to onboard systems with Configuration Manager.
|
||||
|
||||
1. In System Center Configuration Manager console, navigate to **Assets and Compliance \> Overview \> Device Collections**.
|
||||
|
||||

|
||||
|
||||
2. Right Click **Device Collection** and select **Create Device Collection**.
|
||||
|
||||

|
||||
|
||||
3. Provide a **Name** and **Limiting Collection**, then select **Next**.
|
||||
|
||||

|
||||
|
||||
4. Select **Add Rule** and choose **Query Rule**.
|
||||
|
||||

|
||||
|
||||
5. Click **Next** on the **Direct Membership Wizard** and click on **Edit Query Statement**.
|
||||
|
||||

|
||||
|
||||
6. Select **Criteria** and then choose the star icon.
|
||||
|
||||

|
||||
|
||||
7. Keep criterion type as **simple value**, choose where as **Operating System - build number**, operator as **is equal to** and value **10240** and click on **OK**.
|
||||
|
||||

|
||||
|
||||
8. Select **Next** and **Close**.
|
||||
|
||||

|
||||
|
||||
9. Select **Next**.
|
||||
|
||||

|
||||
|
||||
After completing this task, you now have a device collection with all the Windows 10 endpoints in the environment.
|
||||
|
||||
## Endpoint detection and response
|
||||
### Windows 10
|
||||
From within the Microsoft Defender Security Center it is possible to download
|
||||
the '.onboarding' policy that can be used to create the policy in System Center Configuration
|
||||
Manager and deploy that policy to Windows 10 devices.
|
||||
|
||||
1. From a Microsoft Defender Security Center Portal, select [Settings and then Onboarding](https://securitycenter.windows.com/preferences2/onboarding).
|
||||
|
||||
|
||||
|
||||
2. Under Deployment method select the supported version of **System Center Configuration Manager**.
|
||||
|
||||

|
||||
|
||||
3. Select **Download package**.
|
||||
|
||||

|
||||
|
||||
4. Save the package to an accessible location.
|
||||
5. In System Center Configuration Manager, navigate to: **Assets and Compliance > Overview > Endpoint Protection > Microsoft Defender ATP Policies**.
|
||||
|
||||
6. Right-click **Microsoft Defender ATP Policies** and select **Create Microsoft Defender ATP Policy**.
|
||||
|
||||

|
||||
|
||||
7. Enter the name and description, verify **Onboarding** is selected, then select **Next**.
|
||||
|
||||

|
||||
|
||||
8. Click **Browse**.
|
||||
|
||||
9. Navigate to the location of the downloaded file from step 4 above.
|
||||
|
||||

|
||||
|
||||
10. Click **Next**.
|
||||
11. Configure the Agent with the appropriate samples (**None** or **All file types**).
|
||||
|
||||

|
||||
|
||||
12. Select the appropriate telemetry (**Normal** or **Expedited**) then click **Next**.
|
||||
|
||||

|
||||
|
||||
14. Verify the configuration, then click **Next**.
|
||||
|
||||

|
||||
|
||||
15. Click **Close** when the Wizard completes.
|
||||
|
||||
16. In the System Center Configuration Manager console, right-click the Microsoft Defender ATP policy you just created and select **Deploy**.
|
||||
|
||||

|
||||
|
||||
17. On the right panel, select the previously created collection and click **OK**.
|
||||
|
||||

|
||||
|
||||
|
||||
### Previous versions of Windows Client (Windows 7 and Windows 8.1)
|
||||
Follow the steps below to identify the Microsoft Defender ATP Workspace ID and Workspace Key, that will be required for the onboarding of previous versions of Windows.
|
||||
|
||||
1. From a Microsoft Defender Security Center Portal, select **Settings > Onboarding**.
|
||||
|
||||
2. Under operating system choose **Windows 7 SP1 and 8.1**.
|
||||
|
||||

|
||||
|
||||
3. Copy the **Workspace ID** and **Workspace Key** and save them. They will be used later in the process.
|
||||
|
||||
Before the systems can be onboarded into the workspace, the deployment scripts need to be updated to contain the correct information. Failure to do so will result in the systems not being properly onboarded. Depending on the deployment method, this step may have already been completed.
|
||||
|
||||
Edit the InstallMMA.cmd with a text editor, such as notepad and update the
|
||||
following lines and save the file:
|
||||
|
||||

|
||||
|
||||
Edit the ConfiguerOMSAgent.vbs with a text editor, such as notepad, and update the following lines and save the file:
|
||||
|
||||

|
||||
|
||||
Microsoft Monitoring Agent (MMA) is currently (as of January 2019) supported on the following Windows Operating
|
||||
Systems:
|
||||
|
||||
- Server SKUs: Windows Server 2008 SP1 or Newer
|
||||
|
||||
- Client SKUs: Windows 7 SP1 and later
|
||||
|
||||
The MMA agent will need to be installed on Windows devices. To install the
|
||||
agent, some systems will need to download the [Update for customer experience
|
||||
and diagnostic
|
||||
telemetry](https://support.microsoft.com/help/3080149/update-for-customer-experience-and-diagnostic-telemetry)
|
||||
in order to collect the data with MMA. These system versions include but may not
|
||||
be limited to:
|
||||
|
||||
- Windows 8.1
|
||||
|
||||
- Windows 7
|
||||
|
||||
- Windows Server 2016
|
||||
|
||||
- Windows Server 2012 R2
|
||||
|
||||
- Windows Server 2008 R2
|
||||
|
||||
Specifically, for Windows 7 SP1, the following patches must be installed:
|
||||
|
||||
- Install
|
||||
[KB4074598](https://support.microsoft.com/help/4074598/windows-7-update-kb4074598)
|
||||
|
||||
- Install either [.NET Framework
|
||||
4.5](https://www.microsoft.com/en-us/download/details.aspx?id=30653) (or
|
||||
later) **or**
|
||||
[KB3154518](https://support.microsoft.com/help/3154518/support-for-tls-system-default-versions-included-in-the-net-framework).
|
||||
Do not install both on the same system.
|
||||
|
||||
To deploy the MMA with System Center Configuration Manager, follow the steps
|
||||
below to utilize the provided batch files to onboard the systems. The CMD file
|
||||
when executed, will require the system to copy files from a network share by the
|
||||
System, the System will install MMA, Install the DependencyAgent, and configure
|
||||
MMA for enrollment into the workspace.
|
||||
|
||||
|
||||
1. In System Center Configuration Manager console, navigate to **Software
|
||||
Library**.
|
||||
|
||||
2. Expand **Application Management**.
|
||||
|
||||
3. Right-click **Packages** then select **Create Package**.
|
||||
|
||||
4. Provide a Name for the package, then click **Next**
|
||||
|
||||

|
||||
|
||||
5. Verify **Standard Program** is selected.
|
||||
|
||||

|
||||
|
||||
6. Click **Next**.
|
||||
|
||||

|
||||
|
||||
7. Enter a program name.
|
||||
|
||||
8. Browse to the location of the InstallMMA.cmd.
|
||||
|
||||
9. Set Run to **Hidden**.
|
||||
|
||||
10. Set **Program can run** to **Whether or not a user is logged on**.
|
||||
|
||||
11. Click **Next**.
|
||||
|
||||
12. Set the **Maximum allowed run time** to 720.
|
||||
|
||||
13. Click **Next**.
|
||||
|
||||

|
||||
|
||||
14. Verify the configuration, then click **Next**.
|
||||
|
||||

|
||||
|
||||
15. Click **Next**.
|
||||
|
||||
16. Click **Close**.
|
||||
|
||||
17. In the System Center Configuration Manager console, right-click the Microsoft Defender ATP
|
||||
Onboarding Package just created and select **Deploy**.
|
||||
|
||||
18. On the right panel select the appropriate collection.
|
||||
|
||||
19. Click **OK**.
|
||||
|
||||
## Next generation protection
|
||||
Microsoft Defender Antivirus is a built-in antimalware solution that provides next generation protection for desktops, portable computers, and servers.
|
||||
|
||||
1. In the System Center Configuration Manager console, navigate to **Assets and Compliance \> Overview \> Endpoint Protection \> Antimalware Polices** and choose **Create Antimalware Policy**.
|
||||
|
||||

|
||||
|
||||
2. Select **Scheduled scans**, **Scan settings**, **Default actions**, **Real-time protection**, **Exclusion settings**, **Advanced**, **Threat overrides**, **Cloud Protection Service** and **Security intelligence updates** and choose **OK**.
|
||||
|
||||

|
||||
|
||||
In certain industries or some select enterprise customers might have specific
|
||||
needs on how Antivirus is configured.
|
||||
|
||||
|
||||
[Quick scan versus full scan and custom scan](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/scheduled-catch-up-scans-windows-defender-antivirus#quick-scan-versus-full-scan-and-custom-scan)
|
||||
|
||||
For more details, see [Windows Security configuration framework](https://docs.microsoft.com/windows/security/threat-protection/windows-security-configuration-framework/windows-security-configuration-framework)
|
||||
|
||||
|
||||

|
||||
|
||||

|
||||
|
||||

|
||||
|
||||

|
||||
|
||||

|
||||
|
||||

|
||||
|
||||

|
||||
|
||||

|
||||
|
||||
3. Right-click on the newly created antimalware policy and select **Deploy** .
|
||||
|
||||

|
||||
|
||||
4. Target the new antimalware policy to your Windows 10 collection and click **OK**.
|
||||
|
||||

|
||||
|
||||
After completing this task, you now have successfully configured Windows
|
||||
Defender Antivirus.
|
||||
|
||||
## Attack Surface Reduction
|
||||
The attack surface reduction pillar of Microsoft Defender ATP includes the feature set that is available under Exploit Guard. Attack surface reduction (ASR) rules, Controlled Folder Access, Network Protection and Exploit
|
||||
Protection. All these features provide an audit mode and a block mode. In audit mode there is no end user impact all it does is collect additional telemetry and make it available in the Microsoft Defender Security Center. The goal with a deployment is to step by step move security controls into block mode.
|
||||
|
||||
To set ASR rules in Audit mode:
|
||||
|
||||
1. In the System Center Configuration Manager console, navigate to **Assets and Compliance \> Overview \> Endpoint Protection \> Windows Defender Exploit Guard** and choose **Create Exploit Guard Policy**.
|
||||
|
||||

|
||||
|
||||
|
||||
2. Select **Attack Surface Reduction**.
|
||||
|
||||
|
||||
3. Set rules to **Audit** and click **Next**.
|
||||
|
||||

|
||||
|
||||
4. Confirm the new Exploit Guard policy by clicking on **Next**.
|
||||
|
||||

|
||||
|
||||
|
||||
5. Once the policy is created click **Close**.
|
||||
|
||||

|
||||
|
||||
|
||||
|
||||
6. Right-click on the newly created policy and choose **Deploy**.
|
||||
|
||||

|
||||
|
||||
7. Target the policy to the newly created Windows 10 collection and click **OK**.
|
||||
|
||||

|
||||
|
||||
After completing this task, you now have successfully configured ASR rules in audit mode.
|
||||
|
||||
Below are additional steps to verify whether ASR rules are correctly applied to
|
||||
endpoints. (This may take few minutes)
|
||||
|
||||
|
||||
1. From a web browser, navigate to <https://securitycenter.windows.com>.
|
||||
|
||||
2. Select **Configuration management** from left side menu.
|
||||
|
||||

|
||||
|
||||
3. Click **Go to attack surface management** in the Attack surface management panel.
|
||||
|
||||

|
||||
|
||||
4. Click **Configuration** tab in Attack Surface reduction rules reports. It shows ASR rules configuration overview and ASR rules status on each devices.
|
||||
|
||||

|
||||
|
||||
5. Click each device shows configuration details of ASR rules.
|
||||
|
||||

|
||||
|
||||
See [Optimize ASR rule deployment and
|
||||
detections](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-machines-asr) for more details.
|
||||
|
||||
|
||||
### To set Network Protection rules in Audit mode:
|
||||
1. In the System Center Configuration Manager console, navigate to **Assets and Compliance \> Overview \> Endpoint Protection \> Windows Defender Exploit Guard** and choose **Create Exploit Guard Policy**.
|
||||
|
||||

|
||||
|
||||
2. Select **Network protection**.
|
||||
|
||||
3. Set the setting to **Audit** and click **Next**.
|
||||
|
||||

|
||||
|
||||
4. Confirm the new Exploit Guard Policy by clicking **Next**.
|
||||
|
||||

|
||||
|
||||
5. Once the policy is created click on **Close**.
|
||||
|
||||

|
||||
|
||||
6. Right-click on the newly created policy and choose **Deploy**.
|
||||
|
||||

|
||||
|
||||
7. Select the policy to the newly created Windows 10 collection and choose **OK**.
|
||||
|
||||

|
||||
|
||||
After completing this task, you now have successfully configured Network
|
||||
Protection in audit mode.
|
||||
|
||||
### To set Controlled Folder Access rules in Audit mode:
|
||||
|
||||
1. In the System Center Configuration Manager console, navigate to **Assets and Compliance \> Overview \> Endpoint Protection \> Windows Defender Exploit Guard** and choose **Create Exploit Guard Policy**.
|
||||
|
||||

|
||||
|
||||
2. Select **Controlled folder access**.
|
||||
|
||||
3. Set the configuration to **Audit** and click **Next**.
|
||||
|
||||

|
||||
|
||||
4. Confirm the new Exploit Guard Policy by clicking on **Next**.
|
||||
|
||||

|
||||
|
||||
5. Once the policy is created click on **Close**.
|
||||
|
||||

|
||||
|
||||
6. Right-click on the newly created policy and choose **Deploy**.
|
||||
|
||||

|
||||
|
||||
7. Target the policy to the newly created Windows 10 collection and click **OK**.
|
||||
|
||||

|
||||
|
||||
After completing this task, you now have successfully configured Controlled folder access in audit mode.
|
||||
|
@ -174,7 +174,7 @@ DeviceTvmSoftwareInventoryVulnerabilities
|
||||
| where IsExploitAvailable == 1 and CvssScore >= 7
|
||||
| summarize NumOfVulnerabilities=dcount(CveId),
|
||||
DeviceName=any(DeviceName) by DeviceId
|
||||
| join kind =inner(AlertEvents) on DeviceId
|
||||
| join kind =inner(DeviceAlertEvents) on DeviceId
|
||||
| summarize NumOfVulnerabilities=any(NumOfVulnerabilities),
|
||||
DeviceName=any(DeviceName) by DeviceId, AlertId
|
||||
| project DeviceName, NumOfVulnerabilities, AlertId
|
||||
|
@ -34,6 +34,9 @@ You can use the Threat & Vulnerability Management capability in [Microsoft Defen
|
||||
- Select remediation options, triage and track the remediation tasks
|
||||
- Select exception options and track active exceptions
|
||||
|
||||
> [!NOTE]
|
||||
> Machines that are not active in the last 30 days are not factored in on the data that reflects your organization's Threat & Vulnerability Management exposure score and configuration score.
|
||||
|
||||
## Threat & Vulnerability Management in Microsoft Defender Security Center
|
||||
When you open the portal, you’ll see the main areas of the capability:
|
||||
|
||||
@ -66,9 +69,6 @@ Area | Description
|
||||
**Top remediation activities** | Track the remediation activities generated from the security recommendations. You can click each item on the list to see the details in the **Remediation** page or click **Show more** to see the rest of the remediation activities, and active exceptions.
|
||||
**Top exposed machines** | See the exposed machine names and their exposure level. You can click each machine name from the list and it will take you to the machine page where you can view the alerts, risks, incidents, security recommendations, installed software, discovered vulnerabilities associated with the exposed machines. You can also do other EDR-related tasks in it, such as: manage tags, initiate automated investigations, initiate a live response session, collect an investigation package, run antivirus scan, restrict app execution, and isolate machine. You can also click **Show more** to see the rest of the exposed machines list.
|
||||
|
||||
> [!NOTE]
|
||||
> Machines with no alerts seen in the last 30 days do not count towards the exposure score of Threat & Vulnerability Management.
|
||||
|
||||
See [Microsoft Defender ATP icons](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/portal-overview-windows-defender-advanced-threat-protection#windows-defender-atp-icons) for more information on the icons used throughout the portal.
|
||||
|
||||
## Related topics
|
||||
|
@ -47,18 +47,19 @@ You can access the security recommendation from the Microsoft Defender ATP Threa
|
||||
*Security recommendations option from the left navigation menu*
|
||||
|
||||
1. Go to the Threat & Vulnerability Management navigation menu and select **Security recommendations** to open up the list of security recommendations for the threats and vulnerabilities found in your organization. It gives you an overview of the security recommendation context: weaknesses found, related components, the application and operating system where the threat or vulnerabilities were found, network, accounts, and security controls, associated breach, threats, and recommendation insights, exposed machine trends, status, remediation type and activities.
|
||||

|
||||

|
||||
|
||||
>[!NOTE]
|
||||
> The color of the **Exposed machines** graph changes as the trend changes. If the number of exposed machines is on the rise, the color changes into red. If there's a decrease in the amount of exposed machines, the color of the graph will change into green. This happens when the numbers on the right hand side is greater than what’s on the left, which means an increase or decrease at the end of even a single machine will change the graph's color.
|
||||
|
||||
You can filter your view based on related components, status, and remediation type. If you want to see the remediation activities of software and software versions which have reached their end-of-life, select **Active**, then select **Software update** from the **Remediation Type** filter, and click **Apply**.
|
||||
<br></br>
|
||||
<br></br>
|
||||
|
||||
2. Select the security recommendation that you need to investigate or process.
|
||||
<br></br>
|
||||
<br></br>
|
||||
|
||||
*Top security recommendations from the dashboard*
|
||||
|
||||
*Top security recommendations from the dashboard*
|
||||
|
||||
In a given day as a Security Administrator, you can take a look at the dashboard to see your exposure score side-by-side with your configuration score. The goal is to lower down your organization's exposure from vulnerabilities, and increase your organization's security configuration to be more resilient against cybersecurity threat attacks. The top security recommendations list can help you achieve that goal.
|
||||
|
||||
@ -81,12 +82,12 @@ You can report a false positive when you see any vague, inaccurate, incomplete,
|
||||
1. Select the **Security recommendation** tab.
|
||||
|
||||
2. Click **:** beside the security recommendation that you want to report about, then select **Report inaccuracy**.
|
||||

|
||||

|
||||
<br>A flyout pane opens.</br>
|
||||

|
||||

|
||||
|
||||
3. From the flyout pane, select the inaccuracy category from the drop-down menu.
|
||||
<br></br>
|
||||
<br></br>
|
||||
|
||||
4. Include your email address so Microsoft can send you feedback regarding the inaccuracy you reported.
|
||||
|
||||
|
@ -43,6 +43,11 @@ The following steps guide you on how to create roles in Microsoft Defender Secur
|
||||
|
||||
- **Alerts investigation** - Users can manage alerts, initiate automated investigations, collect investigation packages, manage machine tags, and export machine timeline.
|
||||
- **Active remediation actions** - Users can take response actions and approve or dismiss pending remediation actions.
|
||||
- Security operations - Take response actions
|
||||
- Approve or dismiss pending remediation actions
|
||||
- Manage allowed/blocked lists for automation
|
||||
- Manage allowed/blocked create Indicators
|
||||
|
||||
>[!NOTE]
|
||||
>To enable your Security operation personnel to choose remediation options and file exceptions, select **Threat and vulnerability management - Remediation handling**, and **Threat and vulnerability management - Exception handling**.
|
||||
|
||||
|
@ -99,6 +99,7 @@ Over time, new ways to manage security policy settings have been introduced, whi
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
## <a href="" id="bkmk-secpol"></a>Using the Local Security Policy snap-in
|
||||
|
||||
@ -135,7 +136,7 @@ The Security Compliance Manager is a downloadable tool that helps you plan, depl
|
||||
|
||||
**To administer security policies by using the Security Compliance Manager**
|
||||
|
||||
1. Download the most recent version. You can find out more info on the [Microsoft Security Guidance](http://blogs.technet.com/b/secguide/) blog.
|
||||
1. Download the most recent version. You can find out more info on the [Microsoft Security Guidance](https://blogs.technet.com/b/secguide/) blog.
|
||||
2. Read the relevant security baseline documentation that is included in this tool.
|
||||
3. Download and import the relevant security baselines. The installation process steps you through baseline selection.
|
||||
4. Open the Help and follow instructions how to customize, compare, or merge your security baselines before deploying those baselines.
|
||||
@ -208,6 +209,7 @@ The following table lists the features of the Security Configuration Manager.
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
### <a href="" id="bkmk-seccfgana"></a>Security Configuration and Analysis
|
||||
|
||||
|
@ -19,7 +19,7 @@ ms.date: 04/19/2017
|
||||
# Interactive logon: Do not require CTRL+ALT+DEL
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 10
|
||||
|
||||
Describes the best practices, location, values, and security considerations for the **Interactive logon: Do not require CTRL+ALT+DEL** security policy setting.
|
||||
|
||||
@ -27,7 +27,7 @@ Describes the best practices, location, values, and security considerations for
|
||||
|
||||
This security setting determines whether pressing CTRL+ALT+DEL is required before a user can log on.
|
||||
|
||||
If this policy setting is enabled on a device, a user is not required to press CTRL+ALT+DEL to log on. Not having to press CTRL+ALT+DEL leaves users susceptible to attacks that attempt to intercept the users' passwords. Requiring CTRL+ALT+DEL before users log on ensures that users are communicating by means of a trusted path when entering their passwords.
|
||||
If this policy setting is enabled on a device, a user is not required to press CTRL+ALT+DEL to log on.
|
||||
|
||||
If this policy is disabled, any user is required to press CTRL+ALT+DEL before logging on to the Windows operating system (unless they are using a smart card for logon).
|
||||
|
||||
@ -37,13 +37,13 @@ A malicious user might install malware that looks like the standard logon dialog
|
||||
|
||||
### Possible values
|
||||
|
||||
- Enabled
|
||||
- Disabled
|
||||
- Not defined
|
||||
- Enabled
|
||||
- Disabled
|
||||
- Not defined
|
||||
|
||||
### Best practices
|
||||
|
||||
- It is advisable to set **Disable CTRL+ALT+DEL requirement for logon** to **Not configured**.
|
||||
- It is advisable to set **Disable CTRL+ALT+DEL requirement for logon** to **Not configured**.
|
||||
|
||||
### Location
|
||||
|
||||
|
@ -23,11 +23,11 @@ manager: dansimp
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
This topic describes how to collect diagnostic data that can be used by Microsoft support and engineering teams to help troubleshoot issues you may encounter when using the Windows Defender AV Assessment section in the Update Compliance add-in.
|
||||
This article describes how to collect diagnostic data that can be used by Microsoft support and engineering teams to help troubleshoot issues you may encounter when using the Windows Defender AV Assessment section in the Update Compliance add-in.
|
||||
|
||||
Before attempting this process, ensure you have read [Troubleshoot Windows Defender Antivirus reporting](troubleshoot-reporting.md), met all require prerequisites, and taken any other suggested troubleshooting steps.
|
||||
|
||||
On at least two endpoints that are not reporting or showing up in Update Compliance, obtain the .cab diagnostic file by following this process:
|
||||
On at least two devices that are not reporting or showing up in Update Compliance, obtain the .cab diagnostic file by taking the following steps:
|
||||
|
||||
1. Open an administrator-level version of the command prompt as follows:
|
||||
|
||||
@ -37,19 +37,15 @@ On at least two endpoints that are not reporting or showing up in Update Complia
|
||||
|
||||
c. Enter administrator credentials or approve the prompt.
|
||||
|
||||
2. Navigate to the Windows Defender directory. By default, this is C:\Program Files\Windows Defender, as in the following example:
|
||||
2. Navigate to the Windows Defender directory. By default, this is `C:\Program Files\Windows Defender`.
|
||||
|
||||
```Dos
|
||||
cd c:\program files\windows\defender
|
||||
```
|
||||
|
||||
3. Enter the following command and press **Enter**
|
||||
3. Type the following command, and then press **Enter**
|
||||
|
||||
```Dos
|
||||
mpcmdrun -getfiles
|
||||
```
|
||||
|
||||
4. A .cab file will be generated that contains various diagnostic logs. The location of the file will be specified in the output in the command prompt, but by default it will be in C:\ProgramData\Microsoft\Windows Defender\Support\MpSupportFiles.cab.
|
||||
4. A .cab file will be generated that contains various diagnostic logs. The location of the file will be specified in the output in the command prompt. By default, the location is `C:\ProgramData\Microsoft\Windows Defender\Support\MpSupportFiles.cab`.
|
||||
|
||||
5. Copy these .cab files to a location that can be accessed by Microsoft support. An example could be a password-protected OneDrive folder that you can share with us.
|
||||
|
||||
|