mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-19 04:13:41 +00:00
Merge branch 'master' into repo_sync_working_branch
This commit is contained in:
@ -456,4 +456,4 @@ To view endpoints for non-Enterprise Windows 10 editions, see:
|
||||
## Related links
|
||||
|
||||
- [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US)
|
||||
- [Network infrastructure requirements for Microsoft Intune](https://docs.microsoft.com/intune/get-started/network-infrastructure-requirements-for-microsoft-intune)
|
||||
- [Network infrastructure requirements for Microsoft Intune](https://docs.microsoft.com/mem/intune/fundamentals/intune-endpoints)
|
||||
|
@ -461,4 +461,4 @@ To view endpoints for non-Enterprise Windows 10 editions, see:
|
||||
## Related links
|
||||
|
||||
- [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US)
|
||||
- [Network infrastructure requirements for Microsoft Intune](https://docs.microsoft.com/intune/get-started/network-infrastructure-requirements-for-microsoft-intune)
|
||||
- [Network infrastructure requirements for Microsoft Intune](https://docs.microsoft.com/mem/intune/fundamentals/intune-endpoints)
|
||||
|
@ -187,6 +187,6 @@ To view endpoints for non-Enterprise Windows 10 editions, see:
|
||||
## Related links
|
||||
|
||||
- [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US)
|
||||
- [Network infrastructure requirements for Microsoft Intune](https://docs.microsoft.com/intune/get-started/network-infrastructure-requirements-for-microsoft-intune)
|
||||
- [Network infrastructure requirements for Microsoft Intune](https://docs.microsoft.com/mem/intune/fundamentals/intune-endpoints)
|
||||
|
||||
|
||||
|
@ -138,4 +138,4 @@ To view endpoints for non-Enterprise Windows 10 editions, see:
|
||||
## Related links
|
||||
|
||||
- [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US)
|
||||
- [Network infrastructure requirements for Microsoft Intune](https://docs.microsoft.com/intune/get-started/network-infrastructure-requirements-for-microsoft-intune)
|
||||
- [Network infrastructure requirements for Microsoft Intune](https://docs.microsoft.com/mem/intune/fundamentals/intune-endpoints)
|
||||
|
@ -137,4 +137,4 @@ To view endpoints for non-Enterprise Windows 10 editions, see:
|
||||
## Related links
|
||||
|
||||
- [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US)
|
||||
- [Network infrastructure requirements for Microsoft Intune](https://docs.microsoft.com/intune/get-started/network-infrastructure-requirements-for-microsoft-intune)
|
||||
- [Network infrastructure requirements for Microsoft Intune](https://docs.microsoft.com/mem/intune/fundamentals/intune-endpoints)
|
||||
|
@ -32,7 +32,7 @@ In a mobile-first, cloud-first world, Azure Active Directory enables single sign
|
||||
To improve productivity, Azure Active Directory provides your users with a broad range of options to access your corporate assets. With application access management, Azure Active Directory enables you to ensure that only the right people can access your applications. What if you want to have more control over how the right people are accessing your resources under certain conditions? What if you even have conditions under which you want to block access to certain applications even for the right people? For example, it might be OK for you if the right people are accessing certain applications from a trusted network; however, you might not want them to access these applications from a network you don't trust. You can address these questions using conditional access.
|
||||
|
||||
> [!NOTE]
|
||||
> For more details about the way Windows Hello for Business interacts with Azure Multi Factor Authentication and Conditional Access, see [this article](https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/why-are-my-users-not-prompted-for-mfa-as-expected/ba-p/1449032).
|
||||
> For more details about the way Windows Hello for Business interacts with Azure AD Multi-Factor Authentication and Conditional Access, see [this article](https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/why-are-my-users-not-prompted-for-mfa-as-expected/ba-p/1449032).
|
||||
|
||||
Read [Conditional access in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-azure-portal) to learn more about Conditional Access. Afterwards, read [Getting started with conditional access in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-azure-portal-get-started) to start deploying Conditional access.
|
||||
|
||||
|
@ -100,12 +100,12 @@ The next step of the deployment is to follow the [Creating an Azure AD tenant](h
|
||||
## Multifactor Authentication Services
|
||||
Windows Hello for Business uses multi-factor authentication during provisioning and during user initiated PIN reset scenarios, such as when a user forgets their PIN. There are two preferred multi-factor authentication configurations with hybrid deployments—Azure MFA and AD FS using Azure MFA
|
||||
|
||||
Review the [What is Azure Multi-Factor Authentication](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication) topic to familiarize yourself its purpose and how it works.
|
||||
Review the [What is Azure AD Multi-Factor Authentication](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication) topic to familiarize yourself its purpose and how it works.
|
||||
|
||||
### Azure Multi-Factor Authentication (MFA) Cloud ###
|
||||
### Azure AD Multi-Factor Authentication (MFA) Cloud ###
|
||||
> [!IMPORTANT]
|
||||
> As long as your users have licenses that include Azure Multi-Factor Authentication, there's nothing that you need to do to turn on Azure MFA. You can start requiring two-step verification on an individual user basis. The licenses that enable Azure MFA are:
|
||||
> * Azure Multi-Factor Authentication
|
||||
> As long as your users have licenses that include Azure AD Multi-Factor Authentication, there's nothing that you need to do to turn on Azure MFA. You can start requiring two-step verification on an individual user basis. The licenses that enable Azure MFA are:
|
||||
> * Azure AD Multi-Factor Authentication
|
||||
> * Azure Active Directory Premium
|
||||
> * Enterprise Mobility + Security
|
||||
>
|
||||
@ -115,7 +115,7 @@ Review the [What is Azure Multi-Factor Authentication](https://docs.microsoft.co
|
||||
If your organization uses Azure MFA on a per-consumption model (no licenses), then review the [Create a Multifactor Authentication Provider](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication-get-started-auth-provider) section to create an Azure MFA Authentication provider and associate it with your Azure tenant.
|
||||
|
||||
#### Configure Azure MFA Settings ####
|
||||
Once you have created your Azure MFA authentication provider and associated it with an Azure tenant, you need to configure the multi-factor authentication settings. Review the [Configure Azure Multi-Factor Authentication settings](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication-whats-next) section to configure your settings.
|
||||
Once you have created your Azure MFA authentication provider and associated it with an Azure tenant, you need to configure the multi-factor authentication settings. Review the [Configure Azure AD Multi-Factor Authentication settings](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication-whats-next) section to configure your settings.
|
||||
|
||||
#### Azure MFA User States ####
|
||||
After you have completed configuring your Azure MFA settings, you want to review configure [User States](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication-get-started-user-states) to understand user states. User states determine how you enable Azure MFA for your users.
|
||||
@ -126,12 +126,12 @@ Alternatively, you can configure Windows Server 2016 Active Directory Federation
|
||||
### Section Review
|
||||
|
||||
> [!div class="checklist"]
|
||||
> * Review the overview and uses of Azure Multifactor Authentication.
|
||||
> * Review your Azure Active Directory subscription for Azure Multifactor Authentication.
|
||||
> * Create an Azure Multifactor Authentication Provider, if necessary.
|
||||
> * Configure Azure Multifactor Authentication features and settings.
|
||||
> * Understand the different User States and their effect on Azure Multifactor Authentication.
|
||||
> * Consider using Azure Multifactor Authentication or a third-party multifactor authentication provider with Windows Server 2016 Active Directory Federation Services, if necessary.
|
||||
> * Review the overview and uses of Azure AD Multi-Factor Authentication.
|
||||
> * Review your Azure Active Directory subscription for Azure AD Multi-Factor Authentication.
|
||||
> * Create an Azure AD Multi-Factor Authentication Provider, if necessary.
|
||||
> * Configure Azure AD Multi-Factor Authentication features and settings.
|
||||
> * Understand the different User States and their effect on Azure AD Multi-Factor Authentication Authentication.
|
||||
> * Consider using Azure AD Multi-Factor Authentication Authentication or a third-party multifactor authentication provider with Windows Server 2016 Active Directory Federation Services, if necessary.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Configure Azure Device Registration](hello-hybrid-cert-trust-devreg.md)
|
||||
|
@ -110,13 +110,13 @@ The next step of the deployment is to follow the [Creating an Azure AD tenant](h
|
||||
## Multifactor Authentication Services
|
||||
Windows Hello for Business uses multifactor authentication during provisioning and during user initiated PIN reset scenarios, such as when a user forgets their PIN. There are two preferred multifactor authentication configurations with hybrid deployments—Azure MFA and AD FS using Azure MFA or a third-party MFA adapter
|
||||
|
||||
Review the [What is Azure Multi-Factor Authentication](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication) topic to familiarize yourself its purpose and how it works.
|
||||
Review the [What is Azure AD Multi-Factor Authentication](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication) topic to familiarize yourself its purpose and how it works.
|
||||
|
||||
### Azure Multi-Factor Authentication (MFA) Cloud
|
||||
### Azure AD Multi-Factor Authentication Authentication (MFA) Cloud
|
||||
|
||||
> [!IMPORTANT]
|
||||
> As long as your users have licenses that include Azure Multi-Factor Authentication, there's nothing that you need to do to turn on Azure MFA. You can start requiring two-step verification on an individual user basis. The licenses that enable Azure MFA are:
|
||||
> * Azure Multi-Factor Authentication
|
||||
> As long as your users have licenses that include Azure AD Multi-Factor Authentication, there's nothing that you need to do to turn on Azure MFA. You can start requiring two-step verification on an individual user basis. The licenses that enable Azure MFA are:
|
||||
> * Azure AD Multi-Factor Authentication
|
||||
> * Azure Active Directory Premium
|
||||
> * Enterprise Mobility + Security
|
||||
>
|
||||
@ -124,7 +124,7 @@ Review the [What is Azure Multi-Factor Authentication](https://docs.microsoft.co
|
||||
|
||||
|
||||
#### Configure Azure MFA Settings
|
||||
Review the [Configure Azure Multi-Factor Authentication settings](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication-whats-next) section to configure your settings.
|
||||
Review the [Configure Azure AD Multi-Factor Authentication settings](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication-whats-next) section to configure your settings.
|
||||
|
||||
#### Azure MFA User States
|
||||
After you have completed configuring your Azure MFA settings, you want to review [How to require two-step verification for a user](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication-get-started-user-states) to understand user states. User states determine how you enable Azure MFA for your users.
|
||||
@ -135,12 +135,12 @@ Alternatively, you can configure Windows Server 2016 Active Directory Federation
|
||||
### Section Review
|
||||
|
||||
> [!div class="checklist"]
|
||||
> * Review the overview and uses of Azure Multifactor Authentication.
|
||||
> * Review your Azure Active Directory subscription for Azure Multifactor Authentication.
|
||||
> * Create an Azure Multifactor Authentication Provider, if necessary.
|
||||
> * Configure Azure Multifactor Authentication features and settings.
|
||||
> * Understand the different User States and their effect on Azure Multifactor Authentication.
|
||||
> * Consider using Azure Multifactor Authentication or a third-party multifactor authentication provider with Windows Server Active Directory Federation Services, if necessary.
|
||||
> * Review the overview and uses of Azure AD Multi-Factor Authentication.
|
||||
> * Review your Azure Active Directory subscription for Azure AD Multi-Factor Authentication.
|
||||
> * Create an Azure AD Multi-Factor Authentication Provider, if necessary.
|
||||
> * Configure Azure AD Multi-Factor Authentication features and settings.
|
||||
> * Understand the different User States and their effect on Azure AD Multi-Factor Authentication.
|
||||
> * Consider using Azure AD Multi-Factor Authentication or a third-party multifactor authentication provider with Windows Server Active Directory Federation Services, if necessary.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Configure Azure Device Registration](hello-hybrid-key-trust-devreg.md)
|
||||
|
@ -33,6 +33,7 @@ Windows Hello addresses the following problems with passwords:
|
||||
> | | | |
|
||||
> | :---: | :---: | :---: |
|
||||
> | [](hello-overview.md)</br>[Overview](hello-overview.md) | [](hello-why-pin-is-better-than-password.md)</br>[Why PIN is better than a password](hello-why-pin-is-better-than-password.md) | [](hello-manage-in-organization.md)</br>[Manage Windows Hello in your Organization](hello-manage-in-organization.md) |
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@ -41,7 +42,7 @@ Windows Hello addresses the following problems with passwords:
|
||||
* Windows 10, version 1511 or later
|
||||
* Microsoft Azure Account
|
||||
* Azure Active Directory
|
||||
* Azure Multi-factor authentication
|
||||
* Azure AD Multi-Factor Authentication
|
||||
* Modern Management (Intune or supported third-party MDM), *optional*
|
||||
* Azure AD Premium subscription - *optional*, needed for automatic MDM enrollment when the device joins Azure Active Directory
|
||||
|
||||
|
@ -19,7 +19,7 @@ ms.reviewer:
|
||||
# Validate and Deploy Multi-factor Authentication (MFA)
|
||||
|
||||
> [!IMPORTANT]
|
||||
> As of July 1, 2019, Microsoft will no longer offer MFA Server for new deployments. New customers who would like to require multi-factor authentication from their users should use cloud-based Azure Multi-Factor Authentication. Existing customers who have activated MFA Server prior to July 1 will be able to download the latest version, future updates and generate activation credentials as usual.
|
||||
> As of July 1, 2019, Microsoft will no longer offer MFA Server for new deployments. New customers who would like to require multi-factor authentication from their users should use cloud-based Azure AD Multi-Factor Authentication. Existing customers who have activated MFA Server prior to July 1 will be able to download the latest version, future updates and generate activation credentials as usual.
|
||||
|
||||
**Applies to**
|
||||
|
||||
|
@ -106,13 +106,13 @@ The built-in Windows Hello for Business provisioning experience creates a hardwa
|
||||
#### Multifactor authentication
|
||||
|
||||
> [!IMPORTANT]
|
||||
> As of July 1, 2019, Microsoft will no longer offer MFA Server for new deployments. New customers who require multi-factor authentication for their users should use cloud-based Azure Multi-Factor Authentication. Existing customers who have activated MFA Server prior to July 1, 2019 will be able to download the latest version, future updates and generate activation credentials as usual. See [Getting started with the Azure Multi-Factor Authentication Server](https://docs.microsoft.com/azure/active-directory/authentication/howto-mfaserver-deploy) for more details.
|
||||
> As of July 1, 2019, Microsoft will no longer offer MFA Server for new deployments. New customers who require multi-factor authentication for their users should use cloud-based Azure AD Multi-Factor Authentication. Existing customers who have activated MFA Server prior to July 1, 2019 will be able to download the latest version, future updates and generate activation credentials as usual. See [Getting started with the Azure AD Multi-Factor Authentication Server](https://docs.microsoft.com/azure/active-directory/authentication/howto-mfaserver-deploy) for more details.
|
||||
|
||||
The goal of Windows Hello for Business is to move organizations away from passwords by providing them a strong credential that provides easy two-factor authentication. The built-in provisioning experience accepts the user's weak credentials (username and password) as the first factor authentication; however, the user must provide a second factor of authentication before Windows provisions a strong credential.
|
||||
|
||||
Cloud only and hybrid deployments provide many choices for multi-factor authentication. On-premises deployments must use a multi-factor authentication that provides an AD FS multi-factor adapter to be used in conjunction with the on-premises Windows Server 2016 AD FS server role. Organizations can use the on-premises Azure Multi-factor Authentication server, or choose from several third parties (Read [Microsoft and third-party additional authentication methods](https://docs.microsoft.com/windows-server/identity/ad-fs/operations/configure-additional-authentication-methods-for-ad-fs#microsoft-and-third-party-additional-authentication-methods) for more information).
|
||||
Cloud only and hybrid deployments provide many choices for multi-factor authentication. On-premises deployments must use a multi-factor authentication that provides an AD FS multi-factor adapter to be used in conjunction with the on-premises Windows Server 2016 AD FS server role. Organizations can use the on-premises Azure AD Multi-Factor Authentication server, or choose from several third parties (Read [Microsoft and third-party additional authentication methods](https://docs.microsoft.com/windows-server/identity/ad-fs/operations/configure-additional-authentication-methods-for-ad-fs#microsoft-and-third-party-additional-authentication-methods) for more information).
|
||||
> [!NOTE]
|
||||
> Azure Multi-Factor Authentication is available through:
|
||||
> Azure AD Multi-Factor Authentication is available through:
|
||||
> * Microsoft Enterprise Agreement
|
||||
> * Open Volume License Program
|
||||
> * Cloud Solution Providers program
|
||||
|
@ -106,7 +106,7 @@
|
||||
#### [Device control]()
|
||||
##### [Code integrity](device-guard/enable-virtualization-based-protection-of-code-integrity.md)
|
||||
##### [Control USB devices](device-control/control-usb-devices-using-intune.md)
|
||||
|
||||
##### [Device control report](device-control/device-control-report.md)
|
||||
|
||||
#### [Exploit protection]()
|
||||
##### [Protect devices from exploits](microsoft-defender-atp/exploit-protection.md)
|
||||
@ -298,6 +298,7 @@
|
||||
##### [Set preferences](microsoft-defender-atp/linux-preferences.md)
|
||||
##### [Detect and block Potentially Unwanted Applications](microsoft-defender-atp/linux-pua.md)
|
||||
##### [Schedule scans with Microsoft Defender ATP for Linux](microsoft-defender-atp/linux-schedule-scan-atp.md)
|
||||
##### [Schedule an update of the Microsoft Defender for Endpoint (Linux)](microsoft-defender-atp/linux-update-MDE-Linux.md)
|
||||
|
||||
#### [Troubleshoot]()
|
||||
##### [Troubleshoot installation issues](microsoft-defender-atp/linux-support-install.md)
|
||||
|
@ -0,0 +1,73 @@
|
||||
---
|
||||
title: Protect your organization’s data with device control
|
||||
description: Monitor your organization's data security through device control reports.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
ms.author: v-ajupudi
|
||||
author: alluthewriter
|
||||
ms.reviewer: dansimp
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
---
|
||||
# Protect your organization’s data with device control
|
||||
|
||||
**Applies to:** [Microsoft Defender for Endpoint](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
Microsoft Defender for Endpoint device control protects against data loss, by monitoring and controlling media use by devices in your organization, such as the use of removable storage devices and USB drives.
|
||||
|
||||
With the device control report, you can view events that relate to media usage, such as:
|
||||
|
||||
- **Audit events:** Shows the number of audit events that occur when external media is connected.
|
||||
- **Policy events:** Shows the number of policy events that occur when a device control policy is triggered.
|
||||
|
||||
> [!NOTE]
|
||||
> The audit event to track media usage is enabled by default for devices onboarded to Microsoft Defender for Endpoint.
|
||||
|
||||
## Understanding the audit events
|
||||
|
||||
The audit events include:
|
||||
|
||||
- **USB drive mount and unmount:** Audit events that are generated when a USB drive is mounted or unmounted.
|
||||
- **PnP:** Plug and Play audit events are generated when removable storage, a printer, or Bluetooth media is connected.
|
||||
|
||||
## Monitor device control security
|
||||
|
||||
Device control in Microsoft Defender for Endpoint empowers security administrators with tools that enable them to track their organization’s device control security through reports. You can find the device control report in the Microsoft 365 security center by going to **Reports > Device protection**.
|
||||
|
||||
The Device protection card on the **Reports** dashboard shows the number of audit events generated by media type, over the last 180 days.
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
|
||||
The **View details** button shows more media usage data in the **device control report** page.
|
||||
|
||||
The page provides a dashboard with aggregated number of events per type and a list of events. Administrators can filter on time range, media class name, and device ID.
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
|
||||
When you select an event, a flyout appears that shows you more information:
|
||||
|
||||
- **General details:** Date, Action mode, and the policy of this event.
|
||||
- **Media information:** Media information includes Media name, Class name, Class GUID, Device ID, Vendor ID, Volume, Serial number, and Bus type.
|
||||
- **Location details:** Device name and MDATP device ID.
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
|
||||
To see real-time activity for this media across the organization, select the **Open Advanced hunting** button. This includes an embedded, pre-defined query.
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
|
||||
To see the security of the device, select the **Open device page** button on the flyout. This button opens the device entity page.
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
|
||||
## Reporting delays
|
||||
|
||||
The device control report can have a 12-hour delay from the time a media connection occurs to the time the event is reflected in the card or in the domain list.
|
Binary file not shown.
After Width: | Height: | Size: 139 KiB |
Binary file not shown.
After Width: | Height: | Size: 266 KiB |
Binary file not shown.
After Width: | Height: | Size: 196 KiB |
Binary file not shown.
After Width: | Height: | Size: 94 KiB |
Binary file not shown.
After Width: | Height: | Size: 187 KiB |
@ -55,9 +55,9 @@ DO NOT USE THE APPLICATION.**
|
||||
of this application on Android enabled device or devices that you own
|
||||
or control. You may use this application with your company's valid
|
||||
subscription of Microsoft Defender for Endpoint or
|
||||
an online service that includes MDATP functionalities.
|
||||
an online service that includes Microsoft Defender for Endpoint functionalities.
|
||||
|
||||
2. **Updates.** Updates or upgrades to MDATP may be required for full
|
||||
2. **Updates.** Updates or upgrades to Microsoft Defender for Endpoint may be required for full
|
||||
functionality. Some functionality may not be available in all countries.
|
||||
|
||||
3. **Third-Party Programs.** The application may include third-party
|
||||
|
@ -36,7 +36,7 @@ Retrieves specific [Alert](alerts.md) by its ID.
|
||||
|
||||
|
||||
## Permissions
|
||||
One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Use Microsoft Defender ATP APIs](apis-intro.md)
|
||||
One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Use Microsoft Defender for Endpoint APIs](apis-intro.md)
|
||||
|
||||
Permission type | Permission | Permission display name
|
||||
:---|:---|:---
|
||||
|
@ -36,7 +36,7 @@ Retrieves a collection of [Machines](machine.md) that have communicated to or fr
|
||||
|
||||
|
||||
## Permissions
|
||||
One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Use Microsoft Defender ATP APIs](apis-intro.md)
|
||||
One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Use Microsoft Defender for Endpoint APIs](apis-intro.md)
|
||||
|
||||
Permission type | Permission | Permission display name
|
||||
:---|:---|:---
|
||||
|
@ -27,7 +27,7 @@ ms.topic: article
|
||||
Retrieves a security recommendation by its ID.
|
||||
|
||||
## Permissions
|
||||
One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Use Microsoft Defender ATP APIs](apis-intro.md) for details.
|
||||
One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Use Microsoft Defender for Endpoint APIs](apis-intro.md) for details.
|
||||
|
||||
Permission type | Permission | Permission display name
|
||||
:---|:---|:---
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Become a Microsoft Defender ATP partner
|
||||
title: Become a Microsoft Defender for Endpoint partner
|
||||
ms.reviewer:
|
||||
description: Learn the steps and requirements to integrate your solution with Microsoft Defender ATP and be a partner
|
||||
keywords: partner, integration, solution validation, certification, requirements, member, misa, application portal
|
||||
@ -40,17 +40,23 @@ Once the Microsoft Defender for Endpoint team has reviewed and approves the inte
|
||||
[Microsoft Intelligent Security Association](https://www.microsoft.com/security/partnerships/intelligent-security-association) is a program specifically for Microsoft security partners to help enrich your security products and improve customer discoverability of your integrations to Microsoft security products.
|
||||
|
||||
## Step 4: Get listed in the Microsoft Defender for Endpoint partner application portal
|
||||
Microsoft Defender ATP supports third-party applications discovery and integration using the in-product [partner page](partner-applications.md) that is embedded within the Microsoft Defender for Endpoint management portal.
|
||||
Microsoft Defender for Endpoint supports third-party applications discovery and integration using the in-product [partner page](partner-applications.md) that is embedded within the Microsoft Defender for Endpoint management portal.
|
||||
|
||||
To have your company listed as a partner in the in-product partner page, you will need to provide the following information:
|
||||
|
||||
1. A square logo (SVG).
|
||||
2. Name of the product to be presented.
|
||||
3. Provide a 15-word product description.
|
||||
4. Link to the landing page for the customer to complete the integration or blog post that will include sufficient information for customers. Any press release including the Microsoft Defender ATP product name should be reviewed by the marketing and engineering teams. Wait for at least 10 days for the review process to be done.
|
||||
4. Link to the landing page for the customer to complete the integration or blog post that will include sufficient information for customers. Any press release including the Microsoft Defender for Endpoint product name should be reviewed by the marketing and engineering teams. Wait for at least 10 days for the review process to be done.
|
||||
5. If you use a multi-tenant Azure AD approach, we will need the Azure AD application name to track usage of the application.
|
||||
6. Include the User-Agent field in each API call made to Microsoft Defender for Endpoint public set of APIs or Graph Security APIs. This will be used for statistical purposes, troubleshooting, and partner recognition. In addition, this step is a requirement for membership in Microsoft Intelligent Security Association (MISA).
|
||||
|
||||
Follow these steps:
|
||||
1. Identify a name adhering to the following nomenclature that includes your company name and the Microsoft Defender for Endpoint-integrated product with the version of the product that includes this integration.
|
||||
- ISV Nomenclature: `MdatpPartner-{CompanyName}-{ProductName}/{Version}`
|
||||
- Security partner Nomenclature: `MdatpPartner-{CompanyName}-{ProductName}/{TenantID}`
|
||||
|
||||
|
||||
- Set the User-Agent field in each HTTP request header to the name based on the Following nomenclature.
|
||||
|
||||
- `MsdePartner-{CompanyName}-{ProductName}/{Version}`
|
||||
|
Binary file not shown.
After Width: | Height: | Size: 42 KiB |
@ -68,7 +68,7 @@ rbacGroupNames | String | Comma-separated list of RBAC group names the indicator
|
||||
category | String | Category of the alert. Examples include: Execution and credential access. **Optional**
|
||||
mitretechniques| String | MITRE techniques code/id (comma separated). For more information, see [Enterprise tactics](https://attack.mitre.org/tactics/enterprise/). **Optional** It is recommended to add a value in category when a MITRE technique.
|
||||
|
||||
For more information, see [Microsoft Defender ATP alert categories are now aligned with MITRE ATT&CK!](https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/microsoft-defender-atp-alert-categories-are-now-aligned-with/ba-p/732748).
|
||||
For more information, see [Microsoft Defender for Endpoint alert categories are now aligned with MITRE ATT&CK!](https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/microsoft-defender-atp-alert-categories-are-now-aligned-with/ba-p/732748).
|
||||
|
||||
|
||||
## See also
|
||||
|
@ -143,7 +143,7 @@ To further inspect the event and related events, you can quickly run an [advance
|
||||
|
||||
### Security recommendations
|
||||
|
||||
**Security recommendations** are generated from Microsoft Defender ATP's [Threat & Vulnerability Management](tvm-dashboard-insights.md) capability. Selecting a recommendation will show a panel where you can view relevant details such as description of the recommendation and the potential risks associated with not enacting it. See [Security recommendation](tvm-security-recommendation.md) for details.
|
||||
**Security recommendations** are generated from Microsoft Defender for Endpoint's [Threat & Vulnerability Management](tvm-dashboard-insights.md) capability. Selecting a recommendation will show a panel where you can view relevant details such as description of the recommendation and the potential risks associated with not enacting it. See [Security recommendation](tvm-security-recommendation.md) for details.
|
||||
|
||||

|
||||
|
||||
|
@ -38,7 +38,7 @@ This article describes how to deploy Microsoft Defender for Endpoint for Linux m
|
||||
|
||||
## Prerequisites and system requirements
|
||||
|
||||
Before you get started, see [Microsoft Defender ATP for Linux](microsoft-defender-atp-linux.md) for a description of prerequisites and system requirements for the current software version.
|
||||
Before you get started, see [Microsoft Defender for Endpoint for Linux](microsoft-defender-atp-linux.md) for a description of prerequisites and system requirements for the current software version.
|
||||
|
||||
## Configure the Linux software repository
|
||||
|
||||
|
@ -98,7 +98,7 @@ The following fields are considered common for all events:
|
||||
|
||||
**Required diagnostic data** is the minimum data necessary to help keep Defender for Endpoint secure, up-to-date, and perform as expected on the device it’s installed on.
|
||||
|
||||
Required diagnostic data helps to identify problems with Microsoft Defender ATP that may be related to a device or software configuration. For example, it can help determine if a Defender for Endpoint feature crashes more frequently on a particular operating system version, with newly introduced features, or when certain Defender for Endpoint features are disabled. Required diagnostic data helps Microsoft detect, diagnose, and fix these problems more quickly so the impact to users or organizations is reduced.
|
||||
Required diagnostic data helps to identify problems with Microsoft Defender for Endpoint that may be related to a device or software configuration. For example, it can help determine if a Defender for Endpoint feature crashes more frequently on a particular operating system version, with newly introduced features, or when certain Defender for Endpoint features are disabled. Required diagnostic data helps Microsoft detect, diagnose, and fix these problems more quickly so the impact to users or organizations is reduced.
|
||||
|
||||
#### Software setup and inventory data events
|
||||
|
||||
|
@ -55,7 +55,7 @@ Check if the mdatp service is running:
|
||||
systemctl status mdatp
|
||||
```
|
||||
```Output
|
||||
● mdatp.service - Microsoft Defender ATP
|
||||
● mdatp.service - Microsoft Defender for Endpoint
|
||||
Loaded: loaded (/lib/systemd/system/mdatp.service; enabled; vendor preset: enabled)
|
||||
Active: active (running) since Thu 2020-03-26 10:37:30 IST; 23h ago
|
||||
Main PID: 1966 (wdavdaemon)
|
||||
|
@ -0,0 +1,182 @@
|
||||
---
|
||||
title: How to schedule an update of the Microsoft Defender for Endpoint (Linux)
|
||||
description: Learn how to schedule an update of the Microsoft Defender for Endpoint (Linux) to better protect your organization's assets.
|
||||
keywords: microsoft, defender, atp, linux, scans, antivirus, microsoft defender for endpoint (linux)
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dansimp
|
||||
author: dansimp
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
---
|
||||
|
||||
# Schedule an update of the Microsoft Defender for Endpoint (Linux)
|
||||
|
||||
To run an update on Microsoft Defender for Endpoint for Linux, see [Deploy updates for Microsoft Defender for Endpoint for Linux](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/linux-updates).
|
||||
|
||||
Linux (and Unix) have a tool called **crontab** (similar to Task Scheduler) to be able to run scheduled tasks.
|
||||
|
||||
## Pre-requisite
|
||||
|
||||
> [!NOTE]
|
||||
> To get a list of all the time zones, run the following command:
|
||||
> `timedatectl list-timezones`<br>
|
||||
> Examples for timezones: <br>
|
||||
> - `America/Los_Angeles`
|
||||
> - `America/New_York`
|
||||
> - `America/Chicago`
|
||||
> - `America/Denver`
|
||||
|
||||
## To set the Cron job
|
||||
Use the following commands:
|
||||
|
||||
**To backup crontab entries**
|
||||
|
||||
`sudo crontab -l > /var/tmp/cron_backup_201118.dat`
|
||||
|
||||
> [!NOTE]
|
||||
> Where 201118 == YYMMDD
|
||||
|
||||
> [!TIP]
|
||||
> Do this before you edit or remove. <br>
|
||||
|
||||
To edit the crontab, and add a new job as a root user: <br>
|
||||
`sudo crontab -e`
|
||||
|
||||
> [!NOTE]
|
||||
> The default editor is VIM.
|
||||
|
||||
You might see:
|
||||
|
||||
0****/etc/opt/microsoft/mdatp/logrorate.sh
|
||||
|
||||
And
|
||||
|
||||
02**sat /bin/mdatp scan quick>~/mdatp_cron_job.log
|
||||
|
||||
See [Schedule scans with Microsoft Defender for Endpoint (Linux)](linux-schedule-scan-atp.md)
|
||||
|
||||
Press “Insert”
|
||||
|
||||
Add the following entries:
|
||||
|
||||
CRON_TZ=America/Los_Angeles
|
||||
|
||||
> #!RHEL and variants (CentOS and Oracle Linux)
|
||||
|
||||
`06**sun[$(date +\%d) -le 15] sudo yum update mdatp>>~/mdatp_cron_job.log`
|
||||
|
||||
> #!SLES and variants
|
||||
|
||||
`06**sun[$(date +\%d) -le 15] sudo zypper update mdatp>>~/mdatp_cron_job.log`
|
||||
|
||||
> #!Ubuntu and Debian systems
|
||||
|
||||
`06**sun [$(date +\%d) -le 15] sudo apt-get install --only-upgrade mdatp>>~/mdatp_cron_job.log`
|
||||
|
||||
> [!NOTE]
|
||||
> In the examples above, we are setting it to 00 minutes, 6 a.m.(hour in 24 hour format), any day of the month, any month, on Sundays.[$(date +\%d) -le 15] == Won’t run unless it’s equal or less than the 15th day (3rd week). Meaning it will run every 3rd Sundays(7) of the month at 6:00 a.m. Pacific (UTC -8).
|
||||
|
||||
Press “Esc”
|
||||
|
||||
Type “:wq” w/o the double quotes.
|
||||
|
||||
> [!NOTE]
|
||||
> w == write, q == quit
|
||||
|
||||
To view your cron jobs, type `sudo crontab -l`
|
||||
|
||||
:::image type="content" source="images/update-MDE-linux-4634577.jpg" alt-text="update MDE linux":::
|
||||
|
||||
To inspect cron job runs:
|
||||
`sudo grep mdatp /var/log/cron`
|
||||
|
||||
To inspect the mdatp_cron_job.log
|
||||
`sudo nano mdatp_cron_job.log`
|
||||
|
||||
## For those who use Ansible, Chef, or Puppet
|
||||
|
||||
Use the following commands:
|
||||
### To set cron jobs in Ansible
|
||||
|
||||
`cron – Manage cron.d and crontab entries`
|
||||
|
||||
See [https://docs.ansible.com/ansible/latest/modules/cron_module.html](https://docs.ansible.com/ansible/latest/modules/cron_module.html) for more information.
|
||||
|
||||
### To set crontabs in Chef
|
||||
`cron resource`
|
||||
|
||||
See [https://docs.chef.io/resources/cron/](https://docs.chef.io/resources/cron/) for more information.
|
||||
|
||||
### To set cron jobs in Puppet
|
||||
Resource Type: cron
|
||||
|
||||
See [https://puppet.com/docs/puppet/5.5/types/cron.html](https://puppet.com/docs/puppet/5.5/types/cron.html) for more information.
|
||||
|
||||
Automating with Puppet: Cron jobs and scheduled tasks
|
||||
|
||||
See [https://puppet.com/blog/automating-puppet-cron-jobs-and-scheduled-tasks/](https://puppet.com/blog/automating-puppet-cron-jobs-and-scheduled-tasks/) for more information.
|
||||
|
||||
## Additional information
|
||||
|
||||
**To get help with crontab**
|
||||
|
||||
`man crontab`
|
||||
|
||||
**To get a list of crontab file of the current user**
|
||||
|
||||
`crontab -l`
|
||||
|
||||
**To get a list of crontab file of another user**
|
||||
|
||||
`crontab -u username -l`
|
||||
|
||||
**To backup crontab entries**
|
||||
|
||||
`crontab -l > /var/tmp/cron_backup.dat`
|
||||
|
||||
> [!TIP]
|
||||
> Do this before you edit or remove. <br>
|
||||
|
||||
**To restore crontab entries**
|
||||
|
||||
`crontab /var/tmp/cron_backup.dat`
|
||||
|
||||
**To edit the crontab and add a new job as a root user**
|
||||
|
||||
`sudo crontab -e`
|
||||
|
||||
**To edit the crontab and add a new job**
|
||||
|
||||
`crontab -e`
|
||||
|
||||
**To edit other user’s crontab entries**
|
||||
|
||||
`crontab -u username -e`
|
||||
|
||||
**To remove all crontab entries**
|
||||
|
||||
`crontab -r`
|
||||
|
||||
**To remove other user’s crontab entries**
|
||||
|
||||
`crontab -u username -r`
|
||||
|
||||
**Explanation**
|
||||
|
||||
<pre>
|
||||
+—————- minute (values: 0 – 59) (special characters: , – * /) <br>
|
||||
| +————- hour (values: 0 – 23) (special characters: , – * /) <br>
|
||||
| | +———- day of month (values: 1 – 31) (special characters: , – * / L W C) <br>
|
||||
| | | +——- month (values: 1 – 12) (special characters: ,- * / ) <br>
|
||||
| | | | +—- day of week (values: 0 – 6) (Sunday=0 or 7) (special characters: , – * / L W C) <br>
|
||||
| | | | |*****command to be executed
|
||||
</pre>
|
||||
|
@ -112,4 +112,4 @@ As part of the Endpoint Detection and Response capabilities, Microsoft Defender
|
||||
|
||||
## Check installation status
|
||||
|
||||
Run [mdatp](mac-install-with-jamf.md) on a client device to check the onboarding status.
|
||||
Run [Microsoft Defender for Endpoint](mac-install-with-jamf.md) on a client device to check the onboarding status.
|
||||
|
@ -46,13 +46,13 @@ If you can reproduce a problem, increase the logging level, run the system for s
|
||||
|
||||
3. Run `sudo mdatp diagnostic create` to back up the Microsoft Defender for Endpoint logs. The files will be stored inside a .zip archive. This command will also print out the file path to the backup after the operation succeeds.
|
||||
|
||||
> [!TIP]
|
||||
> By default, diagnostic logs are saved to `/Library/Application Support/Microsoft/Defender/wdavdiag/`. To change the directory where diagnostic logs are saved, pass `--path [directory]` to the below command, replacing `[directory]` with the desired directory.
|
||||
> [!TIP]
|
||||
> By default, diagnostic logs are saved to `/Library/Application Support/Microsoft/Defender/wdavdiag/`. To change the directory where diagnostic logs are saved, pass `--path [directory]` to the below command, replacing `[directory]` with the desired directory.
|
||||
|
||||
```bash
|
||||
sudo mdatp diagnostic create
|
||||
```
|
||||
```Output
|
||||
```console
|
||||
Diagnostic file created: "/Library/Application Support/Microsoft/Defender/wdavdiag/932e68a8-8f2e-4ad0-a7f2-65eb97c0de01.zip"
|
||||
```
|
||||
|
||||
@ -61,7 +61,7 @@ If you can reproduce a problem, increase the logging level, run the system for s
|
||||
```bash
|
||||
mdatp log level set --level info
|
||||
```
|
||||
```Output
|
||||
```console
|
||||
Log level configured successfully
|
||||
```
|
||||
|
||||
@ -102,10 +102,10 @@ Important tasks, such as controlling product settings and triggering on-demand s
|
||||
|Configuration|Turn on audit mode for PUA protection |`mdatp threat policy set --type potentially_unwanted_application -- action audit` |
|
||||
|Configuration|Turn on/off passiveMode |`mdatp config passive-mode --value enabled [enabled/disabled]` |
|
||||
|Diagnostics |Change the log level |`mdatp log level set --level [error/warning/info/verbose]` |
|
||||
|Diagnostics |Generate diagnostic logs |`mdatp diagnostic create --path [directory]` |
|
||||
|Diagnostics |Generate diagnostic logs |`mdatp diagnostic create --path [directory]` |
|
||||
|Health |Check the product's health |`mdatp health` |
|
||||
|Health |Check for a spefic product attribute |`mdatp health --field [attribute: healthy/licensed/engine_version...]` |
|
||||
|Protection |Scan a path |`mdatp scan custom --path [path]` |
|
||||
|Protection |Scan a path |`mdatp scan custom --path [path] [--ignore-exclusions]` |
|
||||
|Protection |Do a quick scan |`mdatp scan quick` |
|
||||
|Protection |Do a full scan |`mdatp scan full` |
|
||||
|Protection |Cancel an ongoing on-demand scan |`mdatp scan cancel` |
|
||||
@ -113,17 +113,17 @@ Important tasks, such as controlling product settings and triggering on-demand s
|
||||
|EDR |Turn on/off EDR preview for Mac |`mdatp edr early-preview [enabled/disabled]` |
|
||||
|EDR |Add group tag to device. EDR tags are used for managing device groups. For more information, please visit https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/machine-groups |`mdatp edr tag set --name GROUP --value [name]` |
|
||||
|EDR |Remove group tag from device |`mdatp edr tag remove --tag-name [name]` |
|
||||
|EDR |Add Group Id |`mdatp edr group-ids --group-id [group]` |
|
||||
|EDR |Add Group ID |`mdatp edr group-ids --group-id [group]` |
|
||||
|
||||
### How to enable autocompletion
|
||||
|
||||
To enable autocompletion in `Bash`, run the following command and restart the Terminal session:
|
||||
To enable autocompletion in bash, run the following command and restart the Terminal session:
|
||||
|
||||
```bash
|
||||
echo "source /Applications/Microsoft\ Defender\ ATP.app/Contents/Resources/Tools/mdatp_completion.bash" >> ~/.bash_profile
|
||||
```
|
||||
|
||||
To enable autocompletion in `zsh`:
|
||||
To enable autocompletion in zsh:
|
||||
|
||||
- Check whether autocompletion is enabled on your device:
|
||||
|
||||
@ -131,7 +131,7 @@ To enable autocompletion in `zsh`:
|
||||
cat ~/.zshrc | grep autoload
|
||||
```
|
||||
|
||||
- If the above command does not produce any output, you can enable autocompletion using the following command:
|
||||
- If the preceding command does not produce any output, you can enable autocompletion using the following command:
|
||||
|
||||
```zsh
|
||||
echo "autoload -Uz compinit && compinit" >> ~/.zshrc
|
||||
@ -152,4 +152,4 @@ To enable autocompletion in `zsh`:
|
||||
|
||||
## Microsoft Defender for Endpoint portal information
|
||||
|
||||
[This blog](https://techcommunity.microsoft.com/t5/microsoft-defender-atp/edr-capabilities-for-macos-have-now-arrived/ba-p/1047801) provides detailed guidance on what to expect in Microsoft Defender for Endpoint Security Center.
|
||||
[EDR capabilities for macOS have now arrived](https://techcommunity.microsoft.com/t5/microsoft-defender-atp/edr-capabilities-for-macos-have-now-arrived/ba-p/1047801), on the Microsoft Defender for Endpoint blog, provides detailed guidance on what to expect in Microsoft Defender for Endpoint Security Center.
|
||||
|
@ -42,7 +42,7 @@ Contact your administrator for help.
|
||||
|
||||
**Cause:**
|
||||
|
||||
You deployed and/or installed the MDATP for macOS package ("Download installation package") but you might have run the configuration script ("Download onboarding package").
|
||||
You deployed and/or installed the Microsoft Defender for Endpoint for macOS package ("Download installation package") but you might have run the configuration script ("Download onboarding package").
|
||||
|
||||
**Solution:**
|
||||
|
||||
|
@ -27,10 +27,17 @@ ms.topic: conceptual
|
||||
> On macOS 11 (Big Sur), Microsoft Defender for Endpoint requires additional configuration profiles. If you are an existing customer upgrading from earlier versions of macOS, make sure to deploy the additional configuration profiles listed on [this page](mac-sysext-policies.md).
|
||||
|
||||
> [!IMPORTANT]
|
||||
> With the agent version 101.13.75+, we released a change that removed conditions when Microsoft Defender for Endpoint was triggering the macOS Big Sur bug that manifests into a kernel panic. With that change Defender code path should no longer directly facilitate the kernel panic.
|
||||
> Support for macOS 10.13 (High Sierra) will be discontinued on February 15th, 2021.
|
||||
|
||||
## 101.15.26
|
||||
|
||||
- Improved the reliability of the agent when running on macOS 11 Big Sur
|
||||
- Added a new command-line switch (`--ignore-exclusions`) to ignore AV exclusions during custom scans (`mdatp scan custom`)
|
||||
- Performance improvements & bug fixes
|
||||
|
||||
## 101.13.75
|
||||
|
||||
- Removed conditions when Microsoft Defender for Endpoint was triggering a macOS 11 (Big Sur) bug that manifests into a kernel panic
|
||||
- Fixed a memory leak in the Endpoint Security system extension when running on mac 11 (Big Sur)
|
||||
- Bug fixes
|
||||
|
||||
|
@ -59,7 +59,7 @@ lastExternalIpAddress | String | Last IP through which the [machine](machine.md)
|
||||
healthStatus | Enum | [machine](machine.md) health status. Possible values are: "Active", "Inactive", "ImpairedCommunication", "NoSensorData" and "NoSensorDataImpairedCommunication"
|
||||
rbacGroupName | String | Machine group Name.
|
||||
rbacGroupId | Int | Machine group unique ID.
|
||||
riskScore | Nullable Enum | Risk score as evaluated by Microsoft Defender ATP. Possible values are: 'None', 'Informational', 'Low', 'Medium' and 'High'.
|
||||
riskScore | Nullable Enum | Risk score as evaluated by Microsoft Defender for Endpoint. Possible values are: 'None', 'Informational', 'Low', 'Medium' and 'High'.
|
||||
exposureScore | Nullable Enum | [Exposure score](tvm-exposure-score.md) as evaluated by Microsoft Defender for Endpoint. Possible values are: 'None', 'Low', 'Medium' and 'High'.
|
||||
aadDeviceId | Nullable representation Guid | AAD Device ID (when [machine](machine.md) is AAD Joined).
|
||||
machineTags | String collection | Set of [machine](machine.md) tags.
|
||||
|
@ -34,7 +34,7 @@ Acknowledging that customer environments and structures can vary, Defender for E
|
||||
|
||||
## Endpoint onboarding and portal access
|
||||
|
||||
Device onboarding is fully integrated into Microsoft Endpoint Configuration Manager and Microsoft Intune for client devices and Azure Security Center for server devices, providing complete end-to-end experience of configuration, deployment, and monitoring. In addition, Microsoft Defender ATP supports Group Policy and other third-party tools used for devices management.
|
||||
Device onboarding is fully integrated into Microsoft Endpoint Configuration Manager and Microsoft Intune for client devices and Azure Security Center for server devices, providing complete end-to-end experience of configuration, deployment, and monitoring. In addition, Microsoft Defender for Endpoint supports Group Policy and other third-party tools used for devices management.
|
||||
|
||||
Defender for Endpoint provides fine-grained control over what users with access to the portal can see and do through the flexibility of role-based access control (RBAC). The RBAC model supports all flavors of security teams structure:
|
||||
- Globally distributed organizations and security teams
|
||||
@ -42,7 +42,7 @@ Defender for Endpoint provides fine-grained control over what users with access
|
||||
- Fully segregated divisions with single centralized global security operations teams
|
||||
|
||||
## Available APIs
|
||||
The Microsoft Defender ATP solution is built on top of an integration-ready platform.
|
||||
The Microsoft Defender for Endpoint solution is built on top of an integration-ready platform.
|
||||
|
||||
Defender for Endpoint exposes much of its data and actions through a set of programmatic APIs. Those APIs will enable you to automate workflows and innovate based on Defender for Endpoint capabilities.
|
||||
|
||||
|
@ -44,7 +44,7 @@ This migration phase includes the following steps:
|
||||
|
||||
## Get and deploy updates across your organization's devices
|
||||
|
||||
As a best practice, keep your organization's devices and endpoints up to date. Make sure your McAfee Endpoint Security (McAfee) solution is up to date, and that the operating systems and apps your organization is also have the latest updates. Doing this now can help prevent problems later as you migrate to Microsoft Defender ATP and Microsoft Defender Antivirus.
|
||||
As a best practice, keep your organization's devices and endpoints up to date. Make sure your McAfee Endpoint Security (McAfee) solution is up to date, and that the operating systems and apps your organization is also have the latest updates. Doing this now can help prevent problems later as you migrate to Microsoft Defender for Endpoint and Microsoft Defender Antivirus.
|
||||
|
||||
### Make sure your McAfee solution is up to date
|
||||
|
||||
@ -72,24 +72,24 @@ Need help updating your organization's devices? See the following resources:
|
||||
|
||||
## Get Microsoft Defender for Endpoint
|
||||
|
||||
Now that you've updated your organization's devices, the next step is to get Microsoft Defender ATP, assign licenses, and make sure the service is provisioned.
|
||||
Now that you've updated your organization's devices, the next step is to get Microsoft Defender for Endpoint, assign licenses, and make sure the service is provisioned.
|
||||
|
||||
1. Buy or try Microsoft Defender for Endpoint today. [Start a free trial or request a quote](https://aka.ms/mdatp).
|
||||
|
||||
2. Verify that your licenses are properly provisioned. [Check your license state](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/production-deployment#check-license-state).
|
||||
|
||||
3. As a global administrator or security administrator, set up your dedicated cloud instance of Microsoft Defender for Endpoint. See [Microsoft Defender ATP setup: Tenant configuration](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/production-deployment#tenant-configuration).
|
||||
3. As a global administrator or security administrator, set up your dedicated cloud instance of Microsoft Defender for Endpoint. See [Microsoft Defender for Endpoint setup: Tenant configuration](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/production-deployment#tenant-configuration).
|
||||
|
||||
4. If endpoints (such as devices) in your organization use a proxy to access the internet, see [Microsoft Defender ATP setup: Network configuration](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/production-deployment#network-configuration).
|
||||
4. If endpoints (such as devices) in your organization use a proxy to access the internet, see [Microsoft Defender for Endpoint setup: Network configuration](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/production-deployment#network-configuration).
|
||||
|
||||
At this point, you are ready to grant access to your security administrators and security operators who will use the Microsoft Defender Security Center ([https://aka.ms/MDATPportal](https://aka.ms/MDATPportal)).
|
||||
|
||||
> [!NOTE]
|
||||
> The Microsoft Defender Security Center is sometimes referred to as the Microsoft Defender ATP portal.
|
||||
> The Microsoft Defender Security Center is sometimes referred to as the Microsoft Defender for Endpoint portal.
|
||||
|
||||
## Grant access to the Microsoft Defender Security Center
|
||||
|
||||
The Microsoft Defender Security Center ([https://aka.ms/MDATPportal](https://aka.ms/MDATPportal)) is where you access and configure features and capabilities of Microsoft Defender ATP. To learn more, see [Overview of the Microsoft Defender Security Center](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/use).
|
||||
The Microsoft Defender Security Center ([https://aka.ms/MDATPportal](https://aka.ms/MDATPportal)) is where you access and configure features and capabilities of Microsoft Defender for Endpoint. To learn more, see [Overview of the Microsoft Defender Security Center](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/use).
|
||||
|
||||
Permissions to the Microsoft Defender Security Center can be granted by using either basic permissions or role-based access control (RBAC). We recommend using RBAC so that you have more granular control over permissions.
|
||||
|
||||
@ -106,16 +106,16 @@ Permissions to the Microsoft Defender Security Center can be granted by using ei
|
||||
|
||||
## Configure device proxy and internet connectivity settings
|
||||
|
||||
To enable communication between your devices and Microsoft Defender ATP, configure proxy and internet settings. The following table includes links to resources you can use to configure your proxy and internet settings for various operating systems and capabilities:
|
||||
To enable communication between your devices and Microsoft Defender for Endpoint, configure proxy and internet settings. The following table includes links to resources you can use to configure your proxy and internet settings for various operating systems and capabilities:
|
||||
|
||||
|Capabilities | Operating System | Resources |
|
||||
|--|--|--|
|
||||
|[Endpoint detection and response](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/overview-endpoint-detection-response) (EDR) |- [Windows 10](https://docs.microsoft.com/windows/release-information) <br/>- [Windows Server 2019](https://docs.microsoft.com/windows/release-information/status-windows-10-1809-and-windows-server-2019)<br/>- [Windows Server 1803 or later](https://docs.microsoft.com/windows-server/get-started/whats-new-in-windows-server-1803) |[Configure machine proxy and internet connectivity settings](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-proxy-internet) |
|
||||
|EDR |- [Windows Server 2016](https://docs.microsoft.com/windows/release-information/status-windows-10-1607-and-windows-server-2016) <br/>- [Windows Server 2012 R2](https://docs.microsoft.com/windows/release-information/status-windows-8.1-and-windows-server-2012-r2)<br/>- [Windows Server 2008 R2 SP1](https://docs.microsoft.com/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1)<br/>- [Windows 8.1](https://docs.microsoft.com/windows/release-information/status-windows-8.1-and-windows-server-2012-r2)<br/>- [Windows 7 SP1](https://docs.microsoft.com/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1) |[Configure proxy and internet connectivity settings](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/onboard-downlevel#configure-proxy-and-internet-connectivity-settings) |
|
||||
|EDR |macOS: <br/>- 10.15 (Catalina)<br/>- 10.14 (Mojave) <br/>- 10.13 (High Sierra) |[Microsoft Defender ATP for Mac: Network connections](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac#network-connections) |
|
||||
|EDR |macOS: <br/>- 10.15 (Catalina)<br/>- 10.14 (Mojave) <br/>- 10.13 (High Sierra) |[Microsoft Defender for Endpoint for Mac: Network connections](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac#network-connections) |
|
||||
|[Microsoft Defender Antivirus](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-antivirus/microsoft-defender-antivirus-in-windows-10) |- [Windows 10](https://docs.microsoft.com/windows/release-information) <br/>- [Windows Server 2019](https://docs.microsoft.com/windows/release-information/status-windows-10-1809-and-windows-server-2019)<br/>- [Windows Server 1803 or later](https://docs.microsoft.com/windows-server/get-started/whats-new-in-windows-server-1803) <br/>- [Windows Server 2016](https://docs.microsoft.com/windows-server/get-started/whats-new-in-windows-server-2016) |[Configure and validate Microsoft Defender Antivirus network connections](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-antivirus/configure-network-connections-microsoft-defender-antivirus)<br/> |
|
||||
|Antivirus |macOS: <br/>- 10.15 (Catalina)<br/>- 10.14 (Mojave) <br/>- 10.13 (High Sierra) |[Microsoft Defender ATP for Mac: Network connections](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac#network-connections) |
|
||||
|Antivirus |Linux: <br/>- RHEL 7.2+<br/>- CentOS Linux 7.2+<br/>- Ubuntu 16 LTS, or higher LTS<br/>- SLES 12+<br/>- Debian 9+<br/>- Oracle Linux 7.2 |[Microsoft Defender ATP for Linux: Network connections](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-linux#network-connections)
|
||||
|Antivirus |macOS: <br/>- 10.15 (Catalina)<br/>- 10.14 (Mojave) <br/>- 10.13 (High Sierra) |[Microsoft Defender for Endpoint for Mac: Network connections](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac#network-connections) |
|
||||
|Antivirus |Linux: <br/>- RHEL 7.2+<br/>- CentOS Linux 7.2+<br/>- Ubuntu 16 LTS, or higher LTS<br/>- SLES 12+<br/>- Debian 9+<br/>- Oracle Linux 7.2 |[Microsoft Defender for Endpoint for Linux: Network connections](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-linux#network-connections)
|
||||
|
||||
## Next step
|
||||
|
||||
|
@ -106,7 +106,7 @@ The [DisableAntiSpyware](https://docs.microsoft.com/windows-hardware/customize/d
|
||||
|
||||
### Set Microsoft Defender Antivirus to passive mode on Windows Server
|
||||
|
||||
Because your organization is still using McAfee, you must set Microsoft Defender Antivirus to passive mode. That way, McAfee and Microsoft Defender Antivirus can run side by side until you have finished onboarding to Microsoft Defender ATP.
|
||||
Because your organization is still using McAfee, you must set Microsoft Defender Antivirus to passive mode. That way, McAfee and Microsoft Defender Antivirus can run side by side until you have finished onboarding to Microsoft Defender for Endpoint.
|
||||
|
||||
1. Open Registry Editor, and then navigate to <br/>
|
||||
`Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Windows Advanced Threat Protection`.
|
||||
@ -193,7 +193,7 @@ You can choose from several methods to add your exclusions to Microsoft Defender
|
||||
|
||||
## Add McAfee to the exclusion list for Microsoft Defender for Endpoint
|
||||
|
||||
To add exclusions to Microsoft Defender ATP, you create [indicators](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/manage-indicators#create-indicators-for-files).
|
||||
To add exclusions to Microsoft Defender for Endpoint, you create [indicators](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/manage-indicators#create-indicators-for-files).
|
||||
|
||||
1. Go to the Microsoft Defender Security Center ([https://aka.ms/MDATPportal](https://aka.ms/MDATPportal)) and sign in.
|
||||
|
||||
|
@ -18,7 +18,7 @@ ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Configure Microsoft Cloud App Security in Microsoft Defender ATP
|
||||
# Configure Microsoft Cloud App Security in Microsoft Defender for Endpoint
|
||||
|
||||
[!INCLUDE [Microsoft 365 Defender rebranding](../../includes/microsoft-defender.md)]
|
||||
|
||||
@ -32,7 +32,7 @@ To benefit from Microsoft Defender for Endpoint cloud app discovery signals, tur
|
||||
>[!NOTE]
|
||||
>This feature will be available with an E5 license for [Enterprise Mobility + Security](https://www.microsoft.com/cloud-platform/enterprise-mobility-security) on devices running Windows 10, version 1709 (OS Build 16299.1085 with [KB4493441](https://support.microsoft.com/help/4493441)), Windows 10, version 1803 (OS Build 17134.704 with [KB4493464](https://support.microsoft.com/help/4493464)), Windows 10, version 1809 (OS Build 17763.379 with [KB4489899](https://support.microsoft.com/help/4489899)) or later Windows 10 versions.
|
||||
|
||||
> See [Microsoft Defender for Endpoint integration with Microsoft Cloud App Security](https://docs.microsoft.com/cloud-app-security/wdatp-integration) for detailed integration of Microsoft Defender ATP with Microsoft Cloud App Security.
|
||||
> See [Microsoft Defender for Endpoint integration with Microsoft Cloud App Security](https://docs.microsoft.com/cloud-app-security/wdatp-integration) for detailed integration of Microsoft Defender for Endpoint with Microsoft Cloud App Security.
|
||||
|
||||
## Enable Microsoft Cloud App Security in Microsoft Defender for Endpoint
|
||||
|
||||
|
@ -88,7 +88,7 @@ The attack surface reduction set of capabilities provides the first line of defe
|
||||
<a name="ngp"></a>
|
||||
|
||||
**[Next-generation protection](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-antivirus/microsoft-defender-antivirus-in-windows-10)**<br>
|
||||
To further reinforce the security perimeter of your network, Microsoft Defender ATP uses next-generation protection designed to catch all types of emerging threats.
|
||||
To further reinforce the security perimeter of your network, Microsoft Defender for Endpoint uses next-generation protection designed to catch all types of emerging threats.
|
||||
|
||||
<a name="edr"></a>
|
||||
|
||||
@ -98,7 +98,7 @@ Endpoint detection and response capabilities are put in place to detect, investi
|
||||
<a name="ai"></a>
|
||||
|
||||
**[Automated investigation and remediation](automated-investigations.md)**<br>
|
||||
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.
|
||||
In conjunction with being able to quickly respond to advanced attacks, Microsoft Defender for Endpoint offers automatic investigation and remediation capabilities that help reduce the volume of alerts in minutes at scale.
|
||||
|
||||
<a name="ss"></a>
|
||||
|
||||
|
@ -66,12 +66,12 @@ There are several methods and deployment tools that you can use to install and c
|
||||
The three most recent major releases of macOS are supported.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> On macOS 11 (Big Sur), Microsoft Defender for Endpoint requires additional configuration profiles. If you are an existing customer upgrading from earlier versions of macOS, make sure to deploy the additional configuration profiles listed on [this page](mac-sysext-policies.md).
|
||||
> On macOS 11 (Big Sur), Microsoft Defender for Endpoint requires additional configuration profiles. If you are an existing customer upgrading from earlier versions of macOS, make sure to deploy the additional configuration profiles listed on [New configuration profiles for macOS Catalina and newer versions of macOS](mac-sysext-policies.md).
|
||||
|
||||
> [!IMPORTANT]
|
||||
> With the agent version 101.13.75+, we released a change that removed conditions when Microsoft Defender for Endpoint was triggering the macOS Big Sur bug that manifests into a kernel panic. With that change Defender code path should no longer directly facilitate the kernel panic.
|
||||
> Support for macOS 10.13 (High Sierra) will be discontinued on February 15th, 2021.
|
||||
|
||||
- 10.15 (Catalina), 10.14 (Mojave), 10.13 (High Sierra)
|
||||
- 11 (Big Sur), 10.15 (Catalina), 10.14 (Mojave), 10.13 (High Sierra)
|
||||
- Disk space: 1GB
|
||||
|
||||
Beta versions of macOS are not supported.
|
||||
@ -98,7 +98,7 @@ The following downloadable spreadsheet lists the services and their associated U
|
||||
|
||||
|**Spreadsheet of domains list**|**Description**|
|
||||
|:-----|:-----|
|
||||
|<br/> | Spreadsheet of specific DNS records for service locations, geographic locations, and OS. <br><br>[Download the spreadsheet here.](https://github.com/MicrosoftDocs/windows-itpro-docs/raw/public/windows/security/threat-protection/microsoft-defender-atp/downloads/mdatp-urls.xlsx)
|
||||
|<br/> | Spreadsheet of specific DNS records for service locations, geographic locations, and OS. <br><br>Download the spreadsheet here: [mdatp-urls.xlsx](https://github.com/MicrosoftDocs/windows-itpro-docs/raw/public/windows/security/threat-protection/microsoft-defender-atp/downloads/mdatp-urls.xlsx).
|
||||
|
||||
Microsoft Defender for Endpoint can discover a proxy server by using the following discovery methods:
|
||||
- Proxy autoconfig (PAC)
|
||||
@ -144,10 +144,10 @@ Guidance for how to configure the product in enterprise environments is availabl
|
||||
|
||||
## macOS kernel and system extensions
|
||||
|
||||
In alignment with macOS evolution, we are preparing a Microsoft Defender for Endpoint for Mac update that leverages system extensions instead of kernel extensions. Visit [What's new in Microsoft Defender for Endpoint for Mac](mac-whatsnew.md) for relevant details.
|
||||
In alignment with macOS evolution, we are preparing a Microsoft Defender for Endpoint for Mac update that leverages system extensions instead of kernel extensions. For relevant details, see [What's new in Microsoft Defender for Endpoint for Mac](mac-whatsnew.md).
|
||||
|
||||
## Resources
|
||||
|
||||
- For more information about logging, uninstalling, or other topics, see the [Resources](mac-resources.md) page.
|
||||
- For more information about logging, uninstalling, or other topics, see [Resources for Microsoft Defender for Endpoint for Mac](mac-resources.md).
|
||||
|
||||
- [Privacy for Microsoft Defender for Endpoint for Mac](mac-privacy.md)
|
||||
- [Privacy for Microsoft Defender for Endpoint for Mac](mac-privacy.md).
|
||||
|
@ -32,7 +32,7 @@ This article is part of the Deployment guide and acts as an example onboarding m
|
||||
|
||||
This onboarding guidance will walk you through the following basic steps that you need to take when using Microsoft Endpoint Configuration Manager:
|
||||
- **Creating a collection in Microsoft Endpoint Configuration Manager**
|
||||
- **Configuring Microsoft Defender ATP capabilities using Microsoft Endpoint Configuration Manager**
|
||||
- **Configuring Microsoft Defender for Endpoint capabilities using Microsoft Endpoint Configuration Manager**
|
||||
|
||||
>[!NOTE]
|
||||
>Only Windows devices are covered in this example deployment.
|
||||
|
@ -176,14 +176,14 @@ how the endpoint security suite should be enabled.
|
||||
| Component | Description | Adoption Order Rank |
|
||||
|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|
|
||||
| Endpoint Detection & Response (EDR) | Defender for Endpoint 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. <br> [Learn more.](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/overview-endpoint-detection-response) | 1 |
|
||||
|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: <br> - Real-time endpoint detection and response (EDR) insights correlated with endpoint vulnerabilities <br> - Invaluable device vulnerability context during incident investigations <br> - Built-in remediation processes through Microsoft Intune and Microsoft System Center Configuration Manager <br> [Learn more](https://techcommunity.microsoft.com/t5/Windows-Defender-ATP/Introducing-a-risk-based-approach-to-threat-and-vulnerability/ba-p/377845).| 2 |
|
||||
|Threat & Vulnerability Management (TVM)|Threat & Vulnerability Management is a component of Microsoft Defender for Endpoint, and provides both security administrators and security operations teams with unique value, including: <br> - Real-time endpoint detection and response (EDR) insights correlated with endpoint vulnerabilities <br> - Invaluable device vulnerability context during incident investigations <br> - Built-in remediation processes through Microsoft Intune and Microsoft System Center Configuration Manager <br> [Learn more](https://techcommunity.microsoft.com/t5/Windows-Defender-ATP/Introducing-a-risk-based-approach-to-threat-and-vulnerability/ba-p/377845).| 2 |
|
||||
| Next-generation protection (NGP) | Microsoft Defender Antivirus is a built-in antimalware solution that provides next-generation protection for desktops, portable computers, and servers. Microsoft Defender Antivirus includes: <br> -Cloud-delivered protection for near-instant detection and blocking of new and emerging threats. Along with machine learning and the Intelligent Security Graph, cloud-delivered protection is part of the next-gen technologies that power Microsoft Defender Antivirus. <br> - Always-on scanning using advanced file and process behavior monitoring and other heuristics (also known as "real-time protection"). <br> - Dedicated protection updates based on machine-learning, human and automated big-data analysis, and in-depth threat resistance research. <br> [Learn more](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-antivirus/microsoft-defender-antivirus-in-windows-10). |3 |
|
||||
| Attack Surface Reduction (ASR) | Attack surface reduction capabilities in Microsoft Defender ATP help protect the devices and applications in the organization from new and emerging threats. <br> [Learn more.](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/overview-attack-surface-reduction) | 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. <br>[Learn more.](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/automated-investigations-windows-defender-advanced-threat-protection) | Not applicable |
|
||||
| Attack Surface Reduction (ASR) | Attack surface reduction capabilities in Microsoft Defender for Endpoint help protect the devices and applications in the organization from new and emerging threats. <br> [Learn more.](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/overview-attack-surface-reduction) | 4 |
|
||||
| Auto Investigation & Remediation (AIR) | Microsoft Defender for Endpoint 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. <br>[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. <br>[Learn more.](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/microsoft-threat-experts) | Not applicable |
|
||||
|
||||
## Next step
|
||||
|||
|
||||
|:-------|:-----|
|
||||
| <br>[Phase 2: Setup](production-deployment.md) | Set up Microsoft Defender ATP deployment
|
||||
| <br>[Phase 2: Setup](production-deployment.md) | Set up Microsoft Defender for Endpoint deployment
|
||||
|
||||
|
@ -54,7 +54,7 @@ Turn on the preview experience setting to be among the first to try upcoming fea
|
||||
## Preview features
|
||||
|
||||
The following features are included in the preview release:
|
||||
- [Microsoft Defender for Endpoint for iOS](microsoft-defender-atp-ios.md) <br> Microsoft Defender ATP now adds support for iOS. Learn how to install, configure, and use Microsoft Defender ATP for iOS.
|
||||
- [Microsoft Defender for Endpoint for iOS](microsoft-defender-atp-ios.md) <br> Microsoft Defender for Endpoint now adds support for iOS. Learn how to install, configure, and use Microsoft Defender for Endpoint for iOS.
|
||||
|
||||
- [Microsoft Defender for Endpoint for Android](microsoft-defender-atp-android.md) <br> Microsoft Defender for Endpoint now adds support for Android. Learn how to install, configure, and use Microsoft Defender for Endpoint for Android.
|
||||
|
||||
|
@ -72,7 +72,7 @@ Want to experience Defender for Endpoint? [Sign up for a free trial.](https://ww
|
||||
|
||||
- Each event hub message in Azure Event Hubs contains list of records.
|
||||
|
||||
- Each record contains the event name, the time Microsoft Defender ATP received the event, the tenant it belongs (you will only get events from your tenant), and the event in JSON format in a property called "**properties**".
|
||||
- Each record contains the event name, the time Microsoft Defender for Endpoint received the event, the tenant it belongs (you will only get events from your tenant), and the event in JSON format in a property called "**properties**".
|
||||
|
||||
- For more information about the schema of Microsoft Defender for Endpoint events, see [Advanced Hunting overview](advanced-hunting-overview.md).
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Take response actions on a file in Microsoft Defender ATP
|
||||
description: Take response actions on file related alerts by stopping and quarantining a file or blocking a file and checking activity details.
|
||||
description: Take response actions on file-related alerts by stopping and quarantining a file or blocking a file and checking activity details.
|
||||
keywords: respond, stop and quarantine, block file, deep analysis
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
@ -133,6 +133,9 @@ You can roll back and remove a file from quarantine if you’ve determined that
|
||||
>
|
||||
> Defender for Endpoint will restore all custom blocked files that were quarantined on this device in the last 30 days.
|
||||
|
||||
> [!Important]
|
||||
> A file that was quarantined as a potential network threat might not be recoverable. If a user attempts to restore the file after quarantine, that file might not be accessible. This can be due to the system no longer having network credentials to access the file. Typically, this is a result of a temporary log on to a system or shared folder and the access tokens expired.
|
||||
|
||||
## Add indicator to block or allow a file
|
||||
|
||||
You can prevent further propagation of an attack in your organization by banning potentially malicious files or suspected malware. If you know a potentially malicious portable executable (PE) file, you can block it. This operation will prevent it from being read, written, or executed on devices in your organization.
|
||||
@ -213,6 +216,7 @@ The Deep analysis summary includes a list of observed *behaviors*, some of which
|
||||
Results of deep analysis are matched against threat intelligence and any matches will generate appropriate alerts.
|
||||
|
||||
Use the deep analysis feature to investigate the details of any file, usually during an investigation of an alert or for any other reason where you suspect malicious behavior. This feature is available within the **Deep analysis** tab, on the file's profile page.
|
||||
<br/>
|
||||
|
||||
>[!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4aAYy?rel=0]
|
||||
|
||||
@ -240,7 +244,8 @@ When the sample is collected, Defender for Endpoint runs the file in is a secure
|
||||
|
||||

|
||||
|
||||
>**Note** Only PE files are supported, including _.exe_ and _.dll_ files
|
||||
> [!NOTE]
|
||||
> Only PE files are supported, including _.exe_ and _.dll_ files.
|
||||
|
||||
A progress bar is displayed and provides information on the different stages of the analysis. You can then view the report when the analysis is done.
|
||||
|
||||
|
@ -17,7 +17,7 @@ ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
---
|
||||
|
||||
# Supported Microsoft Defender ATP query APIs
|
||||
# Supported Microsoft Defender for Endpoint query APIs
|
||||
|
||||
[!INCLUDE [Microsoft 365 Defender rebranding](../../includes/microsoft-defender.md)]
|
||||
|
||||
|
@ -69,7 +69,7 @@ To verify that your onboarded devices are properly connected to Microsoft Defend
|
||||
|
||||
|Operating system |Guidance |
|
||||
|---------|---------|
|
||||
|- Windows 10 <br/>- Windows Server 2019 <br/>- Windows Server, version 1803 <br/>- Windows Server 2016 <br/>- Windows Server 2012 R2 |See [Run a detection test](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/run-detection-test). <br/><br/>Visit the Microsoft Defender ATP demo scenarios site ([https://demo.wd.microsoft.com](https://demo.wd.microsoft.com)) and try one or more of the scenarios. For example, try the **Cloud-delivered protection** demo scenario. |
|
||||
|- Windows 10 <br/>- Windows Server 2019 <br/>- Windows Server, version 1803 <br/>- Windows Server 2016 <br/>- Windows Server 2012 R2 |See [Run a detection test](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/run-detection-test). <br/><br/>Visit the Microsoft Defender for Endpoint demo scenarios site ([https://demo.wd.microsoft.com](https://demo.wd.microsoft.com)) and try one or more of the scenarios. For example, try the **Cloud-delivered protection** demo scenario. |
|
||||
|macOS<br/>- 10.15 (Catalina)<br/>- 10.14 (Mojave)<br/>- 10.13 (High Sierra) |Download and use the DIY app at [https://aka.ms/mdatpmacosdiy](https://aka.ms/mdatpmacosdiy). <br/><br/>For more information, see [Microsoft Defender Advanced Threat Protection for Mac](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac). |
|
||||
|Linux:<br/>- RHEL 7.2+<br/>- CentOS Linux 7.2+<br/>- Ubuntu 16 LTS, or higher LTS<br/>- SLES 12+<br/>- Debian 9+<br/>- Oracle Linux 7.2 |1. Run the following command, and look for a result of **1**: <br/>`mdatp health --field real_time_protection_enabled`. <br/><br/>2. Open a Terminal window, and run the following command: <br/>`curl -o ~/Downloads/eicar.com.txt https://www.eicar.org/download/eicar.com.txt`. <br/><br/>3. Run the following command to list any detected threats: <br/>`mdatp threat list`. <br/><br/>For more information, see [Microsoft Defender for Endpoint for Linux](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-linux). |
|
||||
|
||||
|
@ -72,4 +72,4 @@ This topic provides instructions on how to run the tool via Live Response.
|
||||
> GetFile "C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Downloads\MDATPClientAnalyzerResult.zip" -auto
|
||||
> ```
|
||||
>
|
||||
> - For more information on gathering data locally on a machine in case the machine isn't communicating with Microsoft Defender for Endpoint cloud services, or does not appear in MDATP portal as expected, see [Verify client connectivity to Microsoft Defender for Endpoint service URLs](configure-proxy-internet.md#verify-client-connectivity-to-microsoft-defender-atp-service-urls).
|
||||
> - For more information on gathering data locally on a machine in case the machine isn't communicating with Microsoft Defender for Endpoint cloud services, or does not appear in Microsoft Defender for Endpoint portal as expected, see [Verify client connectivity to Microsoft Defender for Endpoint service URLs](configure-proxy-internet.md#verify-client-connectivity-to-microsoft-defender-atp-service-urls).
|
||||
|
Reference in New Issue
Block a user