diff --git a/.gitignore b/.gitignore index 604950802e..a39f55da7b 100644 --- a/.gitignore +++ b/.gitignore @@ -12,4 +12,4 @@ Tools/NuGet/ packages.config # User-specific files -.vs/ \ No newline at end of file +.vs/ diff --git a/browsers/internet-explorer/ie11-deploy-guide/change-history-for-internet-explorer-11.md b/browsers/internet-explorer/ie11-deploy-guide/change-history-for-internet-explorer-11.md index 1949a24903..1717c9f622 100644 --- a/browsers/internet-explorer/ie11-deploy-guide/change-history-for-internet-explorer-11.md +++ b/browsers/internet-explorer/ie11-deploy-guide/change-history-for-internet-explorer-11.md @@ -11,6 +11,11 @@ ms.sitesec: library # Change history for Internet Explorer 11 This topic lists new and updated topics in the Internet Explorer 11 documentation for both Windows 10 and Windows 10 Mobile. +## March 2017 +|New or changed topic | Description | +|----------------------|-------------| +|[New group policy settings for Internet Explorer 11](new-group-policy-settings-for-ie11.md) |Updated to add the Allow VBScript to run in Internet Explorer and the Hide the button (next to the New Tab button) that opens Microsoft Edge settings. | + ## November 2016 |New or changed topic | Description | |----------------------|-------------| diff --git a/browsers/internet-explorer/ie11-deploy-guide/new-group-policy-settings-for-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/new-group-policy-settings-for-ie11.md index d63465dbe0..149ef61a09 100644 --- a/browsers/internet-explorer/ie11-deploy-guide/new-group-policy-settings-for-ie11.md +++ b/browsers/internet-explorer/ie11-deploy-guide/new-group-policy-settings-for-ie11.md @@ -16,63 +16,33 @@ Internet Explorer 11 gives you some new Group Policy settings to help you manag |Policy |Category Path |Supported on |Explanation | |-------|--------------|-------------|------------| -|Turn off loading websites and content in the background to optimize performance |Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page |IE11 on Windows 10 |This policy setting determines whether Internet Explorer preemptively loads websites and content in the background, speeding up performance such that when the user clicks a hyperlink, the background page seamlessly switches into view.

If you enable this policy setting, IE doesn't load any websites or content in the background.

If you disable this policy setting, IE preemptively loads websites and content in the background.

If you don’t configure this policy setting, users can turn this behavior on or off, using IE settings. This feature is turned on by default. | -|Allow Microsoft services to provide enhanced suggestions as the user types in the Address bar |Administrative Templates\Windows Components\Internet Explorer |IE11 on Windows 10 |This policy setting allows IE to provide enhanced suggestions as the user types in the Address bar. To provide enhanced suggestions, the user’s keystrokes are sent to Microsoft through Microsoft services.

If you enable this policy setting, users receive enhanced suggestions while typing in the Address bar. In addition, users won’t be able to change the **Suggestions** setting on the **Settings** charm.

If you disable this policy setting, users won’t receive enhanced suggestions while typing in the Address bar. In addition, users won’t be able to change the **Suggestions** setting on the **Settings** charm.

If you don’t configure this policy setting, users can change the **Suggestions** setting on the **Settings** charm. | -|Turn off phone number detection |Administrative Templates\Windows Components\Internet Explorer\Internet Settings\Advanced settings\Browsing |IE11 on Windows 10 |This policy setting determines whether phone numbers are recognized and turned into hyperlinks, which can be used to invoke the default phone application on the system.

If you enable this policy setting, phone number detection is turned off. Users won’t be able to modify this setting.

If you disable this policy setting, phone number detection is turned on. Users won’t be able to modify this setting.

If you don't configure this policy setting, users can turn this behavior on or off, using IE settings. The default is on. | -|Allow IE to use the SPDY/3 network protocol |Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page |IE11 on Windows 10 |This policy setting determines whether Internet Explorer uses the SPDY/3 network protocol. SPDY/3 works with HTTP requests to optimize the latency of network requests through compression, multiplexing and prioritization.

If you enable this policy setting, Internet Explorer uses the SPDY/3 network protocol.

If you disable this policy setting, Internet Explorer won't use the SPDY/3 network protocol.

If you don't configure this policy setting, users can turn this behavior on or off, on the **Advanced* tab of the **Internet Options** dialog box. The default is on.

**Note**
We've replaced the SPDY/3 protocol with the HTTP2 protocol in Windows 10. You can configure the HTTP2 protocol by using the **Allow IE to use the HTTP2 network protocol** setting. | |Allow IE to use the HTTP2 network protocol |Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page |IE11 on Windows 10 |This policy setting determines whether IE uses the HTTP2 network protocol. HTTP2 works with HTTP requests to optimize the latency of network requests through compression, multiplexing, and prioritization.

If you enable this policy setting, IE uses the HTTP2 network protocol.

If you disable this policy setting, IE won't use the HTTP2 network protocol.

If you don't configure this policy setting, users can turn this behavior on or off, using the **Internet Explorer Advanced Internet Options** settings. The default is on. | +|Allow IE to use the SPDY/3 network protocol |Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page |IE11 on Windows 10 |This policy setting determines whether Internet Explorer uses the SPDY/3 network protocol. SPDY/3 works with HTTP requests to optimize the latency of network requests through compression, multiplexing and prioritization.

If you enable this policy setting, Internet Explorer uses the SPDY/3 network protocol.

If you disable this policy setting, Internet Explorer won't use the SPDY/3 network protocol.

If you don't configure this policy setting, users can turn this behavior on or off, on the **Advanced* tab of the **Internet Options** dialog box. The default is on.

**Note**
We've replaced the SPDY/3 protocol with the HTTP2 protocol in Windows 10. You can configure the HTTP2 protocol by using the **Allow IE to use the HTTP2 network protocol** setting. | +|Allow Microsoft services to provide enhanced suggestions as the user types in the Address bar |Administrative Templates\Windows Components\Internet Explorer |IE11 on Windows 10 |This policy setting allows IE to provide enhanced suggestions as the user types in the Address bar. To provide enhanced suggestions, the user’s keystrokes are sent to Microsoft through Microsoft services.

If you enable this policy setting, users receive enhanced suggestions while typing in the Address bar. In addition, users won’t be able to change the **Suggestions** setting on the **Settings** charm.

If you disable this policy setting, users won’t receive enhanced suggestions while typing in the Address bar. In addition, users won’t be able to change the **Suggestions** setting on the **Settings** charm.

If you don’t configure this policy setting, users can change the **Suggestions** setting on the **Settings** charm. | +|Allow only approved domains to use the TDC ActiveX control |

|IE11 in Windows 10 |This policy setting determines whether users can run the Tabular Data Control (TDC) ActiveX control, based on security zone. By default, the TDC ActiveX Control is disabled in the **Internet** and **Restricted Sites** security zones.

If you enable this policy setting, users won’t be able to run the TDC ActiveX control from all sites in the specified zone.

If you disable this policy setting, users can run the TDC Active X control from all sites in the specified zone. | +|Allow SSL3 Fallback |Administrative Templates\Windows Components\Internet Explorer\Security Features |Internet Explorer 11 on Windows 10 |This policy setting allows you to stop websites from falling back to using Secure Socket Layer (SSL) 3.0 or lower, if Transport Layer Security (TLS) 1.0 or higher, fails. This setting doesn’t affect which security protocols are enabled.

If you enable this policy setting and a website fails while using the TLS 1.0 or higher security protocols, Internet Explorer will try to fallback and use SSL 3.0 or lower security protocols.

If you disable or don’t configure this setting, Internet Explorer uses the default system protocols.

**Important:**
By default, SSL 3.0 is disabled. If you choose to enable SSL 3.0, we recommend that you disable or don't configure this setting to help mitigate potential man-in-the-middle attacks. | +|Allow VBScript to run in Internet Explorer|

|Internet Explorer 11|This policy setting lets you decide whether VBScript can run on pages in specific Internet Explorer zones.

If you enable this policy setting (default), you must also pick one of the following options from the Options box:

If you disable or don’t configure this policy setting, VBScript runs without any interaction in the specified zone.| +|Always send Do Not Track header |Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page |At least Internet Explorer 10 |This policy setting allows you to configure how IE sends the Do Not Track (DNT) header.

If you enable this policy setting, IE sends a `DNT:1` header with all HTTP and HTTPS requests. The `DNT:1` header signals to the servers not to track the user.

**In Internet Explorer 9 and 10:**
If you disable this policy setting, IE only sends the Do Not Track header if a Tracking Protection List is enabled or inPrivate Browsing mode is used.

**In at least IE11:**
If you disable this policy setting, IE only sends the Do Not Track header if inPrivate Browsing mode is used.

If you don't configure the policy setting, users can select the **Always send Do Not Track header** option on the **Advanced* tab of the **Internet Options** dialog box. By selecting this option, IE sends a `DNT:1` header with all HTTP and HTTPS requests; unless the user grants a site-specific exception, in which case IE sends a `DNT:0` header. By default, this option is enabled. | |Don't run antimalware programs against ActiveX controls
(Internet, Restricted Zones) |

|IE11 on Windows 10 |This policy setting determines whether IE runs antimalware programs against ActiveX controls, to check if they're safe to load on pages.

If you enable this policy setting, IE won't check with your antimalware program to see if it's safe to create an instance of the ActiveX control.

If you disable this policy setting, IE always checks with your antimalware program to see if it's safe to create an instance of the ActiveX control.

If you don't configure this policy setting, IE always checks with your antimalware program to see if it's safe to create an instance of the ActiveX control. Users can turn this behavior on or off, using the Internet Explorer's **Security** settings. | |Don't run antimalware programs against ActiveX controls
(Intranet, Trusted, Local Machine Zones) |

|IE11 on Windows 10 |This policy setting determines whether IE runs antimalware programs against ActiveX controls, to check if they're safe to load on pages.

If you enable this policy setting, IE won't check with your antimalware program to see if it's safe to create an instance of the ActiveX control.

If you disable this policy setting, IE always checks with your antimalware program to see if it's safe to create an instance of the ActiveX control.

If you don't configure this policy setting, IE won't check with your antimalware program to see if it's safe to create an instance of the ActiveX control. Users can turn this behavior on or off, using Internet Explorer's **Security** settings. | -|Turn on 64-bit tab processes when running in Enhanced Protected Mode on 64-bit versions of Windows |Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page |IE11 on Windows 10 |This policy setting determines whether IE11 uses 64-bit processes (for greater security) or 32-bit processes (for greater compatibility) when running in Enhanced Protected Mode on 64-bit versions of Windows.

If you enable this policy setting, IE11 will use 64-bit tab processes when running in Enhanced Protected Mode on 64-bit versions of Windows.

If you disable this policy setting, IE11 will use 32-bit tab processes when running in Enhanced Protected Mode on 64-bit versions of Windows.

If you don't configure this policy setting, users can turn this feature on or off using IE settings. This feature is turned off by default.

**Important**
When using 64-bit processes, some ActiveX controls and toolbars might not be available. | -|Turn off sending UTF-8 query strings for URLs |Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page |IE11 on Windows 10 |This policy setting determines whether IE uses 8-bit Unicode Transformation Format (UTF-8) to encode query strings in URLs before sending them to servers or to proxy servers.

If you enable this policy setting, you must specify when to use UTF-8 to encode query strings:

If you disable or don't configure this policy setting, users can turn this behavior on or off, using IE Advanced Options settings. The default is to encode all query strings in UTF-8. | -|Turn off sending URL path as UTF-8 |User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Settings\URL Encoding |At least Windows Internet Explorer 7 |This policy setting determines whether to let IE send the path portion of a URL using the UTF-8 standard. This standard defines characters so they're readable in any language and lets you exchange Internet addresses (URLs) with characters included in any language.

If you enable this policy setting, UTF-8 is not allowed. Users won't be able to change this setting.

If you disable this policy setting, UTF-8 is allowed. Users won't be able to change this setting.

If you don't configure this policy setting, users can turn this behavior on or off. | -|Turn off the flip ahead with page prediction feature |Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page |At least Internet Explorer 10 on Windows 8 |This policy setting determines whether a user can swipe across a screen or click Forward to go to the next pre-loaded page of a website.

If you enable this policy setting, flip ahead with page prediction is turned off and the next webpage isn’t loaded into the background.

If you disable this policy setting, flip ahead with page prediction is turned on and the next webpage is loaded into the background.

If you don’t configure this setting, users can turn this behavior on or off, using the **Settings** charm.

**Note**
Microsoft collects your browsing history to improve how flip ahead with page prediction works. This feature isn’t available for Internet Explorer for the desktop. | -|Prevent deleting ActiveX Filtering, Tracking Protection and Do Not Track data |Administrative Templates\Windows Components\Internet Explorer\Delete Browsing History |At least Windows Internet Explorer 9 |**In Internet Explorer 9 and Internet Explorer 10:**
This policy setting prevents users from deleting ActiveX Filtering and Tracking Protection data, which includes the list of websites for which the user has chosen to disable ActiveX Filtering or Tracking Protection. In addition, Tracking Protection data is also collected if users turn on the **Personalized Tracking Protection List**, which blocks third-party items while the user is browsing.

**In IE11:**
This policy setting prevents users from deleting ActiveX Filtering, Tracking Protection data, and Do Not Track exceptions, stored in the **Delete Browsing History** dialog box, for visited websites.

If you enable this policy setting, ActiveX Filtering, Tracking Protection and Do Not Track data is preserved when the user clicks **Delete**.

If you disable this policy setting, ActiveX Filtering, Tracking Protection and Do Not Track data is deleted when the user clicks **Delete**.

If you don’t configure this policy setting, users can turn this feature on and off, determining whether to delete ActiveX Filtering, Tracking Protection, and Do Not Track data when clicking **Delete**. | -|Always send Do Not Track header |Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page |At least Internet Explorer 10 |This policy setting allows you to configure how IE sends the Do Not Track (DNT) header.

If you enable this policy setting, IE sends a `DNT:1` header with all HTTP and HTTPS requests. The `DNT:1` header signals to the servers not to track the user.

**In Internet Explorer 9 and 10:**
If you disable this policy setting, IE only sends the Do Not Track header if a Tracking Protection List is enabled or inPrivate Browsing mode is used.

**In at least IE11:**
If you disable this policy setting, IE only sends the Do Not Track header if inPrivate Browsing mode is used.

If you don't configure the policy setting, users can select the **Always send Do Not Track header** option on the **Advanced* tab of the **Internet Options** dialog box. By selecting this option, IE sends a `DNT:1` header with all HTTP and HTTPS requests; unless the user grants a site-specific exception, in which case IE sends a `DNT:0` header. By default, this option is enabled. | -|Turn off the ability to launch report site problems using a menu option |Administrative Templates\Windows Components\Internet Explorer\Browser menus |Internet Explorer 11 |This policy setting allows you to manage whether users can start the **eport Site Problems** dialog box from the **Internet Explorer** settings area or from the **Tools** menu.

If you enable this policy setting, users won’t be able to start the **Report Site Problems** dialog box from the Internet Explorer settings or the Tools menu.

