Merge branch 'master' into master
@ -44,7 +44,7 @@
|
||||
#### [Attack surface reduction](microsoft-defender-atp/attack-surface-reduction.md)
|
||||
#### [Network firewall](windows-firewall/windows-firewall-with-advanced-security.md)
|
||||
|
||||
### [Next generation protection](windows-defender-antivirus/windows-defender-antivirus-in-windows-10.md)
|
||||
### [Next-generation protection](windows-defender-antivirus/windows-defender-antivirus-in-windows-10.md)
|
||||
#### [Better together: Windows Defender Antivirus and Microsoft Defender ATP](windows-defender-antivirus/why-use-microsoft-antivirus.md)
|
||||
|
||||
### [Endpoint detection and response]()
|
||||
@ -76,7 +76,7 @@
|
||||
##### [Take response actions on a machine]()
|
||||
###### [Response actions on machines](microsoft-defender-atp/respond-machine-alerts.md)
|
||||
###### [Manage tags](microsoft-defender-atp/respond-machine-alerts.md#manage-tags)
|
||||
###### [Initiate Automated investigation](microsoft-defender-atp/respond-machine-alerts.md#initiate-automated-investigation)
|
||||
###### [Initiate an automated investigation](microsoft-defender-atp/respond-machine-alerts.md#initiate-automated-investigation)
|
||||
###### [Initiate Live Response session](microsoft-defender-atp/respond-machine-alerts.md#initiate-live-response-session)
|
||||
###### [Collect investigation package](microsoft-defender-atp/respond-machine-alerts.md#collect-investigation-package-from-machines)
|
||||
###### [Run antivirus scan](microsoft-defender-atp/respond-machine-alerts.md#run-windows-defender-antivirus-scan-on-machines)
|
||||
@ -105,8 +105,8 @@
|
||||
|
||||
### [Automated investigation and remediation]()
|
||||
#### [Automated investigation and remediation overview](microsoft-defender-atp/automated-investigations.md)
|
||||
#### [Learn about the automated investigation and remediation dashboard](microsoft-defender-atp/manage-auto-investigation.md)
|
||||
##### [Manage actions related to automated investigation and remediation](microsoft-defender-atp/auto-investigation-action-center.md)
|
||||
#### [Use the automated investigation and remediation dashboard](microsoft-defender-atp/manage-auto-investigation.md)
|
||||
#### [Manage actions related to automated investigation and remediation](microsoft-defender-atp/auto-investigation-action-center.md)
|
||||
|
||||
### [Secure score](microsoft-defender-atp/overview-secure-score.md)
|
||||
### [Threat analytics](microsoft-defender-atp/threat-analytics.md)
|
||||
@ -187,7 +187,7 @@
|
||||
##### [Controlled folder access](microsoft-defender-atp/evaluate-controlled-folder-access.md)
|
||||
##### [Attack surface reduction](microsoft-defender-atp/evaluate-attack-surface-reduction.md)
|
||||
##### [Network firewall](windows-firewall/evaluating-windows-firewall-with-advanced-security-design-examples.md)
|
||||
##### [Evaluate next generation protection](windows-defender-antivirus/evaluate-windows-defender-antivirus.md)
|
||||
##### [Evaluate next-generation protection](windows-defender-antivirus/evaluate-windows-defender-antivirus.md)
|
||||
|
||||
### [Access the Windows Defender Security Center Community Center](microsoft-defender-atp/community.md)
|
||||
|
||||
@ -231,7 +231,7 @@
|
||||
|
||||
|
||||
|
||||
### [Configure next generation protection]()
|
||||
### [Configure next-generation protection]()
|
||||
#### [Configure Windows Defender Antivirus features](windows-defender-antivirus/configure-windows-defender-antivirus-features.md)
|
||||
|
||||
#### [Utilize Microsoft cloud-delivered protection](windows-defender-antivirus/utilize-microsoft-cloud-protection-windows-defender-antivirus.md)
|
||||
@ -291,7 +291,7 @@
|
||||
#### [Manage antivirus in your business]()
|
||||
##### [Management overview](windows-defender-antivirus/configuration-management-reference-windows-defender-antivirus.md)
|
||||
##### [Use Group Policy settings to configure and manage antivirus](windows-defender-antivirus/use-group-policy-windows-defender-antivirus.md)
|
||||
##### [Use System Center Configuration Manager and Microsoft Intune to configure and manage antivirus](windows-defender-antivirus/use-intune-config-manager-windows-defender-antivirus.md)
|
||||
##### [Use Microsoft Endpoint Configuration Manager and Microsoft Intune to configure and manage antivirus](windows-defender-antivirus/use-intune-config-manager-windows-defender-antivirus.md)
|
||||
##### [Use PowerShell cmdlets to configure and manage antivirus](windows-defender-antivirus/use-powershell-cmdlets-windows-defender-antivirus.md)
|
||||
##### [Use Windows Management Instrumentation (WMI) to configure and manage antivirus](windows-defender-antivirus/use-wmi-windows-defender-antivirus.md)
|
||||
##### [Use the mpcmdrun.exe commandline tool to configure and manage antivirus](windows-defender-antivirus/command-line-arguments-windows-defender-antivirus.md)
|
||||
@ -315,15 +315,15 @@
|
||||
##### [Run and review the results of an offline scan](windows-defender-antivirus/windows-defender-offline.md)
|
||||
##### [Restore quarantined files](windows-defender-antivirus/restore-quarantined-files-windows-defender-antivirus.md)
|
||||
|
||||
#### [Manage next generation protection in your business]()
|
||||
#### [Manage next-generation protection in your business]()
|
||||
##### [Handle false positives/negatives in Windows Defender Antivirus](windows-defender-antivirus/antivirus-false-positives-negatives.md)
|
||||
##### [Management overview](windows-defender-antivirus/configuration-management-reference-windows-defender-antivirus.md)
|
||||
##### [Use Microsoft Intune and System Center Configuration Manager to manage next generation protection](windows-defender-antivirus/use-intune-config-manager-windows-defender-antivirus.md)
|
||||
##### [Use Microsoft Intune and Microsoft Endpoint Configuration Manager to manage next generation protection](windows-defender-antivirus/use-intune-config-manager-windows-defender-antivirus.md)
|
||||
##### [Use Group Policy settings to manage next generation protection](windows-defender-antivirus/use-group-policy-windows-defender-antivirus.md)
|
||||
##### [Use PowerShell cmdlets to manage next generation protection](windows-defender-antivirus/use-powershell-cmdlets-windows-defender-antivirus.md)
|
||||
##### [Use Windows Management Instrumentation (WMI) to manage next generation protection](windows-defender-antivirus/use-wmi-windows-defender-antivirus.md)
|
||||
##### [Use the mpcmdrun.exe command line tool to manage next generation protection](windows-defender-antivirus/command-line-arguments-windows-defender-antivirus.md)
|
||||
|
||||
|
||||
### [Microsoft Defender Advanced Threat Protection for Mac](microsoft-defender-atp/microsoft-defender-atp-mac.md)
|
||||
#### [What's New](microsoft-defender-atp/mac-whatsnew.md)
|
||||
#### [Deploy]()
|
||||
@ -354,7 +354,7 @@
|
||||
##### [Onboard Windows 10 machines]()
|
||||
###### [Onboarding tools and methods](microsoft-defender-atp/configure-endpoints.md)
|
||||
###### [Onboard machines using Group Policy](microsoft-defender-atp/configure-endpoints-gp.md)
|
||||
###### [Onboard machines using System Center Configuration Manager](microsoft-defender-atp/configure-endpoints-sccm.md)
|
||||
###### [Onboard machines using Microsoft Endpoint Configuration Manager](microsoft-defender-atp/configure-endpoints-sccm.md)
|
||||
###### [Onboard machines using Mobile Device Management tools](microsoft-defender-atp/configure-endpoints-mdm.md)
|
||||
###### [Onboard machines using a local script](microsoft-defender-atp/configure-endpoints-script.md)
|
||||
###### [Onboard non-persistent virtual desktop infrastructure (VDI) machines](microsoft-defender-atp/configure-endpoints-vdi.md)
|
||||
@ -373,7 +373,7 @@
|
||||
###### [Troubleshoot subscription and portal access issues](microsoft-defender-atp/troubleshoot-onboarding-error-messages.md)
|
||||
|
||||
#### [Microsoft Defender ATP API]()
|
||||
##### [Get started with Microsoft Defender ATP APIs]()
|
||||
##### [Get started]()
|
||||
###### [Microsoft Defender ATP API license and terms](microsoft-defender-atp/api-terms-of-use.md)
|
||||
###### [Access the Microsoft Defender ATP APIs](microsoft-defender-atp/apis-intro.md)
|
||||
###### [Hello World](microsoft-defender-atp/api-hello-world.md)
|
||||
@ -383,6 +383,7 @@
|
||||
|
||||
##### [Microsoft Defender ATP APIs Schema]()
|
||||
###### [Supported Microsoft Defender ATP APIs](microsoft-defender-atp/exposed-apis-list.md)
|
||||
###### [Common REST API error codes](microsoft-defender-atp/common-errors.md)
|
||||
###### [Advanced Hunting](microsoft-defender-atp/run-advanced-query-api.md)
|
||||
|
||||
###### [Alert]()
|
||||
@ -460,7 +461,7 @@
|
||||
####### [Score methods and properties](microsoft-defender-atp/score.md)
|
||||
####### [List exposure score by machine group](microsoft-defender-atp/get-machine-group-exposure-score.md)
|
||||
####### [Get exposure score](microsoft-defender-atp/get-exposure-score.md)
|
||||
####### [Get device secure score](microsoft-defender-atp/get-device-secure-score.md)
|
||||
####### [Get machine secure score](microsoft-defender-atp/get-device-secure-score.md)
|
||||
|
||||
###### [Software]()
|
||||
####### [Software methods and properties](microsoft-defender-atp/software.md)
|
||||
@ -472,7 +473,7 @@
|
||||
|
||||
###### [Vulnerability]()
|
||||
####### [Vulnerability methods and properties](microsoft-defender-atp/vulnerability.md)
|
||||
####### [Get all vulnerabilities](microsoft-defender-atp/get-all-vulnerabilities.md)
|
||||
####### [List vulnerabilities](microsoft-defender-atp/get-all-vulnerabilities.md)
|
||||
####### [Get vulnerability by Id](microsoft-defender-atp/get-vulnerability-by-id.md)
|
||||
####### [List machines by vulnerability](microsoft-defender-atp/get-machines-by-vulnerability.md)
|
||||
|
||||
@ -481,8 +482,8 @@
|
||||
####### [List all recommendations](microsoft-defender-atp/get-all-recommendations.md)
|
||||
####### [Get recommendation by Id](microsoft-defender-atp/get-recommendation-by-id.md)
|
||||
####### [Get recommendation by software](microsoft-defender-atp/get-recommendation-software.md)
|
||||
####### [Get recommendation by machines](microsoft-defender-atp/get-recommendation-machines.md)
|
||||
####### [Get recommendation by vulnerabilities](microsoft-defender-atp/get-recommendation-vulnerabilities.md)
|
||||
####### [List machines by recommendation](microsoft-defender-atp/get-recommendation-machines.md)
|
||||
####### [List vulnerabilities by recommendation](microsoft-defender-atp/get-recommendation-vulnerabilities.md)
|
||||
|
||||
##### [How to use APIs - Samples]()
|
||||
###### [Microsoft Flow](microsoft-defender-atp/api-microsoft-flow.md)
|
||||
@ -611,7 +612,7 @@
|
||||
#### [Network protection](microsoft-defender-atp/troubleshoot-np.md)
|
||||
#### [Attack surface reduction rules](microsoft-defender-atp/troubleshoot-asr.md)
|
||||
|
||||
### [Troubleshoot next generation protection](windows-defender-antivirus/troubleshoot-windows-defender-antivirus.md)
|
||||
### [Troubleshoot next-generation protection](windows-defender-antivirus/troubleshoot-windows-defender-antivirus.md)
|
||||
|
||||
|
||||
|
||||
|
@ -25,9 +25,9 @@ Audit Authorization Policy Change allows you to audit assignment and removal of
|
||||
|
||||
| Computer Type | General Success | General Failure | Stronger Success | Stronger Failure | Comments |
|
||||
|-------------------|-----------------|-----------------|------------------|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Domain Controller | IF | No | IF | No | IF – With Success auditing for this subcategory, you can get information related to changes in user rights policies, or changes of resource attributes or Central Access Policy applied to file system objects.<br>However, if you are using an application or system service that makes changes to system privileges through the AdjustPrivilegesToken API, we do not recommend Success auditing because of the high volume of event “[4703](event-4703.md)(S): A user right was adjusted” that may be generated. As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is System Center Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from **svchost.exe**).<br>If one of your applications or services is generating a large number of 4703 events, you might find that your event-management software has filtering logic that can automatically discard the recurring events, which would make it easier to work with Success auditing for this category.<br>This subcategory doesn’t have Failure events, so there is no recommendation to enable Failure auditing for this subcategory. |
|
||||
| Member Server | IF | No | IF | No | IF – With Success auditing for this subcategory, you can get information related to changes in user rights policies, or changes of resource attributes or Central Access Policy applied to file system objects.<br>However, if you are using an application or system service that makes changes to system privileges through the AdjustPrivilegesToken API, we do not recommend Success auditing because of the high volume of event “[4703](event-4703.md)(S): A user right was adjusted” that may be generated. As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is System Center Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from **svchost.exe**).<br>If one of your applications or services is generating a large number of 4703 events, you might find that your event-management software has filtering logic that can automatically discard the recurring events, which would make it easier to work with Success auditing for this category.<br>This subcategory doesn’t have Failure events, so there is no recommendation to enable Failure auditing for this subcategory. |
|
||||
| Workstation | IF | No | IF | No | IF – With Success auditing for this subcategory, you can get information related to changes in user rights policies, or changes of resource attributes or Central Access Policy applied to file system objects.<br>However, if you are using an application or system service that makes changes to system privileges through the AdjustPrivilegesToken API, we do not recommend Success auditing because of the high volume of event “[4703](event-4703.md)(S): A user right was adjusted” that may be generated. As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is System Center Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from **svchost.exe**).<br>If one of your applications or services is generating a large number of 4703 events, you might find that your event-management software has filtering logic that can automatically discard the recurring events, which would make it easier to work with Success auditing for this category.<br>This subcategory doesn’t have Failure events, so there is no recommendation to enable Failure auditing for this subcategory. |
|
||||
| Domain Controller | IF | No | IF | No | IF – With Success auditing for this subcategory, you can get information related to changes in user rights policies, or changes of resource attributes or Central Access Policy applied to file system objects.<br>However, if you are using an application or system service that makes changes to system privileges through the AdjustPrivilegesToken API, we do not recommend Success auditing because of the high volume of event “[4703](event-4703.md)(S): A user right was adjusted” that may be generated. As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is Microsoft Endpoint Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from **svchost.exe**).<br>If one of your applications or services is generating a large number of 4703 events, you might find that your event-management software has filtering logic that can automatically discard the recurring events, which would make it easier to work with Success auditing for this category.<br>This subcategory doesn’t have Failure events, so there is no recommendation to enable Failure auditing for this subcategory. |
|
||||
| Member Server | IF | No | IF | No | IF – With Success auditing for this subcategory, you can get information related to changes in user rights policies, or changes of resource attributes or Central Access Policy applied to file system objects.<br>However, if you are using an application or system service that makes changes to system privileges through the AdjustPrivilegesToken API, we do not recommend Success auditing because of the high volume of event “[4703](event-4703.md)(S): A user right was adjusted” that may be generated. As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is Microsoft Endpoint Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from **svchost.exe**).<br>If one of your applications or services is generating a large number of 4703 events, you might find that your event-management software has filtering logic that can automatically discard the recurring events, which would make it easier to work with Success auditing for this category.<br>This subcategory doesn’t have Failure events, so there is no recommendation to enable Failure auditing for this subcategory. |
|
||||
| Workstation | IF | No | IF | No | IF – With Success auditing for this subcategory, you can get information related to changes in user rights policies, or changes of resource attributes or Central Access Policy applied to file system objects.<br>However, if you are using an application or system service that makes changes to system privileges through the AdjustPrivilegesToken API, we do not recommend Success auditing because of the high volume of event “[4703](event-4703.md)(S): A user right was adjusted” that may be generated. As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is Microsoft Endpoint Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from **svchost.exe**).<br>If one of your applications or services is generating a large number of 4703 events, you might find that your event-management software has filtering logic that can automatically discard the recurring events, which would make it easier to work with Success auditing for this category.<br>This subcategory doesn’t have Failure events, so there is no recommendation to enable Failure auditing for this subcategory. |
|
||||
|
||||
**Events List:**
|
||||
|
||||
|
@ -1,6 +1,11 @@
|
||||
---
|
||||
title: Audit Token Right Adjusted (Windows 10)
|
||||
description: This topic for the IT professional describes the Advanced Security Audit policy setting, Audit Token Right Adjusted, which determines whether the operating system generates audit events when specific changes are made to the privileges of a token.
|
||||
manager: dansimp
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.pagetype: security
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Audit Token Right Adjusted
|
||||
@ -16,9 +21,9 @@ For more information, see [Security Monitoring: A Possible New Way to Detect Pri
|
||||
|
||||
| Computer Type | General Success | General Failure | Stronger Success | Stronger Failure | Comments |
|
||||
|-------------------|-----------------|-----------------|------------------|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Domain Controller | IF | No | IF | No | IF – With Success auditing for this subcategory, you can get information related to changes to the privileges of a token.<br>However, if you are using an application or system service that dynamically adjusts token privileges, we do not recommend Success auditing because of the high volume of event “[4703](event-4703.md)(S): A user right was adjusted” that may be generated. As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is System Center Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from **svchost.exe**).<br>If one of your applications or services is generating a large number of 4703 events, you might find that your event-management software has filtering logic that can automatically discard the recurring events, which would make it easier to work with Success auditing for this category.<br>This subcategory doesn’t have Failure events, so there is no recommendation to enable Failure auditing for this subcategory. |
|
||||
| Member Server | IF | No | IF | No | IF – With Success auditing for this subcategory, you can get information related to changes to the privileges of a token.<br>However, if you are using an application or system service that dynamically adjusts token privileges, we do not recommend Success auditing because of the high volume of event “[4703](event-4703.md)(S): A user right was adjusted” that may be generated. As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is System Center Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from **svchost.exe**).<br>If one of your applications or services is generating a large number of 4703 events, you might find that your event-management software has filtering logic that can automatically discard the recurring events, which would make it easier to work with Success auditing for this category.<br>This subcategory doesn’t have Failure events, so there is no recommendation to enable Failure auditing for this subcategory. |
|
||||
| Workstation | IF | No | IF | No | IF – With Success auditing for this subcategory, you can get information related to changes to the privileges of a token.<br>However, if you are using an application or system service that dynamically adjusts token privileges, we do not recommend Success auditing because of the high volume of event “[4703](event-4703.md)(S): A user right was adjusted” that may be generated. As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is System Center Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from **svchost.exe**).<br>If one of your applications or services is generating a large number of 4703 events, you might find that your event-management software has filtering logic that can automatically discard the recurring events, which would make it easier to work with Success auditing for this category.<br>This subcategory doesn’t have Failure events, so there is no recommendation to enable Failure auditing for this subcategory. |
|
||||
| Domain Controller | IF | No | IF | No | IF – With Success auditing for this subcategory, you can get information related to changes to the privileges of a token.<br>However, if you are using an application or system service that dynamically adjusts token privileges, we do not recommend Success auditing because of the high volume of event “[4703](event-4703.md)(S): A user right was adjusted” that may be generated. As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is Microsoft Endpoint Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from **svchost.exe**).<br>If one of your applications or services is generating a large number of 4703 events, you might find that your event-management software has filtering logic that can automatically discard the recurring events, which would make it easier to work with Success auditing for this category.<br>This subcategory doesn’t have Failure events, so there is no recommendation to enable Failure auditing for this subcategory. |
|
||||
| Member Server | IF | No | IF | No | IF – With Success auditing for this subcategory, you can get information related to changes to the privileges of a token.<br>However, if you are using an application or system service that dynamically adjusts token privileges, we do not recommend Success auditing because of the high volume of event “[4703](event-4703.md)(S): A user right was adjusted” that may be generated. As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is Microsoft Endpoint Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from **svchost.exe**).<br>If one of your applications or services is generating a large number of 4703 events, you might find that your event-management software has filtering logic that can automatically discard the recurring events, which would make it easier to work with Success auditing for this category.<br>This subcategory doesn’t have Failure events, so there is no recommendation to enable Failure auditing for this subcategory. |
|
||||
| Workstation | IF | No | IF | No | IF – With Success auditing for this subcategory, you can get information related to changes to the privileges of a token.<br>However, if you are using an application or system service that dynamically adjusts token privileges, we do not recommend Success auditing because of the high volume of event “[4703](event-4703.md)(S): A user right was adjusted” that may be generated. As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is Microsoft Endpoint Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from **svchost.exe**).<br>If one of your applications or services is generating a large number of 4703 events, you might find that your event-management software has filtering logic that can automatically discard the recurring events, which would make it easier to work with Success auditing for this category.<br>This subcategory doesn’t have Failure events, so there is no recommendation to enable Failure auditing for this subcategory. |
|
||||
|
||||
**Events List:**
|
||||
|
||||
|
@ -158,7 +158,7 @@ This event generates when a logon session is created (on destination machine). I
|
||||
|
||||
- **Restricted Admin Mode** \[Version 2\] \[Type = UnicodeString\]**:** Only populated for **RemoteInteractive** logon type sessions. This is a Yes/No flag indicating if the credentials provided were passed using Restricted Admin mode. Restricted Admin mode was added in Win8.1/2012R2 but this flag was added to the event in Win10.
|
||||
|
||||
Reference: <http://blogs.technet.com/b/kfalde/archive/2013/08/14/restricted-admin-mode-for-rdp-in-windows-8-1-2012-r2.aspx>.
|
||||
Reference: <https://blogs.technet.com/b/kfalde/archive/2013/08/14/restricted-admin-mode-for-rdp-in-windows-8-1-2012-r2.aspx>.
|
||||
|
||||
If not a **RemoteInteractive** logon, then this will be "-" string.
|
||||
|
||||
|
@ -26,7 +26,7 @@ ms.author: dansimp
|
||||
|
||||
***Event Description:***
|
||||
|
||||
This event generates when [token privileges](https://msdn.microsoft.com/library/windows/desktop/aa446619(v=vs.85).aspx) were enabled or disabled for a specific account’s token. As of Windows 10, event 4703 is also logged by applications or services that dynamically adjust token privileges. An example of such an application is System Center Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from svchost.exe). If you are using an application or system service that makes changes to system privileges through the AdjustPrivilegesToken API, you might need to disable Success auditing for this subcategory (Audit Authorization Policy Change), or work with a very high volume of event 4703.
|
||||
This event generates when [token privileges](https://msdn.microsoft.com/library/windows/desktop/aa446619(v=vs.85).aspx) were enabled or disabled for a specific account’s token. As of Windows 10, event 4703 is also logged by applications or services that dynamically adjust token privileges. An example of such an application is Microsoft Endpoint Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from svchost.exe). If you are using an application or system service that makes changes to system privileges through the AdjustPrivilegesToken API, you might need to disable Success auditing for this subcategory (Audit Authorization Policy Change), or work with a very high volume of event 4703.
|
||||
|
||||
> **Note** For recommendations, see [Security Monitoring Recommendations](#security-monitoring-recommendations) for this event.
|
||||
|
||||
@ -185,7 +185,7 @@ Token privileges provide the ability to take certain system-level actions that y
|
||||
|
||||
For 4703(S): A user right was adjusted.
|
||||
|
||||
As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is System Center Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from svchost.exe). If you are using an application or system service that makes changes to system privileges through the AdjustPrivilegesToken API, you might need to disable Success auditing for this subcategory, [Audit Authorization Policy Change](audit-authorization-policy-change.md), or work with a very high volume of event 4703.
|
||||
As of Windows 10, event 4703 is generated by applications or services that dynamically adjust token privileges. An example of such an application is Microsoft Endpoint Configuration Manager, which makes WMI queries at recurring intervals and quickly generates a large number of 4703 events (with the WMI activity listed as coming from svchost.exe). If you are using an application or system service that makes changes to system privileges through the AdjustPrivilegesToken API, you might need to disable Success auditing for this subcategory, [Audit Authorization Policy Change](audit-authorization-policy-change.md), or work with a very high volume of event 4703.
|
||||
|
||||
Otherwise, see the recommendations in the following table.
|
||||
|
||||
|
@ -30,7 +30,7 @@ This event generates each time the [Password Policy Checking API](https://msdn.m
|
||||
|
||||
The Password Policy Checking API allows an application to check password compliance against an application-provided account database or single account and verify that passwords meet the complexity, aging, minimum length, and history reuse requirements of a password policy.
|
||||
|
||||
This event, for example, generates during Directory Services Restore Mode ([DSRM](http://blogs.technet.com/b/askds/archive/2009/03/11/ds-restore-mode-password-maintenance.aspx)) account password reset procedure to check new DSRM password.
|
||||
This event, for example, generates during Directory Services Restore Mode ([DSRM](https://blogs.technet.com/b/askds/archive/2009/03/11/ds-restore-mode-password-maintenance.aspx)) account password reset procedure to check new DSRM password.
|
||||
|
||||
This event generates on the computer where Password Policy Checking API was called.
|
||||
|
||||
|
@ -34,7 +34,7 @@ This event is always logged regardless of the "Audit Policy Change" sub-category
|
||||
|
||||
More information about Special Groups auditing can be found here:
|
||||
|
||||
<http://blogs.technet.com/b/askds/archive/2008/03/11/special-groups-auditing-via-group-policy-preferences.aspx>
|
||||
<https://blogs.technet.com/b/askds/archive/2008/03/11/special-groups-auditing-via-group-policy-preferences.aspx>
|
||||
|
||||
<https://support.microsoft.com/kb/947223>
|
||||
|
||||
|
@ -26,7 +26,7 @@ ms.author: dansimp
|
||||
|
||||
***Event Description:***
|
||||
|
||||
This event generates when [resource attributes](http://blogs.technet.com/b/canitpro/archive/2013/05/07/step-by-step-protecting-your-information-with-dynamic-access-control.aspx) of the file system object were changed.
|
||||
This event generates when [resource attributes](https://blogs.technet.com/b/canitpro/archive/2013/05/07/step-by-step-protecting-your-information-with-dynamic-access-control.aspx) of the file system object were changed.
|
||||
|
||||
Resource attributes for file or folder can be changed, for example, using Windows File Explorer (object’s Properties->Classification tab).
|
||||
|
||||
|
@ -26,7 +26,7 @@ ms.author: dansimp
|
||||
|
||||
***Event Description:***
|
||||
|
||||
This event occurs when an account that is a member of any defined [Special Group](http://blogs.technet.com/b/askds/archive/2008/03/11/special-groups-auditing-via-group-policy-preferences.aspx) logs in.
|
||||
This event occurs when an account that is a member of any defined [Special Group](https://blogs.technet.com/b/askds/archive/2008/03/11/special-groups-auditing-via-group-policy-preferences.aspx) logs in.
|
||||
|
||||
> **Note** For recommendations, see [Security Monitoring Recommendations](#security-monitoring-recommendations) for this event.
|
||||
|
||||
@ -94,7 +94,7 @@ This event occurs when an account that is a member of any defined [Special Group
|
||||
|
||||
> S-1-5-32-544;S-1-5-32-123-54-65
|
||||
|
||||
> For more information see: <http://blogs.technet.com/b/askds/archive/2008/03/11/special-groups-auditing-via-group-policy-preferences.aspx>
|
||||
> For more information see: <https://blogs.technet.com/b/askds/archive/2008/03/11/special-groups-auditing-via-group-policy-preferences.aspx>
|
||||
|
||||
***Field Descriptions:***
|
||||
|
||||
|
@ -28,9 +28,9 @@ For more information about Cryptographic Next Generation (CNG) visit these pages
|
||||
|
||||
- <https://msdn.microsoft.com/library/windows/desktop/bb204775(v=vs.85).aspx>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=1251>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=1251>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=30688>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=30688>
|
||||
|
||||
This event is mainly used for Cryptographic Next Generation (CNG) troubleshooting.
|
||||
|
||||
|
@ -28,9 +28,9 @@ For more information about Cryptographic Next Generation (CNG) visit these pages
|
||||
|
||||
- <https://msdn.microsoft.com/library/windows/desktop/bb204775(v=vs.85).aspx>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=1251>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=1251>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=30688>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=30688>
|
||||
|
||||
This event is mainly used for Cryptographic Next Generation (CNG) troubleshooting.
|
||||
|
||||
|
@ -28,9 +28,9 @@ For more information about Cryptographic Next Generation (CNG) visit these pages
|
||||
|
||||
- <https://msdn.microsoft.com/library/windows/desktop/bb204775(v=vs.85).aspx>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=1251>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=1251>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=30688>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=30688>
|
||||
|
||||
This event is mainly used for Cryptographic Next Generation (CNG) troubleshooting.
|
||||
|
||||
|
@ -28,9 +28,9 @@ For more information about Cryptographic Next Generation (CNG) visit these pages
|
||||
|
||||
- <https://msdn.microsoft.com/library/windows/desktop/aa376214(v=vs.85).aspx>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=1251>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=1251>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=30688>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=30688>
|
||||
|
||||
This event is mainly used for Cryptographic Next Generation (CNG) troubleshooting.
|
||||
|
||||
|
@ -28,9 +28,9 @@ For more information about Cryptographic Next Generation (CNG) visit these pages
|
||||
|
||||
- <https://msdn.microsoft.com/library/windows/desktop/aa376214(v=vs.85).aspx>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=1251>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=1251>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=30688>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=30688>
|
||||
|
||||
This event is mainly used for Cryptographic Next Generation (CNG) troubleshooting.
|
||||
|
||||
|
@ -28,9 +28,9 @@ For more information about Cryptographic Next Generation (CNG) visit these pages
|
||||
|
||||
- <https://msdn.microsoft.com/library/windows/desktop/aa376214(v=vs.85).aspx>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=1251>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=1251>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=30688>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=30688>
|
||||
|
||||
This event is mainly used for Cryptographic Next Generation (CNG) troubleshooting.
|
||||
|
||||
|
@ -28,9 +28,9 @@ For more information about Cryptographic Next Generation (CNG) visit these pages
|
||||
|
||||
- <https://msdn.microsoft.com/library/windows/desktop/aa376214(v=vs.85).aspx>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=1251>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=1251>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=30688>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=30688>
|
||||
|
||||
This event is mainly used for Cryptographic Next Generation (CNG) troubleshooting.
|
||||
|
||||
|
@ -28,9 +28,9 @@ For more information about Cryptographic Next Generation (CNG) visit these pages
|
||||
|
||||
- <https://msdn.microsoft.com/library/windows/desktop/aa376214(v=vs.85).aspx>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=1251>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=1251>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=30688>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=30688>
|
||||
|
||||
This event is mainly used for Cryptographic Next Generation (CNG) troubleshooting.
|
||||
|
||||
|
@ -26,9 +26,9 @@ For more information about Cryptographic Next Generation (CNG) visit these pages
|
||||
|
||||
- <https://msdn.microsoft.com/library/windows/desktop/aa376214(v=vs.85).aspx>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=1251>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=1251>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=30688>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=30688>
|
||||
|
||||
This event is mainly used for Cryptographic Next Generation (CNG) troubleshooting.
|
||||
|
||||
|
@ -28,9 +28,9 @@ For more information about Cryptographic Next Generation (CNG) visit these pages
|
||||
|
||||
- <https://msdn.microsoft.com/library/windows/desktop/aa376214(v=vs.85).aspx>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=1251>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=1251>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=30688>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=30688>
|
||||
|
||||
This event is mainly used for Cryptographic Next Generation (CNG) troubleshooting.
|
||||
|
||||
|
@ -28,9 +28,9 @@ For more information about Cryptographic Next Generation (CNG) visit these pages
|
||||
|
||||
- <https://msdn.microsoft.com/library/windows/desktop/aa376214(v=vs.85).aspx>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=1251>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=1251>
|
||||
|
||||
- <http://www.microsoft.com/en-us/download/details.aspx?id=30688>
|
||||
- <https://www.microsoft.com/download/details.aspx?id=30688>
|
||||
|
||||
This event is mainly used for Cryptographic Next Generation (CNG) troubleshooting.
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Monitor central access policies on a file server (Windows 10)
|
||||
description: Learn how to monitor changes to the central access policies that apply to a file server, when using advanced security auditing options.
|
||||
description: Learn how to monitor changes to the central access policies that apply to a file server when using advanced security auditing options.
|
||||
ms.assetid: 126b051e-c20d-41f1-b42f-6cff24dcf20c
|
||||
ms.reviewer:
|
||||
ms.author: dansimp
|
||||
@ -22,40 +22,42 @@ ms.date: 04/19/2017
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
|
||||
This topic for the IT professional describes how to monitor changes to the central access policies that apply to a file server when using advanced security auditing options to monitor dynamic access control objects. Central access policies are created on a domain controller and then applied to file servers through Group Policy management.
|
||||
This article describes how to monitor changes to the central access policies (CAPs) that apply to a file server when using advanced security auditing options to monitor dynamic access control objects. CAPs are created on a domain controller and then applied to file servers through Group Policy management.
|
||||
|
||||
Use the following procedures to configure and verify security auditing settings that are used to monitor changes to the set of central access policies on a file server. The following procedures assume that you have configured and deployed dynamic access control, including central access policies, and claims in your network. If you have not yet deployed dynamic access control in your network, see [Deploy a Central Access Policy (Demonstration Steps)](https://technet.microsoft.com/library/hh846167.aspx).
|
||||
Use the following procedures to configure and verify security auditing settings that are used to monitor changes to the set of CAPs on a file server. The following procedures assume that you have configured and deployed dynamic access control, including CAPs and claims, in your network. If you have not yet deployed dynamic access control in your network, see [Deploy a Central Access Policy (Demonstration Steps)](https://technet.microsoft.com/library/hh846167.aspx).
|
||||
|
||||
**To configure settings to monitor changes to central access policies**
|
||||
|
||||
1. Sign in to your domain controller by using domain administrator credentials.
|
||||
2. In Server Manager, point to **Tools**, and then click **Group Policy Management**.
|
||||
3. In the console tree, right-click the flexible access Group Policy Object, and then click **Edit**.
|
||||
4. Double-click **Computer Configuration**, double-click **Security Settings**, double-click **Advanced Audit Policy Configuration**, double-click **Policy Change**, and then double-click **Other Policy Change Events**.
|
||||
2. In Server Manager, point to **Tools**, and then select **Group Policy Management**.
|
||||
3. In the console tree, select the flexible access Group Policy Object, and then select **Edit**.
|
||||
4. Select **Computer Configuration** > **Security Settings** > **Advanced Audit Policy Configuration** > **Policy Change** > **Other Policy Change Events**.
|
||||
|
||||
>**Note:** This policy setting monitors policy changes that might not be captured otherwise, such as central access policy changes or trusted platform module configuration changes.
|
||||
> [!NOTE]
|
||||
> This policy setting monitors policy changes that might not be captured otherwise, such as CAP changes or trusted platform module configuration changes.
|
||||
|
||||
5. Select the **Configure the following audit events** check box, select the **Success** check box (and the **Failure** check box, if desired), and then click **OK**.
|
||||
5. Select the **Configure the following audit events** check box, select the **Success** check box (and the **Failure** check box, if desired), and then select **OK**.
|
||||
|
||||
After you modify the central access policies on the domain controller, verify that the changes have been applied to the file server and that the proper events are logged.
|
||||
After you modify the CAPs on the domain controller, verify that the changes have been applied to the file server and that the proper events are logged.
|
||||
|
||||
**To verify changes to the central access policies**
|
||||
|
||||
1. Sign in to your domain controller by using domain administrator credentials.
|
||||
2. Open the Group Policy Management Console.
|
||||
3. Right-click **Default domain policy**, and then click **Edit**.
|
||||
4. Double-click **Computer Configuration**, double-click **Policies**, and then double-click **Windows Settings**.
|
||||
5. Double-click **Security Settings**, right-click **File system**, and then click **Manage CAPs**.
|
||||
6. In the wizard that appears, follow the instructions to add a new central access policy (CAP), and then click **OK**.
|
||||
7. Use local administrator credentials to sign in to the server that hosts resources that are subject to the central access policies you changed.
|
||||
8. Press the Windows key + R, then type **cmd** to open a Command Prompt window.
|
||||
3. Select **Default domain policy**, and then select **Edit**.
|
||||
4. Select **Computer Configuration** > **Policies**, and then select **Windows Settings**.
|
||||
5. Select **Security Settings** > **File system**, and then select **Manage CAPs**.
|
||||
6. In the wizard that appears, follow the instructions to add a new CAP, and then select **OK**.
|
||||
7. Use local administrator credentials to sign in to the server that hosts resources that are subject to the CAPs you changed.
|
||||
8. Select the Windows logo key+R, and then type **cmd** to open a command prompt window.
|
||||
|
||||
>**Note:** If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click **Yes**.
|
||||
> [!NOTE]
|
||||
> If the **User Account Control** dialog box appears, confirm that the action it displays is what you want, and then select **Yes**.
|
||||
|
||||
9. Type **gpupdate /force**, and press ENTER.
|
||||
10. In Server Manager, click **Tools**, and then click **Event Viewer**.
|
||||
11. Expand **Windows Logs**, and then click **Security**. Verify that event 4819 appears in the security log.
|
||||
9. Type **gpupdate /force**, and then select the Enter key.
|
||||
10. In Server Manager, select **Tools**, and then select **Event Viewer**.
|
||||
11. Expand **Windows Logs**, and then select **Security**. Verify that event 4819 appears in the security log.
|
||||
|
||||
## Related resource
|
||||
## Related resources
|
||||
|
||||
- [Using advanced security auditing options to monitor dynamic access control objects](using-advanced-security-auditing-options-to-monitor-dynamic-access-control-objects.md)
|
||||
|
@ -26,15 +26,12 @@ This can cause devices or software to malfunction and in rare cases may result i
|
||||
If this happens, see [Troubleshooting](#troubleshooting) for remediation steps.
|
||||
|
||||
>[!NOTE]
|
||||
>HVCI works with modern 7th gen CPUs or higher and its equivalent on AMD. CPU new feature is required *Mode based execution control (MBE) Virtualization*. AMD CPUs do not have MBE.
|
||||
|
||||
>[!TIP]
|
||||
> "The Secure Kernel relies on the Mode-Based Execution Control (MBEC) feature, if present in hardware, which enhances the SLAT with a user/kernel executable bit, or the hypervisor’s software emulation of this feature, called Restricted User Mode (RUM)." Mark Russinovich and Alex Ionescu. Windows Internals 7th Edition book
|
||||
>Because it makes use of *Mode Based Execution Control*, HVCI works better with Intel Kaby Lake or AMD Zen 2 CPUs and newer. Processors without MBEC will rely on an emulation of this feature, called *Restricted User Mode*, which has a bigger impact on performance.
|
||||
|
||||
## HVCI Features
|
||||
|
||||
* HVCI protects modification of the Code Flow Guard (CFG) bitmap.
|
||||
* HVCI also ensure your other Truslets, like Credential Guard have a valid certificate.
|
||||
* HVCI protects modification of the Control Flow Guard (CFG) bitmap.
|
||||
* HVCI also ensure your other Truslets, like Credential Guard, have a valid certificate.
|
||||
* Modern device drivers must also have an EV (Extended Validation) certificate and should support HVCI.
|
||||
|
||||
## How to turn on HVCI in Windows 10
|
||||
@ -43,7 +40,7 @@ To enable HVCI on Windows 10 devices with supporting hardware throughout an ente
|
||||
- [Windows Security app](#windows-security-app)
|
||||
- [Microsoft Intune (or another MDM provider)](#enable-hvci-using-intune)
|
||||
- [Group Policy](#enable-hvci-using-group-policy)
|
||||
- [System Center Configuration Manager](https://cloudblogs.microsoft.com/enterprisemobility/2015/10/30/managing-windows-10-device-guard-with-configuration-manager/)
|
||||
- [Microsoft Endpoint Configuration Manager](https://cloudblogs.microsoft.com/enterprisemobility/2015/10/30/managing-windows-10-device-guard-with-configuration-manager/)
|
||||
- [Registry](#use-registry-keys-to-enable-virtualization-based-protection-of-code-integrity)
|
||||
|
||||
### Windows Security app
|
||||
|
@ -40,7 +40,7 @@ The toolkit supports formats created by the Windows GPO backup feature (.pol, .i
|
||||
|
||||
Not yet. PowerShell-based DSC is rapidly gaining popularity, and more DSC tools are coming online to convert GPOs and DSC and to validate system configuration. We are currently developing a tool to provide customers with these features.
|
||||
|
||||
**Does SCT support the creation of System Center Configuration Manager (SCCM) DCM packs?**
|
||||
**Does SCT support the creation of Microsoft Endpoint Configuration Manager DCM packs?**
|
||||
|
||||
No. A potential alternative is Desired State Configuration (DSC), a feature of the [Windows Management Framework](https://www.microsoft.com/download/details.aspx?id=40855). A tool that supports conversion of GPO backups to DSC format can be found [here](https://github.com/Microsoft/BaselineManagement).
|
||||
|
||||
|
Before Width: | Height: | Size: 1.9 KiB |
Before Width: | Height: | Size: 2.4 KiB |
Before Width: | Height: | Size: 2.8 KiB |
Before Width: | Height: | Size: 2.5 KiB |
Before Width: | Height: | Size: 2.0 KiB |
BIN
windows/security/threat-protection/images/air-icon.png
Normal file
After Width: | Height: | Size: 2.2 KiB |
BIN
windows/security/threat-protection/images/asr-icon.png
Normal file
After Width: | Height: | Size: 1.5 KiB |
BIN
windows/security/threat-protection/images/edr-icon.png
Normal file
After Width: | Height: | Size: 1.6 KiB |
BIN
windows/security/threat-protection/images/mte-icon.png
Normal file
After Width: | Height: | Size: 2.1 KiB |
BIN
windows/security/threat-protection/images/ngp-icon.png
Normal file
After Width: | Height: | Size: 1.7 KiB |
@ -23,12 +23,11 @@ ms.topic: conceptual
|
||||
<table>
|
||||
<tr>
|
||||
<td><a href="#tvm"><center><img src="images/TVM_icon.png"> <br><b>Threat & Vulnerability Management</b></center></a></td>
|
||||
<td><a href="#asr"><center><img src="images/ASR_icon.png"> <br><b>Attack surface reduction</b></center></a></td>
|
||||
<td><center><a href="#ngp"><img src="images/NGP_icon.png"><br> <b>Next generation protection</b></a></center></td>
|
||||
<td><center><a href="#edr"><img src="images/EDR_icon.png"><br> <b>Endpoint detection and response</b></a></center></td>
|
||||
<td><center><a href="#ai"><img src="images/AR_icon.png"><br> <b>Automated investigation and remediation</b></a></center></td>
|
||||
<td><center><a href="#ss"><img src="images/SS_icon.png"><br><b>Secure score</b></a></center></td>
|
||||
<td><center><a href="#mte"><img src="images/MTE_icon.png"><br> <b>Microsoft Threat Experts</b></a></center></td>
|
||||
<td><a href="#asr"><center><img src="images/asr-icon.png"> <br><b>Attack surface reduction</b></center></a></td>
|
||||
<td><center><a href="#ngp"><img src="images/ngp-icon.png"><br> <b>Next generation protection</b></a></center></td>
|
||||
<td><center><a href="#edr"><img src="images/edr-icon.png"><br> <b>Endpoint detection and response</b></a></center></td>
|
||||
<td><center><a href="#ai"><img src="images/air-icon.png"><br> <b>Automated investigation and remediation</b></a></center></td>
|
||||
<td><center><a href="#mte"><img src="images/mte-icon.png"><br> <b>Microsoft Threat Experts</b></a></center></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td colspan="7">
|
||||
|
@ -29,8 +29,12 @@ Advanced hunting is a query-based threat-hunting tool that lets you explore up t
|
||||
You can use the same threat-hunting queries to build custom detection rules. These rules run automatically to check for and respond to various events and system states, including suspected breach activity and misconfigured machines.
|
||||
|
||||
## Get started with advanced hunting
|
||||
Watch this video for a quick overview of advanced hunting and a short tutorial that will get you started fast.
|
||||
<p></p>
|
||||
|
||||
We recommend going through several steps to quickly get up and running with advanced hunting.
|
||||
> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4bGqo]
|
||||
|
||||
You can also go through each of the following steps to ramp up your advanced hunting knowledge.
|
||||
|
||||
| Learning goal | Description | Resource |
|
||||
|--|--|--|
|
||||
|
@ -40,7 +40,7 @@ For information on other tables in the advanced hunting schema, see [the advance
|
||||
| `OSPlatform` | string | Platform of the operating system running on the machine. This indicates specific operating systems, including variations within the same family, such as Windows 10 and Windows 7. |
|
||||
| `OSVersion` | string | Version of the operating system running on the machine |
|
||||
| `OSArchitecture` | string | Architecture of the operating system running on the machine |
|
||||
| `SoftwareVendor` | string | Severity level assigned to the security vulnerability based on the CVSS score and dynamic factors influenced by the threat landscape |
|
||||
| `SoftwareVendor` | string | Name of the software vendor |
|
||||
| `SoftwareName` | string | Name of the software product |
|
||||
| `SoftwareVersion` | string | Version number of the software product |
|
||||
| `CveId` | string | Unique identifier assigned to the security vulnerability under the Common Vulnerabilities and Exposures (CVE) system |
|
||||
|
@ -26,6 +26,9 @@ ms.topic: conceptual
|
||||
|
||||
Microsoft Defender ATP 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 Microsoft Defender ATP capabilities. The API access requires OAuth2.0 authentication. For more information, see [OAuth 2.0 Authorization Code Flow](https://docs.microsoft.com/azure/active-directory/develop/active-directory-v2-protocols-oauth-code).
|
||||
|
||||
Watch this video for a quick overview of Microsoft Defender ATP's APIs.
|
||||
>[!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4d73M]
|
||||
|
||||
In general, you’ll need to take the following steps to use the APIs:
|
||||
- Create an AAD application
|
||||
- Get an access token using this application
|
||||
|
@ -81,7 +81,7 @@ The "engine version" of attack surface reduction events in the event log, is gen
|
||||
|
||||
## Attack surface reduction rules
|
||||
|
||||
The following sections describe each of the 15 attack surface reduction rules. This table shows their corresponding GUIDs, which you use if you're configuring the rules with Group Policy or PowerShell. If you use System Center Configuration Manager or Microsoft Intune, you do not need the GUIDs:
|
||||
The following sections describe each of the 15 attack surface reduction rules. This table shows their corresponding GUIDs, which you use if you're configuring the rules with Group Policy or PowerShell. If you use Microsoft Endpoint Configuration Manager or Microsoft Intune, you do not need the GUIDs:
|
||||
|
||||
Rule name | GUID | File & folder exclusions
|
||||
-----------|------|--------------------------
|
||||
@ -110,11 +110,11 @@ This rule blocks the following file types from launching from email in Microsoft
|
||||
* Executable files (such as .exe, .dll, or .scr)
|
||||
* Script files (such as a PowerShell .ps, VisualBasic .vbs, or JavaScript .js file)
|
||||
|
||||
This rule was introduced in: Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
|
||||
This rule was introduced in: Windows 10 1709, Windows Server 1809, Windows Server 2019, Microsoft Endpoint Configuration Manager CB 1710
|
||||
|
||||
Intune name: Execution of executable content (exe, dll, ps, js, vbs, etc.) dropped from email (webmail/mail client) (no exceptions)
|
||||
|
||||
SCCM name: Block executable content from email client and webmail
|
||||
Microsoft Endpoint Configuration Manager name: Block executable content from email client and webmail
|
||||
|
||||
GUID: BE9BA2D9-53EA-4CDC-84E5-9B1EEEE46550
|
||||
|
||||
@ -124,19 +124,19 @@ This rule blocks Office apps from creating child processes. This includes Word,
|
||||
|
||||
This is a typical malware behavior, especially malware that abuses Office as a vector, using VBA macros and exploit code to download and attempt to run additional payload. Some legitimate line-of-business applications might also use behaviors like this, including spawning a command prompt or using PowerShell to configure registry settings.
|
||||
|
||||
This rule was introduced in: Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
|
||||
This rule was introduced in: Windows 10 1709, Windows Server 1809, Windows Server 2019, Configuration Manager CB 1710
|
||||
|
||||
Intune name: Office apps launching child processes
|
||||
|
||||
SCCM name: Block Office application from creating child processes
|
||||
Configuration Manager name: Block Office application from creating child processes
|
||||
|
||||
GUID: D4F940AB-401B-4EFC-AADC-AD5F3C50688A
|
||||
|
||||
### Block Office applications from creating executable content
|
||||
|
||||
This rule prevents Office apps, including Word, Excel, and PowerPoint, from creating executable content.
|
||||
This rule prevents Office apps, including Word, Excel, and PowerPoint, from creating potentially malicious executable content, by blocking malicious code from being written to disk.
|
||||
|
||||
This rule targets a typical behavior where malware uses Office as a vector to break out of Office and save malicious components to disk, where they persist and survive a computer reboot. This rule prevents malicious code from being written to disk.
|
||||
Malware that abuse Office as a vector may attempt to break out of Office and save malicious components to disk. These malicious components would survive a computer reboot and persist on the system. Therefore, this rule defends against a common persistence technique.
|
||||
|
||||
This rule was introduced in: Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
|
||||
|
||||
@ -152,11 +152,11 @@ Attackers might attempt to use Office apps to migrate malicious code into other
|
||||
|
||||
This rule applies to Word, Excel, and PowerPoint.
|
||||
|
||||
This rule was introduced in: Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
|
||||
This rule was introduced in: Windows 10 1709, Windows Server 1809, Windows Server 2019, Configuration Manager CB 1710
|
||||
|
||||
Intune name: Office apps injecting code into other processes (no exceptions)
|
||||
|
||||
SCCM name: Block Office applications from injecting code into other processes
|
||||
Configuration Manager name: Block Office applications from injecting code into other processes
|
||||
|
||||
GUID: 75668C1F-73B5-4CF0-BB93-3ECF5CB7CC84
|
||||
|
||||
@ -169,11 +169,11 @@ Malware written in JavaScript or VBS often acts as a downloader to fetch and lau
|
||||
> [!IMPORTANT]
|
||||
> File and folder exclusions don't apply to this attack surface reduction rule.
|
||||
|
||||
This rule was introduced in: Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
|
||||
This rule was introduced in: Windows 10 1709, Windows Server 1809, Windows Server 2019, Configuration Manager CB 1710
|
||||
|
||||
Intune name: js/vbs executing payload downloaded from Internet (no exceptions)
|
||||
|
||||
SCCM name: Block JavaScript or VBScript from launching downloaded executable content
|
||||
Configuration Manager name: Block JavaScript or VBScript from launching downloaded executable content
|
||||
|
||||
GUID: D3E037E1-3EB8-44C8-A917-57927947596D
|
||||
|
||||
@ -181,11 +181,11 @@ GUID: D3E037E1-3EB8-44C8-A917-57927947596D
|
||||
|
||||
Script obfuscation is a common technique that both malware authors and legitimate applications use to hide intellectual property or decrease script loading times. This rule detects suspicious properties within an obfuscated script.
|
||||
|
||||
This rule was introduced in: Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
|
||||
This rule was introduced in: Windows 10 1709, Windows Server 1809, Windows Server 2019, Configuration Manager CB 1710
|
||||
|
||||
Intune name: Obfuscated js/vbs/ps/macro code
|
||||
|
||||
SCCM name: Block execution of potentially obfuscated scripts.
|
||||
Configuration Manager name: Block execution of potentially obfuscated scripts.
|
||||
|
||||
GUID: 5BEB7EFE-FD9A-4556-801D-275E5FFC04CC
|
||||
|
||||
@ -193,11 +193,11 @@ GUID: 5BEB7EFE-FD9A-4556-801D-275E5FFC04CC
|
||||
|
||||
Office VBA provides the ability to use Win32 API calls, which malicious code can abuse. Most organizations don't use this functionality, but might still rely on using other macro capabilities. This rule allows you to prevent using Win32 APIs in VBA macros, which reduces the attack surface.
|
||||
|
||||
This rule was introduced in: Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
|
||||
This rule was introduced in: Windows 10 1709, Windows Server 1809, Windows Server 2019, Configuration Manager CB 1710
|
||||
|
||||
Intune name: Win32 imports from Office macro code
|
||||
|
||||
SCCM name: Block Win32 API calls from Office macros
|
||||
Configuration Manager name: Block Win32 API calls from Office macros
|
||||
|
||||
GUID: 92E97FA1-2EDF-4476-BDD6-9DD0B4DDDC7B
|
||||
|
||||
@ -215,11 +215,11 @@ This rule blocks the following file types from launching unless they either meet
|
||||
>
|
||||
>You can specify individual files or folders (using folder paths or fully qualified resource names) but you can't specify which rules or exclusions apply to.
|
||||
|
||||
This rule was introduced in: Windows 10 1803, Windows Server 1809, Windows Server 2019, SCCM CB 1802
|
||||
This rule was introduced in: Windows 10 1803, Windows Server 1809, Windows Server 2019, Configuration Manager CB 1802
|
||||
|
||||
Intune name: Executables that don't meet a prevalence, age, or trusted list criteria.
|
||||
|
||||
SCCM name: Block executable files from running unless they meet a prevalence, age, or trusted list criteria
|
||||
Configuration Manager name: Block executable files from running unless they meet a prevalence, age, or trusted list criteria
|
||||
|
||||
GUID: 01443614-cd74-433a-b99e-2ecdc07bfc25
|
||||
|
||||
@ -230,11 +230,11 @@ This rule provides an extra layer of protection against ransomware. It scans exe
|
||||
> [!NOTE]
|
||||
> You must [enable cloud-delivered protection](../windows-defender-antivirus/enable-cloud-protection-windows-defender-antivirus.md) to use this rule.
|
||||
|
||||
This rule was introduced in: Windows 10 1803, Windows Server 1809, Windows Server 2019, SCCM CB 1802
|
||||
This rule was introduced in: Windows 10 1803, Windows Server 1809, Windows Server 2019, Configuration Manager CB 1802
|
||||
|
||||
Intune name: Advanced ransomware protection
|
||||
|
||||
SCCM name: Use advanced protection against ransomware
|
||||
Configuration Manager name: Use advanced protection against ransomware
|
||||
|
||||
GUID: c1db55ab-c21a-4637-bb3f-a12568109d35
|
||||
|
||||
@ -245,11 +245,11 @@ Local Security Authority Subsystem Service (LSASS) authenticates users who log i
|
||||
> [!NOTE]
|
||||
> In some apps, the code enumerates all running processes and attempts to open them with exhaustive permissions. This rule denies the app's process open action and logs the details to the security event log. This rule can generate a lot of noise. If you have an app that overly enumerates LSASS, you need to add it to the exclusion list. By itself, this event log entry doesn't necessarily indicate a malicious threat.
|
||||
|
||||
This rule was introduced in: Windows 10 1803, Windows Server 1809, Windows Server 2019, SCCM CB 1802
|
||||
This rule was introduced in: Windows 10 1803, Windows Server 1809, Windows Server 2019, Configuration Manager CB 1802
|
||||
|
||||
Intune name: Flag credential stealing from the Windows local security authority subsystem
|
||||
|
||||
SCCM name: Block credential stealing from the Windows local security authority subsystem
|
||||
Configuration Manager name: Block credential stealing from the Windows local security authority subsystem
|
||||
|
||||
GUID: 9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2
|
||||
|
||||
@ -261,13 +261,13 @@ This rule blocks processes through PsExec and WMI commands from running, to prev
|
||||
> File and folder exclusions do not apply to this attack surface reduction rule.
|
||||
|
||||
> [!WARNING]
|
||||
> Only use this rule if you're managing your devices with [Intune](https://docs.microsoft.com/intune) or another MDM solution. This rule is incompatible with management through [System Center Configuration Manager](https://docs.microsoft.com/sccm) because this rule blocks WMI commands the SCCM client uses to function correctly.
|
||||
> Only use this rule if you're managing your devices with [Intune](https://docs.microsoft.com/intune) or another MDM solution. This rule is incompatible with management through [Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/configmgr) because this rule blocks WMI commands the Configuration Manager client uses to function correctly.
|
||||
|
||||
This rule was introduced in: Windows 10 1803, Windows Server 1809, Windows Server 2019
|
||||
|
||||
Intune name: Process creation from PSExec and WMI commands
|
||||
|
||||
SCCM name: Not applicable
|
||||
Configuration Manager name: Not applicable
|
||||
|
||||
GUID: d1e49aac-8f56-4280-b9ba-993a6d77406c
|
||||
|
||||
@ -278,11 +278,11 @@ With this rule, admins can prevent unsigned or untrusted executable files from r
|
||||
* Executable files (such as .exe, .dll, or .scr)
|
||||
* Script files (such as a PowerShell .ps, VisualBasic .vbs, or JavaScript .js file)
|
||||
|
||||
This rule was introduced in: Windows 10 1803, Windows Server 1809, Windows Server 2019, SCCM CB 1802
|
||||
This rule was introduced in: Windows 10 1803, Windows Server 1809, Windows Server 2019, Configuration Manager CB 1802
|
||||
|
||||
Intune name: Untrusted and unsigned processes that run from USB
|
||||
|
||||
SCCM name: Block untrusted and unsigned processes that run from USB
|
||||
Configuration Manager name: Block untrusted and unsigned processes that run from USB
|
||||
|
||||
GUID: b2b3f03d-6a65-4f7b-a9c7-1c7ef74a9ba4
|
||||
|
||||
@ -297,7 +297,7 @@ This rule was introduced in: Windows 10 1809, Windows Server 1809, Windows Serve
|
||||
|
||||
Intune name: Process creation from Office communication products (beta)
|
||||
|
||||
SCCM name: Not yet available
|
||||
Configuration Manager name: Not yet available
|
||||
|
||||
GUID: 26190899-1602-49e8-8b27-eb1d0a1ce869
|
||||
|
||||
@ -309,7 +309,7 @@ This rule was introduced in: Windows 10 1809, Windows Server 1809, Windows Serve
|
||||
|
||||
Intune name: Process creation from Adobe Reader (beta)
|
||||
|
||||
SCCM name: Not yet available
|
||||
Configuration Manager name: Not yet available
|
||||
|
||||
GUID: 7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c
|
||||
|
||||
@ -321,7 +321,7 @@ This rule was introduced in: Windows 10 1903, Windows Server 1903
|
||||
|
||||
Intune name: Block persistence through WMI event subscription
|
||||
|
||||
SCCM name: Not yet available
|
||||
Configuration Manager name: Not yet available
|
||||
|
||||
GUID: e6db77e5-3df2-4cf1-b95a-636979351e5b
|
||||
|
||||
|
@ -19,6 +19,8 @@ ms.topic: conceptual
|
||||
|
||||
# Overview of automated investigations
|
||||
|
||||
> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4bOeh]
|
||||
|
||||
Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP) offers a wide breadth of visibility on multiple machines. With this kind of optics, the service generates a multitude of alerts. The volume of alerts generated can be challenging for a typical security operations team to individually address. To address this challenge, Microsoft Defender ATP uses automated investigation and remediation capabilities to significantly reduce the volume of alerts that must 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. The **Automated investigations** list shows all the investigations that were initiated automatically, and includes details, such as status, detection source, and when the investigation was initiated.
|
||||
@ -26,10 +28,7 @@ The automated investigation feature leverages various inspection algorithms, and
|
||||
> [!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-automated-investigations-abovefoldlink)
|
||||
|
||||
|
||||
## Understand the automated investigation flow
|
||||
|
||||
### How the automated investigation starts
|
||||
## How the automated investigation starts
|
||||
|
||||
When an alert is triggered, a security playbook goes into effect. Depending on the security playbook, an automated investigation can start. For example, suppose a malicious file resides on a machine. When that file is detected, an alert is triggered. The automated investigation process begins. Microsoft Defender ATP checks to see if the malicious file is present on any other machines in the organization. Details from the investigation, including verdicts (Malicious, Suspicious, and Clean) are available during and after the automated investigation.
|
||||
|
||||
@ -40,7 +39,7 @@ When an alert is triggered, a security playbook goes into effect. Depending on t
|
||||
>- Windows 10, version 1803 (OS Build 17134.704 with [KB4493464](https://support.microsoft.com/help/4493464/windows-10-update-kb4493464)) or later
|
||||
>- Later versions of Windows 10
|
||||
|
||||
### Details of an automated investigation
|
||||
## Details of an automated investigation
|
||||
|
||||
During and after an automated investigation, you can view details about the investigation. Selecting a triggering alert brings you to the investigation details view where you can pivot from the **Investigation graph**, **Alerts**, **Machines**, **Evidence**, **Entities**, and **Log** tabs.
|
||||
|
||||
@ -56,13 +55,13 @@ During and after an automated investigation, you can view details about the inve
|
||||
> [!IMPORTANT]
|
||||
> Go to the **Action center** to get an aggregated view all pending actions and manage remediation actions. The **Action center** also acts as an audit trail for all automated investigation actions.
|
||||
|
||||
### How an automated investigation expands its scope
|
||||
## How an automated investigation expands its scope
|
||||
|
||||
While an investigation is running, any other alerts generated from the machine are added to an ongoing automated investigation until that investigation is completed. In addition, if the same threat is seen on other machines, those machines are added to the investigation.
|
||||
|
||||
If an incriminated entity is seen in another machine, the automated investigation process will expand its scope to include that machine, and a general security playbook will start on that machine. If 10 or more machines are found during this expansion process from the same entity, then that expansion action will require an approval and will be seen in the **Pending actions** view.
|
||||
|
||||
### How threats are remediated
|
||||
## How threats are remediated
|
||||
|
||||
Depending on how you set up the machine groups and their level of automation, the automated investigation will either require user approval (default) or automatically remediate threats.
|
||||
|
||||
|
@ -0,0 +1,83 @@
|
||||
---
|
||||
title: Common Microsoft Defender ATP API errors
|
||||
description: List of common Microsoft Defender ATP API errors with descriptions.
|
||||
keywords: apis, mdatp api, errors, troubleshooting
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
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
|
||||
---
|
||||
|
||||
# Common REST API error codes
|
||||
|
||||
* The error codes listed in the following table may be returned by an operation on any of Microsoft Defender ATP APIs.
|
||||
* Note that in addition to the error code, every error response contains an error message which can help resolving the problem.
|
||||
* Note that the message is a free text that can be changed.
|
||||
* At the bottom of the page you can find response examples.
|
||||
|
||||
Error code |HTTP status code |Message
|
||||
:---|:---|:---
|
||||
BadRequest | BadRequest (400) | General Bad Request error message.
|
||||
ODataError | BadRequest (400) | Invalid OData URI query (the specific error is specified).
|
||||
InvalidInput | BadRequest (400) | Invalid input {the invalid input}.
|
||||
InvalidRequestBody | BadRequest (400) | Invalid request body.
|
||||
InvalidHashValue | BadRequest (400) | Hash value {the invalid hash} is invalid.
|
||||
InvalidDomainName | BadRequest (400) | Domain name {the invalid domain} is invalid.
|
||||
InvalidIpAddress | BadRequest (400) | IP address {the invalid IP} is invalid.
|
||||
InvalidUrl | BadRequest (400) | URL {the invalid URL} is invalid.
|
||||
MaximumBatchSizeExceeded | BadRequest (400) | Maximum batch size exceeded. Received: {batch size received}, allowed: {batch size allowed}.
|
||||
MissingRequiredParameter | BadRequest (400) | Parameter {the missing parameter} is missing.
|
||||
OsPlatformNotSupported | BadRequest (400) | OS Platform {the client OS Platform} is not supported for this action.
|
||||
ClientVersionNotSupported | BadRequest (400) | {The requested action} is supported on client version {supported client version} and above.
|
||||
Unauthorized | Unauthorized (401) | Unauthorized (usually invalid or expired authorization header).
|
||||
Forbidden | Forbidden (403) | Forbidden (valid token but insufficient permission for the action).
|
||||
DisabledFeature | Forbidden (403) | Tenant feature is not enabled.
|
||||
DisallowedOperation | Forbidden (403) | {the disallowed operation and the reason}.
|
||||
NotFound | Not Found (404) | General Not Found error message.
|
||||
ResourceNotFound | Not Found (404) | Resource {the requested resource} was not found.
|
||||
InternalServerError | Internal Server Error (500) | (No error message, try retry the operation or contact us if it does not resolved)
|
||||
|
||||
## Body parameters are case sensitive
|
||||
|
||||
The submitted body parameters are currently case sensitive.
|
||||
<br>If you experience an **InvalidRequestBody** or **MissingRequiredParameter** errors, it might be caused from a wrong parameter capital or lower-case letter.
|
||||
<br>It is recommended to go to the requested Api documentation page and check that the submitted parameters match the relevant example.
|
||||
|
||||
## Correlation request ID
|
||||
|
||||
Each error response contains a unique ID parameter for tracking.
|
||||
<br>The property name of this parameter is "target".
|
||||
<br>When contacting us about an error, attaching this ID will help find the root cause of the problem.
|
||||
|
||||
## Examples
|
||||
|
||||
```json
|
||||
{
|
||||
"error": {
|
||||
"code": "ResourceNotFound",
|
||||
"message": "Machine 123123123 was not found",
|
||||
"target": "43f4cb08-8fac-4b65-9db1-745c2ae65f3a"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
```json
|
||||
{
|
||||
"error": {
|
||||
"code": "InvalidRequestBody",
|
||||
"message": "Request body is incorrect",
|
||||
"target": "1fa66c0f-18bd-4133-b378-36d76f3a2ba0"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
|
@ -28,6 +28,8 @@ ms.topic: article
|
||||
|
||||
Conditional Access is a capability that helps you better protect your users and enterprise information by making sure that only secure devices have access to applications.
|
||||
|
||||
> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4byD1]
|
||||
|
||||
With Conditional Access, you can control access to enterprise information based on the risk level of a device. This helps keep trusted users on trusted devices using trusted applications.
|
||||
|
||||
You can define security conditions under which devices and applications can run and access information from your network by enforcing policies to stop applications from running until a device returns to a compliant state.
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configure Threat & Vulnerability Management in Microsoft Defender ATP
|
||||
ms.reviewer:
|
||||
description: Configuring TVM's integration with Microsoft Intune and Microsoft System Center Configuration Manager (SCCM) helps security and IT admins collaborate seamlessly
|
||||
description: Configure your Threat & Vulnerability Management to allow security administrators and IT administrators to collaborate seamlessly to remediate issues via Microsoft intune and Microsoft Endpoint Configuration Manager integrations.
|
||||
keywords: RBAC, Threat & Vulnerability Management configuration, Threat & Vulnerability Management integrations, Microsft Intune integration with TVM, SCCM integration with TVM
|
||||
search.product: Windows 10
|
||||
search.appverid: met150
|
||||
@ -23,16 +23,16 @@ ms.topic: article
|
||||
|
||||
[!include[Prerelease information](../../includes/prerelease.md)]
|
||||
|
||||
This section guides you through the steps you need to take to configure Threat & Vulnerability Management's integration with Microsoft Intune or Microsoft System Center Configuration Manager (SCCM) for a seamless collaboration of issue remediation.
|
||||
This section guides you through the steps you need to take to configure Threat & Vulnerability Management's integration with Microsoft Intune or Microsoft Endpoint Configuration Manager for a seamless collaboration of issue remediation.
|
||||
|
||||
### Before you begin
|
||||
> [!IMPORTANT]
|
||||
> Threat & Vulnerability Management data currently supports Windows 10 machines. Upgrade to Windows 10 to account for the rest of your devices’ threat and vulnerability exposure data.</br>
|
||||
|
||||
Ensure that you have the right RBAC permissions to configure your Threat & Vulnerability Management integration with Microsoft Intune or Microsoft System Center Configuration Manager (SCCM).
|
||||
Ensure that you have the right RBAC permissions to configure your Threat & Vulnerability Management integration with Microsoft Intune or Microsoft Endpoint Configuration Manager.
|
||||
|
||||
>[!WARNING]
|
||||
>Only Intune and SCCM enrolled devices are supported in this scenario.</br>
|
||||
>Only Intune and Microsoft Endpoint Configuration Manager enrolled devices are supported in this scenario.</br>
|
||||
>Use any of the following options to enroll devices in Intune:
|
||||
>- IT Admin: For more information on how to enabling auto-enrollment, see [Windows Enrollment](https://docs.microsoft.com/intune/windows-enroll#enable-windows-10-automatic-enrollment)
|
||||
>- End-user: For more information on how to enroll your Windows 10 device in Intune, see [Enroll your Windows 10 device in Intune](https://docs.microsoft.com/intune-user-help/enroll-your-w10-device-access-work-or-school)
|
||||
|
@ -23,7 +23,7 @@ ms.date: 07/01/2018
|
||||
You can configure attack surface reduction with a number of tools, including:
|
||||
|
||||
* Microsoft Intune
|
||||
* System Center Configuration Manager
|
||||
* Microsoft Endpoint Configuration Manager
|
||||
* Group Policy
|
||||
* PowerShell cmdlets
|
||||
|
||||
|
@ -150,7 +150,7 @@ With Group Policy there isn’t an option to monitor deployment of policies on t
|
||||
|
||||
|
||||
## Related topics
|
||||
- [Onboard Windows 10 machines using System Center Configuration Manager](configure-endpoints-sccm.md)
|
||||
- [Onboard Windows 10 machines using Microsoft Endpoint Configuration Manager](configure-endpoints-sccm.md)
|
||||
- [Onboard Windows 10 machines using Mobile Device Management tools](configure-endpoints-mdm.md)
|
||||
- [Onboard Windows 10 machines using a local script](configure-endpoints-script.md)
|
||||
- [Onboard non-persistent virtual desktop infrastructure (VDI) machines](configure-endpoints-vdi.md)
|
||||
|
@ -86,7 +86,7 @@ For more information on Microsoft Intune policy settings see, [Windows 10 policy
|
||||
|
||||
## Related topics
|
||||
- [Onboard Windows 10 machines using Group Policy](configure-endpoints-gp.md)
|
||||
- [Onboard Windows 10 machines using System Center Configuration Manager](configure-endpoints-sccm.md)
|
||||
- [Onboard Windows 10 machines using Microsoft Endpoint Configuration Manager](configure-endpoints-sccm.md)
|
||||
- [Onboard Windows 10 machines using a local script](configure-endpoints-script.md)
|
||||
- [Onboard non-persistent virtual desktop infrastructure (VDI) machines](configure-endpoints-vdi.md)
|
||||
- [Run a detection test on a newly onboarded Microsoft Defender ATP machine](run-detection-test.md)
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Onboard Windows 10 machines using System Center Configuration Manager
|
||||
description: Use System Center Configuration Manager to deploy the configuration package on machines so that they are onboarded to the service.
|
||||
keywords: onboard machines using sccm, machine management, configure Windows ATP machines, configure Microsoft Defender Advanced Threat Protection machines, sccm
|
||||
title: Onboard Windows 10 machines using Configuration Manager
|
||||
description: Use Configuration Manager to deploy the configuration package on machines so that they are onboarded to the service.
|
||||
keywords: onboard machines using sccm, machine management, configure Windows ATP machines, configure Microsoft Defender Advanced Threat Protection machines
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
@ -15,43 +15,34 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 12/11/2018
|
||||
ms.date: 02/07/2020
|
||||
---
|
||||
|
||||
# Onboard Windows 10 machines using System Center Configuration Manager
|
||||
# Onboard Windows 10 machines using Configuration Manager
|
||||
|
||||
**Applies to:**
|
||||
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
- System Center 2012 Configuration Manager or later versions
|
||||
|
||||
|
||||
- Microsoft Endpoint Configuration Manager current branch
|
||||
- System Center 2012 R2 Configuration Manager
|
||||
|
||||
>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-configureendpointssccm-abovefoldlink)
|
||||
|
||||
<span id="sccm1606"/>
|
||||
## Onboard Windows 10 machines using System Center Configuration Manager (current branch) version 1606
|
||||
System Center Configuration Manager (SCCM) (current branch) version 1606, has UI integrated support for configuring and managing Microsoft Defender ATP on machines. For more information, see <a href="https://go.microsoft.com/fwlink/p/?linkid=823682" data-raw-source="[Support for Microsoft Defender Advanced Threat Protection service](https://go.microsoft.com/fwlink/p/?linkid=823682)">Support for Microsoft Defender Advanced Threat Protection service</a>.
|
||||
|
||||
>[!NOTE]
|
||||
> If you’re using SCCM client version 1606 with server version 1610 or above, you must upgrade the client version to match the server version.
|
||||
> Starting with version 1606 of Configuration Manager, see [Microsoft Defender Advanced Threat Protection](https://docs.microsoft.com/sccm/protect/deploy-use/windows-defender-advanced-threat-protection) for ATP configuration.
|
||||
## Onboard Windows 10 machines using Microsoft Endpoint Configuration Manager current branch
|
||||
|
||||
Configuration Manager current branch has integrated support to configure and manage Microsoft Defender ATP on managed devices. For more information, see [Microsoft Defender Advanced Threat Protection in Microsoft Endpoint Configuration Manager current branch](https://docs.microsoft.com/configmgr/protect/deploy-use/windows-defender-advanced-threat-protection).
|
||||
|
||||
<span id="sccm1602"/>
|
||||
## Onboard Windows 10 machines using System Center Configuration Manager earlier versions
|
||||
You can use existing System Center Configuration Manager functionality to create a policy to configure your machines. This is supported in the following System Center Configuration Manager versions:
|
||||
|
||||
- System Center 2012 Configuration Manager
|
||||
- System Center 2012 R2 Configuration Manager
|
||||
- System Center Configuration Manager (current branch), version 1511
|
||||
- System Center Configuration Manager (current branch), version 1602
|
||||
## Onboard Windows 10 machines using earlier versions of System Center Configuration Manager
|
||||
|
||||
You can use existing Configuration Manager functionality to create a policy to configure your machines. This action is supported in System Center 2012 R2 Configuration Manager.
|
||||
|
||||
### Onboard machines using System Center Configuration Manager
|
||||
|
||||
|
||||
1. Open the SCCM configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from [Microsoft Defender Security Center](https://securitycenter.windows.com/):
|
||||
1. Open the Configuration Manager configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from [Microsoft Defender Security Center](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
@ -63,7 +54,7 @@ You can use existing System Center Configuration Manager functionality to create
|
||||
|
||||
2. Extract the contents of the .zip file to a shared, read-only location that can be accessed by the network administrators who will deploy the package. You should have a file named *WindowsDefenderATPOnboardingScript.cmd*.
|
||||
|
||||
3. Deploy the package by following the steps in the [Packages and Programs in Configuration Manager](https://docs.microsoft.com/sccm/apps/deploy-use/packages-and-programs) topic.
|
||||
3. Deploy the package by following the steps in the [Packages and Programs in System Center 2012 R2 Configuration Manager](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/gg699369\(v=technet.10\)) article.
|
||||
|
||||
a. Choose a predefined device collection to deploy the package to.
|
||||
|
||||
@ -72,8 +63,16 @@ You can use existing System Center Configuration Manager functionality to create
|
||||
|
||||
>[!TIP]
|
||||
> After onboarding the machine, you can choose to run a detection test to verify that an machine is properly onboarded to the service. For more information, see [Run a detection test on a newly onboarded Microsoft Defender ATP machine](run-detection-test.md).
|
||||
>
|
||||
> Note that it is possible to create a detection rule on a Configuration Manager application to continuously check if a machine has been onboarded. An application is a different type of object than a package and program.
|
||||
> If a machine is not yet onboarded (due to pending OOBE completion or any other reason), Configuration Manager will retry to onboard the machine until the rule detects the status change.
|
||||
>
|
||||
> This behavior can be accomplished by creating a detection rule checking if the "OnboardingState" registry value (of type REG_DWORD) = 1.
|
||||
> This registry value is located under "HKLM\SOFTWARE\Microsoft\Windows Advanced Threat Protection\Status".
|
||||
For more information, see [Configure Detection Methods in System Center 2012 R2 Configuration Manager](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/gg682159\(v=technet.10\)#step-4-configure-detection-methods-to-indicate-the-presence-of-the-deployment-type).
|
||||
|
||||
### Configure sample collection settings
|
||||
|
||||
For each machine, you can set a configuration value to state whether samples can be collected from the machine when a request is made through Microsoft Defender Security Center to submit a file for deep analysis.
|
||||
|
||||
You can set a compliance rule for configuration item in System Center Configuration Manager to change the sample share setting on a machine.
|
||||
@ -94,17 +93,23 @@ Possible values are:
|
||||
|
||||
The default value in case the registry key doesn’t exist is 1.
|
||||
|
||||
For more information about System Center Configuration Manager Compliance see [Get started with compliance settings in System Center Configuration Manager](https://docs.microsoft.com/sccm/compliance/get-started/get-started-with-compliance-settings).
|
||||
For more information about System Center Configuration Manager Compliance see [Introduction to compliance settings in System Center 2012 R2 Configuration Manager](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/gg682139\(v=technet.10\)).
|
||||
|
||||
|
||||
|
||||
## Offboard machines using System Center Configuration Manager
|
||||
## Offboard machines using Configuration Manager
|
||||
|
||||
For security reasons, the package used to Offboard machines will expire 30 days after the date it was downloaded. Expired offboarding packages sent to an machine will be rejected. When downloading an offboarding package you will be notified of the packages expiry date and it will also be included in the package name.
|
||||
|
||||
> [!NOTE]
|
||||
> Onboarding and offboarding policies must not be deployed on the same machine at the same time, otherwise this will cause unpredictable collisions.
|
||||
|
||||
### Offboard machines using Microsoft Endpoint Configuration Manager current branch
|
||||
|
||||
If you use Microsoft Endpoint Configuration Manager current branch, see [Create an offboarding configuration file](https://docs.microsoft.com/configmgr/protect/deploy-use/windows-defender-advanced-threat-protection#create-an-offboarding-configuration-file).
|
||||
|
||||
### Offboard machines using System Center 2012 R2 Configuration Manager
|
||||
|
||||
1. Get the offboarding package from [Microsoft Defender Security Center](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Offboarding**.
|
||||
@ -117,7 +122,7 @@ For security reasons, the package used to Offboard machines will expire 30 days
|
||||
|
||||
2. Extract the contents of the .zip file to a shared, read-only location that can be accessed by the network administrators who will deploy the package. You should have a file named *WindowsDefenderATPOffboardingScript_valid_until_YYYY-MM-DD.cmd*.
|
||||
|
||||
3. Deploy the package by following the steps in the [Packages and Programs in Configuration Manager](https://docs.microsoft.com/sccm/apps/deploy-use/packages-and-programs) topic.
|
||||
3. Deploy the package by following the steps in the [Packages and Programs in System Center 2012 R2 Configuration Manager](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/gg699369\(v=technet.10\)) article.
|
||||
|
||||
a. Choose a predefined device collection to deploy the package to.
|
||||
|
||||
@ -125,16 +130,19 @@ For security reasons, the package used to Offboard machines will expire 30 days
|
||||
> Offboarding causes the machine to stop sending sensor data to the portal but data from the machine, including reference to any alerts it has had will be retained for up to 6 months.
|
||||
|
||||
|
||||
### Monitor machine configuration
|
||||
Monitoring with SCCM consists of two parts:
|
||||
## Monitor machine configuration
|
||||
|
||||
If you're using Microsoft Endpoint Configuration Manager current branch, use the built-in Microsoft Defender ATP dashboard in the Configuration Manager console. For more information, see [Microsoft Defender Advanced Threat Protection - Monitor](https://docs.microsoft.com/configmgr/protect/deploy-use/windows-defender-advanced-threat-protection#monitor).
|
||||
|
||||
If you're using System Center 2012 R2 Configuration Manager, monitoring consists of two parts:
|
||||
|
||||
1. Confirming the configuration package has been correctly deployed and is running (or has successfully run) on the machines in your network.
|
||||
|
||||
2. Checking that the machines are compliant with the Microsoft Defender ATP service (this ensures the machine can complete the onboarding process and can continue to report data to the service).
|
||||
|
||||
**To confirm the configuration package has been correctly deployed:**
|
||||
### Confirm the configuration package has been correctly deployed
|
||||
|
||||
1. In the SCCM console, click **Monitoring** at the bottom of the navigation pane.
|
||||
1. In the Configuration Manager console, click **Monitoring** at the bottom of the navigation pane.
|
||||
|
||||
2. Click **Overview** and then **Deployments**.
|
||||
|
||||
@ -142,12 +150,13 @@ Monitoring with SCCM consists of two parts:
|
||||
|
||||
4. Review the status indicators under **Completion Statistics** and **Content Status**.
|
||||
|
||||
If there are failed deployments (machines with **Error**, **Requirements Not Met**, or **Failed statuses**), you may need to troubleshoot the machines. For more information see, [Troubleshoot Microsoft Defender Advanced Threat Protection onboarding issues](troubleshoot-onboarding.md).
|
||||
If there are failed deployments (machines with **Error**, **Requirements Not Met**, or **Failed statuses**), you may need to troubleshoot the machines. For more information see, [Troubleshoot Microsoft Defender Advanced Threat Protection onboarding issues](troubleshoot-onboarding.md).
|
||||
|
||||

|
||||

|
||||
|
||||
**Check that the machines are compliant with the Microsoft Defender ATP service:**<br>
|
||||
You can set a compliance rule for configuration item in System Center Configuration Manager to monitor your deployment.
|
||||
### Check that the machines are compliant with the Microsoft Defender ATP service
|
||||
|
||||
You can set a compliance rule for configuration item in System Center 2012 R2 Configuration Manager to monitor your deployment.
|
||||
|
||||
This rule should be a *non-remediating* compliance rule configuration item that monitors the value of a registry key on targeted machines.
|
||||
|
||||
@ -157,7 +166,7 @@ Path: “HKLM\SOFTWARE\Microsoft\Windows Advanced Threat Protection\Status”
|
||||
Name: “OnboardingState”
|
||||
Value: “1”
|
||||
```
|
||||
For more information about System Center Configuration Manager Compliance see [Get started with compliance settings in System Center Configuration Manager](https://docs.microsoft.com/sccm/compliance/get-started/get-started-with-compliance-settings).
|
||||
For more information, see [Introduction to compliance settings in System Center 2012 R2 Configuration Manager](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/gg682139\(v=technet.10\)).
|
||||
|
||||
## Related topics
|
||||
- [Onboard Windows 10 machines using Group Policy](configure-endpoints-gp.md)
|
||||
|
@ -136,7 +136,7 @@ Monitoring can also be done directly on the portal, or by using the different de
|
||||
|
||||
## Related topics
|
||||
- [Onboard Windows 10 machines using Group Policy](configure-endpoints-gp.md)
|
||||
- [Onboard Windows 10 machines using System Center Configuration Manager](configure-endpoints-sccm.md)
|
||||
- [Onboard Windows 10 machines using Microsoft Endpoint Configuration Manager](configure-endpoints-sccm.md)
|
||||
- [Onboard Windows 10 machines using Mobile Device Management tools](configure-endpoints-mdm.md)
|
||||
- [Onboard non-persistent virtual desktop infrastructure (VDI) machines](configure-endpoints-vdi.md)
|
||||
- [Run a detection test on a newly onboarded Microsoft Defender ATP machine](run-detection-test.md)
|
||||
|
@ -97,7 +97,7 @@ The following steps will guide you through onboarding VDI machines and will high
|
||||
|
||||
## Related topics
|
||||
- [Onboard Windows 10 machines using Group Policy](configure-endpoints-gp.md)
|
||||
- [Onboard Windows 10 machines using System Center Configuration Manager](configure-endpoints-sccm.md)
|
||||
- [Onboard Windows 10 machines using Microsoft Endpoint Configuration Manager](configure-endpoints-sccm.md)
|
||||
- [Onboard Windows 10 machines using Mobile Device Management tools](configure-endpoints-mdm.md)
|
||||
- [Onboard Windows 10 machines using a local script](configure-endpoints-script.md)
|
||||
- [Troubleshoot Microsoft Defender Advanced Threat Protection onboarding issues](troubleshoot-onboarding.md)
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Onboarding tools and methods for Windows 10 machines
|
||||
description: Onboard Windows 10 machines so that they can send sensor data to the Microsoft Defender ATP sensor
|
||||
keywords: Onboard Windows 10 machines, group policy, system center configuration manager, mobile device management, local script, gp, sccm, mdm, intune
|
||||
keywords: Onboard Windows 10 machines, group policy, endpoint configuration manager, mobile device management, local script, gp, sccm, mdm, intune
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
@ -31,7 +31,7 @@ Machines in your organization must be configured so that the Microsoft Defender
|
||||
The following deployment tools and methods are supported:
|
||||
|
||||
- Group Policy
|
||||
- System Center Configuration Manager
|
||||
- Microsoft Endpoint Configuration Manager
|
||||
- Mobile Device Management (including Microsoft Intune)
|
||||
- Local script
|
||||
|
||||
@ -39,7 +39,7 @@ The following deployment tools and methods are supported:
|
||||
Topic | Description
|
||||
:---|:---
|
||||
[Onboard Windows 10 machines using Group Policy](configure-endpoints-gp.md) | Use Group Policy to deploy the configuration package on machines.
|
||||
[Onboard Windows 10 machines using System Center Configuration Manager](configure-endpoints-sccm.md) | You can use either use System Center Configuration Manager (current branch) version 1606 or System Center Configuration Manager(current branch) version 1602 or earlier to deploy the configuration package on machines.
|
||||
[Onboard Windows machines using Microsoft Endpoint Configuration Manager](configure-endpoints-sccm.md) | You can use either use Microsoft Endpoint Configuration Manager (current branch) version 1606 or Microsoft Endpoint Configuration Manager (current branch) version 1602 or earlier to deploy the configuration package on machines.
|
||||
[Onboard Windows 10 machines using Mobile Device Management tools](configure-endpoints-mdm.md) | Use Mobile Device Management tools or Microsoft Intune to deploy the configuration package on machine.
|
||||
[Onboard Windows 10 machines using a local script](configure-endpoints-script.md) | Learn how to use the local script to deploy the configuration package on endpoints.
|
||||
[Onboard non-persistent virtual desktop infrastructure (VDI) machines](configure-endpoints-vdi.md) | Learn how to use the configuration package to configure VDI machines.
|
||||
|
@ -26,8 +26,9 @@ ms.topic: article
|
||||
## Before you begin
|
||||
Ensure that you have Microsoft Defender ATP deployed in your environment with machines enrolled, and not just on a laboratory set-up.
|
||||
|
||||
>[!NOTE]
|
||||
>Microsoft Defender ATP customers need to apply for the Microsoft Threat Experts managed threat hunting service to get proactive targeted attack notifications and to collaborate with experts on demand. A Microsoft Threat Experts subscription is a prerequisite for experts on demand collaboration.
|
||||
Microsoft Defender ATP customers need to apply for the Microsoft Threat Experts managed threat hunting service to get proactive Targeted Attack Notifications and to collaborate with experts on demand. Experts on Demand is an add-on service. Targeted Attack Notifications are always included after you have been accepted into Microsoft Threat Experts managed threat hunting service.
|
||||
|
||||
If you are not enrolled yet and would like to experience its benefits, go to **Settings** > **General** > **Advanced features** > **Microsoft Threat Experts** to apply. Once accepted, you will get the benefits of Targeted Attack Notifications, and start a 90-day trial of Experts on Demand. Contact your Microsoft representative to get a full Experts on Demand subscription.
|
||||
|
||||
## Register to Microsoft Threat Experts managed threat hunting service
|
||||
If you're already a Microsoft Defender ATP customer, you can apply through the Microsoft Defender ATP portal.
|
||||
|
@ -40,7 +40,7 @@ You'll need to take the following configuration steps to enable the managed secu
|
||||
|
||||
The integration will allow MSSPs to take the following actions:
|
||||
|
||||
- Get access to MSSP customer's Windows Defender Security Center portal
|
||||
- Get access to MSSP customer's Microsoft Defender Security Center portal
|
||||
- Get email notifications, and
|
||||
- Fetch alerts through security information and event management (SIEM) tools
|
||||
|
||||
@ -53,7 +53,7 @@ Typically, MSSP customers take the initial configuration steps to grant MSSPs ac
|
||||
In general, the following configuration steps need to be taken:
|
||||
|
||||
|
||||
- **Grant the MSSP access to Windows Defender Security Center** <br>
|
||||
- **Grant the MSSP access to Microsoft Defender Security Center** <br>
|
||||
This action needs to be done by the MSSP customer. It grants the MSSP access to the MSSP customer's Windows Defender ATP tenant.
|
||||
|
||||
|
||||
@ -74,7 +74,7 @@ This action is taken by the MSSP. It allows MSSPs to fetch alerts using APIs.
|
||||
> These set of steps are directed towards the MSSP customer. <br>
|
||||
> Access to the portal can only be done by the MSSP customer.
|
||||
|
||||
As a MSSP customer, you'll need to take the following configuration steps to grant the MSSP access to Windows Defender Security Center.
|
||||
As a MSSP customer, you'll need to take the following configuration steps to grant the MSSP access to Microsoft Defender Security Center.
|
||||
|
||||
|
||||
Authentication and authorization of the MSSP user is built on top of Azure Active Directory (Azure AD) B2B functionality.
|
||||
@ -82,7 +82,7 @@ Authentication and authorization of the MSSP user is built on top of Azure Activ
|
||||
You'll need to take the following 2 steps:
|
||||
- Add MSSP user to your tenant as a guest user
|
||||
|
||||
- Grant MSSP user access to Windows Defender Security Center
|
||||
- Grant MSSP user access to Microsoft Defender Security Center
|
||||
|
||||
|
||||
### Add MSSP user to your tenant as a guest user
|
||||
@ -90,8 +90,8 @@ Add a user who is a member of the MSSP tenant to your tenant as a guest user.
|
||||
|
||||
To grant portal access to the MSSP, you must add the MSSP user to your Azure AD as a guest user. For more information, see [Add Azure Active Directory B2B collaboration users in the Azure portal](https://docs.microsoft.com/azure/active-directory/b2b/add-users-administrator).
|
||||
|
||||
### Grant MSSP user access to Windows Defender Security Center
|
||||
Grant the guest user access and permissions to your Windows Defender Security Center tenant.
|
||||
### Grant MSSP user access to Microsoft Defender Security Center
|
||||
Grant the guest user access and permissions to your Microsoft Defender Security Center tenant.
|
||||
|
||||
Granting access to guest user is done the same way as granting access to a user who is a member of your tenant.
|
||||
|
||||
@ -108,12 +108,12 @@ It is recommended that groups are created for MSSPs to make authorization access
|
||||
As a MSSP customer, you can always remove or modify the permissions granted to the MSSP by updating the Azure AD user groups.
|
||||
|
||||
|
||||
## Access the Windows Defender Security Center MSSP customer portal
|
||||
## Access the Microsoft Defender Security Center MSSP customer portal
|
||||
|
||||
>[!NOTE]
|
||||
>These set of steps are directed towards the MSSP.
|
||||
|
||||
By default, MSSP customers access their Windows Defender Security Center tenant through the following URL: `https://securitycenter.windows.com`.
|
||||
By default, MSSP customers access their Microsoft Defender Security Center tenant through the following URL: `https://securitycenter.windows.com`.
|
||||
|
||||
|
||||
MSSPs however, will need to use a tenant-specific URL in the following format: `https://securitycenter.windows.com?tid=customer_tenant_id` to access the MSSP customer portal.
|
||||
@ -159,7 +159,7 @@ Step 1: Create a third-party application
|
||||
|
||||
Step 2: Get access and refresh tokens from your customer's tenant
|
||||
|
||||
Step 3: Whitelist your application on Windows Defender Security Center
|
||||
Step 3: Whitelist your application on Microsoft Defender Security Center
|
||||
|
||||
|
||||
|
||||
@ -279,8 +279,8 @@ After providing your credentials, you'll need to grant consent to the applicatio
|
||||
8. In the PowerShell window, you'll receive an access token and a refresh token. Save the refresh token to configure your SIEM connector.
|
||||
|
||||
|
||||
### Step 3: Whitelist your application on Windows Defender Security Center
|
||||
You'll need to whitelist the application you created in Windows Defender Security Center.
|
||||
### Step 3: Whitelist your application on Microsoft Defender Security Center
|
||||
You'll need to whitelist the application you created in Microsoft Defender Security Center.
|
||||
|
||||
|
||||
You'll need to have **Manage portal system settings** permission to whitelist the application. Otherwise, you'll need to request your customer to whitelist the application for you.
|
||||
|
@ -105,20 +105,24 @@ See [Netsh Command Syntax, Contexts, and Formatting](https://docs.microsoft.com/
|
||||
If a proxy or firewall is blocking all traffic by default and allowing only specific domains through or HTTPS scanning (SSL inspection) is enabled, make sure that the following URLs are not blocked by default. Do not disable security monitoring or inspection of these URLs, but allow them as you would other internet traffic. They permit communication with Microsoft Defender ATP service in port 80 and 443:
|
||||
|
||||
> [!NOTE]
|
||||
> 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.
|
||||
> settings-win.data.microsoft.com is only needed if you have Windows 10 machines running version 1803 or earlier.<br>
|
||||
> URLs that include v20 in them are only needed if you have Windows 10 machines running version 1803 or later. For example, ```us-v20.events.data.microsoft.com``` is needed for a Windows 10 machine running version 1803 or later and onboarded to US Data Storage region.
|
||||
|
||||
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```
|
||||
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``` <br>```automatedirstrprdweu.blob.core.windows.net``` <br>```automatedirstrprdneu.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``` <br>```automatedirstrprduks.blob.core.windows.net``` <br>```automatedirstrprdukw.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``` <br> ```automatedirstrprdcus.blob.core.windows.net``` <br> ```automatedirstrprdeus.blob.core.windows.net```
|
||||
|
||||
> [!NOTE]
|
||||
> If you are using Windows Defender Antivirus in your environment, please refer to the following article for details on allowing connections to the Windows Defender Antivirus cloud service: https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/configure-network-connections-windows-defender-antivirus
|
||||
|
||||
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 your 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 added to an "allow" list in the prior section, you can use the following information.
|
||||
|
||||
Microsoft Defender ATP is built on Azure cloud, deployed in the following regions:
|
||||
|
||||
@ -139,9 +143,9 @@ You can find the Azure IP range on [Microsoft Azure Datacenter IP Ranges](https:
|
||||
|
||||
Verify the proxy configuration completed successfully, that WinHTTP can discover and communicate through the proxy server in your environment, and that the proxy server allows traffic to the Microsoft Defender ATP service URLs.
|
||||
|
||||
1. Download the [connectivity verification tool](https://aka.ms/mdatpanalyzer) to the PC where Microsoft Defender ATP sensor is running on.
|
||||
1. Download the [MDATP Client Analyzer tool](https://aka.ms/mdatpanalyzer) to the PC where Microsoft Defender ATP sensor is running on.
|
||||
|
||||
2. Extract the contents of MDATPClientAnalyzer on the machine.
|
||||
2. Extract the contents of MDATPClientAnalyzer.zip on the machine.
|
||||
|
||||
3. Open an elevated command-line:
|
||||
|
||||
|
@ -129,7 +129,7 @@ Once completed, you should see onboarded servers in the portal within an hour.
|
||||
To onboard Windows Server, version 1803 or Windows Server 2019, please refer to the supported methods and versions below.
|
||||
|
||||
> [!NOTE]
|
||||
> The Onboarding package for Windows Server 2019 through System Center Configuration Manager currently ships a script. For more information on how to deploy scripts in System Center Configuration Manager, see [Packages and programs in Configuration Manager](https://docs.microsoft.com/sccm/apps/deploy-use/packages-and-programs).
|
||||
> The Onboarding package for Windows Server 2019 through Microsoft Endpoint Configuration Manager currently ships a script. For more information on how to deploy scripts in Microsoft Endpoint Configuration Manager, see [Packages and programs in Configuration Manager](https://docs.microsoft.com/configmgr/apps/deploy-use/packages-and-programs).
|
||||
|
||||
Supported tools include:
|
||||
- Local script
|
||||
|
@ -25,13 +25,13 @@ ms.custom: asr
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
Controlled folder access helps you protect valuable data from malicious apps and threats, such as ransomware. It protects your data by checking against a list of known, trusted apps. Controlled folder access is supported on Windows Server 2019 as well as Windows 10 clients. It can be turned on via the Windows Security App, or from the System Center Configuration Manager (SCCM) and Intune, for managed devices. Controlled folder access works best with [Microsoft Defender Advanced Threat Protection](../microsoft-defender-atp/microsoft-defender-advanced-threat-protection.md), which gives you detailed reporting into controlled folder access events and blocks as part of the usual [alert investigation scenarios](../microsoft-defender-atp/investigate-alerts.md).
|
||||
Controlled folder access helps you protect valuable data from malicious apps and threats, such as ransomware. It protects your data by checking against a list of known, trusted apps. Controlled folder access is supported on Windows Server 2019 as well as Windows 10 clients. It can be turned on via the Windows Security App, or from the Microsoft Endpoint Configuration Manager and Intune, for managed devices. Controlled folder access works best with [Microsoft Defender Advanced Threat Protection](../microsoft-defender-atp/microsoft-defender-advanced-threat-protection.md), which gives you detailed reporting into controlled folder access events and blocks as part of the usual [alert investigation scenarios](../microsoft-defender-atp/investigate-alerts.md).
|
||||
|
||||
Controlled folder access works by only allowing apps to access protected folders if the app is included on a list of trusted software. If an app isn't on the list, Controlled folder access will block it from making changes to files inside protected folders.
|
||||
|
||||
Apps are added to the trusted list based upon their prevalence and reputation. Apps that are highly prevalent throughout your organization, and that have never displayed any malicious behavior, are deemed trustworthy and automatically added to the list.
|
||||
|
||||
Apps can also be manually added to the trusted list via SCCM and Intune. Additional actions, such as [adding a file indicator](../microsoft-defender-atp/respond-file-alerts.md#add-indicator-to-block-or-allow-a-file) for the app, can be performed from the Security Center Console.
|
||||
Apps can also be manually added to the trusted list via Configuration Manager and Intune. Additional actions, such as [adding a file indicator](../microsoft-defender-atp/respond-file-alerts.md#add-indicator-to-block-or-allow-a-file) for the app, can be performed from the Security Center Console.
|
||||
|
||||
Controlled folder access is especially useful in helping to protect your documents and information from [ransomware](https://www.microsoft.com/wdsi/threats/ransomware) that can attempt to encrypt your files and hold them hostage.
|
||||
|
||||
|
@ -24,8 +24,9 @@ ms.topic: article
|
||||
|
||||
|
||||
## API description
|
||||
Creates new [Alert](alerts.md).
|
||||
<br>Microsoft Defender ATP Event is a required parameter for the alert creation.
|
||||
Creates new [Alert](alerts.md) on top of **Event**.
|
||||
<br>**Microsoft Defender ATP Event** is required for the alert creation.
|
||||
<br>You will need to supply 3 parameters from the Event in the request: **Event Time**, **Machine ID** and **Report ID**. See example below.
|
||||
<br>You can use an event found in Advanced Hunting API or Portal.
|
||||
<br>If there existing an open alert on the same Machine with the same Title, the new created alert will be merged with it.
|
||||
<br>An automatic investigation starts automatically on alerts created via the API.
|
||||
@ -68,13 +69,13 @@ In the request body, supply the following values (all are required):
|
||||
|
||||
Property | Type | Description
|
||||
:---|:---|:---
|
||||
eventTime | DateTime(UTC) | The precise time of the event as string, as obtained from advanced hunting. e.g. ```2018-08-03T16:45:21.7115183Z``` **Required**.
|
||||
reportId | String | The reportId of the event, as obtained from advanced hunting. **Required**.
|
||||
machineId | String | Id of the machine on which the event was identified. **Required**.
|
||||
severity | String | Severity of the alert. The property values are: 'Low', 'Medium' and 'High'. **Required**.
|
||||
title | String | Title for the alert. **Required**.
|
||||
description | String | Description of the alert. **Required**.
|
||||
recommendedAction| String | Action that is recommended to be taken by security officer when analyzing the alert. **Required**.
|
||||
eventTime | DateTime(UTC) | The time of the event, as obtained from the advanced query. **Required**.
|
||||
reportId | String | The reportId, as obtained from the advanced query. **Required**.
|
||||
category| String | Category of the alert. The property values are: "General", "CommandAndControl", "Collection", "CredentialAccess", "DefenseEvasion", "Discovery", "Exfiltration", "Exploit", "Execution", "InitialAccess", "LateralMovement", "Malware", "Persistence", "PrivilegeEscalation", "Ransomware", "SuspiciousActivity" **Required**.
|
||||
|
||||
## Response
|
||||
@ -91,16 +92,16 @@ Here is an example of the request.
|
||||
|
||||
```
|
||||
POST https://api.securitycenter.windows.com/api/alerts/CreateAlertByReference
|
||||
Content-Length: application/json
|
||||
|
||||
```
|
||||
```json
|
||||
{
|
||||
"machineId": "1e5bc9d7e413ddd7902c2932e418702b84d0cc07",
|
||||
"severity": "Low",
|
||||
"title": "test alert",
|
||||
"description": "test alert",
|
||||
"recommendedAction": "test alert",
|
||||
"eventTime": "2018-08-03T16:45:21.7115183Z",
|
||||
"reportId": "20776",
|
||||
"category": "None"
|
||||
"machineId": "1e5bc9d7e413ddd7902c2932e418702b84d0cc07",
|
||||
"severity": "Low",
|
||||
"title": "example",
|
||||
"description": "example alert",
|
||||
"recommendedAction": "nothing",
|
||||
"eventTime": "2018-08-03T16:45:21.7115183Z",
|
||||
"reportId": "20776",
|
||||
"category": "Exploit"
|
||||
}
|
||||
```
|
||||
|
@ -33,11 +33,11 @@ You can enable attack surface reduction rules by using any of these methods:
|
||||
|
||||
* [Microsoft Intune](#intune)
|
||||
* [Mobile Device Management (MDM)](#mdm)
|
||||
* [System Center Configuration Manager (SCCM)](#sccm)
|
||||
* [Microsoft Endpoint Configuration Manager](#microsoft-endpoint-configuration-manager)
|
||||
* [Group Policy](#group-policy)
|
||||
* [PowerShell](#powershell)
|
||||
|
||||
Enterprise-level management such as Intune or SCCM is recommended. Enterprise-level management will overwrite any conflicting Group Policy or PowerShell settings on startup.
|
||||
Enterprise-level management such as Intune or Microsoft Endpoint Configuration Manager is recommended. Enterprise-level management will overwrite any conflicting Group Policy or PowerShell settings on startup.
|
||||
|
||||
## Exclude files and folders from ASR rules
|
||||
|
||||
@ -56,7 +56,7 @@ You can exclude files and folders from being evaluated by most attack surface re
|
||||
|
||||
You can specify individual files or folders (using folder paths or fully qualified resource names) but you can't specify which rules the exclusions apply to. An exclusion is applied only when the excluded application or service starts. For example, if you add an exclusion for an update service that is already running, the update service will continue to trigger events until the service is stopped and restarted.
|
||||
|
||||
ASR rules support environment variables and wildcards. For information about using wildcards, see [Use wildcards in the file name and folder path or extension exclusion lists](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/configure-extension-file-exclusions-windows-defender-antivirus#use-wildcards-in-the-file-name-and-folder-path-or-extension-exclusion-lists).
|
||||
ASR rules support environment variables and wildcards. For information about using wildcards, see [Use wildcards in the file name and folder path or extension exclusion lists](../windows-defender-antivirus/configure-extension-file-exclusions-windows-defender-antivirus.md#use-wildcards-in-the-file-name-and-folder-path-or-extension-exclusion-lists).
|
||||
|
||||
The following procedures for enabling ASR rules include instructions for how to exclude files and folders.
|
||||
|
||||
@ -76,7 +76,7 @@ The following procedures for enabling ASR rules include instructions for how to
|
||||
|
||||
Use the [./Vendor/MSFT/Policy/Config/Defender/AttackSurfaceReductionRules](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-defender#defender-attacksurfacereductionrules) configuration service provider (CSP) to individually enable and set the mode for each rule.
|
||||
|
||||
The following is a sample for reference, using [GUID values for ASR rules](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-exploit-guard/attack-surface-reduction#attack-surface-reduction-rules).
|
||||
The following is a sample for reference, using [GUID values for ASR rules](attack-surface-reduction.md#attack-surface-reduction-rules).
|
||||
|
||||
OMA-URI path: ./Vendor/MSFT/Policy/Config/Defender/AttackSurfaceReductionRules
|
||||
|
||||
@ -99,9 +99,9 @@ Value: c:\path|e:\path|c:\Whitelisted.exe
|
||||
> [!NOTE]
|
||||
> Be sure to enter OMA-URI values without spaces.
|
||||
|
||||
## SCCM
|
||||
## Microsoft Endpoint Configuration Manager
|
||||
|
||||
1. In System Center Configuration Manager, click **Assets and Compliance** > **Endpoint Protection** > **Windows Defender Exploit Guard**.
|
||||
1. In Microsoft Endpoint Configuration Manager, click **Assets and Compliance** > **Endpoint Protection** > **Windows Defender Exploit Guard**.
|
||||
1. Click **Home** > **Create Exploit Guard Policy**.
|
||||
1. Enter a name and a description, click **Attack Surface Reduction**, and click **Next**.
|
||||
1. Choose which rules will block or audit actions and click **Next**.
|
||||
@ -111,7 +111,7 @@ Value: c:\path|e:\path|c:\Whitelisted.exe
|
||||
## Group Policy
|
||||
|
||||
> [!WARNING]
|
||||
> If you manage your computers and devices with Intune, SCCM, or other enterprise-level management platform, the management software will overwrite any conflicting Group Policy settings on startup.
|
||||
> If you manage your computers and devices with Intune, Configuration Manager, or other enterprise-level management platform, the management software will overwrite any conflicting Group Policy settings on startup.
|
||||
|
||||
1. On your Group Policy management computer, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**.
|
||||
|
||||
@ -134,7 +134,7 @@ Value: c:\path|e:\path|c:\Whitelisted.exe
|
||||
## PowerShell
|
||||
|
||||
>[!WARNING]
|
||||
>If you manage your computers and devices with Intune, SCCM, or other enterprise-level management platform, the management software will overwrite any conflicting PowerShell settings on startup.
|
||||
>If you manage your computers and devices with Intune, Configuration Manager, or other enterprise-level management platform, the management software will overwrite any conflicting PowerShell settings on startup.
|
||||
|
||||
1. Type **powershell** in the Start menu, right-click **Windows PowerShell** and click **Run as administrator**.
|
||||
|
||||
@ -186,4 +186,4 @@ Value: c:\path|e:\path|c:\Whitelisted.exe
|
||||
|
||||
* [Reduce attack surfaces with attack surface reduction rules](attack-surface-reduction.md)
|
||||
* [Evaluate attack surface reduction](evaluate-attack-surface-reduction.md)
|
||||
* [Enable cloud-delivered protection](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/enable-cloud-protection-windows-defender-antivirus)
|
||||
* [Enable cloud-delivered protection](../windows-defender-antivirus/configure-extension-file-exclusions-windows-defender-antivirus.md)
|
||||
|
@ -30,7 +30,7 @@ You can enable controlled folder access by using any of these methods:
|
||||
* [Windows Security app](#windows-security-app)
|
||||
* [Microsoft Intune](#intune)
|
||||
* [Mobile Device Management (MDM)](#mdm)
|
||||
* [System Center Configuration Manager (SCCM)](#sccm)
|
||||
* [Microsoft Endpoint Configuration Manager](#microsoft-endpoint-configuration-manager)
|
||||
* [Group Policy](#group-policy)
|
||||
* [PowerShell](#powershell)
|
||||
|
||||
@ -78,9 +78,9 @@ For more information about disabling local list merging, see [Prevent or allow u
|
||||
|
||||
Use the [./Vendor/MSFT/Policy/Config/ControlledFolderAccessProtectedFolders](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-defender#defender-controlledfolderaccessprotectedfolders) configuration service provider (CSP) to allow apps to make changes to protected folders.
|
||||
|
||||
## SCCM
|
||||
## Microsoft Endpoint Configuration Manager
|
||||
|
||||
1. In System Center Configuration Manager, click **Assets and Compliance** > **Endpoint Protection** > **Windows Defender Exploit Guard**.
|
||||
1. In Microsoft Endpoint Configuration Manager, click **Assets and Compliance** > **Endpoint Protection** > **Windows Defender Exploit Guard**.
|
||||
2. Click **Home** > **Create Exploit Guard Policy**.
|
||||
3. Enter a name and a description, click **Controlled folder access**, and click **Next**.
|
||||
4. Choose whether block or audit changes, allow other apps, or add other folders, and click **Next**.
|
||||
@ -98,14 +98,16 @@ Use the [./Vendor/MSFT/Policy/Config/ControlledFolderAccessProtectedFolders](htt
|
||||
3. Expand the tree to **Windows components > Windows Defender Antivirus > Windows Defender Exploit Guard > Controlled folder access**.
|
||||
|
||||
4. Double-click the **Configure Controlled folder access** setting and set the option to **Enabled**. In the options section you must specify one of the following:
|
||||
* **Enable** - Malicious and suspicious apps will not be allowed to make changes to files in protected folders. A notification will be provided in the Windows event log
|
||||
* **Enable** - Malicious and suspicious apps will not be allowed to make changes to files in protected folders. A notification will be provided in the Windows event log.
|
||||
* **Disable (Default)** - The Controlled folder access feature will not work. All apps can make changes to files in protected folders.
|
||||
* **Audit Mode** - If a malicious or suspicious app attempts to make a change to a file in a protected folder, the change will be allowed but will be recorded in the Windows event log. This allows you to assess the impact of this feature on your organization.
|
||||
* **Block disk modification only** - Attempts by untrusted apps to write to disk sectors will be logged in Windows Event log. These logs can be found in **Applications and Services Logs** > Microsoft > Windows > Windows Defender > Operational > ID 1123.
|
||||
* **Audit disk modification only** - Only attempts to write to protected disk sectors will be recorded in the Windows event log (under **Applications and Services Logs** > **Microsoft** > **Windows** > **Windows Defender** > **Operational** > **ID 1124**). Attempts to modify or delete files in protected folders will not be recorded.
|
||||
|
||||

|
||||

|
||||
|
||||
> [!IMPORTANT]
|
||||
> To fully enable controlled folder access, you must set the Group Policy option to **Enabled** and also select **Enable** in the options drop-down menu.
|
||||
> To fully enable controlled folder access, you must set the Group Policy option to **Enabled** and select **Block** in the options drop-down menu.
|
||||
|
||||
## PowerShell
|
||||
|
||||
|
@ -32,12 +32,12 @@ Many features from the Enhanced Mitigation Experience Toolkit (EMET) are include
|
||||
|
||||
You can enable each mitigation separately by using any of these methods:
|
||||
|
||||
- [Windows Security app](#windows-security-app)
|
||||
- [Microsoft Intune](#intune)
|
||||
- [Mobile Device Management (MDM)](#mdm)
|
||||
- [System Center Configuration Manager (SCCM)](#sccm)
|
||||
- [Group Policy](#group-policy)
|
||||
- [PowerShell](#powershell)
|
||||
* [Windows Security app](#windows-security-app)
|
||||
* [Microsoft Intune](#intune)
|
||||
* [Mobile Device Management (MDM)](#mdm)
|
||||
* [Microsoft Endpoint Configuration Manager](#microsoft-endpoint-configuration-manager)
|
||||
* [Group Policy](#group-policy)
|
||||
* [PowerShell](#powershell)
|
||||
|
||||
Exploit protection is configured by default in Windows 10. You can set each mitigation to on, off, or to its default value. Some mitigations have additional options.
|
||||
|
||||
@ -121,14 +121,14 @@ The result will be that DEP will be enabled for *test.exe*. DEP will not be enab
|
||||
|
||||
Use the [./Vendor/MSFT/Policy/Config/ExploitGuard/ExploitProtectionSettings](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-exploitguard) configuration service provider (CSP) to enable or disable exploit protection mitigations or to use audit mode.
|
||||
|
||||
## SCCM
|
||||
## Microsoft Endpoint Configuration Manager
|
||||
|
||||
1. In System Center Configuration Manager, click **Assets and Compliance** > **Endpoint Protection** > **Windows Defender Exploit Guard**.
|
||||
2. Click **Home** > **Create Exploit Guard Policy**.
|
||||
3. Enter a name and a description, click **Exploit protection**, and click **Next**.
|
||||
4. Browse to the location of the exploit protection XML file and click **Next**.
|
||||
5. Review the settings and click **Next** to create the policy.
|
||||
6. After the policy is created, click **Close**.
|
||||
1. In Microsoft Endpoint Configuration Manager, click **Assets and Compliance** > **Endpoint Protection** > **Windows Defender Exploit Guard**.
|
||||
1. Click **Home** > **Create Exploit Guard Policy**.
|
||||
1. Enter a name and a description, click **Exploit protection**, and click **Next**.
|
||||
1. Browse to the location of the exploit protection XML file and click **Next**.
|
||||
1. Review the settings and click **Next** to create the policy.
|
||||
1. After the policy is created, click **Close**.
|
||||
|
||||
## Group Policy
|
||||
|
||||
|
@ -30,7 +30,7 @@ You can enable network protection by using any of these methods:
|
||||
|
||||
* [Microsoft Intune](#intune)
|
||||
* [Mobile Device Management (MDM)](#mdm)
|
||||
* [System Center Configuration Manager (SCCM)](#sccm)
|
||||
* [Microsoft Endpoint Configuration Manager](#microsoft-endpoint-configuration-manager)
|
||||
* [Group Policy](#group-policy)
|
||||
* [PowerShell](#powershell)
|
||||
|
||||
@ -49,9 +49,9 @@ You can enable network protection by using any of these methods:
|
||||
|
||||
Use the [./Vendor/MSFT/Policy/Config/Defender/EnableNetworkProtection](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-defender#defender-enablenetworkprotection) configuration service provider (CSP) to enable or disable network protection or enable audit mode.
|
||||
|
||||
## SCCM
|
||||
## Microsoft Endpoint Configuration Manager
|
||||
|
||||
1. In System Center Configuration Manager, click **Assets and Compliance** > **Endpoint Protection** > **Windows Defender Exploit Guard**.
|
||||
1. In Microsoft Endpoint Configuration Manager, click **Assets and Compliance** > **Endpoint Protection** > **Windows Defender Exploit Guard**.
|
||||
1. Click **Home** > **Create Exploit Guard Policy**.
|
||||
1. Enter a name and a description, click **Network protection**, and click **Next**.
|
||||
1. Choose whether to block or audit access to suspicious domains and click **Next**.
|
||||
|
@ -50,7 +50,7 @@ You can also use Group Policy, Intune, or MDM CSPs to configure and deploy the s
|
||||
|
||||
## Review attack surface reduction events in Windows Event Viewer
|
||||
|
||||
To review apps that would have been blocked, open Event Viewer and filter for Event ID 1121 in the Microsoft-Windows-Windows-Defender/Operational log. The following table lists all network protection events.
|
||||
To review apps that would have been blocked, open Event Viewer and filter for Event ID 1121 in the Microsoft-Windows-Windows Defender/Operational log. The following table lists all network protection events.
|
||||
|
||||
Event ID | Description
|
||||
-|-
|
||||
|
@ -46,7 +46,7 @@ Set-MpPreference -EnableControlledFolderAccess AuditMode
|
||||
|
||||
> [!TIP]
|
||||
> If you want to fully audit how controlled folder access will work in your organization, you'll need to use a management tool to deploy this setting to machines in your network(s).
|
||||
You can also use Group Policy, Intune, MDM, or System Center Configuration Manager to configure and deploy the setting, as described in the main [controlled folder access topic](controlled-folders.md).
|
||||
You can also use Group Policy, Intune, MDM, or Microsoft Endpoint Configuration Manager to configure and deploy the setting, as described in the main [controlled folder access topic](controlled-folders.md).
|
||||
|
||||
## Review controlled folder access events in Windows Event Viewer
|
||||
|
||||
|
@ -127,8 +127,8 @@ If you are looking for a pre-made simulation, you can use our ["Do It Yourself"
|
||||
|
||||
You can also use [Advanced hunting](advanced-hunting-query-language.md) to query data and [Threat analytics](threat-analytics.md) to view reports about emerging threats.
|
||||
|
||||
>[!NOTE]
|
||||
>The connection to the test machines is done using RDP. Make sure that your firewall settings allow RDP connections.
|
||||
> [!NOTE]
|
||||
> The connection to the test machines is done using RDP. Make sure that your firewall settings allow RDP connections.
|
||||
|
||||
1. Connect to your machine and run an attack simulation by selecting **Connect**.
|
||||
|
||||
@ -179,4 +179,3 @@ Your feedback helps us get better in protecting your environment from advanced a
|
||||
Let us know what you think, by selecting **Provide feedback**.
|
||||
|
||||

|
||||
|
||||
|
@ -24,7 +24,7 @@ ms.custom: asr
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
Exploit protection automatically applies a number of exploit mitigation techniques to operating system processes and apps. Exploit protection is supported beginning with Windows 10, version 1709 and Windows Server 2016, version 1803.
|
||||
Exploit protection automatically applies a number of exploit mitigation techniques to operating system processes and apps. Exploit protection is supported beginning with Windows 10, version 1709 and Windows Server, version 1803.
|
||||
|
||||
> [!TIP]
|
||||
> You can visit the Windows Defender Testground website at [demo.wd.microsoft.com](https://demo.wd.microsoft.com?ocid=cx-wddocs-testground) to confirm the feature is working and see how it works.
|
||||
@ -93,7 +93,7 @@ Win32K | 260 | Untrusted Font
|
||||
|
||||
## Mitigation comparison
|
||||
|
||||
The mitigations available in EMET are included natively in Windows 10 (starting with version 1709) and Windows Server 2016 (starting with version 1803), under [Exploit protection](exploit-protection.md).
|
||||
The mitigations available in EMET are included natively in Windows 10 (starting with version 1709) and Windows Server (starting with version 1803), under [Exploit protection](exploit-protection.md).
|
||||
|
||||
The table in this section indicates the availability and support of native mitigations between EMET and exploit protection.
|
||||
|
||||
|
@ -34,7 +34,6 @@ In general, you’ll need to take the following steps to use the APIs:
|
||||
- Use the token to access Microsoft Defender ATP API.
|
||||
|
||||
The following steps with guide you how to create an AAD application, get an access token to Microsoft Defender ATP and validate the token.
|
||||
<br>**To become an official partner of Microsoft Defender ATP and appear in our partner page, you will provide us with your application identifier.**
|
||||
|
||||
## Create the multi-tenant app
|
||||
|
||||
|
@ -66,8 +66,7 @@ GET https://api.securitycenter.windows.com/api/recommendations
|
||||
Here is an example of the response.
|
||||
|
||||
|
||||
```
|
||||
Content-type: json
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api.securitycenter.windows.com/api/$metadata#Recommendations",
|
||||
"value": [
|
||||
@ -99,7 +98,8 @@ Content-type: json
|
||||
"nonProductivityImpactedAssets": 0,
|
||||
"relatedComponent": "Windows 10"
|
||||
}
|
||||
]
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
## Related topics
|
||||
|
@ -16,7 +16,7 @@ ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Get all vulnerabilities
|
||||
# List vulnerabilities
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
@ -66,8 +66,7 @@ GET https://api.securitycenter.windows.com/api/Vulnerabilities
|
||||
Here is an example of the response.
|
||||
|
||||
|
||||
```
|
||||
Content-type: json
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api-us.securitycenter.windows.com/api/$metadata#Vulnerabilities",
|
||||
"value": [
|
||||
@ -86,8 +85,9 @@ Content-type: json
|
||||
"exploitTypes": [],
|
||||
"exploitUris": []
|
||||
}
|
||||
]
|
||||
{
|
||||
...
|
||||
]
|
||||
|
||||
}
|
||||
```
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Get Device Secure score
|
||||
description: Retrieves the organizational device secure score.
|
||||
title: Get Machine Secure score
|
||||
description: Retrieves the organizational machine secure score.
|
||||
keywords: apis, graph api, supported apis, get, alerts, recent
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
ms.prod: w10
|
||||
@ -16,7 +16,7 @@ ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Get Device Secure score
|
||||
# Get Machine Secure score
|
||||
|
||||
**Applies to:** [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
@ -75,8 +75,7 @@ Here is an example of the response.
|
||||
{
|
||||
"@odata.context": "https://api-us.securitycenter.windows.com/api/$metadata#ConfigurationScore/$entity",
|
||||
"time": "2019-12-03T09:15:58.1665846Z",
|
||||
"score": 340,
|
||||
"rbacGroupId": null
|
||||
"score": 340
|
||||
}
|
||||
```
|
||||
|
||||
|
@ -76,8 +76,7 @@ Here is an example of the response.
|
||||
{
|
||||
"@odata.context": "https://api-us.securitycenter.windows.com/api/$metadata#ExposureScore/$entity",
|
||||
"time": "2019-12-03T07:23:53.280499Z",
|
||||
"score": 33.491554051195706,
|
||||
"rbacGroupId": null
|
||||
"score": 33.491554051195706
|
||||
}
|
||||
|
||||
```
|
||||
|
@ -18,9 +18,9 @@ ms.topic: article
|
||||
|
||||
# List exposure score by machine group
|
||||
|
||||
**Applies to:**
|
||||
**Applies to:** [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
- Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-exposedapis-abovefoldlink)
|
||||
|
||||
[!include[Prerelease information](../../includes/prerelease.md)]
|
||||
|
||||
@ -74,23 +74,14 @@ Here is an example of the response.
|
||||
{
|
||||
"time": "2019-12-03T09:51:28.214338Z",
|
||||
"score": 41.38041766305988,
|
||||
"rbacGroupId": 10
|
||||
"rbacGroupName": "GroupOne"
|
||||
},
|
||||
{
|
||||
"time": "2019-12-03T09:51:28.2143399Z",
|
||||
"score": 37.403726933165366,
|
||||
"rbacGroupId": 11
|
||||
},
|
||||
{
|
||||
"time": "2019-12-03T09:51:28.2143407Z",
|
||||
"score": 26.390921344426033,
|
||||
"rbacGroupId": 9
|
||||
},
|
||||
{
|
||||
"time": "2019-12-03T09:51:28.2143414Z",
|
||||
"score": 23.58823563070858,
|
||||
"rbacGroupId": 5
|
||||
"rbacGroupName": "GroupTwo"
|
||||
}
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
@ -24,7 +24,7 @@ ms.topic: article
|
||||
|
||||
[!include[Prerelease information](../../includes/prerelease.md)]
|
||||
|
||||
Retrieve a list of machines that has this software installed.
|
||||
Retrieve a list of machine references that has this software installed.
|
||||
|
||||
## 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.
|
||||
@ -75,15 +75,16 @@ Here is an example of the response.
|
||||
"id": "7c7e1896fa39efb0a32a2cf421d837af1b9bf762",
|
||||
"computerDnsName": "dave_desktop",
|
||||
"osPlatform": "Windows10",
|
||||
"rbacGroupId": 9
|
||||
"rbacGroupName": "GroupTwo"
|
||||
},
|
||||
{
|
||||
"id": "7d5cc2e7c305e4a0a290392abf6707f9888fda0d",
|
||||
"computerDnsName": "jane_PC",
|
||||
"osPlatform": "Windows10",
|
||||
"rbacGroupId": 9
|
||||
"rbacGroupName": "GroupTwo"
|
||||
}
|
||||
]
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
|
@ -66,8 +66,7 @@ GET https://api.securitycenter.windows.com/api/vulnerabilities/CVE-2019-0608/mac
|
||||
Here is an example of the response.
|
||||
|
||||
|
||||
```
|
||||
Content-type: json
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api.securitycenter.windows.com/api/$metadata#MachineReferences",
|
||||
"value": [
|
||||
@ -75,14 +74,15 @@ Content-type: json
|
||||
"id": "235a2e6278c63fcf85bab9c370396972c58843de",
|
||||
"computerDnsName": "h1mkn_PC",
|
||||
"osPlatform": "Windows10",
|
||||
"rbacGroupId": 1268
|
||||
"rbacGroupName": "GroupTwo"
|
||||
},
|
||||
{
|
||||
"id": "afb3f807d1a185ac66668f493af028385bfca184",
|
||||
"computerDnsName": "chat_Desk ",
|
||||
"osPlatform": "Windows10",
|
||||
"rbacGroupId": 410
|
||||
"rbacGroupName": "GroupTwo"
|
||||
}
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
@ -65,8 +65,7 @@ GET https://api.securitycenter.windows.com/api/recommendations/va-_-google-_-chr
|
||||
|
||||
Here is an example of the response.
|
||||
|
||||
```
|
||||
Content-type: json
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api.securitycenter.windows.com/api/$metadata#Recommendations/$entity",
|
||||
"id": "va-_-google-_-chrome",
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Get recommendation by machines
|
||||
title: List machines by recommendation
|
||||
description: Retrieves a list of machines associated with the security recommendation.
|
||||
keywords: apis, graph api, supported apis, get, security recommendation for vulnerable machines, threat and vulnerability management, threat and vulnerability management api
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
@ -16,7 +16,7 @@ ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Get recommendation by machines
|
||||
# List machines by recommendation
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
@ -73,9 +73,10 @@ Here is an example of the response.
|
||||
"id": "e058770379bc199a9c179ce52a23e16fd44fd2ee",
|
||||
"computerDnsName": "niw_pc",
|
||||
"osPlatform": "Windows10",
|
||||
"rbacGroupId": 2154
|
||||
"rbacGroupName": "GroupTwo"
|
||||
}
|
||||
]
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
|
@ -65,8 +65,7 @@ GET https://api.securitycenter.windows.com/api/recommendations/va-_-google-_-chr
|
||||
|
||||
Here is an example of the response.
|
||||
|
||||
```
|
||||
Content-type: json
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api.securitycenter.windows.com/api/$metadata#Analytics.Contracts.PublicAPI.PublicProductDto",
|
||||
"id": "google-_-chrome",
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Get recommendation by vulnerabilities
|
||||
title: List vulnerabilities by recommendation
|
||||
description: Retrieves a list of vulnerabilities associated with the security recommendation.
|
||||
keywords: apis, graph api, supported apis, get, list of vulnerabilities, security recommendation, security recommendation for vulnerabilities, threat and vulnerability management, threat and vulnerability management api
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
@ -16,7 +16,7 @@ ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Get recommendation by vulnerabilities
|
||||
# List vulnerabilities by recommendation
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
@ -65,8 +65,7 @@ GET https://api.securitycenter.windows.com/api/recommendations/va-_-google-_-chr
|
||||
|
||||
Here is an example of the response.
|
||||
|
||||
```
|
||||
Content-type: json
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api.securitycenter.windows.com/api/$metadata#Collection(Analytics.Contracts.PublicAPI.PublicVulnerabilityDto)",
|
||||
"value": [
|
||||
@ -85,7 +84,8 @@ Content-type: json
|
||||
"exploitTypes": [],
|
||||
"exploitUris": []
|
||||
}
|
||||
]
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
|
@ -81,7 +81,8 @@ Here is an example of the response.
|
||||
"installations": 750,
|
||||
"vulnerabilities": 0
|
||||
}
|
||||
]
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
|
@ -17,10 +17,10 @@ ms.topic: article
|
||||
---
|
||||
|
||||
# List software inventory API
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
[!include[Prerelease information](../../includes/prerelease.md)]
|
||||
**Applies to:** [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
- Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-exposedapis-abovefoldlink)
|
||||
|
||||
Retrieves the organization software inventory.
|
||||
|
||||
@ -66,20 +66,21 @@ GET https://api.securitycenter.windows.com/api/Software
|
||||
Here is an example of the response.
|
||||
|
||||
|
||||
```
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api-us.securitycenter.windows.com/api/$metadata#Software",
|
||||
"value": [
|
||||
{
|
||||
"id": "microsoft-_-edge",
|
||||
"name": "edge",
|
||||
"vendor": "microsoft",
|
||||
"weaknesses": 467,
|
||||
"publicExploit": true,
|
||||
"activeAlert": false,
|
||||
"exposedMachines": 172,
|
||||
"impactScore": 2.39947438
|
||||
}
|
||||
{
|
||||
"id": "microsoft-_-edge",
|
||||
"name": "edge",
|
||||
"vendor": "microsoft",
|
||||
"weaknesses": 467,
|
||||
"publicExploit": true,
|
||||
"activeAlert": false,
|
||||
"exposedMachines": 172,
|
||||
"impactScore": 2.39947438
|
||||
}
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
@ -71,21 +71,22 @@ Here is an example of the response.
|
||||
{
|
||||
"@odata.context": "https://api-us.securitycenter.windows.com/api/$metadata#Collection(Analytics.Contracts.PublicAPI.PublicVulnerabilityDto)",
|
||||
"value": [
|
||||
{
|
||||
"id": "CVE-2017-0140",
|
||||
"name": "CVE-2017-0140",
|
||||
"description": "A security feature bypass vulnerability exists when Microsoft Edge improperly handles requests of different origins. The vulnerability allows Microsoft Edge to bypass Same-Origin Policy (SOP) restrictions, and to allow requests that should otherwise be ignored. An attacker who successfully exploited the vulnerability could force the browser to send data that would otherwise be restricted.In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability through Microsoft Edge and then convince a user to view the website. The attacker could also take advantage of compromised websites, and websites that accept or host user-provided content or advertisements. These websites could contain specially crafted content that could exploit the vulnerability.The security update addresses the vulnerability by modifying how affected Microsoft Edge handles different-origin requests.",
|
||||
"severity": "Medium",
|
||||
"cvssV3": 4.2,
|
||||
"exposedMachines": 1,
|
||||
"publishedOn": "2017-03-14T00:00:00Z",
|
||||
"updatedOn": "2019-10-03T00:03:00Z",
|
||||
"publicExploit": false,
|
||||
"exploitVerified": false,
|
||||
"exploitInKit": false,
|
||||
"exploitTypes": [],
|
||||
"exploitUris": []
|
||||
}
|
||||
{
|
||||
"id": "CVE-2017-0140",
|
||||
"name": "CVE-2017-0140",
|
||||
"description": "A security feature bypass vulnerability exists when Microsoft Edge improperly handles requests of different origins. The vulnerability allows Microsoft Edge to bypass Same-Origin Policy (SOP) restrictions, and to allow requests that should otherwise be ignored. An attacker who successfully exploited the vulnerability could force the browser to send data that would otherwise be restricted.In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability through Microsoft Edge and then convince a user to view the website. The attacker could also take advantage of compromised websites, and websites that accept or host user-provided content or advertisements. These websites could contain specially crafted content that could exploit the vulnerability.The security update addresses the vulnerability by modifying how affected Microsoft Edge handles different-origin requests.",
|
||||
"severity": "Medium",
|
||||
"cvssV3": 4.2,
|
||||
"exposedMachines": 1,
|
||||
"publishedOn": "2017-03-14T00:00:00Z",
|
||||
"updatedOn": "2019-10-03T00:03:00Z",
|
||||
"publicExploit": false,
|
||||
"exploitVerified": false,
|
||||
"exploitInKit": false,
|
||||
"exploitTypes": [],
|
||||
"exploitUris": []
|
||||
}
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
@ -65,8 +65,7 @@ GET https://api.securitycenter.windows.com/api/Vulnerabilities/CVE-2019-0608
|
||||
|
||||
Here is an example of the response.
|
||||
|
||||
```
|
||||
Content-type: json
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api-us.securitycenter.windows.com/api/$metadata#Vulnerabilities/$entity",
|
||||
"id": "CVE-2019-0608",
|
||||
|
Before Width: | Height: | Size: 2.4 KiB |
Before Width: | Height: | Size: 3.2 KiB |
Before Width: | Height: | Size: 2.8 KiB |
Before Width: | Height: | Size: 2.2 KiB |
Before Width: | Height: | Size: 2.5 KiB |
Before Width: | Height: | Size: 2.8 KiB |
Before Width: | Height: | Size: 2.0 KiB |
Before Width: | Height: | Size: 1.0 KiB After Width: | Height: | Size: 1.0 KiB |
After Width: | Height: | Size: 2.2 KiB |
After Width: | Height: | Size: 1.5 KiB |
After Width: | Height: | Size: 1.6 KiB |
After Width: | Height: | Size: 2.1 KiB |
After Width: | Height: | Size: 1.7 KiB |
@ -36,7 +36,7 @@ Monitoring network connection behind a forward proxy is possible due to addition
|
||||
|
||||
Network protection can be controlled using the following modes:
|
||||
|
||||
- **Block** <br> Users or apps will be blocked from connecting to dangerous domains. You will be able to see this activity in Windows Defender Security Center.
|
||||
- **Block** <br> Users or apps will be blocked from connecting to dangerous domains. You will be able to see this activity in Microsoft Defender Security Center.
|
||||
- **Audit** <br> Users or apps will not be blocked from connecting to dangerous domains. However, you will still see this activity in Microsoft Defender Security Center.
|
||||
|
||||
|
||||
|
@ -119,11 +119,11 @@ The following commands are available for user roles that's been granted the abil
|
||||
Command | Description
|
||||
:---|:---
|
||||
analyze | Analyses the entity with various incrimination engines to reach a verdict.
|
||||
getfile | Gets a file from the machine. <br> NOTE: This command has a prerequisite command. You can use the `-auto` command in conjuction with `getfile` to automatically run the prerequisite command.
|
||||
getfile | Gets a file from the machine. <br> NOTE: This command has a prerequisite command. You can use the `-auto` command in conjunction with `getfile` to automatically run the prerequisite command.
|
||||
run | Runs a PowerShell script from the library on the machine.
|
||||
library | Lists files that were uploaded to the live response library.
|
||||
putfile | Puts a file from the library to the machine. Files are saved in a working folder and are deleted when the machine restarts by default.
|
||||
remediate | Remediates an entity on the machine. The remediation action will vary depending on the entity type:<br>- File: delete<br>- Process: stop, delete image file<br>- Service: stop, delete image file<br>- Registry entry: delete<br>- Scheduled task: remove<br>- Startup folder item: delete file <br> NOTE: This command has a prerequisite command. You can use the `-auto` command in conjuction with `remediate` to automatically run the prerequisite command.
|
||||
remediate | Remediates an entity on the machine. The remediation action will vary depending on the entity type:<br>- File: delete<br>- Process: stop, delete image file<br>- Service: stop, delete image file<br>- Registry entry: delete<br>- Scheduled task: remove<br>- Startup folder item: delete file <br> NOTE: This command has a prerequisite command. You can use the `-auto` command in conjunction with `remediate` to automatically run the prerequisite command.
|
||||
undo | Restores an entity that was remediated.
|
||||
|
||||
|
||||
|
@ -56,7 +56,7 @@ For more information on how to configure exclusions from JAMF, Intune, or anothe
|
||||
|
||||
Open the Microsoft Defender ATP application and navigate to **Manage settings** > **Add or Remove Exclusion...**, as shown in the following screenshot:
|
||||
|
||||

|
||||

|
||||
|
||||
Select the type of exclusion that you wish to add and follow the prompts.
|
||||
|
||||
|
@ -34,14 +34,14 @@ Before you get started, see [the main Microsoft Defender ATP for Mac page](micro
|
||||
|
||||
## Download installation and onboarding packages
|
||||
|
||||
Download the installation and onboarding packages from Windows Defender Security Center:
|
||||
Download the installation and onboarding packages from Microsoft Defender Security Center:
|
||||
|
||||
1. In Windows Defender Security Center, go to **Settings > Machine Management > Onboarding**.
|
||||
1. In Microsoft Defender Security Center, go to **Settings > Machine Management > Onboarding**.
|
||||
2. In Section 1 of the page, set operating system to **Linux, macOS, iOS, and Android** and Deployment method to **Local script**.
|
||||
3. In Section 2 of the page, select **Download installation package**. Save it as wdav.pkg to a local directory.
|
||||
4. In Section 2 of the page, select **Download onboarding package**. Save it as WindowsDefenderATPOnboardingPackage.zip to the same directory.
|
||||
|
||||

|
||||

|
||||
|
||||
5. From a command prompt, verify that you have the two files.
|
||||
Extract the contents of the .zip files:
|
||||
@ -112,6 +112,7 @@ The installation proceeds.
|
||||
After installation, you'll see the Microsoft Defender icon in the macOS status bar in the top-right corner.
|
||||
|
||||

|
||||
|
||||
|
||||
## How to Allow Full Disk Access
|
||||
|
||||
|
@ -43,7 +43,7 @@ Download the installation and onboarding packages from Microsoft Defender Securi
|
||||
4. In Section 2 of the page, select **Download onboarding package**. Save it as _WindowsDefenderATPOnboardingPackage.zip_ to the same directory.
|
||||
5. Download **IntuneAppUtil** from [https://docs.microsoft.com/intune/lob-apps-macos](https://docs.microsoft.com/intune/lob-apps-macos).
|
||||
|
||||

|
||||

|
||||
|
||||
6. From a command prompt, verify that you have the three files.
|
||||
Extract the contents of the .zip files:
|
||||
@ -90,19 +90,19 @@ You need no special provisioning for a Mac device beyond a standard [Company Por
|
||||
|
||||
1. You are asked to confirm device management.
|
||||
|
||||

|
||||

|
||||
|
||||
Select **Open System Preferences**, locate **Management Profile** on the list, and select **Approve...**. Your Management Profile would be displayed as **Verified**:
|
||||
Select **Open System Preferences**, locate **Management Profile** on the list, and select **Approve...**. Your Management Profile would be displayed as **Verified**:
|
||||
|
||||

|
||||

|
||||
|
||||
2. Select **Continue** and complete the enrollment.
|
||||
|
||||
You may now enroll more devices. You can also enroll them later, after you have finished provisioning system configuration and application packages.
|
||||
You may now enroll more devices. You can also enroll them later, after you have finished provisioning system configuration and application packages.
|
||||
|
||||
3. In Intune, open **Manage** > **Devices** > **All devices**. Here you can see your device among those listed:
|
||||
|
||||

|
||||

|
||||
|
||||
## Create System Configuration profiles
|
||||
|
||||
@ -284,9 +284,9 @@ You may now enroll more devices. You can also enroll them later, after you have
|
||||
|
||||
10. Select **Manage > Assignments**. In the **Include** tab, select **Assign to All Users & All devices**.
|
||||
|
||||
Once the Intune changes are propagated to the enrolled devices, you can see them listed under **Monitor** > **Device status**:
|
||||
Once the Intune changes are propagated to the enrolled devices, you can see them listed under **Monitor** > **Device status**:
|
||||
|
||||

|
||||

|
||||
|
||||
## Publish application
|
||||
|
||||
@ -294,27 +294,28 @@ Once the Intune changes are propagated to the enrolled devices, you can see them
|
||||
2. Select **App type=Other/Line-of-business app**.
|
||||
3. Select **file=wdav.pkg.intunemac**. Select **OK** to upload.
|
||||
4. Select **Configure** and add the required information.
|
||||
5. Use **macOS High Sierra 10.13** as the minimum OS and set *Ignore app version* to **Yes**. Other settings can be any arbitrary value.
|
||||
5. Use **macOS High Sierra 10.13** as the minimum OS.
|
||||
6. Set *Ignore app version* to **Yes**. Other settings can be any arbitrary value.
|
||||
|
||||
> [!CAUTION]
|
||||
> Failure to set *Ignore app version* to **Yes** impacts the ability of the application to receive updates through Microsoft AutoUpdate. See [Deploy updates for Microsoft Defender ATP for Mac](mac-updates.md) for additional information about how the product is updated.
|
||||
> Setting *Ignore app version* to **No** impacts the ability of the application to receive updates through Microsoft AutoUpdate. If the version uploaded by Intune is lower than the version on the device, then the lower version will be installed, effectively downgrading Defender. This could result in a non-functioning application. See [Deploy updates for Microsoft Defender ATP for Mac](mac-updates.md) for additional information about how the product is updated. If you deployed Defender with *Ignore app version* set to **No**, please change it to **Yes**. If Defender still cannot be installed on a client machine, then uninstall Defender and push the updated policy.
|
||||
|
||||

|
||||
|
||||
6. Select **OK** and **Add**.
|
||||
7. Select **OK** and **Add**.
|
||||
|
||||

|
||||
|
||||
7. It may take a few moments to upload the package. After it's done, select the package from the list and go to **Assignments** and **Add group**.
|
||||
8. It may take a few moments to upload the package. After it's done, select the package from the list and go to **Assignments** and **Add group**.
|
||||
|
||||

|
||||
|
||||
8. Change **Assignment type** to **Required**.
|
||||
9. Select **Included Groups**. Select **Make this app required for all devices=Yes**. Click **Select group to include** and add a group that contains the users you want to target. Select **OK** and **Save**.
|
||||
9. Change **Assignment type** to **Required**.
|
||||
10. Select **Included Groups**. Select **Make this app required for all devices=Yes**. Click **Select group to include** and add a group that contains the users you want to target. Select **OK** and **Save**.
|
||||
|
||||

|
||||
|
||||
10. After some time the application will be published to all enrolled devices. You can see it listed in **Monitor** > **Device**, under **Device install status**:
|
||||
11. After some time the application will be published to all enrolled devices. You can see it listed in **Monitor** > **Device**, under **Device install status**:
|
||||
|
||||

|
||||
|
||||
|
@ -38,14 +38,19 @@ In addition, for JAMF deployment, you need to be familiar with JAMF administrati
|
||||
|
||||
## Download installation and onboarding packages
|
||||
|
||||
Download the installation and onboarding packages from Windows Defender Security Center:
|
||||
Download the installation and onboarding packages from Microsoft Defender Security Center:
|
||||
|
||||
1. In Windows Defender Security Center, go to **Settings > device Management > Onboarding**.
|
||||
2. In Section 1 of the page, set the operating system to **Linux, macOS, iOS or Android** and deployment method to **Mobile Device Management / Microsoft Intune**.
|
||||
3. In Section 2 of the page, select **Download installation package**. Save it as _wdav.pkg_ to a local directory.
|
||||
4. In Section 2 of the page, select **Download onboarding package**. Save it as _WindowsDefenderATPOnboardingPackage.zip_ to the same directory.
|
||||
1. In Microsoft Defender Security Center, go to **Settings > Machine management > Onboarding**.
|
||||
2. In Section 1 of the page, set the operating system to **Linux, macOS, iOS or Android**.
|
||||
3. Set the deployment method to **Mobile Device Management / Microsoft Intune**.
|
||||
|
||||
>[!NOTE]
|
||||
>JamF falls under **Mobile Device Management**.
|
||||
|
||||
4. In Section 2 of the page, select **Download installation package**. Save it as _wdav.pkg_ to a local directory.
|
||||
5. In Section 2 of the page, select **Download onboarding package**. Save it as _WindowsDefenderATPOnboardingPackage.zip_ to the same directory.
|
||||
|
||||

|
||||

|
||||
|
||||
5. From the command prompt, verify that you have the two files. Extract the contents of the .zip files like so:
|
||||
|
||||
@ -87,7 +92,7 @@ To approve the kernel extension:
|
||||
1. In **Computers > Configuration Profiles** select **Options > Approved Kernel Extensions**.
|
||||
2. Use **UBF8T346G9** for Team Id.
|
||||
|
||||

|
||||

|
||||
|
||||
### Privacy Preferences Policy Control
|
||||
|
||||
@ -103,7 +108,7 @@ Add the following JAMF policy to grant Full Disk Access to Microsoft Defender AT
|
||||
3. Set Code Requirement to `identifier "com.microsoft.wdav" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = UBF8T346G9`.
|
||||
4. Set app or service to SystemPolicyAllFiles and access to Allow.
|
||||
|
||||

|
||||

|
||||
|
||||
#### Configuration Profile's Scope
|
||||
|
||||
@ -153,16 +158,16 @@ You'll need no special provisioning for a macOS computer, beyond the standard JA
|
||||
> [!NOTE]
|
||||
> After a computer is enrolled, it will show up in the Computers inventory (All Computers).
|
||||
|
||||
1. Open **Device Profiles**, from the **General** tab, and make sure that **User Approved MDM** is set to **Yes**. If it's currently set to No, the user needs to open **System Preferences > Profiles** and select **Approve** on the MDM Profile.
|
||||
- Open **Device Profiles**, from the **General** tab, and make sure that **User Approved MDM** is set to **Yes**. If it's currently set to No, the user needs to open **System Preferences > Profiles** and select **Approve** on the MDM Profile.
|
||||
|
||||
<br/>
|
||||

|
||||
<br/>
|
||||

|
||||
|
||||
After a moment, the device's User Approved MDM status will change to **Yes**.
|
||||
After a moment, the device's User Approved MDM status will change to **Yes**.
|
||||
|
||||

|
||||

|
||||
|
||||
You may now enroll additional devices. You may also enroll them later, after you have finished provisioning system configuration and application packages.
|
||||
You may now enroll additional devices. You may also enroll them later, after you have finished provisioning system configuration and application packages.
|
||||
|
||||
## Deployment
|
||||
|
||||
|
@ -80,6 +80,18 @@ Specify whether the antivirus engine runs in passive mode. Passive mode has the
|
||||
| **Possible values** | false (default) <br/> true |
|
||||
| **Comments** | Available in Microsoft Defender ATP version 100.67.60 or higher. |
|
||||
|
||||
#### Exclusion merge policy
|
||||
|
||||
Specify the merge policy for exclusions. This can be a combination of administrator-defined and user-defined exclusions (`merge`) or only administrator-defined exclusions (`admin_only`). This setting can be used to restrict local users from defining their own exclusions.
|
||||
|
||||
|||
|
||||
|:---|:---|
|
||||
| **Domain** | `com.microsoft.wdav` |
|
||||
| **Key** | exclusionsMergePolicy |
|
||||
| **Data type** | String |
|
||||
| **Possible values** | merge (default) <br/> admin_only |
|
||||
| **Comments** | Available in Microsoft Defender ATP version 100.83.73 or higher. |
|
||||
|
||||
#### Scan exclusions
|
||||
|
||||
Specify entities excluded from being scanned. Exclusions can be specified by full paths, extensions, or file names.
|
||||
@ -138,9 +150,9 @@ Specify content excluded from being scanned by file extension.
|
||||
| **Possible values** | valid file extensions |
|
||||
| **Comments** | Applicable only if *$type* is *excludedFileExtension* |
|
||||
|
||||
##### Name of excluded content
|
||||
##### Process excluded from the scan
|
||||
|
||||
Specify content excluded from being scanned by file name.
|
||||
Specify a process for which all file activity is excluded from scanning. The process can be specified either by its name (e.g. `cat`) or full path (e.g. `/bin/cat`).
|
||||
|
||||
|||
|
||||
|:---|:---|
|
||||
@ -160,6 +172,18 @@ Specify threats by name that are not blocked by Microsoft Defender ATP for Mac.
|
||||
| **Key** | allowedThreats |
|
||||
| **Data type** | Array of strings |
|
||||
|
||||
#### Disallowed threat actions
|
||||
|
||||
Restricts the actions that the local user of a device can take when threats are detected. The actions included in this list are not displayed in the user interface.
|
||||
|
||||
|||
|
||||
|:---|:---|
|
||||
| **Domain** | `com.microsoft.wdav` |
|
||||
| **Key** | disallowedThreatActions |
|
||||
| **Data type** | Array of strings |
|
||||
| **Possible values** | allow (restricts users from allowing threats) <br/> restore (restricts users from restoring threats from the quarantine) |
|
||||
| **Comments** | Available in Microsoft Defender ATP version 100.83.73 or higher. |
|
||||
|
||||
#### Threat type settings
|
||||
|
||||
Specify how certain threat types are handled by Microsoft Defender ATP for Mac.
|
||||
@ -197,6 +221,18 @@ Specify what action to take when a threat of the type specified in the preceding
|
||||
| **Data type** | String |
|
||||
| **Possible values** | audit (default) <br/> block <br/> off |
|
||||
|
||||
#### Threat type settings merge policy
|
||||
|
||||
Specify the merge policy for threat type settings. This can be a combination of administrator-defined and user-defined settings (`merge`) or only administrator-defined settings (`admin_only`). This setting can be used to restrict local users from defining their own settings for different threat types.
|
||||
|
||||
|||
|
||||
|:---|:---|
|
||||
| **Domain** | `com.microsoft.wdav` |
|
||||
| **Key** | threatTypeSettingsMergePolicy |
|
||||
| **Data type** | String |
|
||||
| **Possible values** | merge (default) <br/> admin_only |
|
||||
| **Comments** | Available in Microsoft Defender ATP version 100.83.73 or higher. |
|
||||
|
||||
### Cloud-delivered protection preferences
|
||||
|
||||
Configure the cloud-driven protection features of Microsoft Defender ATP for Mac.
|
||||
@ -371,6 +407,10 @@ The following configuration profile will:
|
||||
### Intune profile
|
||||
|
||||
```XML
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
|
||||
<plist version="1">
|
||||
<dict>
|
||||
<key>PayloadUUID</key>
|
||||
<string>C4E6A782-0C8D-44AB-A025-EB893987A295</string>
|
||||
<key>PayloadType</key>
|
||||
@ -439,6 +479,8 @@ The following configuration profile will:
|
||||
</dict>
|
||||
</dict>
|
||||
</array>
|
||||
</dict>
|
||||
</plist>
|
||||
```
|
||||
|
||||
## Full configuration profile example
|
||||
@ -482,11 +524,24 @@ The following configuration profile contains entries for all settings described
|
||||
<key>extension</key>
|
||||
<string>pdf</string>
|
||||
</dict>
|
||||
<dict>
|
||||
<key>$type</key>
|
||||
<string>excludedFileName</string>
|
||||
<key>name</key>
|
||||
<string>cat</string>
|
||||
</dict>
|
||||
</array>
|
||||
<key>exclusionsMergePolicy</key>
|
||||
<string>merge</string>
|
||||
<key>allowedThreats</key>
|
||||
<array>
|
||||
<string>EICAR-Test-File (not a virus)</string>
|
||||
</array>
|
||||
<key>disallowedThreatActions</key>
|
||||
<array>
|
||||
<string>allow</string>
|
||||
<string>restore</string>
|
||||
</array>
|
||||
<key>threatTypeSettings</key>
|
||||
<array>
|
||||
<dict>
|
||||
@ -502,6 +557,8 @@ The following configuration profile contains entries for all settings described
|
||||
<string>audit</string>
|
||||
</dict>
|
||||
</array>
|
||||
<key>threatTypeSettingsMergePolicy</key>
|
||||
<string>merge</string>
|
||||
</dict>
|
||||
<key>cloudService</key>
|
||||
<dict>
|
||||
@ -593,11 +650,24 @@ The following configuration profile contains entries for all settings described
|
||||
<key>extension</key>
|
||||
<string>pdf</string>
|
||||
</dict>
|
||||
<dict>
|
||||
<key>$type</key>
|
||||
<string>excludedFileName</string>
|
||||
<key>name</key>
|
||||
<string>cat</string>
|
||||
</dict>
|
||||
</array>
|
||||
<key>exclusionsMergePolicy</key>
|
||||
<string>merge</string>
|
||||
<key>allowedThreats</key>
|
||||
<array>
|
||||
<string>EICAR-Test-File (not a virus)</string>
|
||||
</array>
|
||||
<key>disallowedThreatActions</key>
|
||||
<array>
|
||||
<string>allow</string>
|
||||
<string>restore</string>
|
||||
</array>
|
||||
<key>threatTypeSettings</key>
|
||||
<array>
|
||||
<dict>
|
||||
@ -613,6 +683,8 @@ The following configuration profile contains entries for all settings described
|
||||
<string>audit</string>
|
||||
</dict>
|
||||
</array>
|
||||
<key>threatTypeSettingsMergePolicy</key>
|
||||
<string>merge</string>
|
||||
</dict>
|
||||
<key>cloudService</key>
|
||||
<dict>
|
||||
|
@ -19,6 +19,12 @@ ms.topic: conceptual
|
||||
|
||||
# What's new in Microsoft Defender Advanced Threat Protection for Mac
|
||||
|
||||
## 100.83.73
|
||||
|
||||
- Added more controls for IT administrators around [management of exclusions](mac-preferences.md#exclusion-merge-policy), [management of threat type settings](mac-preferences.md#threat-type-settings-merge-policy), and [disallowed threat actions](mac-preferences.md#disallowed-threat-actions)
|
||||
- When Full Disk Access is not enabled on the device, a warning is now displayed in the status menu
|
||||
- Performance improvements & bug fixes
|
||||
|
||||
## 100.82.60
|
||||
|
||||
- Addressed an issue where the product fails to start following a definition update.
|
||||
|