If you disable or don’t configure this policy setting, users will be able to start the **Report Site Problems** dialog box from the **Internet Explorer** settings area or from the **Tools** menu. | -|Allow only approved domains to use the TDC ActiveX control |

|IE11 in Windows 10 |This policy setting determines whether users can run the Tabular Data Control (TDC) ActiveX control, based on security zone. By default, the TDC ActiveX Control is disabled in the **Internet** and **Restricted Sites** security zones.

If you enable this policy setting, users won’t be able to run the TDC ActiveX control from all sites in the specified zone.

If you disable this policy setting, users can run the TDC Active X control from all sites in the specified zone. | -|Turn on Site Discovery XML output |Administrative Templates\Windows Components\Internet Explorer |At least Internet Explorer 8 |This policy setting allows you to manage the XML output functionality of the Internet Explorer Site Discovery Toolkit.

If you enable this policy setting, the Internet Explorer Site Discovery Toolkit will log its collected data to an XML file, stored in your specified location.

If you disable or don’t configure this setting, the Internet Explorer Site Discovery Toolkit won’t log its collected data to an XML file.

**Note:**
Enabling or disabling this setting won’t impact any other output methods available to the Internet Explorer Site Discovery Toolkit. | -|Turn on Site Discovery WMI output |Administrative Templates\Windows Components\Internet Explorer |At least Internet Explorer 8 |This policy setting allows you to manage the WMI output functionality of the Internet Explorer Site Discovery Toolkit.

If you enable this policy setting, the Internet Explorer Site Discovery Toolkit will log its collected data to an WMI class, which can be aggregated by using a client-management solution, such as System Center Configuration Manager.

If you disable or don’t configure this setting, the Internet Explorer Site Discovery Toolkit won’t log its collected data to an WMI class.

**Note:**
Enabling or disabling this setting won’t impact any other output methods available to the Internet Explorer Site Discovery Toolkit. | +|Hide the button (next to the New Tab button) that opens Microsoft Edge |User Configuration\Administrative Templates\Windows Components/Internet Explorer\Internet Settings\Advanced Settings\Browsing\ |IE11 on Windows 10, Windows Insider Program |This policy setting lets you decide whether employees can see the open Microsoft Edge button, which appears next to the New Tab button.

If you enable this policy setting, the button to open Microsoft Edge from Internet Explorer will be hidden.

If you disable this policy setting, the button to open Microsoft Edge from Internet Explorer appears.

If you don't configure this policy setting, the button to open Microsoft Edge from Internet Explorer can be configured by your employees. | +|Let users turn on and use Enterprise Mode from the **Tools** menu |Administrative Templates\Windows Components\Internet Explorer |IE11 on Windows 10 |This policy setting lets you decide whether users can turn on Enterprise Mode for websites with compatibility issues. Optionally, this policy also lets you specify where to get reports (through post messages) about the websites for which users turn on Enterprise Mode using the **Tools** menu.

If you enable this policy setting, users can see and use the **Enterprise Mode** option from the **Tools** menu. If you enable this setting, but don’t specify a report location, Enterprise Mode will still be available to your users, but you won’t get any reports.

If you disable or don’t configure this policy setting, the menu option won’t appear and users won’t be able to turn on Enterprise Mode locally. | |Limit Site Discovery output by Domain |Administrative Templates\Windows Components\Internet Explorer |At least Internet Explorer 8 |This policy setting allows you to control which domains are included in the discovery function of the Internet Explorer Site Discovery Toolkit.

If you enable this policy setting, the Internet Explorer Site Discovery Toolkit collects data from all sites in your specified domains, configured by adding one domain per line to the included text box.

If you disable or don’t configure this setting, the Internet Explorer Site Discovery Toolkit collects data from all sites in all domains.

**Note:**
You can use this setting in conjunction with the other settings that control the Internet Explorer Site Discovery Toolkit. | |Limit Site Discovery output by Zone |Administrative Templates\Windows Components\Internet Explorer |At least Internet Explorer 8 |This policy setting allows you to control which zones are included in the discovery function of the Internet Explorer Site Discovery Toolkit.

If you enable this policy setting, the Internet Explorer Site Discovery Toolkit collects data from all specified security zones.

If you disable or don’t configure this setting, the Internet Explorer Site Discovery Toolkit collects data from all sites in all security zones.

To specify which zones can collect data, you must include a binary number that represents your selected zones, based on this order:


**Example 1:** Include only the Local Intranet zone (binary representation: 00010), based on:

**Example 2:** Include only the Restricted Sites, Trusted Sites, and Local Intranet zones (binary representation: 10110), based on:

**Note:**
You can use this setting in conjunction with the other settings that control the Internet Explorer Site Discovery Toolkit. | -|Allow SSL3 Fallback |Administrative Templates\Windows Components\Internet Explorer\Security Features |Internet Explorer 11 on Windows 10 |This policy setting allows you to stop websites from falling back to using Secure Socket Layer (SSL) 3.0 or lower, if Transport Layer Security (TLS) 1.0 or higher, fails. This setting doesn’t affect which security protocols are enabled.

If you enable this policy setting and a website fails while using the TLS 1.0 or higher security protocols, Internet Explorer will try to fallback and use SSL 3.0 or lower security protocols.

If you disable or don’t configure this setting, Internet Explorer uses the default system protocols.**Important:**
By default, SSL 3.0 is disabled. If you choose to enable SSL 3.0, we recommend that you disable or don't configure this setting to help mitigate potential man-in-the-middle attacks. | -|Turn off automatic download of the ActiveX VersionList |Administrative Templates\Windows Components\Internet Explorer\Security Features\Add-on Management |At least Windows Internet Explorer 8 |This policy setting allows you to decide whether Internet Explorer automatically downloads updated versions of Microsoft's VersionList.XML file. This file tells Internet Explorer whether to stop specific ActiveX controls from loading.

If you enable this policy setting, Internet Explorer stops automatically downloading updated versions of the VersionList.XML file.

If you disable or don’t configure this setting, Internet Explorer continues to download updated versions of the VersionList.XML file.

**Important:**
Stopping this file from updating breaks the out-of-date ActiveX control blocking feature, potentially compromising the security of the device. For more info, see the Out-of-Date ActiveX Control Blocking (https://technet.microsoft.com/en-us/itpro/internet-explorer/ie11-deploy-guide/out-of-date-activex-control-blocking) topic. | -|Let users turn on and use Enterprise Mode from the **Tools** menu |Administrative Templates\Windows Components\Internet Explorer |IE11 on Windows 10 |This policy setting lets you decide whether users can turn on Enterprise Mode for websites with compatibility issues. Optionally, this policy also lets you specify where to get reports (through post messages) about the websites for which users turn on Enterprise Mode using the **Tools** menu.

If you enable this policy setting, users can see and use the **Enterprise Mode** option from the **Tools** menu. If you enable this setting, but don’t specify a report location, Enterprise Mode will still be available to your users, but you won’t get any reports.

If you disable or don’t configure this policy setting, the menu option won’t appear and users won’t be able to turn on Enterprise Mode locally. | -|Use the Enterprise Mode IE website list |Administrative Templates\Windows Components\Internet Explorer |IE11 on Windows 10, version 1511 |This policy setting lets you specify where to find the list of websites you want opened using Enterprise Mode, instead of Standard mode, because of compatibility issues. Users can’t edit this list.

If you enable this policy setting, Internet Explorer downloads the Enterprise Mode website list from the `HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE`\Software\Policies\Microsoft\Internet Explorer\Main\EnterpriseMode hive, opening all included websites using Enterprise Mode. We recommend storing and downloading your list from a secure web server `(https://)`, to help protect against data tampering.

If you disable or don’t configure this policy setting, Internet Explorer opens all websites using **Standard** mode. | +|Prevent deleting ActiveX Filtering, Tracking Protection and Do Not Track data |Administrative Templates\Windows Components\Internet Explorer\Delete Browsing History |At least Windows Internet Explorer 9 |**In Internet Explorer 9 and Internet Explorer 10:**
This policy setting prevents users from deleting ActiveX Filtering and Tracking Protection data, which includes the list of websites for which the user has chosen to disable ActiveX Filtering or Tracking Protection. In addition, Tracking Protection data is also collected if users turn on the **Personalized Tracking Protection List**, which blocks third-party items while the user is browsing.

**In IE11:**
This policy setting prevents users from deleting ActiveX Filtering, Tracking Protection data, and Do Not Track exceptions, stored in the **Delete Browsing History** dialog box, for visited websites.

If you enable this policy setting, ActiveX Filtering, Tracking Protection and Do Not Track data is preserved when the user clicks **Delete**.

If you disable this policy setting, ActiveX Filtering, Tracking Protection and Do Not Track data is deleted when the user clicks **Delete**.

If you don’t configure this policy setting, users can turn this feature on and off, determining whether to delete ActiveX Filtering, Tracking Protection, and Do Not Track data when clicking **Delete**. | |Send all sites not included in the Enterprise Mode Site List to Microsoft Edge |Administrative Templates\Windows Components\Internet Explorer |IE11 on Windows 10, version 1607 |This policy setting lets you decide whether to open all sites that aren’t specified to open in IE11 by the Enterprise Mode site list, to open in Microsoft Edge.

If you enable this policy setting, you must also enable the Administrative Templates\Windows Components\Internet Explorer\Use the Enterprise Mode IE website list policy setting and you must include at least one site in the Enterprise Mode site list.

If you disable or don't configure this policy setting, all sites will open based on the currently active browser.

**Note:**
If you’ve also enabled the Administrative Templates\Windows Components\Microsoft Edge\Send all intranet sites to Internet Explorer 11 policy setting, then all intranet sites will continue to open in Internet Explorer 11. | |Show message when opening sites in Microsoft Edge using Enterprise Mode |Administrative Templates\Windows Components\Internet Explorer |IE11 on Windows 10, version 1607 |This policy setting lets you decide whether employees see an additional page in Internet Explorer 11, stating that a site has been opened using Microsoft Edge with Enterprise Mode.

If you enable this policy setting, employees see an additional page in Internet Explorer 11, stating that a site has been opened using Microsoft Edge with Enterprise Mode.

If you disable or don't configure this policy setting, the default app behavior occurs and no additional page appears. | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +|Turn off automatic download of the ActiveX VersionList |Administrative Templates\Windows Components\Internet Explorer\Security Features\Add-on Management |At least Windows Internet Explorer 8 |This policy setting allows you to decide whether Internet Explorer automatically downloads updated versions of Microsoft's VersionList.XML file. This file tells Internet Explorer whether to stop specific ActiveX controls from loading.

If you enable this policy setting, Internet Explorer stops automatically downloading updated versions of the VersionList.XML file.

If you disable or don’t configure this setting, Internet Explorer continues to download updated versions of the VersionList.XML file.

**Important:**
Stopping this file from updating breaks the out-of-date ActiveX control blocking feature, potentially compromising the security of the device. For more info, see the Out-of-Date ActiveX Control Blocking (https://technet.microsoft.com/en-us/itpro/internet-explorer/ie11-deploy-guide/out-of-date-activex-control-blocking) topic. | +|Turn off loading websites and content in the background to optimize performance |Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page |IE11 on Windows 10 |This policy setting determines whether Internet Explorer preemptively loads websites and content in the background, speeding up performance such that when the user clicks a hyperlink, the background page seamlessly switches into view.

If you enable this policy setting, IE doesn't load any websites or content in the background.

If you disable this policy setting, IE preemptively loads websites and content in the background.

If you don’t configure this policy setting, users can turn this behavior on or off, using IE settings. This feature is turned on by default. | +|Turn off phone number detection |Administrative Templates\Windows Components\Internet Explorer\Internet Settings\Advanced settings\Browsing |IE11 on Windows 10 |This policy setting determines whether phone numbers are recognized and turned into hyperlinks, which can be used to invoke the default phone application on the system.

If you enable this policy setting, phone number detection is turned off. Users won’t be able to modify this setting.

If you disable this policy setting, phone number detection is turned on. Users won’t be able to modify this setting.

If you don't configure this policy setting, users can turn this behavior on or off, using IE settings. The default is on. | +|Turn off sending URL path as UTF-8 |User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Settings\URL Encoding |At least Windows Internet Explorer 7 |This policy setting determines whether to let IE send the path portion of a URL using the UTF-8 standard. This standard defines characters so they're readable in any language and lets you exchange Internet addresses (URLs) with characters included in any language.

If you enable this policy setting, UTF-8 is not allowed. Users won't be able to change this setting.

If you disable this policy setting, UTF-8 is allowed. Users won't be able to change this setting.

If you don't configure this policy setting, users can turn this behavior on or off. | +|Turn off sending UTF-8 query strings for URLs |Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page |IE11 on Windows 10 |This policy setting determines whether IE uses 8-bit Unicode Transformation Format (UTF-8) to encode query strings in URLs before sending them to servers or to proxy servers.

If you enable this policy setting, you must specify when to use UTF-8 to encode query strings:

If you disable or don't configure this policy setting, users can turn this behavior on or off, using IE Advanced Options settings. The default is to encode all query strings in UTF-8. | +|Turn off the ability to launch report site problems using a menu option |Administrative Templates\Windows Components\Internet Explorer\Browser menus |Internet Explorer 11 |This policy setting allows you to manage whether users can start the **eport Site Problems** dialog box from the **Internet Explorer** settings area or from the **Tools** menu.

If you enable this policy setting, users won’t be able to start the **Report Site Problems** dialog box from the Internet Explorer settings or the Tools menu.

If you disable or don’t configure this policy setting, users will be able to start the **Report Site Problems** dialog box from the **Internet Explorer** settings area or from the **Tools** menu. | +|Turn off the flip ahead with page prediction feature |Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page |At least Internet Explorer 10 on Windows 8 |This policy setting determines whether a user can swipe across a screen or click Forward to go to the next pre-loaded page of a website.

If you enable this policy setting, flip ahead with page prediction is turned off and the next webpage isn’t loaded into the background.

If you disable this policy setting, flip ahead with page prediction is turned on and the next webpage is loaded into the background.

If you don’t configure this setting, users can turn this behavior on or off, using the **Settings** charm.

**Note**
Microsoft collects your browsing history to improve how flip ahead with page prediction works. This feature isn’t available for Internet Explorer for the desktop. | +|Turn on 64-bit tab processes when running in Enhanced Protected Mode on 64-bit versions of Windows |Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page |IE11 on Windows 10 |This policy setting determines whether IE11 uses 64-bit processes (for greater security) or 32-bit processes (for greater compatibility) when running in Enhanced Protected Mode on 64-bit versions of Windows.

If you enable this policy setting, IE11 will use 64-bit tab processes when running in Enhanced Protected Mode on 64-bit versions of Windows.

If you disable this policy setting, IE11 will use 32-bit tab processes when running in Enhanced Protected Mode on 64-bit versions of Windows.

If you don't configure this policy setting, users can turn this feature on or off using IE settings. This feature is turned off by default.

**Important**
When using 64-bit processes, some ActiveX controls and toolbars might not be available. | +|Turn on Site Discovery WMI output |Administrative Templates\Windows Components\Internet Explorer |At least Internet Explorer 8 |This policy setting allows you to manage the WMI output functionality of the Internet Explorer Site Discovery Toolkit.

If you enable this policy setting, the Internet Explorer Site Discovery Toolkit will log its collected data to an WMI class, which can be aggregated by using a client-management solution, such as System Center Configuration Manager.

If you disable or don’t configure this setting, the Internet Explorer Site Discovery Toolkit won’t log its collected data to an WMI class.

**Note:**
Enabling or disabling this setting won’t impact any other output methods available to the Internet Explorer Site Discovery Toolkit. | +|Turn on Site Discovery XML output |Administrative Templates\Windows Components\Internet Explorer |At least Internet Explorer 8 |This policy setting allows you to manage the XML output functionality of the Internet Explorer Site Discovery Toolkit.

If you enable this policy setting, the Internet Explorer Site Discovery Toolkit will log its collected data to an XML file, stored in your specified location.

If you disable or don’t configure this setting, the Internet Explorer Site Discovery Toolkit won’t log its collected data to an XML file.

**Note:**
Enabling or disabling this setting won’t impact any other output methods available to the Internet Explorer Site Discovery Toolkit. | +|Use the Enterprise Mode IE website list |Administrative Templates\Windows Components\Internet Explorer |IE11 on Windows 10, version 1511 |This policy setting lets you specify where to find the list of websites you want opened using Enterprise Mode, instead of Standard mode, because of compatibility issues. Users can’t edit this list.

If you enable this policy setting, Internet Explorer downloads the Enterprise Mode website list from the `HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE`\Software\Policies\Microsoft\Internet Explorer\Main\EnterpriseMode hive, opening all included websites using Enterprise Mode. We recommend storing and downloading your list from a secure web server `(https://)`, to help protect against data tampering.

If you disable or don’t configure this policy setting, Internet Explorer opens all websites using **Standard** mode. | ## Removed Group Policy settings IE11 no longer supports these Group Policy settings: diff --git a/education/windows/index.md b/education/windows/index.md index bf4146606d..6ee2d1946a 100644 --- a/education/windows/index.md +++ b/education/windows/index.md @@ -1,6 +1,6 @@ --- title: Windows 10 for Education (Windows 10) -description: Learn how to use Windows 10 in schools. +description: Learn how to use Windows 10 in schools. keywords: Windows 10, education ms.prod: w10 ms.mktglfcycl: deploy diff --git a/windows/deploy/images/ur-overview.PNG b/windows/deploy/images/ur-overview.PNG index f1818d7073..cf9563ece5 100644 Binary files a/windows/deploy/images/ur-overview.PNG and b/windows/deploy/images/ur-overview.PNG differ diff --git a/windows/deploy/upgrade-readiness-upgrade-overview.md b/windows/deploy/upgrade-readiness-upgrade-overview.md index 29777cad6f..bf09694a38 100644 --- a/windows/deploy/upgrade-readiness-upgrade-overview.md +++ b/windows/deploy/upgrade-readiness-upgrade-overview.md @@ -17,9 +17,13 @@ The following color-coded status changes are reflected on the upgrade overview b - No delay in processing device inventory data = "Last updated" banner is displayed in green. - Delay processing device inventory data = "Last updated" banner is displayed in amber. - Computers with incomplete data: - - Less than 4% = Count is displayed in black. + - Less than 4% = Count is displayed in green. - 4% - 10% = Count is displayed in amber. - Greater than 10% = Count is displayed in red. +- Computers with outdated KB: + - Less than 10% = Count is displayed in green. + - 10% - 30% = Count is displayed in amber. + - Greater than 30% = Count is displayed in red. - User changes: - Pending user changes = User changes count displays "Data refresh pending" in amber. - No pending user changes = User changes count displays "Up to date" in green. @@ -28,6 +32,8 @@ The following color-coded status changes are reflected on the upgrade overview b - If the current value is an older OS version than the recommended value, but not deprecated, the version is displayed in amber. - If the current value is a deprecated OS version, the version is displayed in red. +Click on a row to drill down and see details about individual computers. If KBs are missing, see [Deploy the compatibility update and related KBs](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#deploy-the-compatibility-update-and-related-kbs) for information on required KBs. + In the following example, there is no delay in data processing, less than 4% of computers (6k\294k) have incomplete data, there are no pending user changes, and the currently selected target OS version is the same as the recommended version: ![Upgrade overview](images/ur-overview.png) diff --git a/windows/keep-secure/TOC.md b/windows/keep-secure/TOC.md index 82fea36b85..f46902d45e 100644 --- a/windows/keep-secure/TOC.md +++ b/windows/keep-secure/TOC.md @@ -168,6 +168,7 @@ ##### [Choose the Right BitLocker Countermeasure](choose-the-right-bitlocker-countermeasure.md) #### [Protecting cluster shared volumes and storage area networks with BitLocker](protecting-cluster-shared-volumes-and-storage-area-networks-with-bitlocker.md) ### [Encrypted Hard Drive](encrypted-hard-drive.md) +### [Enterprise Certificate Pinning](enterprise-certificate-pinning.md) ### [Security auditing](security-auditing-overview.md) #### [Basic security audit policies](basic-security-audit-policies.md) ##### [Create a basic audit policy for an event category](create-a-basic-audit-policy-settings-for-an-event-category.md) @@ -572,7 +573,7 @@ ###### [Domain member: Maximum machine account password age](domain-member-maximum-machine-account-password-age.md) ###### [Domain member: Require strong (Windows 2000 or later) session key](domain-member-require-strong-windows-2000-or-later-session-key.md) ###### [Interactive logon: Display user information when the session is locked](interactive-logon-display-user-information-when-the-session-is-locked.md) -###### [Interactive logon: Don\'t display last signed-in](interactive-logon-do-not-display-last-user-name.md) +###### [Interactive logon: Don't display last signed-in](interactive-logon-do-not-display-last-user-name.md) ###### [Interactive logon: Do not require CTRL+ALT+DEL](interactive-logon-do-not-require-ctrl-alt-del.md) ###### [Interactive logon: Machine account lockout threshold](interactive-logon-machine-account-lockout-threshold.md) ###### [Interactive logon: Machine inactivity limit](interactive-logon-machine-inactivity-limit.md) @@ -768,10 +769,12 @@ ######## [Submit files for analysis](respond-file-alerts-windows-defender-advanced-threat-protection.md#submit-files-for-analysis) ######## [View deep analysis reports](respond-file-alerts-windows-defender-advanced-threat-protection.md#view-deep-analysis-reports) ######## [Troubleshoot deep analysis](respond-file-alerts-windows-defender-advanced-threat-protection.md#troubleshoot-deep-analysis) -#### [Configure SIEM tools to consume alerts](configure-siem-windows-defender-advanced-threat-protection.md) -##### [Configure an Azure Active Directory application for SIEM integration](configure-aad-windows-defender-advanced-threat-protection.md) -##### [Configure Splunk to consume Windows Defender ATP alerts](configure-splunk-windows-defender-advanced-threat-protection.md) -##### [Configure HP ArcSight to consume Windows Defender ATP alerts](configure-arcsight-windows-defender-advanced-threat-protection.md) +#### [Pull alerts to your SIEM tools](configure-siem-windows-defender-advanced-threat-protection.md) +##### [Enable SIEM integration in Windows Defender ATP](enable-siem-integration-windows-defender-advanced-threat-protection.md) +##### [Configure Splunk to pull Windows Defender ATP alerts](configure-splunk-windows-defender-advanced-threat-protection.md) +##### [Configure HP ArcSight to pull Windows Defender ATP alerts](configure-arcsight-windows-defender-advanced-threat-protection.md) +##### [Windows Defender ATP alert API fields](api-portal-mapping-windows-defender-advanced-threat-protection.md) +##### [Pull Windows Defender ATP alerts using REST API](pull-alerts-using-rest-api-windows-defender-advanced-threat-protection.md) #### [Use the threat intelligence API to create custom alerts](use-custom-ti-windows-defender-advanced-threat-protection.md) ##### [Understand threat intelligence concepts](threat-indicator-concepts-windows-defender-advanced-threat-protection.md) ##### [Enable the custom threat intelligence application](enable-custom-ti-windows-defender-advanced-threat-protection.md) diff --git a/windows/keep-secure/api-portal-mapping-windows-defender-advanced-threat-protection.md b/windows/keep-secure/api-portal-mapping-windows-defender-advanced-threat-protection.md new file mode 100644 index 0000000000..e242add755 --- /dev/null +++ b/windows/keep-secure/api-portal-mapping-windows-defender-advanced-threat-protection.md @@ -0,0 +1,73 @@ +--- +title: Windows Defender ATP alert API fields +description: Understand how the alert API fields map to the values in the Windows Defender ATP portal. +keywords: alerts, alert fields, fields, api, fields, pull alerts, rest api, request, response +search.product: eADQiWindows 10XVcnh +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.pagetype: security +author: mjcaparas +localizationpriority: high +--- + +# Windows Defender ATP alert API fields + +**Applies to:** + +- Windows 10 Enterprise +- Windows 10 Education +- Windows 10 Pro +- Windows 10 Pro Education +- Windows Defender Advanced Threat Protection (Windows Defender ATP) + +Understand what data fields are exposed as part of the alerts API and how they map to the Windows Defender ATP portal. + + +# Alert API fields and portal mapping +Field numbers match the numbers in the images below. + +Portal label | SIEM field name | Description +:---|:---|:--- +1 | LinkToWDATP | Link back to the alert page in Windows Defender ATP +2 | Alert ID | Alert ID visible in the link: `https://securitycenter.windows.com/alert/` +3 | AlertTitle | Alert title +4 | Actor | Actor name +5 | AlertTime | Last time the alert was observed +6 | Severity | Alert severity +7 | Category | Alert category +8 | Status in queue | Alert status in queue +9 | ComputerDnsName| Computer DNS name and machine name +10| IoaDefinitionId | (Internal only)

ID for the IOA (Indication of attack) that this alert belongs to. It usually correlates with the title.

**Note**: This is an internal ID of the rule which triggers the alert. It's provided here as it can be used for aggregations in the SIEM. +11 | UserName | The user context relevant to the activity on the machine which triggered the alert. NOTE: Not yet populated. +12 | FileName | File name +13 | FileHash | Sha1 of file observed +14 | FilePath | File path +15 | IpAddress | IP of the IOC (when relevant) +16 | URL | URL of the IOC (when relevant) +17 | FullId | (Internal only)

Unique ID for each combination of IOC and Alert ID. Provides the ability to apply dedup logic in the SIEM. +18 | AlertPart | (Internal only)

Alerts which contain multiple IOCs will be split into several messages, each message contains one IOC and a running counter. The counter provides the ability to reconstruct the alerts in the SIEM. +19 | LastProccesedTimeUtc | (Internal only)

Time the alert was last processed in Windows Defender ATP. +20 | Source| Alert detection source (Windows Defender AV, Windows Defender ATP, and Device Guard) +21 | ThreatCategory| Windows Defender AV threat category +22 | ThreatFamily | Windows Defender AV family name +23 | RemediationAction | Windows Defender AV threat category | +24 | WasExecutingWhileDetected | Indicates if a file was running while being detected. +25| RemediationIsSuccess | Indicates if an alert was successfully remediated. +26 | Sha1 | Sha1 of file observed in alert timeline and in file side pane (when available) +27 | Md5 | Md5 of file observed (when available) +28 | Sha256 | Sha256 of file observed (when available) +29 | ThreatName | Windows Defender AV threat name + +>[!NOTE] +> Fields #21-29 are related to Windows Defender Antivirus alerts. + +![Image of actor profile with numbers](images/atp-actor.png) + +![Image of alert timeline with numbers](images/atp-alert-timeline-numbered.png) + +![Image of new alerts with numbers](images/atp-alert-source.png) + +![Image of machine timeline with numbers](images/atp-remediated-alert.png) + +![Image of file details](images/atp-file-details.png) diff --git a/windows/keep-secure/configure-aad-windows-defender-advanced-threat-protection.md b/windows/keep-secure/configure-aad-windows-defender-advanced-threat-protection.md index d7147d12a9..7f3ba226aa 100644 --- a/windows/keep-secure/configure-aad-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/configure-aad-windows-defender-advanced-threat-protection.md @@ -22,7 +22,7 @@ localizationpriority: high - Windows 10 Pro Education - Windows Defender Advanced Threat Protection (Windows Defender ATP) -You need to add an application in your Azure Active Directory (AAD) tenant then authorize the Windows Defender ATP Alerts Export application to communicate with it so that your security information and events management (SIEM) tool can consume alerts from Windows Defender ATP portal. +You need to add an application in your Azure Active Directory (AAD) tenant then authorize the Windows Defender ATP Alerts Export application to communicate with it so that your security information and events management (SIEM) tool can pull alerts from Windows Defender ATP portal. 1. Login to the [Azure management portal](https://ms.portal.azure.com). @@ -78,12 +78,12 @@ You need to add an application in your Azure Active Directory (AAD) tenant then 23. Save the application changes. -After configuring the application in AAD, you'll need to obtain a refresh token. You'll need to use the token when you configure the connector for your SIEM tool in the next steps. The token lets the connector access Windows Defender ATP events to be consumed by your SIEM. +After configuring the application in AAD, you'll need to obtain a refresh token. You'll need to use the token when you configure the connector for your SIEM tool in the next steps. The token lets the connector access Windows Defender ATP events to be pulled by your SIEM. ## Obtain a refresh token using an events URL Obtain a refresh token used to retrieve the Windows Defender Advanced Threat Protection events to your SIEM. This section provides information on how you can use an events URL to obtain the required refresh token. >[!NOTE] ->For HP ArcSight, you can obtain a refresh token using the restutil tool. For more information, see [Configure HP ArcSight to consume alerts](configure-arcsight-windows-defender-advanced-threat-protection.md). +>For HP ArcSight, you can obtain a refresh token using the restutil tool. For more information, see [Configure HP ArcSight to pull alerts](configure-arcsight-windows-defender-advanced-threat-protection.md). ### Before you begin Get the following information from your Azure Active Directory (AAD) application by selecting the **View Endpoint** on the application configuration page: @@ -111,6 +111,6 @@ You'll use these values to obtain a refresh token. After configuring your AAD application and generating a refresh token, you can proceed to configure your SIEM tool. ## Related topics -- [Configure security information and events management (SIEM) tools to consume alerts](configure-siem-windows-defender-advanced-threat-protection.md) -- [Configure Splunk to consume alerts](configure-splunk-windows-defender-advanced-threat-protection.md) -- [Configure HP ArcSight to consume alerts](configure-arcsight-windows-defender-advanced-threat-protection.md) +- [Configure security information and events management (SIEM) tools to pull alerts](configure-siem-windows-defender-advanced-threat-protection.md) +- [Configure Splunk to pull alerts](configure-splunk-windows-defender-advanced-threat-protection.md) +- [Configure HP ArcSight to pull alerts](configure-arcsight-windows-defender-advanced-threat-protection.md) diff --git a/windows/keep-secure/configure-arcsight-windows-defender-advanced-threat-protection.md b/windows/keep-secure/configure-arcsight-windows-defender-advanced-threat-protection.md index c4ebb2bd23..fba8ebda15 100644 --- a/windows/keep-secure/configure-arcsight-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/configure-arcsight-windows-defender-advanced-threat-protection.md @@ -1,6 +1,6 @@ --- -title: Configure HP ArcSight to consume Windows Defender ATP alerts -description: Configure HP ArcSight to receive and consume alerts from the Windows Defender ATP portal. +title: Configure HP ArcSight to pull Windows Defender ATP alerts +description: Configure HP ArcSight to receive and pull alerts from the Windows Defender ATP portal. keywords: configure hp arcsight, security information and events management tools, arcsight search.product: eADQiWindows 10XVcnh ms.prod: w10 @@ -11,7 +11,7 @@ author: mjcaparas localizationpriority: high --- -# Configure HP ArcSight to consume Windows Defender ATP alerts +# Configure HP ArcSight to pull Windows Defender ATP alerts **Applies to:** @@ -21,86 +21,163 @@ localizationpriority: high - Windows 10 Pro Education - Windows Defender Advanced Threat Protection (Windows Defender ATP) -You'll need to configure HP ArcSight so that it can consume Windows Defender ATP alerts. +You'll need to install and configure some files and tools to use HP ArcSight so that it can pull Windows Defender ATP alerts. ## Before you begin +Configuring the HP ArcSight Connector tool requires several configuration files for it to pull and parse alerts from your Azure Active Directory (AAD) application. -- Get the following information from your Azure Active Directory (AAD) application by selecting **View Endpoint** on the application configuration page: - - OAuth 2 Token refresh URL - - OAuth 2 Client ID - - OAuth 2 Client secret -- Download the [WDATP-connector.properties](http://download.microsoft.com/download/3/9/C/39C703C2-487C-4C3E-AFD8-14C2253C2F12/WDATP-connector.properties) file and update the following values: +This section guides you in getting the necessary information to set and use the required configuration files correctly. - - **client_ID**: OAuth 2 Client ID - - **client_secret**: OAuth 2 Client secret - - **auth_url**: ```https://login.microsoftonline.com/?resource=https%3A%2F%2FWDATPAlertExport.Seville.onmicrosoft.com ``` +- Make sure you have enabled the SIEM integration feature from the **Preferences setup** menu. For more information, see [Enable SIEM integration in Windows Defender ATP](enable-siem-integration-windows-defender-advanced-threat-protection.md). - >[!NOTE] - >Replace *tenantID* with your tenant ID. +- Have the file you saved from enabling the SIEM integration feature ready. You'll need to get the following values: + - OAuth 2.0 Token refresh URL + - OAuth 2.0 Client ID + - OAuth 2.0 Client secret - - **token_url**: `https://login.microsoftonline.com//oauth2/token` +- Have the following configuration files ready: + - WDATP-connector.properties + - WDATP-connector.jsonparser.properties - >[!NOTE] - >Replace the *tenantID* value with your tenant ID. + You would have saved a .zip file which contains these two files when you chose HP ArcSight as the SIEM type you use in your organization. - - **redirect_uri**: ```https://localhost:44300/wdatpconnector``` - - **scope**: Leave the value blank +- Make sure you generate the following tokens and have them ready: + - Access token + - Refresh token -- Download the [WDATP-connector.jsonparser.properties](http://download.microsoft.com/download/0/8/A/08A4957D-0923-4353-B25F-395EAE363E8C/WDATP-connector.jsonparser.properties) file. This file is used to parse the information from Windows Defender ATP to HP ArcSight consumable format. -- Install the HP ArcSight REST FlexConnector package. You can find this in the HPE Software center. Install the package on a server that has access to the Internet. + You can generate these tokens from the **SIEM integration** setup section of the portal. -## Configure HP ArcSight -The following steps assume that you have completed all the required steps in [Before you begin](#before-you-begin). For more information, see the ArcSight FlexConnector Developer's guide. +## Install and configure HP ArcSight SmartConnector +The following steps assume that you have completed all the required steps in [Before you begin](#before-you-begin). -1. Save the [WDATP-connector.jsonparser.properties file](http://download.microsoft.com/download/0/8/A/08A4957D-0923-4353-B25F-395EAE363E8C/WDATP-connector.jsonparser.properties) file into the connector installation folder. +1. Install the latest 32-bit Windows SmartConnector installer. You can find this in the HPE Software center. The tool is typically installed in the following default location: `C:\Program Files\ArcSightSmartConnectors\current\bin`.

You can choose where to save the tool, for example C:\\*folder_location*\current\bin where *folder_location* represents the installation location. -2. Save the [WDATP-connector.properties](http://download.microsoft.com/download/3/9/C/39C703C2-487C-4C3E-AFD8-14C2253C2F12/WDATP-connector.properties) file into the `\current\user\agent\flexagent` folder of the connector installation folder. +2. Follow the installation wizard through the following tasks: + - Introduction + - Choose Install Folder + - Choose Install Set + - Choose Shortcut Folder + - Pre-Installation Summary + - Installing... -3. Open an elevated command-line: + You can keep the default values for each of these tasks or modify the selection to suit your requirements. - a. Go to **Start** and type **cmd**. +3. Open File Explorer and locate the two configuration files you saved when you enabled the SIEM integration feature. Put the two files in the SmartConnector installation location, for example: - b. Right-click **Command prompt** and select **Run as administrator**. + - WDATP-connector.jsonparser.properties: C:\\*folder_location*\current\user\agent\flexagent\ -4. Enter the following command and press **Enter**: ```runagentsetup.bat```. The Connector Setup pop-up window appears. + - WDATP-connector.properties: C:\\*folder_location*\current\user\agent\flexagent\ -5. In the form fill in the following required fields with these values: - >[!NOTE] - >All other values in the form are optional and can be left blank. + >[!NOTE] + >You must put the configuration files in this location, where *folder_location* represents the location where you installed the tool. +4. After the installation of the core connector completes, the Connector Setup window opens. In the Connector Setup window, select **Add a Connector**. - - - - - - - - - - - - - - - - - - - - - - - -
FieldValue
Configuration FileType in the name of the client property file. It must match the client property file.
Events URLDepending on the location of your datacenter, select either the EU or the US URL:

**For EU**: https://wdatp-alertexporter-eu.windows.com/api/alerts/?sinceTimeUtc=$START_AT_TIME -
**For US:** https://wdatp-alertexporter-us.windows.com/api/alerts/?sinceTimeUtc=$START_AT_TIME
Authentication TypeOAuth 2
OAuth 2 Client Properties fileSelect *wdatp-connector.properties*.
Refresh TokenYou can use the Windows Defender ATP events URL or the restutil tool to get obtain a refresh token.
For more information on getting your refresh token using the events URL, see [Obtain a refresh token](configure-aad-windows-defender-advanced-threat-protection.md#obtain-a-refresh-token).

**To get your refresh token using the restutil tool:**
a. Open a command prompt. Navigate to `C:\ArcSightSmartConnectors\\current\bin`.

b. Type: `arcsight restutil token -config C:\ArcSightSmartConnectors_Prod\WDATP\WDATP-connector.properties`. A Web browser window will open.

c. Type in your credentials then click on the password field to let the page redirect. In the login prompt, enter your credentials.

d. A refresh token is shown in the command prompt.

e. Paste the value in the form. -
-6. Select **Next**, then **Save**. +5. Select Type: **ArcSight FlexConnector REST** and click **Next**. -7. Run the connector. You can choose to run in Service mode or Application mode. +6. Type the following information in the parameter details form. All other values in the form are optional and can be left blank. -8. In the HP ArcSight console, create a **Windows Defender ATP** channel with intervals and properties suitable to your enterprise needs. Windows Defender ATP alerts will appear as discrete events, with “Microsoft” as the vendor and “Windows Defender ATP” as the device name. + + + + + + + + + + + + + + + + + + + + + + + +
FieldValue
Configuration FileType in the name of the client property file. The name must match the file provided in the .zip that you downloaded. + For example, if the configuration file in "flexagent" directory is named "WDATP-Connector.jsonparser.properties", you must type "WDATP-Connector" as the name of the client property file.
Events URLDepending on the location of your datacenter, select either the EU or the US URL:

**For EU**: https://wdatp-alertexporter-eu.windows.com/api/alerts/?sinceTimeUtc=$START_AT_TIME +
**For US:** https://wdatp-alertexporter-us.windows.com/api/alerts/?sinceTimeUtc=$START_AT_TIME
Authentication TypeOAuth 2
OAuth 2 Client Properties fileBrowse to the location of the *wdatp-connector.properties* file. The name must match the file provided in the .zip that you downloaded.
Refresh TokenYou can obtain a refresh token in two ways: by generating a refresh token from the **SIEM integration preferences setup** page or using the restutil tool.

For more information on generating a refresh token from the **Preferences setup** , see [Enable SIEM integration in Windows Defender ATP](enable-siem-integration-windows-defender-advanced-threat-protection.md).

**Get your refresh token using the restutil tool:**
a. Open a command prompt. Navigate to C:\\*folder_location*\current\bin where *folder_location* represents the location where you installed the tool.

b. Type: `arcsight restutil token -config` from the bin directory. A Web browser window will open.

c. Type in your credentials then click on the password field to let the page redirect. In the login prompt, enter your credentials.

d. A refresh token is shown in the command prompt.

e. Copy and paste it into the **Refresh Token** field. +
+7. A browser window is opened by the connector. Login with your application credentials. After you log in, you'll be asked to give permission to your OAuth2 Client. You must give permission to your OAuth 2 Client so that the connector configuration can authenticate.

+If the `redirect_uri` is a https URL, you'll be redirected to a URL on the local host. You'll see a page that requests for you to trust the certificate supplied by the connector running on the local host. You'll need to trust this certificate if the redirect_uri is a https.

If however you specify a http URL for the redirect_uri, you do not need to provide consent in trusting the certificate. + +8. Continue with the connector setup by returning to the HP ArcSight Connector Setup window. + +9. Select the **ArcSight Manager (encrypted)** as the destination and click **Next**. + +10. Type in the destination IP/hostname in **Manager Hostname** and your credentials in the parameters form. All other values in the form should be retained with the default values. Click **Next**. + +11. Type in a name for the connector in the connector details form. All other values in the form are optional and can be left blank. Click **Next**. + +11. The ESM Manager import certificate window is shown. Select **Import the certificate to connector from destination** and click **Next**. The **Add connector Summary** window is displayed and the certificate is imported. + +12. Verify that the details in the **Add connector Summary** window is correct, then click **Next**. + +13. Select **Install as a service** and click **Next**. + +14. Type a name in the **Service Internal Name** field. All other values in the form can be retained with the default values or left blank . Click **Next**. + +13. Type in the service parameters and click **Next**. A window with the **Install Service Summary** is shown. Click **Next**. + +14. Finish the installation by selecting **Exit** and **Next**. + +## Install and configure the HP ArcSight console +1. Follow the installation wizard through the following tasks: + - Introduction + - License Agreement + - Special Notice + - Choose ArcSight installation directory + - Choose Shortcut Folder + - Pre-Installation Summary + +2. Click **Install**. After the installation completes, the ArcSight Console Configuration Wizard opens. + +3. Type localhost in **Manager Host Name** and 8443 in **Manager Port** then click **Next**. + +4. Select **Use direct connection**, then click **Next**. + +5. Select **Password Based Authentication**, then click **Next**. + +6. Select **This is a single user installation. (Recommended)**, then click **Next**. + +7. Click **Done** to quit the installer. + +8. Login to the HP ArcSight console. + +9. Navigate to **Active channel set** > **New Condition** > **Device** > **Device Product**. + +10. Set **Device Product = Windows Defender ATP**. When you've verified that events are flowing to the tool, stop the process again and go to Windows Services and start the ArcSight FlexConnector REST. + +You can now run queries in the HP ArcSight console. + +Windows Defender ATP alerts will appear as discrete events, with "Microsoft” as the vendor and “Windows Defender ATP” as the device name. + + +## Troubleshooting HP ArcSight connection +**Problem:** Failed to refresh the token. You can find the log located in C:\\*folder_location*\current\logs where *folder_location* represents the location where you installed the tool. Open _agent.log_ and look for `ERROR/FATAL/WARN`. + +**Symptom:** You get the following error message: + +`Failed to refresh the token. Set reauthenticate to true: com.arcsight.common.al.e: Failed to refresh access token: status=HTTP/1.1 400 Bad Request FATAL EXCEPTION: Could not refresh the access token` + +**Solution:** +1. Stop the process by clicking Ctrl + C on the Connector window. Click **Y** when asked "Terminate batch job Y/N?". +2. Navigate to the folder where you stored the WDATP-connector.properties file and edit it to add the following value: +`reauthenticate=true`. + +3. Restart the connector by running the following command: `arcsight.bat connectors`. + + A browser window appears. Allow it to run, it should disappear, and the connector should now be running. + + > [!NOTE] + > Verify that the connector is running by stopping the process again. Then start the connector again, and no browser window should appear. ## Related topics -- [Configure security information and events management (SIEM) tools to consume alerts](configure-siem-windows-defender-advanced-threat-protection.md) -- [Configure Azure Active Directory application for SIEM integration](configure-aad-windows-defender-advanced-threat-protection.md) -- [Configure Splunk to consume alerts](configure-splunk-windows-defender-advanced-threat-protection.md) +- [Configure security information and events management (SIEM) tools to pull alerts](configure-siem-windows-defender-advanced-threat-protection.md) +- [Enable SIEM integration in Windows Defender ATP](enable-siem-integration-windows-defender-advanced-threat-protection.md) +- [Configure Splunk to pull alerts](configure-splunk-windows-defender-advanced-threat-protection.md) diff --git a/windows/keep-secure/configure-siem-windows-defender-advanced-threat-protection.md b/windows/keep-secure/configure-siem-windows-defender-advanced-threat-protection.md index 35dead1efe..ba1f5cc851 100644 --- a/windows/keep-secure/configure-siem-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/configure-siem-windows-defender-advanced-threat-protection.md @@ -1,6 +1,6 @@ --- -title: Consume alerts and create custom indicators in Windows Defender Advanced Threat Protection -description: Learn how to configure supported security information and events management tools to receive and consume alerts and create custom indicators using REST API. +title: Pull alerts to your SIEM tools from Windows Defender Advanced Threat Protection +description: Learn how to use REST API and configure supported security information and events management tools to receive and pull alerts. keywords: configure siem, security information and events management tools, splunk, arcsight, custom indicators, rest api, alert definitions, indicators of compromise search.product: eADQiWindows 10XVcnh ms.prod: w10 @@ -11,7 +11,7 @@ author: mjcaparas localizationpriority: high --- -# Consume alerts and create custom indicators +# Pull alerts to your SIEM tools **Applies to:** @@ -21,8 +21,10 @@ localizationpriority: high - Windows 10 Pro Education - Windows Defender Advanced Threat Protection (Windows Defender ATP) -## Consume alerts using supported security information and events management (SIEM) tools -Windows Defender ATP supports (SIEM) tools to consume alerts. Windows Defender ATP exposes alerts through an HTTPS endpoint hosted in Azure. The endpoint can be configured to get alerts from your enterprise tenant in Azure Active Directory (AAD) using the OAuth 2.0 authentication protocol for an AAD application that represents the specific SIEM connector installed in your environment. +[Some information relates to pre-released product, which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.] + +## Pull alerts using supported security information and events management (SIEM) tools +Windows Defender ATP supports (SIEM) tools to pull alerts. Windows Defender ATP exposes alerts through an HTTPS endpoint hosted in Azure. The endpoint can be configured to pull alerts from your enterprise tenant in Azure Active Directory (AAD) using the OAuth 2.0 authentication protocol for an AAD application that represents the specific SIEM connector installed in your environment. Windows Defender ATP currently supports the following SIEM tools: @@ -32,20 +34,26 @@ Windows Defender ATP currently supports the following SIEM tools: To use either of these supported SIEM tools you'll need to: -- [Configure an Azure Active Directory application for SIEM integration in your tenant](configure-aad-windows-defender-advanced-threat-protection.md) +- [Enable SIEM integration in Windows Defender ATP](enable-siem-integration-windows-defender-advanced-threat-protection.md) - Configure the supported SIEM tool: - - [Configure Splunk to consume alerts](configure-splunk-windows-defender-advanced-threat-protection.md) - - [Configure HP ArcSight to consume alerts](configure-arcsight-windows-defender-advanced-threat-protection.md) + - [Configure Splunk to pull alerts](configure-splunk-windows-defender-advanced-threat-protection.md) + - [Configure HP ArcSight to pull alerts](configure-arcsight-windows-defender-advanced-threat-protection.md) -## Create custom threat indicators in Windows Defender ATP -You can also create custom threat indicators using the available REST API so that you can create specific alerts that are applicable to your organization. +For more information on the list of fields exposed in the alerts API see, [Windows Defender ATP alert API fields](api-portal-mapping-windows-defender-advanced-threat-protection.md). + + +## Pull Windows Defender ATP alerts using REST API +Windows Defender ATP supports the OAuth 2.0 protocol to pull alerts using REST API. + +For more information, see [Pull Windows Defender ATP alerts using REST API](pull-alerts-using-rest-api-windows-defender-advanced-threat-protection.md). -For more information, see [Create custom threat indicators (TI) using REST API](custom-ti-api-windows-defender-advanced-threat-protection.md). ## In this section Topic | Description :---|:--- -[Configure an Azure Active Directory application](configure-aad-windows-defender-advanced-threat-protection.md)| Learn about configuring an Azure Active Directory application to integrate with supported security information and events management (SIEM) tools. - [Configure Splunk](configure-splunk-windows-defender-advanced-threat-protection.md)| Learn about installing the REST API Modular Input app and other configuration settings to enable Splunk to consume Windows Defender ATP alerts. - [Configure ArcSight](configure-arcsight-windows-defender-advanced-threat-protection.md)| Learn about installing the HP ArcSight REST FlexConnector package and the files you need to configure ArcSight to consume Windows Defender ATP alerts. +[Enable SIEM integration in Windows Defender ATP](enable-siem-integration-windows-defender-advanced-threat-protection.md)| Learn about enabling the SIEM integration feature in the **Preferences setup** page in the portal so that you can use and generate the required information to configure supported SIEM tools. +[Configure Splunk](configure-splunk-windows-defender-advanced-threat-protection.md)| Learn about installing the REST API Modular Input app and other configuration settings to enable Splunk to pull Windows Defender ATP alerts. +[Configure ArcSight](configure-arcsight-windows-defender-advanced-threat-protection.md)| Learn about installing the HP ArcSight REST FlexConnector package and the files you need to configure ArcSight to pull Windows Defender ATP alerts. +[Windows Defender ATP alert API fields](api-portal-mapping-windows-defender-advanced-threat-protection.md) | Understand what data fields are exposed as part of the alerts API and how they map to the Windows Defender ATP portal. +[Pull Windows Defender ATP alerts using REST API](pull-alerts-using-rest-api-windows-defender-advanced-threat-protection.md) | Use the Client credentials OAuth 2.0 flow to pull alerts from Windows Defender ATP using REST API. diff --git a/windows/keep-secure/configure-splunk-windows-defender-advanced-threat-protection.md b/windows/keep-secure/configure-splunk-windows-defender-advanced-threat-protection.md index 8dc36252d3..18fa8ef5d5 100644 --- a/windows/keep-secure/configure-splunk-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/configure-splunk-windows-defender-advanced-threat-protection.md @@ -1,6 +1,6 @@ --- -title: Configure Splunk to consume Windows Defender ATP alerts -description: Configure Splunk to receive and consume alerts from the Windows Defender ATP portal. +title: Configure Splunk to pull Windows Defender ATP alerts +description: Configure Splunk to receive and pull alerts from the Windows Defender ATP portal. keywords: configure splunk, security information and events management tools, splunk search.product: eADQiWindows 10XVcnh ms.prod: w10 @@ -11,7 +11,7 @@ author: mjcaparas localizationpriority: high --- -# Configure Splunk to consume Windows Defender ATP alerts +# Configure Splunk to pull Windows Defender ATP alerts **Applies to:** @@ -21,16 +21,19 @@ localizationpriority: high - Windows 10 Pro Education - Windows Defender Advanced Threat Protection (Windows Defender ATP) -You'll need to configure Splunk so that it can consume Windows Defender ATP alerts. +You'll need to configure Splunk so that it can pull Windows Defender ATP alerts. ## Before you begin - Install the [REST API Modular Input app](https://splunkbase.splunk.com/app/1546/) in Splunk. -- Obtain your refresh token. For more information, see [Obtain a refresh token](configure-aad-windows-defender-advanced-threat-protection.md#obtain-a-refresh-token). -- Get the following information from your Azure Active Directory (AAD) application by selecting **View Endpoint** on the application configuration page: - - OAuth 2 Token refresh URL - - OAuth 2 Client ID - - OAuth 2 Client secret +- Make sure you have enabled the **SIEM integration** feature from the **Preferences setup** menu. For more information, see [Enable SIEM integration in Windows Defender ATP](enable-siem-integration-windows-defender-advanced-threat-protection.md) + +- Have the details file you saved from enabling the **SIEM integration** feature ready. You'll need to get the following values: + - OAuth 2 Token refresh URL + - OAuth 2 Client ID + - OAuth 2 Client secret + +- Have the refresh token that you generated from the SIEM integration feature ready. ## Configure Splunk @@ -56,8 +59,7 @@ You'll need to configure Splunk so that it can consume Windows Defender ATP aler Endpoint URL - Depending on the location of your datacenter, select either the EU or the US URL:

**For EU**: https://wdatp-alertexporter-eu.windows.com/api/alerts
**For US:** https://wdatp-alertexporter-us.windows.com/api/alerts - + Depending on the location of your datacenter, select either the EU or the US URL:

**For EU**: `https://wdatp-alertexporter-eu.securitycenter.windows.com/api/alerts`
**For US:**` https://wdatp-alertexporter-us.securitycenter.windows.com/api/alerts` HTTP Method @@ -66,16 +68,24 @@ You'll need to configure Splunk so that it can consume Windows Defender ATP aler Authentication Type oauth2 + OAuth 2 Access token + Use the value that you generated when you enabled the SIEM integration feature.

NOTE: The access token expires after an hour. + + + OAuth 2 Refresh Token + Use the value that you generated when you enabled the **SIEM integration** feature. + + OAuth 2 Token Refresh URL - Value taken from AAD application + Use the value from the details file you saved when you enabled the **SIEM integration** feature. OAuth 2 Client ID - Value taken from AAD application + Use the value from the details file you saved when you enabled the **SIEM integration** feature. OAuth 2 Client Secret - Value taken from AAD application + Use the value from the details file you saved when you enabled the **SIEM integration** feature. Response type @@ -102,11 +112,26 @@ You'll need to configure Splunk so that it can consume Windows Defender ATP aler After completing these configuration steps, you can go to the Splunk dashboard and run queries. -You can use the following query as an example in Splunk:
-```source="rest://windows atp alerts"|spath|table*``` +## View alerts using Splunk solution explorer +Use the solution explorer to view alerts in Splunk. + +1. In Splunk, go to **Settings** > **Searchers, reports, and alerts**. + +2. Select **New**. + +3. Enter the following details: + - Destination app: Select Search & Reporting (search) + - Search name: Enter a name for the query + - Search: Enter a query, for example:
+ `source="rest://windows atp alerts"|spath|table*` + + Other values are optional and can be left with the default values. +4. Click **Save**. The query is saved in the list of searches. + +5. Find the query you saved in the list and click **Run**. The results are displayed based on your query. ## Related topics -- [Configure security information and events management (SIEM) tools to consume alerts](configure-siem-windows-defender-advanced-threat-protection.md) -- [Configure Azure Active Directory application for SIEM integration](configure-aad-windows-defender-advanced-threat-protection.md) -- [Configure HP ArcSight to consume alerts](configure-arcsight-windows-defender-advanced-threat-protection.md) +- [Configure security information and events management (SIEM) tools to pull alerts](configure-siem-windows-defender-advanced-threat-protection.md) +- [Enable SIEM integration in Windows Defender ATP](enable-siem-integration-windows-defender-advanced-threat-protection.md) +- [Configure HP ArcSight to pull alerts](configure-arcsight-windows-defender-advanced-threat-protection.md) diff --git a/windows/keep-secure/enable-siem-integration-windows-defender-advanced-threat-protection.md b/windows/keep-secure/enable-siem-integration-windows-defender-advanced-threat-protection.md new file mode 100644 index 0000000000..5746ab6157 --- /dev/null +++ b/windows/keep-secure/enable-siem-integration-windows-defender-advanced-threat-protection.md @@ -0,0 +1,51 @@ +--- +title: Enable SIEM integration in Windows Defender Advanced Threat Protection +description: Enable SIEM integration to receive alerts in your security information and event management (SIEM) solution. +keywords: enable siem connector, siem, connector, security information and events +search.product: eADQiWindows 10XVcnh +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.pagetype: security +author: mjcaparas +localizationpriority: high +--- + +# Enable SIEM integration in Windows Defender ATP + +**Applies to:** + +- Windows 10 Enterprise +- Windows 10 Education +- Windows 10 Pro +- Windows 10 Pro Education +- Windows Defender Advanced Threat Protection (Windows Defender ATP) + +Enable security information and event management (SIEM) integration so you can pull alerts from the Windows Defender ATP portal using your SIEM solution or by connecting directly to the alerts REST API. + +1. In the navigation pane, select **Preferences setup** > **SIEM integration**. + + ![Image of SIEM integration from Preferences setup menu](images/atp-siem-integration.png) + +2. Select **Enable SIEM integration**. This activates the **SIEM connector access details** section with pre-populated values and an application is created under you Azure Active Directory (AAD) tenant. + + >[!WARNING] + >The client secret is only displayed once. Make sure you keep a copy of it in a safe place. + >For more information about getting a new secret see, [Learn how to get a new secret](troubleshoot-custom-ti-windows-defender-advanced-threat-protection.md#learn-how-to-get-a-new-client-secret). + +3. Choose the SIEM type you use in your organization. + >[!NOTE] + >If you select HP ArcSight, you'll need to save these two configuration files: + > - WDATP-connector.jsonparser.properties + > - WDATP-connector.properties + > If you want to connect directly to the alerts REST API through programmatic access, choose **Generic API**. + +4. Copy the individual values or select **Save details to file** to download a file that contains all the values. + +5. Select **Generate tokens** to get an access and refresh token. + +You can now proceed with configuring your SIEM solution or connecting to the alerts REST API through programmatic access. You'll need to use the tokens when configuring your SIEM solution to allow it to receive alerts from the Windows Defender ATP portal. + +## Related topics +- [Configure Splunk to pull Windows Defender ATP alerts](configure-splunk-windows-defender-advanced-threat-protection.md) +- [Configure HP ArcSight to pull Windows Defender ATP alerts](configure-arcsight-windows-defender-advanced-threat-protection.md) diff --git a/windows/keep-secure/enterprise-certificate-pinning.md b/windows/keep-secure/enterprise-certificate-pinning.md new file mode 100644 index 0000000000..b6b15f7df9 --- /dev/null +++ b/windows/keep-secure/enterprise-certificate-pinning.md @@ -0,0 +1,450 @@ +--- +ms.mktglfcycl: manage +ms.sitesec: library +ms.author: mstephens +author: MikeStephens-MS +description: Enterprise certificate pinning is a Windows feature for remembering, or “pinning” a root, issuing certificate authority, or end entity certificate to a given domain name. +manager: alanth +ms.date: 2016-12-27 +ms.prod: w10 +ms.technology: security +ms.sitesec: library +ms.pagetype: security +localizationpriority: high +--- + +# Enterprise Certificate Pinning + +**Applies to** +- Windows 10 + +Enterprise certificate pinning is a Windows feature for remembering, or “pinning,” a root issuing certificate authority or end entity certificate to a given domain name. +Enterprise certificate pinning helps reduce man-in-the-middle attacks by enabling you to protect your internal domain names from chaining to unwanted certificates or to fraudulently issued certificates. + +>[!NOTE] +> External domain names, where the certificate issued to these domains is issued by a public certificate authority, are not ideal for enterprise certificate pinning. Web administrators should configure their web servers to use HTTP public key pinning (HPKP) and encourage users to use web browsers that support HPKP. + +Windows Certificate APIs (CertVerifyCertificateChainPolicy and WinVerifyTrust) are updated to check if the site’s server authentication certificate chain matches a restricted set of certificates. +These restrictions are encapsulated in a Pin Rules Certificate Trust List (CTL) that is configured and deployed to Windows 10 computers. +Any site certificate triggering a name mismatch causes Windows to write an event to the CAPI2 event log and prevents the user from navigating to the web site using Microsoft Edge or Internet Explorer. + +## Deployment + +To deploy enterprise certificate pinning, you need to: + +- Create a well-formatted certificate pinning rule XML file +- Create a pin rules certificate trust list file from the XML file +- Apply the pin rules certificate trust list file to a reference administrative computer +- Deploy the registry configuration on the reference computer using Group Policy Management Console (GPMC), which is included in the [Remote Server Administration Tools (RSAT)](https://www.microsoft.com/download/details.aspx?id=45520). + +### Create a Pin Rules XML file + +The XML-based pin rules file consists of a sequence of PinRule elements. +Each PinRule element contains a sequence of one or more Site elements and a sequence of zero or more Certificate elements. + +```code + + + + + + + + + + + + + + + + + + + + + + +``` + +#### PinRules Element + +The PinRules element can have the following attributes. +For help with formatting Pin Rules, see [Representing a Date in XML](#representing-a-date-in-xml) or [Representing a Duration in XML](#representing-a-duration-in-xml). + +- **Duration** or **NextUpdate** + + Specifies when the Pin Rules will expire. + Either is required. + **NextUpdate** takes precedence if both are specified. + + **Duration**, represented as an XML TimeSpan data type, does not allow years and months. + You represent the **NextUpdate** attribute as a XML DateTime data type in UTC. + + **Required?** Yes. At least one is required. + +- **LogDuration** or **LogEndDate** + + Configures auditing only to extend beyond the expiration of enforcing the Pin Rules. + + **LogEndDate**, represented as an XML DateTime data type in UTC, takes precedence if both are specified. + + You represent **LogDuration** as an XML TimeSpan data type, which does not allow years and months. + + If neither attribute is specified, auditing expiration uses **Duration** or **NextUpdate** attributes. + + **Required?** No. + +- **ListIdentifier** + + Provides a friendly name for the list of pin rules. + Windows does not use this attribute for certificate pinning enforcement, however it is included when the pin rules are converted to a certificate trust list (CTL). + + **Required?** No. + +#### PinRule Element + +The **PinRule** element can have the following attributes: + +- **Name** + + Uniquely identifies the **PinRule**. + Windows uses this attribute to identify the element for a parsing error or for verbose output. + The attribute is not included in the generated certificate trust list (CTL). + + **Required?** Yes. + +- **Error** + + Describes the action Windows performs when it encounters a PIN mismatch. + You can choose from the following string values: + - **Revoked** - Windows reports the certificate protecting the site as if it was revoked. This typically prevents the user from accessing the site. + - **InvalidName** - Windows reports the certificate protecting the site as if the name on the certificate does not match the name of the site. This typically results in prompting the user before accessing the site. + - **None** - The default value. No error is returned. You can use this setting to audit the pin rules without introducing any user friction. + + **Required?** No. + +- **Log** + + A Boolean value represent as string that equals **true** or **false**. + By default, logging is enabled (**true**). + + **Required?** No. + +#### Certificate element + +The **Certificate** element can have the following attributes: + +- **File** + + Path to a file containing one or more certificates. + Where the certificate(s) can be encoded as: + - single certificate + - p7b + - sst. + + These files can also be Base64 formatted. + All **Site** elements included in the same **PinRule** element can match any of these certificates. + + **Required?** Yes (File, Directory or Base64 must be present). + +- **Directory** + + Path to a directory containing one or more of the above certificate files. + Skips any files not containing any certificates. + + **Required?** Yes (File, Directory or Base64 must be present). + +- **Base64** + + Base64 encoded certificate(s). + Where the certificate(s) can be encoded as: + - single certificate + - p7b + - sst. + + This allows the certificates to be included in the XML file without a file directory dependency. + + > [!Note] + > You can use **certutil -encode** to a .cer file into base64. You can then use Notepad to copy and paste the base64 encoded certificate into the pin rule. + + **Required?** Yes (File, Directory or Base64 must be present). + +- **EndDate** + + Enables you to configure an expiration date for when the certificate is no longer valid in the pin rule. + + If you are in the process of switching to a new root or CA, you can set the **EndDate** to allow matching of this element’s certificates. + + If the current time is past the **EndDate**, then, when creating the certificate trust list (CTL), the parser outputs a warning message and exclude the certificate(s) from the Pin Rule in the generated CTL. + + For help with formatting Pin Rules, see [Representing a Date in XML](#representing-a-date-in-xml). + + **Required?** No. + +#### Site element + +The **Site** element can have the following attributes: + +- **Domain** + + Contains the DNS name to be matched for this pin rule. + When creating the certificate trust list, the parser normalizes the input name string value as follows: + - If the DNS name has a leading "*" it is removed. + - Non-ASCII DNS name are converted to ASCII Puny Code. + - Upper case ASCII characters are converted to lower case. + + If the normalized name has a leading ".", then, wildcard left hand label matching is enabled. + For example, ".xyz.com" would match "abc.xyz.com". + + **Required?** Yes. + +- **AllSubdomains** + + By default, wildcard left hand label matching is restricted to a single left hand label. + This attribute can be set to "true" to enable wildcard matching of all of the left hand labels. + + For example, setting this attribute would also match "123.abc.xyz.com" for the ".xyz.com" domain value. + + **Required?** No. + +### Create a Pin Rules Certificate Trust List + +The command line utility, **Certutil.exe**, includes the **generatePinRulesCTL** argument to parse the XML file and generate the encoded certificate trust list (CTL) that you add to your reference Windows 10 version 1703 computer and subsequently deploy. +The usage syntax is: + +```code +CertUtil [Options] -generatePinRulesCTL XMLFile CTLFile [SSTFile] + Generate Pin Rules CTL + XMLFile -- input XML file to be parsed. + CTLFile -- output CTL file to be generated. + SSTFile -- optional .sst file to be created. + The .sst file contains all of the certificates + used for pinning. + +Options: + -f -- Force overwrite + -v -- Verbose operation +``` + +The same certificate(s) can occur in multiple **PinRule** elements. +The same domain can occur in multiple **PinRule** elements. +Certutil coalesces these in the resultant pin rules certificate trust list. + +Certutil.exe does not strictly enforce the XML schema definition. +It does perform the following to enable other tools to add/consume their own specific elements and attributes: + +- Skips elements before and after the **PinRules** element. +- Skips any element not matching **Certificate** or **Site** within the **PinRules** element. +- Skips any attributes not matching the above names for each element type. + +Use the **certutil** command with the **generatePinRulesCTL** argument along with your XML file that contains your certificate pinning rules. +Lastly, provide the name of an output file that will include your certificate pinning rules in the form of a certificate trust list. + +```code +certutil -generatePinRulesCTL certPinRules.xml pinrules.stl +``` + +### Applying Certificate Pinning Rules to a Reference Computer + +Now that your certificate pinning rules are in the certificate trust list format, you need to apply the settings to a reference computer as a prerequisite to deploying the setting to your enterprise. +To simplify the deployment configuration, it is best to apply your certificate pinning rules to a computer that has the Group Policy Management Console (GPMC) that is include in the Remote Server Administration Tools (RSAT). + +Use **certutil.exe** to apply your certificate pinning rules to your reference computer using the **setreg** argument. +The **setreg** argument takes a secondary argument that determines the location of where certutil writes the certificate pining rules. +This secondary argument is **chain\PinRules**. +The last argument you provide is the name of file that contains your certificate pinning rules in certificate trust list format (.stl). +You’ll pass the name of the file as the last argument; however, you need to prefix the file name with the '@' symbol as shown in the following example. +You need to perform this command from an elevated command prompt. + +```code +Certutil -setreg chain\PinRules @pinrules.stl +``` + +Certutil writes the binary information to the following registration location: + +| Name | Value | +|------|-------| +| Key | HKLM\SOFTWARE\Microsoft\Cryptography\OID\EncodingType0\CertDllCreateCertificateChainEngine\Config | +| Name | PinRules | +| Value | Binary contents from the certificate pin rules certificate trust list file | +| Data type | REG_BINARY | + +![Registry binary information](images/enterprise-pinning-registry-binary-information.png) + +### Deploying Enterprise Pin Rule Settings using Group Policy + +You’ve successfully created a certificate pinning rules XML file. +From the XML file you have created a certificate pinning trust list file, and you have applied the contents of that file to your reference computer from which you can run the Group Policy Management Console. +Now you need to configure a Group Policy object to include the applied certificate pin rule settings and deploy it to your environment. + +Sign-in to the reference computer using domain administrator equivalent credentials. + +1. Start the **Group Policy Management Console** (gpmc.msc) +2. In the navigation pane, expand the forest node and then expand the domain node. +3. Expand the node that has contains your Active Directory’s domain name +4. Select the **Group Policy objects** node. Right-click the **Group Policy objects** node and click **New**. +5. In the **New GPO** dialog box, type _Enterprise Certificate Pinning Rules_ in the **Name** text box and click **OK**. +6. In the content pane, right-click the **Enterprise Certificate Pinning Rules** Group Policy object and click **Edit**. +7. In the **Group Policy Management Editor**, in the navigation pane, expand the **Preferences** node under **Computer Configuration**. Expand **Windows Settings**. +8. Right-click the **Registry** node and click **New**. +9. In the **New Registry Properties** dialog box, select **Update** from the **Action** list. Select **HKEY_LOCAL_MACHINE** from the **Hive** list. +10. For the **Key Path**, click **…** to launch the **Registry Item Browser**. Navigate to the following registry key and select the **PinRules** registry value name: + HKLM\SOFTWARE\Microsoft\Cryptography\OID\EncodingType0\CertDllCreateCertificateChainEngine\Config + Click **Select** to close the **Registry Item Browser**. +11. The **Key Path** should contain the selected registry key. The **Value name** configuration should contain the registry value name **_PinRules_**. **Value type** should read **_REGBINARY_** and **Value data** should contain a long series of numbers from 0-9 and letters ranging from A-F (hexadecimal). Click **OK** to save your settings and close the dialog box. + + ![PinRules Properties](images/enterprise-certificate-pinning-pinrules-properties.png) + +12. Close the **Group Policy Management Editor** to save your settings. +13. Link the **Enterprise Certificate Pinning Rules** Group Policy object to apply to computers that run Windows 10, version 1703 in your enterprise. When these domain-joined computers apply Group Policy, the registry information configured in the Group Policy object is applied to the computer. + +## Additional Pin Rules Logging + +To assist in constructing certificate pinning rules, you can configure the **PinRulesLogDir** setting under the certificate chain configuration registry key to include a parent directory to log pin rules. + +```code +HKLM\SOFTWARE\Microsoft\Cryptography\OID\EncodingType0\CertDllCreateCertificateChainEngine\Config +``` + +| Name | Value | +|------|-------| +| Key | HKLM\SOFTWARE\Microsoft\Cryptography\OID\EncodingType0\CertDllCreateCertificateChainEngine\Config | +| Name | PinRulesLogDir | +| Value | The Parent directory where Windows should write the additional pin rule logs | +| Data type | REG_SZ | + +### Permission for the Pin Rule Log Folder + +The folder in which Windows writes the additional pin rule logs must have permissions so that all users and applications have full access. +You can run the following commands from an elevated command prompt to achieved the proper permissions. + +```code +set PinRulesLogDir=c:\PinRulesLog +mkdir %PinRulesLogDir% +icacls %PinRulesLogDir% /grant *S-1-15-2-1:(OI)(CI)(F) +icacls %PinRulesLogDir% /grant *S-1-1-0:(OI)(CI)(F) +icacls %PinRulesLogDir% /grant *S-1-5-12:(OI)(CI)(F) +icacls %PinRulesLogDir% /inheritance:e /setintegritylevel (OI)(CI)L +``` + +Whenever an application verifies a TLS/SSL certificate chain that contains a server name matching a DNS name in the server certificate, Windows writes a .p7b file consisting of all the certificates in the server’s chain to one of three child folders: + +- AdminPinRules + Matched a site in the enterprise certificate pinning rules. +- AutoUpdatePinRules + Matched a site in the certificate pinning rules managed by Microsoft. +- NoPinRules + Didn’t match any site in the certificate pin rules. + +The output file name consists of the leading 8 ASCII hex digits of the root’s SHA1 thumbprint followed by the server name. +For example: + +- D4DE20D0_xsi.outlook.com.p7b +- DE28F4A4_www.yammer.com.p7b + +If there is either an enterprise certificate pin rule or Microsoft certificate pin rule mismatch, then Windows writes the .p7b file to the **MismatchPinRules** child folder. +If the pin rules have expired, then Windows writes the .p7b to the **ExpiredPinRules** child folder. + +## Representing a Date in XML + +Many attributes within the pin rules xml file are dates. +These dates must be properly formatted and represented in UTC. +You can use Windows PowerShell to format these dates. +You can then copy and paste the output of the cmdlet into the XML file. + +![Representing a date](images/enterprise-certificate-pinning-representing-a-date.png) + +For simplicity, you can truncate decimal point (.) and the numbers after it. +However, be certain to append the uppercase “Z” to the end of the XML date string. + +```code +2015-05-11T07:00:00.2655691Z +2015-05-11T07:00:00Z +``` + +## Converting an XML Date + +You can also use Windows PowerShell to validate convert an XML date into a human readable date to validate it’s the correct date. + +![Converting an XML date](images/enterprise-certificate-pinning-converting-an-xml-date.png) + +## Representing a Duration in XML + +Some elements may be configured to use a duration rather than a date. +You must represent the duration as an XML timespan data type. +You can use Windows PowerShell to properly format and validate durations (timespans) and copy and paste them into your XML file. + +![Representing a duration](images/enterprise-certificate-pinning-representing-a-duration.png) + +## Converting an XML Duration + +You can convert a XML formatted timespan into a timespan variable that you can read. + +![Converting an XML duration](images/enterprise-certificate-pinning-converting-a-duration.png) + +## Certificate Trust List XML Schema Definition (XSD) + +```code + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + + + + + + + + + diff --git a/windows/keep-secure/images/atp-actor.png b/windows/keep-secure/images/atp-actor.png new file mode 100644 index 0000000000..dc9c9dd6fc Binary files /dev/null and b/windows/keep-secure/images/atp-actor.png differ diff --git a/windows/keep-secure/images/atp-alert-source.png b/windows/keep-secure/images/atp-alert-source.png new file mode 100644 index 0000000000..c2155cc7ee Binary files /dev/null and b/windows/keep-secure/images/atp-alert-source.png differ diff --git a/windows/keep-secure/images/atp-alert-timeline-numbered.png b/windows/keep-secure/images/atp-alert-timeline-numbered.png new file mode 100644 index 0000000000..e791757460 Binary files /dev/null and b/windows/keep-secure/images/atp-alert-timeline-numbered.png differ diff --git a/windows/keep-secure/images/atp-file-details.png b/windows/keep-secure/images/atp-file-details.png new file mode 100644 index 0000000000..ad92f3af0c Binary files /dev/null and b/windows/keep-secure/images/atp-file-details.png differ diff --git a/windows/keep-secure/images/atp-remediated-alert.png b/windows/keep-secure/images/atp-remediated-alert.png new file mode 100644 index 0000000000..d49b681907 Binary files /dev/null and b/windows/keep-secure/images/atp-remediated-alert.png differ diff --git a/windows/keep-secure/images/atp-siem-integration.png b/windows/keep-secure/images/atp-siem-integration.png new file mode 100644 index 0000000000..0205980406 Binary files /dev/null and b/windows/keep-secure/images/atp-siem-integration.png differ diff --git a/windows/keep-secure/images/enterprise-certificate-pinning-converting-a-duration.png b/windows/keep-secure/images/enterprise-certificate-pinning-converting-a-duration.png new file mode 100644 index 0000000000..6d14d64c36 Binary files /dev/null and b/windows/keep-secure/images/enterprise-certificate-pinning-converting-a-duration.png differ diff --git a/windows/keep-secure/images/enterprise-certificate-pinning-converting-an-xml-date.png b/windows/keep-secure/images/enterprise-certificate-pinning-converting-an-xml-date.png new file mode 100644 index 0000000000..ab932c226f Binary files /dev/null and b/windows/keep-secure/images/enterprise-certificate-pinning-converting-an-xml-date.png differ diff --git a/windows/keep-secure/images/enterprise-certificate-pinning-pinrules-properties.png b/windows/keep-secure/images/enterprise-certificate-pinning-pinrules-properties.png new file mode 100644 index 0000000000..7a9b31f55f Binary files /dev/null and b/windows/keep-secure/images/enterprise-certificate-pinning-pinrules-properties.png differ diff --git a/windows/keep-secure/images/enterprise-certificate-pinning-representing-a-date.png b/windows/keep-secure/images/enterprise-certificate-pinning-representing-a-date.png new file mode 100644 index 0000000000..929cae9617 Binary files /dev/null and b/windows/keep-secure/images/enterprise-certificate-pinning-representing-a-date.png differ diff --git a/windows/keep-secure/images/enterprise-certificate-pinning-representing-a-duration.png b/windows/keep-secure/images/enterprise-certificate-pinning-representing-a-duration.png new file mode 100644 index 0000000000..dd79819a96 Binary files /dev/null and b/windows/keep-secure/images/enterprise-certificate-pinning-representing-a-duration.png differ diff --git a/windows/keep-secure/images/enterprise-pinning-registry-binary-information.png b/windows/keep-secure/images/enterprise-pinning-registry-binary-information.png new file mode 100644 index 0000000000..ee36266a6d Binary files /dev/null and b/windows/keep-secure/images/enterprise-pinning-registry-binary-information.png differ diff --git a/windows/keep-secure/interactive-logon-display-user-information-when-the-session-is-locked.md b/windows/keep-secure/interactive-logon-display-user-information-when-the-session-is-locked.md index ef87e381fc..5442141ce8 100644 --- a/windows/keep-secure/interactive-logon-display-user-information-when-the-session-is-locked.md +++ b/windows/keep-secure/interactive-logon-display-user-information-when-the-session-is-locked.md @@ -12,77 +12,78 @@ author: brianlic-msft # Interactive logon: Display user information when the session is locked **Applies to** -- Windows 10 +- Windows 10 Describes the best practices, location, values, and security considerations for the **Interactive logon: Display user information when the session is locked** security policy setting. ## Reference -This security setting controls whether details such as email address or domain\username appear with the username on the sign-in screen. -For clients that run Windows 10 version 1511 and 1507 (RTM), this setting works similarly to previous versions of Windows. -However, because of a new **Privacy** setting introduced in Windows 10 version 1607, this security setting affects those clients differently. +This security setting controls whether details such as email address or domain\username appear with the username on the sign-in screen. +For clients that run Windows 10 version 1511 and 1507 (RTM), this setting works similarly to previous versions of Windows. +However, because of a new **Privacy** setting introduced in Windows 10 version 1607, this security setting affects those clients differently. -### Changes in Windows 10 version 1607 +### Changes beginning with Windows 10 version 1607 -Beginning with Windows 10 version 1607, new functionality was added to Windows 10 to hide username details such as email address by default, with the ability to change the default to show the details. -This functionality is controlled by a new **Privacy** setting in **Settings** > **Accounts** > **Sign-in options**. -The Privacy setting is off by default, which hides the details. +Beginning with Windows 10 version 1607, new functionality was added to Windows 10 to hide username details such as email address by default, with the ability to change the default to show the details. +This functionality is controlled by a new **Privacy** setting in **Settings** > **Accounts** > **Sign-in options**. +The Privacy setting is off by default, which hides the details. ![Privacy setting](images\privacy-setting-in-sign-in-options.png) -The **Interactive logon: Display user information when the session is locked** Group Policy setting controls the same functionality. +The **Interactive logon: Display user information when the session is locked** Group Policy setting controls the same functionality. This setting has these possible values: - **User display name, domain and user names** - For a local logon, the user's full name is displayed. - If the user signed in using a Microsoft account, the user's email address is displayed. - For a domain logon, the domain\username is displayed. - This has the same effect as turning on the **Privacy** setting. + For a local logon, the user's full name is displayed. + If the user signed in using a Microsoft account, the user's email address is displayed. + For a domain logon, the domain\username is displayed. + This has the same effect as turning on the **Privacy** setting. - **User display name only** - The full name of the user who locked the session is displayed. + The full name of the user who locked the session is displayed. This has the same effect as turning off the **Privacy** setting. - **Do not display user information** - No names are displayed. - Beginning with Windows 10 version 1607, this option is not supported. - If this option is chosen, the full name of the user who locked the session is displayed instead. - This change makes this setting consistent with the functionality of the new **Privacy** setting. + No names are displayed. + Beginning with Windows 10 version 1607, this option is not supported. + If this option is chosen, the full name of the user who locked the session is displayed instead. + This change makes this setting consistent with the functionality of the new **Privacy** setting. To display no user information, enable the Group Policy setting **Interactive logon: Don't display last signed-in**. - Blank. - Default setting. - This translates to “Not defined,” but it will display the user’s full name in the same manner as the option **User display name only**. + Default setting. + This translates to “Not defined,” but it will display the user’s full name in the same manner as the option **User display name only**. When an option is set, you cannot reset this policy to blank, or not defined. ### Hotfix for Windows 10 version 1607 -Clients that run Windows 10 version 1607 will not show details on the sign-in screen even if the **User display name, domain and user names** option is chosen because the **Privacy** setting is off. -If the **Privacy** setting is turned on, details will show. +Clients that run Windows 10 version 1607 will not show details on the sign-in screen even if the **User display name, domain and user names** option is chosen because the **Privacy** setting is off. +If the **Privacy** setting is turned on, details will show. -The **Privacy** setting cannot be changed for clients in bulk. +The **Privacy** setting cannot be changed for clients in bulk. Instead, apply [KB 4013429](http://www.catalog.update.microsoft.com/Search.aspx?q=KB4013429) to clients that run Windows 10 version 1607 so they behave similarly to previous versions of Windows. +Clients that run later versions of Windows 10 do not require a hotfix. There are related Group Policy settings: -- **Computer Configuration\Policies\Administrative Templates\System\Logon\Block user from showing account details on sign-in** prevents users from showing account details on the sign-in screen. +- **Computer Configuration\Policies\Administrative Templates\System\Logon\Block user from showing account details on sign-in** prevents users from showing account details on the sign-in screen. - **Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Don’t display last signed-in** prevents the username of the last user to sign in from being shown. -- **Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Don’t display username at sign-in** prevents the username from being shown at Windows sign-in and immediately after credentials are entered and before the desktop appears. +- **Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Don’t display username at sign-in** prevents the username from being shown at Windows sign-in and immediately after credentials are entered and before the desktop appears. ### Interaction with related Group Policy settings -For all versions of Windows 10, only the user display name is shown by default. +For all versions of Windows 10, only the user display name is shown by default. -If **Block user from showing account details on sign-in** is enabled, then only the user display name is shown regardless of any other Group Policy settings. +If **Block user from showing account details on sign-in** is enabled, then only the user display name is shown regardless of any other Group Policy settings. Users will not be able to show details. -If **Block user from showing account details on sign-in** is not enabled, then you can set **Interactive logon: Display user information when the session is locked** to **User display name, domain and user names** to show additional details such as domain\username. -In this case, clients that run Windows 10 version 1607 need [KB 4013429](http://www.catalog.update.microsoft.com/Search.aspx?q=KB4013429) applied. -Users will not be able to hide additional details. +If **Block user from showing account details on sign-in** is not enabled, then you can set **Interactive logon: Display user information when the session is locked** to **User display name, domain and user names** to show additional details such as domain\username. +In this case, clients that run Windows 10 version 1607 need [KB 4013429](http://www.catalog.update.microsoft.com/Search.aspx?q=KB4013429) applied. +Users will not be able to hide additional details. If **Block user from showing account details on sign-in** is not enabled and **Don’t display last signed-in** is enabled, the username will not be shown. @@ -100,13 +101,13 @@ Computer Configuration\\Windows Settings\\Security Settings\\Local Policies\\Sec | Server type or Group Policy object (GPO) | Default value | | - | - | -| Default domain policy| Not defined| -| Default domain controller policy | Not defined| -| Stand-alone server default settings | Not defined| -| Domain controller effective default settings | **User display name, domain and user names**| -| Member server effective default settings | **User display name, domain and user names**| -| Effective GPO default settings on client computers | **User display name, domain and user names**| -  +| Default domain policy| Not defined| +| Default domain controller policy | Not defined| +| Stand-alone server default settings | Not defined| +| Domain controller effective default settings | **User display name, domain and user names**| +| Member server effective default settings | **User display name, domain and user names**| +| Effective GPO default settings on client computers | **User display name, domain and user names**| + ## Policy management This section describes features and tools that are available to help you manage this policy. diff --git a/windows/keep-secure/interactive-logon-do-not-display-last-user-name.md b/windows/keep-secure/interactive-logon-do-not-display-last-user-name.md index d712d65bdd..302baa44b9 100644 --- a/windows/keep-secure/interactive-logon-do-not-display-last-user-name.md +++ b/windows/keep-secure/interactive-logon-do-not-display-last-user-name.md @@ -40,14 +40,14 @@ Computer Configuration\\Windows Settings\\Security Settings\\Local Policies\\Sec ### Default values -| Server type or Group Policy object (GPO) | Default value| +| Server type or Group Policy object (GPO) | Default value| | - | - | -| Default domain policy| Disabled| -| Default domain controller policy| Disabled| -| Stand-alone server default settings | Disabled| -| Domain controller effective default settings | Disabled| -| Member server effective default settings | Disabled| -| Effective GPO default settings on client computers | Disabled| +| Default domain policy| Disabled| +| Default domain controller policy| Disabled| +| Stand-alone server default settings | Disabled| +| Domain controller effective default settings | Disabled| +| Member server effective default settings | Disabled| +| Effective GPO default settings on client computers | Disabled|   ## Policy management diff --git a/windows/keep-secure/pull-alerts-using-rest-api-windows-defender-advanced-threat-protection.md b/windows/keep-secure/pull-alerts-using-rest-api-windows-defender-advanced-threat-protection.md new file mode 100644 index 0000000000..af7b7f12d0 --- /dev/null +++ b/windows/keep-secure/pull-alerts-using-rest-api-windows-defender-advanced-threat-protection.md @@ -0,0 +1,189 @@ +--- +title: Pull Windows Defender ATP alerts using REST API +description: Pull alerts from the Windows Defender ATP portal REST API. +keywords: alerts, pull alerts, rest api, request, response +search.product: eADQiWindows 10XVcnh +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.pagetype: security +author: mjcaparas +localizationpriority: high +--- + +# Pull Windows Defender ATP alerts using REST API + +**Applies to:** + +- Windows 10 Enterprise +- Windows 10 Education +- Windows 10 Pro +- Windows 10 Pro Education +- Windows Defender Advanced Threat Protection (Windows Defender ATP) + +Windows Defender ATP supports the OAuth 2.0 protocol to pull alerts from the portal. + +In general, the OAuth 2.0 protocol supports four types of flows: +- Authorization grant flow +- Implicit flow +- Client credentials flow +- Resource owner flow + +For more information about the OAuth specifications, see the [OAuth Website](http://www.oauth.net). + +Windows Defender ATP supports the _Authorization grant flow_ and _Client credential flow_ to obtain access to generate alerts from the portal, with Azure Active Directory (AAD) as the authorization server. + +The _Authorization grant flow_ uses user credentials to get an authorization code, which is then used to obtain an access token. + +The _Client credential flow_ uses client credentials to authenticate against the Windows Defender ATP endpoint URL. This flow is suitable for scenarios when an OAuth client creates requests to an API that doesn't require user credentials. + +Use the following method in the Windows Defender ATP API to pull alerts in JSON format. + +## Before you begin +- Before calling the Windows Defender ATP endpoint to pull alerts, you'll need to enable the SIEM integration application in Azure Active Directory (AAD). For more information, see [Enable SIEM integration in Windows Defender ATP](enable-siem-integration-windows-defender-advanced-threat-protection.md). + +- Take note of the following values in your Azure application registration. You need these values to configure the OAuth flow in your service or daemon app: + - Application ID (unique to your application) + - App key, or secret (unique to your application) + - Your app's OAuth 2.0 token endpoint + - Find this value by clicking **View Endpoints** at the bottom of the Azure Management Portal in your app's page. The endpoint will look like `https://login.microsoftonline.com/{tenantId}/oauth2/token`. + +## Get an access token +Before creating calls to the endpoint, you'll need to get an access token. + +You'll use the access token to access the protected resource, which are alerts in Windows Defender ATP. + +To get an access token, you'll need to do a POST request to the token issuing endpoint. Here is a sample request: + +```syntax + +POST /72f988bf-86f1-41af-91ab-2d7cd011db47/oauth2/token HTTP/1.1 +Host: login.microsoftonline.com +Content-Type: application/x-www-form-urlencoded + +resource=https%3A%2F%2FWDATPAlertExport.Seville.onmicrosoft.com&client_id=35e0f735-5fe4-4693-9e68-3de80f1d3745&client_secret=IKXc6PxB2eoFNJ%2FIT%2Bl2JZZD9d9032VXz6Ul3D2WyUQ%3D&grant_type=client_credentials +``` +The response will include an access token and expiry information. + +```json +{ + "token type": "Bearer", + "expires in": "3599" + "ext_expires_in": "0", + "expires_on": "1488720683", + "not_before": "1488720683", + "resource": "https://WDATPAlertExport.Seville.onmicrosoft.com", + "access_token":"eyJ0eXaioJJOIneiowiouqSuzNiZ345FYOVkaJL0625TueyaJasjhIjEnbMlWqP..." +} +``` +You can now use the value in the *access_token* field in a request to the Windows Defender ATP API. + +## Request +With an access token, your app can make authenticated requests to the Windows Defender ATP API. Your app must append the access token to the Authorization header of each request. + +### Request syntax +Method | Request URI +:---|:---| +GET| Use the URI applicable for your region.

**For EU**: `https://wdatp-alertexporter-eu.windows.com/api/alerts`
**For US**: `https://wdatp-alertexporter-us.windows.com/api/alerts` + +### Request header +Header | Type | Description| +:--|:--|:-- +Authorization | string | Required. The Azure AD access token in the form **Bearer** <*token*>. | + +### Request parameters + +Use optional query parameters to specify and control the amount of data returned in a response. If you call this method without parameters, the response contains all the alerts in your organization. + +Name | Value| Description +:---|:---|:--- +DateTime?sinceTimeUtc | string | Defines the time alerts are retrieved from based from `LastProccesedTimeUtc` time to current time.

**NOTE**: When not specified, all alerts generated in the last two hours are retrieved. +int?limit | int | Defines the number of alerts to be retrieved. Most recent alerts will be retrieved based on the number defined.

**NOTE**: When not specified, all alerts available in the time range will be retrieved. + +### Request example +The following example demonstrates how to retrieve all the alerts in your organization. + +```syntax +GET https://wdatp-alertexporter-eu.windows.com/api/alerts +Authorization: Bearer +``` + +The following example demonstrates a request to get the last 20 alerts since 2016-09-12 00:00:00. + +```syntax +GET https://wdatp-alertexporter-eu.windows.com/api/alerts?limit=20&sinceTimeUtc="2016-09-12 00:00:00" +Authorization: Bearer +``` + +## Response +The return value is an array of alert objects in JSON format. + +Here is an example return value: + +```json +{"AlertTime":"2017-01-23T07:32:54.1861171Z", +"ComputerDnsName":"desktop-bvccckk", +"AlertTitle":"Suspicious PowerShell commandline", +"Category":"SuspiciousActivity", +"Severity":"Medium", +"AlertId":"636207535742330111_-1114309685", +"Actor":null, +"LinkToWDATP":"https://securitycenter.windows.com/alert/636207535742330111_-1114309685", +"IocName":null, +"IocValue":null, +"CreatorIocName":null, +"CreatorIocValue":null, +"Sha1":"69484ca722b4285a234896a2e31707cbedc59ef9", +"FileName":"powershell.exe", +"FilePath":"C:\\Windows\\SysWOW64\\WindowsPowerShell\\v1.0", +"IpAddress":null, +"Url":null, +"IoaDefinitiondId":"7f1c3609-a3ff-40e2-995b-c01770161d68", +"UserName":null, +"AlertPart":0, +"FullId":"636207535742330111_-1114309685:9DE735BA9FF87725E392C6DFBEB2AF279035CDE229FCC00D28C0F3242C5A50AF", +"LastProcessedTimeUtc":"2017-01-23T11:33:45.0760449Z", +"ThreatCategory":null, +"ThreatFamily":null, +"ThreatName":null, +"RemediationAction":null, +"RemediationIsSuccess":null, +"Source":"Windows Defender ATP", +"Md5":null, +"Sha256":null, +"WasExecutingWhileDetected":null, +"FileHash":"69484ca722b4285a234896a2e31707cbedc59ef9", +"IocUniqueId":"9DE735BA9FF87725E392C6DFBEB2AF279035CDE229FCC00D28C0F3242C5A50AF"} +``` + +## Code examples +### Get access token +The following code example demonstrates how to obtain an access token and call the Windows Defender ATP API. + +```syntax +AuthenticationContext context = new AuthenticationContext(string.Format("https://login.windows.net/{0}/oauth2", tenantId)); +ClientCredential clientCredentials = new ClientCredential(clientId, clientSecret); +AuthenticationResult authenticationResult = context.AcquireToken(resource, clientCredentials); +``` +### Use token to connect to the alerts endpoint + +``` +HttpClient httpClient = new HttpClient(); +httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue(authenticationResult.AccessTokenType, authenticationResult.AccessToken); +HttpResponseMessage response = httpClient.GetAsync("https://wdatp-alertexporter-eu.windows.com/api/alert").GetAwaiter().GetResult(); +string alertsJson = response.Content.ReadAsStringAsync().Result; +Console.WriteLine("Got alert list: {0}", alertsJson); + +``` + + + + +## Error codes +The Windows Defender ATP REST API returns the following error codes caused by an invalid request. + +HTTP error code | Description +:---|:--- +401 | Malformed request or invalid token. +403 | Unauthorized exception - any of the domains is not managed by the tenant administrator or tenant state is deleted. +500 | Error in the service. diff --git a/windows/keep-secure/types-of-attacks-for-volume-encryption-keys.md b/windows/keep-secure/types-of-attacks-for-volume-encryption-keys.md index 96a64490d0..efc97f3e17 100644 --- a/windows/keep-secure/types-of-attacks-for-volume-encryption-keys.md +++ b/windows/keep-secure/types-of-attacks-for-volume-encryption-keys.md @@ -14,7 +14,7 @@ author: brianlic-msft **Applies to** - Windows 10 -There are many ways Windows helps protect your organization from attacks, including Unified Extensible Firmware Interface (UEFI) secure boot, Trusted Platform Module (TPM), Group Policy, complex passwords, and account lockouts. +There are many ways Windows helps protect your organization from attacks, including Unified Extensible Firmware Interface (UEFI) Secure Boot, Trusted Platform Module (TPM), Group Policy, complex passwords, and account lockouts. The next few sections describe each type of attack that could be used to compromise a volume encryption key, whether for BitLocker or a non-Microsoft encryption solution. After an attacker has compromised a volume encryption key, the attacker can read data from your system drive or even install malware while Windows is offline. Each section begins with a graphical overview of the attack’s strengths and weaknesses as well as suggested mitigations. @@ -40,7 +40,7 @@ Although password protection of the UEFI configuration is important for protecti For this reason, when BitLocker is configured on devices that include a TPM, the TPM and its PCRs are always used to secure and confirm the integrity of the pre–operating system environment before making encrypted volumes accessible. -Any changes to the UEFI configuration invalidates the PCR7 and require the user to enter the BitLocker recovery key. Because of this feature, it’s not critical to password-protect your UEFI configuration. If an attacker successfully turns off Secure Boot or otherwise changes the UEFI configuration, they will need to enter the BitLocker recovery key, but UEFI password protection is a best practice and is still required for systems not using a TPM (such as non-Microsoft alternatives). +Any change to the UEFI configuration invalidates the PCR7 and requires the user to enter the BitLocker recovery key. Because of this feature, it’s not critical to password-protect your UEFI configuration. But UEFI password protection is a best practice and is still required for systems not using a TPM (such as non-Microsoft alternatives). ### Brute-force Sign-in Attacks diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index 54d2793663..151fefd372 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -71,7 +71,7 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in | [Manage device restarts after updates](waas-restart.md) | New | | [Manage Windows 10 in your organization - transitioning to modern management](manage-windows-10-in-your-organization-modern-management.md) | New | | [Cortana integration in your business or enterprise](manage-cortana-in-enterprise.md) |Added an important note about Cortana and Office 365 integration. | -| [Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md) | Fixed the explanation for Start behavior when the .xml file containing the layout is not available when the user signs in. | +| [Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md) | Fixed the explanation for Start behavior when the .xml file containing the layout is not available when the user signs in. | | [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md) | Added link to the Windows Restricted Traffic Limited Functionality Baseline. Added Teredo Group Policy. | | [Manage updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile](waas-mobile-updates.md) | Added Current Branch for Business (CBB) support for Windows 10 IoT Mobile. | @@ -98,7 +98,7 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in ## RELEASE: Windows 10, version 1607 -The topics in this library have been updated for Windows 10, version 1607 (also known as the Anniversary Update). The following new topics have been added: +The topics in this library have been updated for Windows 10, version 1607 (also known as the Anniversary Update). The following new topics have been added: - [Connect to remote Azure Active Directory-joined PC](connect-to-remote-aadj-pc.md) - [Configure Windows 10 taskbar](configure-windows-10-taskbar.md) @@ -130,7 +130,7 @@ The topics in this library have been updated for Windows 10, version 1607 (also | [Configure Windows telemetry in your organization](configure-windows-telemetry-in-your-organization.md) | New telemetry content | | [Manage Wi-Fi Sense in your company](manage-wifi-sense-in-enterprise.md) |Removed info about sharing wi-fi network access with contacts, since it's been deprecated. | | [Set up a kiosk on Windows 10 Pro, Enterprise, or Education](set-up-a-kiosk-for-windows-10-for-desktop-editions.md) | Corrected script for setting a custom shell using Shell Launcher | -| [Windows 10 servicing options for updates and upgrades](introduction-to-windows-10-servicing.md) | Removed Windows 10 Mobile from **Applies to** | +| [Windows 10 servicing options for updates and upgrades](introduction-to-windows-10-servicing.md) | Removed Windows 10 Mobile from **Applies to** | @@ -155,12 +155,12 @@ The topics in this library have been updated for Windows 10, version 1607 (also | New or changed topic | Description | | ---|---| | [Configure telemetry and other settings in your organization](disconnect-your-organization-from-microsoft.md) | Added call history and email to the Settings > Privacy section.
Added the Turn off Windows Mail application Group Policy to the Mail synchronization section. | -| [Customize and export Start layout](customize-and-export-start-layout.md) | Added a note to clarify that partial Start layout is only supported in Windows 10, version 1511 and later | +| [Customize and export Start layout](customize-and-export-start-layout.md) | Added a note to clarify that partial Start layout is only supported in Windows 10, version 1511 and later | | [Customize Windows 10 Start with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md) | Added instructions for replacing markup characters with escape characters in Start layout XML | | [Introduction to configuration service providers (CSPs) for IT pros](how-it-pros-can-use-configuration-service-providers.md) | New | | [Windows 10 Mobile and MDM](windows-10-mobile-and-mdm.md) | New | -| [Windows 10 servicing options for updates and upgrades](introduction-to-windows-10-servicing.md) | Added information on servicing options for Windows 10 Mobile, Windows 10 Mobile Enterprise, and Windows 10 IoT Core (IoT Core). | -  +| [Windows 10 servicing options for updates and upgrades](introduction-to-windows-10-servicing.md) | Added information on servicing options for Windows 10 Mobile, Windows 10 Mobile Enterprise, and Windows 10 IoT Core (IoT Core). | + ## December 2015 @@ -198,5 +198,3 @@ The topics in this library have been updated for Windows 10, version 1607 (also [Change history for Deploy Windows 10](../deploy/change-history-for-deploy-windows-10.md) [Change history for Keep Windows 10 secure](../keep-secure/change-history-for-keep-windows-10-secure.md) - -  diff --git a/windows/manage/waas-optimize-windows-10-updates.md b/windows/manage/waas-optimize-windows-10-updates.md index e8a17a2b8b..681a39ca98 100644 --- a/windows/manage/waas-optimize-windows-10-updates.md +++ b/windows/manage/waas-optimize-windows-10-updates.md @@ -13,24 +13,24 @@ localizationpriority: high **Applies to** -- Windows 10 +- Windows 10 -> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq) +> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq) When considering your content distribution strategy for Windows 10, think about enabling a form of peer-to-peer content sharing to reduce bandwidth issues during updates. Windows 10 offers two peer-to-peer options for update content distribution: Delivery Optimization and BranchCache. These technologies can be used with several of the servicing tools for Windows 10. -Two methods of peer-to-peer content distribution are available in Windows 10. +Two methods of peer-to-peer content distribution are available in Windows 10. -- [Delivery Optimization](waas-delivery-optimization.md) is a new peer-to-peer distribution method in Windows 10. Windows 10 clients can source content from other devices on their local network that have already downloaded the updates or from peers over the internet. Using the settings available for Delivery Optimization, clients can be configured into groups, allowing organizations to identify devices that are possibly the best candidates to fulfil peer-to-peer requests. +- [Delivery Optimization](waas-delivery-optimization.md) is a new peer-to-peer distribution method in Windows 10. Windows 10 clients can source content from other devices on their local network that have already downloaded the updates or from peers over the internet. Using the settings available for Delivery Optimization, clients can be configured into groups, allowing organizations to identify devices that are possibly the best candidates to fulfil peer-to-peer requests. - Windows Update, Windows Update for Business, and Windows Server Update Services (WSUS) can use Delivery Optimization. Delivery Optimization can significantly reduce the amount of network traffic to external Windows Update sources as well as the time it takes for clients to retrieve the updates. + Windows Update, Windows Update for Business, and Windows Server Update Services (WSUS) can use Delivery Optimization. Delivery Optimization can significantly reduce the amount of network traffic to external Windows Update sources as well as the time it takes for clients to retrieve the updates. -- [BranchCache](waas-branchcache.md) is a bandwidth optimization technology that is included in some editions of the Windows Server 2016 Technical Preview and Windows 10 operating systems, as well as in some editions of Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows 8, Windows Server 2008 R2, and Windows 7. +- [BranchCache](waas-branchcache.md) is a bandwidth optimization technology that is included in some editions of the Windows Server 2016 Technical Preview and Windows 10 operating systems, as well as in some editions of Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows 8, Windows Server 2008 R2, and Windows 7. >[!NOTE] >Full BranchCache functionality is supported in Windows 10 Enterprise and Education; Windows 10 Pro supports some BranchCache functionality, including BITS transfers used for servicing operations. - Windows Server Update Services (WSUS) and System Center Configuration Manager can use BranchCache to allow peers to source content from each other versus always having to contact a server. Using BranchCache, files are cached on each individual client, and other clients can retrieve them as needed. This approach distributes the cache rather than having a single point of retrieval, saving a significant amount of bandwidth while drastically reducing the time that it takes for clients to receive the requested content. + Windows Server Update Services (WSUS) and System Center Configuration Manager can use BranchCache to allow peers to source content from each other versus always having to contact a server. Using BranchCache, files are cached on each individual client, and other clients can retrieve them as needed. This approach distributes the cache rather than having a single point of retrieval, saving a significant amount of bandwidth while drastically reducing the time that it takes for clients to receive the requested content.

@@ -50,7 +50,7 @@ Windows 10 update downloads can be large because every package contains all prev ### How Microsoft supports Express - **Express on WSUS Standalone** - + Express update delivery is available on [all support versions of WSUS](https://technet.microsoft.com/library/cc708456(v=ws.10).aspx). - **Express on devices directly connected to Windows Update** - **Enterprise devices managed using [Windows Update for Business](waas-manage-updates-wufb.md)** also get the benefit of Express update delivery support without any change in configuration. @@ -96,7 +96,7 @@ or [Manage Windows 10 updates using System Center Configuration Manager](waas-ma ## Related topics - [Update Windows 10 in the enterprise](waas-update-windows-10.md) -- [Manage updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile](waas-mobile-updates.md) +- [Manage updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile](waas-mobile-updates.md) - [Configure Delivery Optimization for Windows 10 updates](waas-delivery-optimization.md) - [Configure BranchCache for Windows 10 updates](waas-branchcache.md) - [Configure Windows Update for Business](waas-configure-wufb.md) @@ -104,5 +104,3 @@ or [Manage Windows 10 updates using System Center Configuration Manager](waas-ma - [Walkthrough: use Group Policy to configure Windows Update for Business](waas-wufb-group-policy.md) - [Walkthrough: use Intune to configure Windows Update for Business](waas-wufb-intune.md) - [Manage device restarts after updates](waas-restart.md) - - diff --git a/windows/manage/windows-store-for-business-overview.md b/windows/manage/windows-store-for-business-overview.md index 59c4b92895..81941f86f8 100644 --- a/windows/manage/windows-store-for-business-overview.md +++ b/windows/manage/windows-store-for-business-overview.md @@ -254,6 +254,7 @@ Store for Business is currently available in these markets.

  • Luxembourg
  • Malaysia
  • Malta
    • +
  • Mauritius
  • Mexico
  • Mongolia
  • Montenegro
    • @@ -275,12 +276,12 @@ Store for Business is currently available in these markets.
  • Portugal
  • Puerto Rico
  • Qatar
    • -
  • Romania
    • -
  • Rwanda
    • +
  • Romania