Merge remote-tracking branch 'refs/remotes/origin/master' into jd-sandbox
1
.gitignore
vendored
@ -14,3 +14,4 @@ windows/keep-secure/index.md
|
|||||||
|
|
||||||
# User-specific files
|
# User-specific files
|
||||||
.vs/
|
.vs/
|
||||||
|
*.png
|
BIN
atp-mdm-onboarding-package.png
Normal file
After Width: | Height: | Size: 75 KiB |
@ -17,7 +17,7 @@ If you’re having problems launching your legacy apps while running Internet Ex
|
|||||||
|
|
||||||
1. **For x86 systems or for 32-bit processes on x64 systems:** Go to the `HKLM\SOFTWARE\MICROSOFT\.NETFramework` registry key and change the **EnableIEHosting** value to **1**.
|
1. **For x86 systems or for 32-bit processes on x64 systems:** Go to the `HKLM\SOFTWARE\MICROSOFT\.NETFramework` registry key and change the **EnableIEHosting** value to **1**.
|
||||||
|
|
||||||
2. **For x64 systems or for 64-bit processes on x64 systems:** Go to the `HKLM\SOFTWARE\Wow6432Node\.NETFramework` registry key and change the **EnableIEHosting** value to **1**.
|
2. **For x64 systems or for 64-bit processes on x64 systems:** Go to the `HKLM\SOFTWARE\Wow6432Node\MICROSOFT\.NETFramework` registry key and change the **EnableIEHosting** value to **1**.
|
||||||
|
|
||||||
For more information, see the [Web Applications](https://go.microsoft.com/fwlink/p/?LinkId=308903) section of the Application Compatibility in the .NET Framework 4.5 page.
|
For more information, see the [Web Applications](https://go.microsoft.com/fwlink/p/?LinkId=308903) section of the Application Compatibility in the .NET Framework 4.5 page.
|
||||||
|
|
||||||
|
@ -41,8 +41,8 @@ In IE, press **ALT+V** to show the **View** menu, press **T** to enter the **Too
|
|||||||
## Where did the search box go?
|
## Where did the search box go?
|
||||||
IE11 uses the **One Box** feature, which lets users type search terms directly into the **Address bar**. Any text entered into the **Address bar** that doesn't appear to be a URL is automatically sent to the currently selected search provider.
|
IE11 uses the **One Box** feature, which lets users type search terms directly into the **Address bar**. Any text entered into the **Address bar** that doesn't appear to be a URL is automatically sent to the currently selected search provider.
|
||||||
|
|
||||||
**Note**<br>
|
>[!NOTE]
|
||||||
Depending on how you've set up your intranet search, the text entry might resolve to an intranet site. For more information about this, see [Intranet problems with Internet Explorer 11](intranet-problems-and-ie11.md).
|
>Depending on how you've set up your intranet search, the text entry might resolve to an intranet site. For more information about this, see [Intranet problems with Internet Explorer 11](intranet-problems-and-ie11.md).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -101,7 +101,7 @@ When you run ADKsetup.exe for Windows 10, version 1607, select **Configuration D
|
|||||||
|
|
||||||
Provisioning packages make use of configuration service providers (CSPs). If you're not familiar with CSPs, see [Introduction to configuration service providers (CSPs) for IT pros](https://technet.microsoft.com/itpro/windows/manage/how-it-pros-can-use-configuration-service-providers).
|
Provisioning packages make use of configuration service providers (CSPs). If you're not familiar with CSPs, see [Introduction to configuration service providers (CSPs) for IT pros](https://technet.microsoft.com/itpro/windows/manage/how-it-pros-can-use-configuration-service-providers).
|
||||||
|
|
||||||
In Windows ICD, when you create a provisioning package for Windows Holographic, the settings in **Available customizations** are based on [CSPs that are supported in Windows Holographic](https://msdn.microsoft.co/library/windows/hardware/dn920025.aspx#HoloLens). The following table describes settings that you might want to configure for HoloLens.
|
In Windows ICD, when you create a provisioning package for Windows Holographic, the settings in **Available customizations** are based on [CSPs that are supported in Windows Holographic](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/configuration-service-provider-reference#hololens). The following table describes settings that you might want to configure for HoloLens.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
|
BIN
windows/deploy/images/upgrade-analytics-unsubscribe.png
Normal file
After Width: | Height: | Size: 33 KiB |
@ -1,4 +1,4 @@
|
|||||||
---
|
---
|
||||||
title: Troubleshoot Upgrade Analytics (Windows 10)
|
title: Troubleshoot Upgrade Analytics (Windows 10)
|
||||||
description: Provides troubleshooting information for Upgrade Analytics.
|
description: Provides troubleshooting information for Upgrade Analytics.
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
@ -25,9 +25,14 @@ If you still don’t see data in Upgrade Analytics, follow these steps:
|
|||||||
|
|
||||||
If you want to stop using Upgrade Analytics and stop sending telemetry data to Microsoft, follow these steps:
|
If you want to stop using Upgrade Analytics and stop sending telemetry data to Microsoft, follow these steps:
|
||||||
|
|
||||||
1. Unsubscribe from the Upgrade Analytics solution in the OMS portal.
|
1. Unsubscribe from the Upgrade Analytics solution in the OMS portal. In the OMS portal, go to **Settings** > **Connected Sources** > **Windows Telemetry** and choose the **Unsubscribe** option.
|
||||||
|
|
||||||
2. Disable the Customer Experience Improvement Program on computers running Windows 7 SP1 or 8.1. On computers running Windows 10, set the telemetry level to Security.
|

|
||||||
|
|
||||||
3. Delete the CommercialDataOptin key in *HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\DataCollection*
|
2. Disable the Commercial Data Opt-in Key on computers running Windows 7 SP1 or 8.1. On computers running Windows 10, set the telemetry level to **Security**:
|
||||||
|
|
||||||
|
**Windows 7 and Windows 8.1**: Delete CommercialDataOptIn registry property from *HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection*
|
||||||
|
**Windows 10**: Follow the instructions in the [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization#enterprise-management) topic.
|
||||||
|
|
||||||
|
3. If you enabled **Internet Explorer Site Discovery**, you can disable Internet Explorer data collection by setting the *IEDataOptIn* registry key to value "0". The IEDataOptIn key can be found under: *HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection*.
|
||||||
|
4. You can also remove the “CommercialId” key from: "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection". **This is an optional step**.
|
||||||
|
@ -153,7 +153,7 @@ The lab architecture is summarized in the following diagram:
|
|||||||
|
|
||||||
[Verify support and install Hyper-V](#verify-support-and-install-hyper-v)<BR>
|
[Verify support and install Hyper-V](#verify-support-and-install-hyper-v)<BR>
|
||||||
[Download VHD and ISO files](#download-vhd-and-iso-files)<BR>
|
[Download VHD and ISO files](#download-vhd-and-iso-files)<BR>
|
||||||
[Convert PC to VHD](#convert-pc-to-vhd)<BR>
|
[Convert PC to VM](#convert-pc-to-vm)<BR>
|
||||||
[Resize VHD](#resize-vhd)<BR>
|
[Resize VHD](#resize-vhd)<BR>
|
||||||
[Configure Hyper-V](#configure-hyper-v)<BR>
|
[Configure Hyper-V](#configure-hyper-v)<BR>
|
||||||
[Configure VMs](#configure-vms)<BR>
|
[Configure VMs](#configure-vms)<BR>
|
||||||
@ -201,7 +201,9 @@ Starting with Windows 8, the host computer’s microprocessor must support secon
|
|||||||
|
|
||||||
<pre style="overflow-y: visible">Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V –All</pre>
|
<pre style="overflow-y: visible">Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V –All</pre>
|
||||||
|
|
||||||
This command works on all operating systems that support Hyper-V.
|
This command works on all operating systems that support Hyper-V, but on Windows Server operating systems you must type an additional command to add the Hyper-V Windows PowerShell module and the Hyper-V Manager console. This command will also install Hyper-V if it isn't already installed, so if desired you can just type the following command on Windows Server 2012 or 2016 instead of using the Enable-WindowsOptionalFeature command:
|
||||||
|
|
||||||
|
<pre style="overflow-y: visible">Install-WindowsFeature -Name Hyper-V -IncludeManagementTools</pre>
|
||||||
|
|
||||||
When you are prompted to restart the computer, choose **Yes**. The computer might restart more than once. After installation is complete, you can open Hyper-V Manager by typing **virtmgmt.msc** at an elevated command prompt.
|
When you are prompted to restart the computer, choose **Yes**. The computer might restart more than once. After installation is complete, you can open Hyper-V Manager by typing **virtmgmt.msc** at an elevated command prompt.
|
||||||
|
|
||||||
@ -211,7 +213,7 @@ Starting with Windows 8, the host computer’s microprocessor must support secon
|
|||||||
|
|
||||||

|

|
||||||
|
|
||||||
<P>If you choose to install Hyper-V using Server Manager, accept all default selections.
|
<P>If you choose to install Hyper-V using Server Manager, accept all default selections. Also be sure to install both items under **Role Administration Tools\Hyper-V Management Tools**.
|
||||||
|
|
||||||
### Download VHD and ISO files
|
### Download VHD and ISO files
|
||||||
|
|
||||||
@ -505,9 +507,18 @@ Notes:<BR>
|
|||||||
|
|
||||||
### Resize VHD
|
### Resize VHD
|
||||||
|
|
||||||
**Important**: You should take advantage of [enhanced session mode](https://technet.microsoft.com/windows-server-docs/compute/hyper-v/learn-more/Use-local-resources-on-Hyper-V-virtual-machine-with-VMConnect) when completing instructions in this guide. Enhanced session mode enables you to copy and paste the commands from the Hyper-V host to VMs, between VMs, and between RDP sessions. After copying some text, you can paste into a Windows PowerShell window by simply right-clicking. Before right-clicking, do not left click other locations as this can empty the clipboard. You can also copy and paste <U>files</U> directly from one computer to another by right-clicking and selecting copy on one computer, then right-clicking and selecting paste on another computer.
|
<HR size=4>
|
||||||
|
**<I>Enhanced session mode</I>**
|
||||||
|
|
||||||
As mentioned previously: instructions to "type" commands provided in this guide can be typed, but the preferred method is to copy and paste these commands. Most of the commands to this point in the guide have been brief, but many commands in sections below are longer and more complex.
|
**Important**: Before proceeding, verify that you can take advantage of [enhanced session mode](https://technet.microsoft.com/windows-server-docs/compute/hyper-v/learn-more/Use-local-resources-on-Hyper-V-virtual-machine-with-VMConnect) when completing instructions in this guide. Enhanced session mode enables you to copy and paste the commands from the Hyper-V host to VMs, between VMs, and between RDP sessions. After copying some text, you can paste into a Windows PowerShell window by simply right-clicking. Before right-clicking, do not left click other locations as this can empty the clipboard. You can also copy and paste <U>files</U> directly from one computer to another by right-clicking and selecting copy on one computer, then right-clicking and selecting paste on another computer.
|
||||||
|
|
||||||
|
To verify that enhanced session mode is enabled on the Hyper-V host, type the following command at an elevated Windows PowerShell prompt:
|
||||||
|
|
||||||
|
<pre style="overflow-y: visible">Set-VMhost -EnableEnhancedSessionMode $TRUE</pre>
|
||||||
|
|
||||||
|
>If enhanced session mode was not previously enabled, close any existing virtual machine connections and re-open them to enable access to enhanced session mode. As mentioned previously: instructions to "type" commands provided in this guide can be typed, but the preferred method is to copy and paste these commands. Most of the commands to this point in the guide have been brief, but many commands in sections below are longer and more complex.
|
||||||
|
|
||||||
|
<HR size=4>
|
||||||
|
|
||||||
The second Windows Server 2012 R2 VHD needs to be expanded in size from 40GB to 100GB to support installing imaging tools and storing OS images.
|
The second Windows Server 2012 R2 VHD needs to be expanded in size from 40GB to 100GB to support installing imaging tools and storing OS images.
|
||||||
|
|
||||||
@ -826,7 +837,7 @@ The second Windows Server 2012 R2 VHD needs to be expanded in size from 40GB to
|
|||||||
Restart-Computer
|
Restart-Computer
|
||||||
</pre>
|
</pre>
|
||||||
|
|
||||||
>If you do not see the script pane, click **View** and then click **Show Script Pane Top**.
|
>If you do not see the script pane, click **View** and verify **Show Script Pane Top** is enabled. Click **File** and then click **New**.
|
||||||
|
|
||||||
See the following example:
|
See the following example:
|
||||||
|
|
||||||
@ -839,7 +850,9 @@ The second Windows Server 2012 R2 VHD needs to be expanded in size from 40GB to
|
|||||||
Copy-VMFile "PC1" –SourcePath "C:\VHD\pc1.ps1" –DestinationPath "C:\pc1.ps1" –CreateFullPath –FileSource Host
|
Copy-VMFile "PC1" –SourcePath "C:\VHD\pc1.ps1" –DestinationPath "C:\pc1.ps1" –CreateFullPath –FileSource Host
|
||||||
</pre>
|
</pre>
|
||||||
|
|
||||||
>In order for this command to work properly, PC1 must be running the vmicguestinterface (Hyper-V Guest Service Interface) service. If this service is not installed, you can try updating integration services on the VM. This can be done by mounting the Hyper-V Integration Services Setup (vmguest.iso), which is located in C:\Windows\System32 on Windows Server operating systems that are running the Hyper-V role service. Otherwise, just create the file c:\pc1.ps1 on the VM by typing the commands into this file manually. Be sure to save the file as a Windows PowerShell script file with the .ps1 extension and not as a text (.txt) file.
|
>In order for this command to work properly, PC1 must be running the vmicguestinterface (Hyper-V Guest Service Interface) service. If this service is not installed, you can try updating integration services on the VM. This can be done by mounting the Hyper-V Integration Services Setup (vmguest.iso), which is located in C:\Windows\System32 on Windows Server operating systems that are running the Hyper-V role service.
|
||||||
|
|
||||||
|
If the copy-vmfile command does not work and you cannot properly upgrade integration services on PC1, then create the file c:\pc1.ps1 on the VM by typing the commands into this file manually. The copy-vmfile command is only used in this procedure as a demonstration. After typing the script file manually, be sure to save the file as a Windows PowerShell script file with the .ps1 extension and not as a text (.txt) file.
|
||||||
|
|
||||||
21. On PC1, type the following commands at an elevated Windows PowerShell prompt:
|
21. On PC1, type the following commands at an elevated Windows PowerShell prompt:
|
||||||
|
|
||||||
@ -954,7 +967,7 @@ The second Windows Server 2012 R2 VHD needs to be expanded in size from 40GB to
|
|||||||
36. Lastly, because the client computer has different hardware after copying it to a VM, its Windows activation will be invalidated and you might receive a message that you must activate Windows in 3 days. To extend this period to 30 days, type the following commands at an elevated Windows PowerShell prompt on PC1:
|
36. Lastly, because the client computer has different hardware after copying it to a VM, its Windows activation will be invalidated and you might receive a message that you must activate Windows in 3 days. To extend this period to 30 days, type the following commands at an elevated Windows PowerShell prompt on PC1:
|
||||||
|
|
||||||
<pre style="overflow-y: visible">
|
<pre style="overflow-y: visible">
|
||||||
runas /noprofile /env /user:administrator@contoso.com "cmd slmgr -rearm"
|
runas /noprofile /env /user:administrator@contoso.com "cmd /c slmgr -rearm"
|
||||||
Restart-Computer
|
Restart-Computer
|
||||||
</pre>
|
</pre>
|
||||||
|
|
||||||
@ -979,6 +992,8 @@ Set-ADUser -Identity CM_JD -PasswordNeverExpires $true
|
|||||||
Set-ADUser -Identity CM_NAA -PasswordNeverExpires $true
|
Set-ADUser -Identity CM_NAA -PasswordNeverExpires $true
|
||||||
</pre>
|
</pre>
|
||||||
|
|
||||||
|
This completes configuration of the starting PoC environment. Additional services and tools are installed in subsequent guides.
|
||||||
|
|
||||||
## Appendix A: Verify the configuration
|
## Appendix A: Verify the configuration
|
||||||
|
|
||||||
Use the following procedures to verify that the PoC environment is configured properly and working as expected.
|
Use the following procedures to verify that the PoC environment is configured properly and working as expected.
|
||||||
|
@ -31,6 +31,7 @@
|
|||||||
##### [Create and deploy a VPN policy for Windows Information Protection (WIP) using Microsoft Intune](create-vpn-and-wip-policy-using-intune.md)
|
##### [Create and deploy a VPN policy for Windows Information Protection (WIP) using Microsoft Intune](create-vpn-and-wip-policy-using-intune.md)
|
||||||
#### [Create and deploy a Windows Information Protection (WIP) policy using System Center Configuration Manager](create-wip-policy-using-sccm.md)
|
#### [Create and deploy a Windows Information Protection (WIP) policy using System Center Configuration Manager](create-wip-policy-using-sccm.md)
|
||||||
#### [Create and verify an Encrypting File System (EFS) Data Recovery Agent (DRA) certificate](create-and-verify-an-efs-dra-certificate.md)
|
#### [Create and verify an Encrypting File System (EFS) Data Recovery Agent (DRA) certificate](create-and-verify-an-efs-dra-certificate.md)
|
||||||
|
#### [Determine the Enterprise Context of an app running in Windows Information Protection (WIP)](wip-app-enterprise-context.md)
|
||||||
### [Mandatory tasks and settings required to turn on Windows Information Protection (WIP)](mandatory-settings-for-wip.md)
|
### [Mandatory tasks and settings required to turn on Windows Information Protection (WIP)](mandatory-settings-for-wip.md)
|
||||||
### [Testing scenarios for Windows Information Protection (WIP)](testing-scenarios-for-wip.md)
|
### [Testing scenarios for Windows Information Protection (WIP)](testing-scenarios-for-wip.md)
|
||||||
### [Limitations while using Windows Information Protection (WIP)](limitations-with-wip.md)
|
### [Limitations while using Windows Information Protection (WIP)](limitations-with-wip.md)
|
||||||
|
@ -15,6 +15,8 @@ This topic lists new and updated topics in the [Keep Windows 10 secure](index.md
|
|||||||
## January 2017
|
## January 2017
|
||||||
|New or changed topic |Description |
|
|New or changed topic |Description |
|
||||||
|---------------------|------------|
|
|---------------------|------------|
|
||||||
|
|[Determine the Enterprise Context of an app running in Windows Information Protection (WIP)](wip-app-enterprise-context.md) |New |
|
||||||
|
|[Limitations while using Windows Information Protection (WIP)](limitations-with-wip.md) |Updated to include info about USB drives and Azure RMS (Windows Insider Program only) and to add more info about Work Folders and Offline files. |
|
||||||
|[Recommended Enterprise Cloud Resources and Neutral Resources network settings with Windows Information Protection (WIP)](recommended-network-definitions-for-wip.md) |New |
|
|[Recommended Enterprise Cloud Resources and Neutral Resources network settings with Windows Information Protection (WIP)](recommended-network-definitions-for-wip.md) |New |
|
||||||
|[Using Outlook Web Access with Windows Information Protection (WIP)](using-owa-with-wip.md) |New |
|
|[Using Outlook Web Access with Windows Information Protection (WIP)](using-owa-with-wip.md) |New |
|
||||||
|
|
||||||
|
@ -17,20 +17,105 @@ author: brianlic-msft
|
|||||||
This section outlines the best countermeasures you can use to protect your organization from bootkits and rootkits, brute force sign-in, Direct Memory Access (DMA) attacks, Hyberfil.sys attacks, and memory remanence attacks.
|
This section outlines the best countermeasures you can use to protect your organization from bootkits and rootkits, brute force sign-in, Direct Memory Access (DMA) attacks, Hyberfil.sys attacks, and memory remanence attacks.
|
||||||
You can use BitLocker to protect your Windows 10 PCs. Whichever operating system you’re using, Microsoft and Windows-certified devices provide countermeasures to address attacks and improve your data security. In most cases, this protection can be implemented without the need for pre-boot authentication.
|
You can use BitLocker to protect your Windows 10 PCs. Whichever operating system you’re using, Microsoft and Windows-certified devices provide countermeasures to address attacks and improve your data security. In most cases, this protection can be implemented without the need for pre-boot authentication.
|
||||||
|
|
||||||
Figures 2, 3, and 4 summarize the recommended mitigations for different types of attacks against PCs running recent versions of Windows. The orange blocks indicate that the system requires additional configuration from the default
|
Tables 1 and 2 summarize the recommended mitigations for different types of attacks against PCs running recent versions of Windows. The orange blocks indicate that the system requires additional configuration from the default settings.
|
||||||
settings.
|
|
||||||
|
|
||||||

|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="20%" />
|
||||||
|
<col width="25%" />
|
||||||
|
<col width="55%" />
|
||||||
|
</colgroup>
|
||||||
|
<tr>
|
||||||
|
<td></td>
|
||||||
|
<td BGCOLOR="#01BCF3">
|
||||||
|
<p><font color="#FFFFFF"><strong>Windows 8.1<br>without TPM</strong></font></p></td>
|
||||||
|
<td BGCOLOR="#01BCF3">
|
||||||
|
<p><font color="#FFFFFF"><strong>Windows 8.1 Certified<br>(with TPM)</strong></font></p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td BGCOLOR="#FF8C01">
|
||||||
|
<p><font color="#FFFFFF">Bootkits and<br>Rootkits</p></font></td>
|
||||||
|
<td BGCOLOR="#FED198"><p>Without TPM, boot integrity checking is not available</p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>Secure by default when UEFI-based Secure Boot is enabled and a firmware password is required to change settings</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td BGCOLOR="FF8C01">
|
||||||
|
<p><font color="#FFFFFF">Brute Force<br>Sign-in</font></p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>Secure by default, and can be improved with account lockout Group Policy</p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>Secure by default, and can be improved with account lockout and device lockout Group Policy settings</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td BGCOLOR="#FF8C01">
|
||||||
|
<p><font color="#FFFFFF">DMA<br>Attacks</p></font></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>If policy is deployed, secure by default for all lost or stolen devices because new DMA devices are granted access only when an authorized user is signed in</p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>If policy is deployed, secure by default for all lost or stolen devices because new DMA devices are granted access only when an authorized user is signed in</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td BGCOLOR="FF8C01">
|
||||||
|
<p><font color="#FFFFFF">Hyberfil.sys<br>Attacks</font></p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>Secure by default; hyberfil.sys secured on encrypted volume</p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>Secure by default; hyberfil.sys secured on encrypted volume</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td BGCOLOR="#FF8C01">
|
||||||
|
<p><font color="#FFFFFF">Memory<br>Remanence<br>Attacks</p></font></td>
|
||||||
|
<td BGCOLOR="#FED198"><p>Password protect the firmware and disable booting from external media. If an attack is viable, consider pre-boot authentication</p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>Password protect the firmware and ensure Secure Boot is enabled. If an attack is viable, consider pre-boot authentication</p></td>
|
||||||
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
**Figure 2.** How to choose the best countermeasures for Windows 7
|
**Table 1.** How to choose the best countermeasures for Windows 8.1
|
||||||
|
|
||||||

|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="20%" />
|
||||||
|
<col width="25%" />
|
||||||
|
<col width="55%" />
|
||||||
|
</colgroup>
|
||||||
|
<tr>
|
||||||
|
<td></td>
|
||||||
|
<td BGCOLOR="#01BCF3">
|
||||||
|
<p><font color="#FFFFFF"><strong>Windows 10<br>without TPM</strong></font></p></td>
|
||||||
|
<td BGCOLOR="#01BCF3">
|
||||||
|
<p><font color="#FFFFFF"><strong>Windows 10 Certified<br>(with TPM)</strong></font></p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td BGCOLOR="#FF8C01">
|
||||||
|
<p><font color="#FFFFFF">Bootkits and<br>Rootkits</p></font></td>
|
||||||
|
<td BGCOLOR="#FED198"><p>Without TPM, boot integrity checking is not available</p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>Secure by default when UEFI-based Secure Boot is enabled and a firmware password is required to change settings</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td BGCOLOR="FF8C01">
|
||||||
|
<p><font color="#FFFFFF">Brute Force<br>Sign-in</font></p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>Secure by default, and can be improved with account lockout Group Policy</p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>Secure by default, and can be improved with account lockout and device lockout Group Policy settings</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td BGCOLOR="#FF8C01">
|
||||||
|
<p><font color="#FFFFFF">DMA<br>Attacks</p></font></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>If policy is deployed, secure by default for all lost or stolen devices because new DMA devices are granted access only when an authorized user is signed in</p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>Secure by default; certified devices do not expose vulnerable DMA busses.<br>Can be additionally secured by deploying policy to restrict DMA devices:</p>
|
||||||
|
<ul>
|
||||||
|
<li><p><a href="https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#DataProtection_AllowDirectMemoryAccess">DataProtection/AllowDirectMemoryAccess</a></p></li>
|
||||||
|
<li><p><a href="https://support.microsoft.com/en-us/kb/2516445">Block 1394 and Thunderbolt</a></p></li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td BGCOLOR="FF8C01">
|
||||||
|
<p><font color="#FFFFFF">Hyberfil.sys<br>Attacks</font></p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>Secure by default; hyberfil.sys secured on encrypted volume</p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>Secure by default; hyberfil.sys secured on encrypted volume</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td BGCOLOR="#FF8C01">
|
||||||
|
<p><font color="#FFFFFF">Memory<br>Remanence<br>Attacks</p></font></td>
|
||||||
|
<td BGCOLOR="#FED198"><p>Password protect the firmware and disable booting from external media. If an attack is viable, consider pre-boot authentication</p></td>
|
||||||
|
<td BGCOLOR="#99E4FB"><p>Password protect the firmware and ensure Secure Boot is enabled.<br>The most effective mitigation, which we advise for high-security devices, is to configure a TPM+PIN protector, disable Standby power management, and shut down or hibernate the device before it leaves the control of an authorized user.</p></td>
|
||||||
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
**Figure 3.** How to choose the best countermeasures for Windows 8
|
**Table 2.** How to choose the best countermeasures for Windows 10
|
||||||
|
|
||||||

|
|
||||||
|
|
||||||
**Figure 4.** How to choose the best countermeasures for Windows 8.1
|
|
||||||
|
|
||||||
The latest InstantGo devices, primarily tablets, are designed to be secure by default against all attacks that might compromise the BitLocker encryption key. Other Windows devices can be, too. DMA port–based attacks, which represent the attack vector of choice, are not possible on InstantGo devices, because these port types are prohibited. The inclusion of DMA ports on even non-InstantGo devices is extremely rare on recent devices, particularly on mobile ones. This could change if Thunderbolt is broadly adopted, so IT should consider this when purchasing new devices. In any case DMA ports can be disabled entirely, which is an increasingly popular option because the use of
|
The latest InstantGo devices, primarily tablets, are designed to be secure by default against all attacks that might compromise the BitLocker encryption key. Other Windows devices can be, too. DMA port–based attacks, which represent the attack vector of choice, are not possible on InstantGo devices, because these port types are prohibited. The inclusion of DMA ports on even non-InstantGo devices is extremely rare on recent devices, particularly on mobile ones. This could change if Thunderbolt is broadly adopted, so IT should consider this when purchasing new devices. In any case DMA ports can be disabled entirely, which is an increasingly popular option because the use of
|
||||||
DMA ports is infrequent in the non-developer space.
|
DMA ports is infrequent in the non-developer space.
|
||||||
|
@ -79,7 +79,8 @@ The following steps assume that you have completed all the required steps in [Be
|
|||||||
<td>Type in the name of the client property file. It must match the client property file.</td>
|
<td>Type in the name of the client property file. It must match the client property file.</td>
|
||||||
</tr>
|
</tr>
|
||||||
<td>Events URL</td>
|
<td>Events URL</td>
|
||||||
<td>Depending on the location of your datacenter, select either the EU or the US URL: </br></br> **For EU**: https://<i></i>wdatp-alertexporter-eu.securitycenter.windows.com/api/alerts </br>**For US:** https://<i></i>wdatp-alertexporter-us.securitycenter.windows.com/api/alerts</td>
|
<td>Depending on the location of your datacenter, select either the EU or the US URL: </br></br> **For EU**: https://<i></i>wdatp-alertexporter-eu.securitycenter.windows.com/api/alerts/?sinceTimeUtc=$START_AT_TIME
|
||||||
|
</br>**For US:** https://<i></i>wdatp-alertexporter-us.securitycenter.windows.com/api/alerts/?sinceTimeUtc=$START_AT_TIME</td>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Authentication Type</td>
|
<td>Authentication Type</td>
|
||||||
<td>OAuth 2</td>
|
<td>OAuth 2</td>
|
||||||
|
@ -37,14 +37,14 @@ For more information on using Windows Defender ATP CSP see, [WindowsAdvancedThre
|
|||||||
|
|
||||||
b. Select **Mobile Device Management/Microsoft Intune** > **Download package** and save the .zip file.
|
b. Select **Mobile Device Management/Microsoft Intune** > **Download package** and save the .zip file.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
2. Extract the contents of the .zip file to a shared, read-only location that can be accessed by the network administrators who will deploy the package. You should have a file named *WindowsDefenderATP.onboarding*.
|
2. Extract the contents of the .zip file to a shared, read-only location that can be accessed by the network administrators who will deploy the package. You should have a file named *WindowsDefenderATP.onboarding*.
|
||||||
|
|
||||||
3. Use the Microsoft Intune custom configuration policy to deploy the following supported OMA-URI settings. For more information on Microsoft Intune policy settings see, [Windows 10 policy settings in Microsoft Intune](https://docs.microsoft.com/en-us/intune/deploy-use/windows-10-policy-settings-in-microsoft-intune).
|
3. Use the Microsoft Intune custom configuration policy to deploy the following supported OMA-URI settings. For more information on Microsoft Intune policy settings see, [Windows 10 policy settings in Microsoft Intune](https://docs.microsoft.com/en-us/intune/deploy-use/windows-10-policy-settings-in-microsoft-intune).
|
||||||
|
|
||||||
a. Select **Policy** > **Configuration Policies** > **Add**.
|
a. Select **Policy** > **Configuration Policies** > **Add**.
|
||||||

|

|
||||||
|
|
||||||
b. Under **Windows**, select **Custom Configuration (Windows 10 Desktop and Mobile and later)** > **Create and Deploy a Custom Policy** > **Create Policy**.
|
b. Under **Windows**, select **Custom Configuration (Windows 10 Desktop and Mobile and later)** > **Create and Deploy a Custom Policy** > **Create Policy**.
|
||||||

|

|
||||||
|
@ -917,6 +917,7 @@ write-host $tmp -Foreground Red
|
|||||||
- [Isolated User Mode Processes and Features in Windows 10 with Logan Gabriel (Channel 9)](http://channel9.msdn.com/Blogs/Seth-Juarez/Isolated-User-Mode-Processes-and-Features-in-Windows-10-with-Logan-Gabriel)
|
- [Isolated User Mode Processes and Features in Windows 10 with Logan Gabriel (Channel 9)](http://channel9.msdn.com/Blogs/Seth-Juarez/Isolated-User-Mode-Processes-and-Features-in-Windows-10-with-Logan-Gabriel)
|
||||||
- [More on Processes and Features in Windows 10 Isolated User Mode with Dave Probert (Channel 9)](https://channel9.msdn.com/Blogs/Seth-Juarez/More-on-Processes-and-Features-in-Windows-10-Isolated-User-Mode-with-Dave-Probert)
|
- [More on Processes and Features in Windows 10 Isolated User Mode with Dave Probert (Channel 9)](https://channel9.msdn.com/Blogs/Seth-Juarez/More-on-Processes-and-Features-in-Windows-10-Isolated-User-Mode-with-Dave-Probert)
|
||||||
- [Mitigating Credential Theft using the Windows 10 Isolated User Mode (Channel 9)](https://channel9.msdn.com/Blogs/Seth-Juarez/Mitigating-Credential-Theft-using-the-Windows-10-Isolated-User-Mode)
|
- [Mitigating Credential Theft using the Windows 10 Isolated User Mode (Channel 9)](https://channel9.msdn.com/Blogs/Seth-Juarez/Mitigating-Credential-Theft-using-the-Windows-10-Isolated-User-Mode)
|
||||||
|
- [Protecting network passwords with Windows 10 Credential Guard](https://www.microsoft.com/itshowcase/Article/Content/831/Protecting-network-passwords-with-Windows-10-Credential-Guard)
|
||||||
- [Enabling Strict KDC Validation in Windows Kerberos](http://www.microsoft.com/download/details.aspx?id=6382)
|
- [Enabling Strict KDC Validation in Windows Kerberos](http://www.microsoft.com/download/details.aspx?id=6382)
|
||||||
- [What's New in Kerberos Authentication for Windows Server 2012](http://technet.microsoft.com/library/hh831747.aspx)
|
- [What's New in Kerberos Authentication for Windows Server 2012](http://technet.microsoft.com/library/hh831747.aspx)
|
||||||
- [Authentication Mechanism Assurance for AD DS in Windows Server 2008 R2 Step-by-Step Guide](http://technet.microsoft.com/library/dd378897.aspx)
|
- [Authentication Mechanism Assurance for AD DS in Windows Server 2008 R2 Step-by-Step Guide](http://technet.microsoft.com/library/dd378897.aspx)
|
||||||
|
@ -26,13 +26,14 @@ The credentials are put in Credential Manager as a "`*Session`" credential.
|
|||||||
A "`*Session`" credential implies that it is valid for the current user session.
|
A "`*Session`" credential implies that it is valid for the current user session.
|
||||||
The credentials are also cleaned up when the WiFi or VPN connection is disconnected.
|
The credentials are also cleaned up when the WiFi or VPN connection is disconnected.
|
||||||
|
|
||||||
When the user tries to access a domain resource, using Edge for example, Edge has the right Enterprise Authentication capability so WinInit.exe can release the credentials that it gets from the Credential Manager to the SSP that is requesting it.
|
When the user tries to access a domain resource, using Edge for example, Edge has the right Enterprise Authentication capability so [WinInet](https://msdn.microsoft.com/library/windows/desktop/aa385483.aspx) can release the credentials that it gets from the Credential Manager to the SSP that is requesting it.
|
||||||
For more information about the Enterprise Authentication capability, see [App capability declarations](https://msdn.microsoft.com/windows/uwp/packaging/app-capability-declarations).
|
For more information about the Enterprise Authentication capability, see [App capability declarations](https://msdn.microsoft.com/windows/uwp/packaging/app-capability-declarations).
|
||||||
|
|
||||||
WinInit.exe will look at the device application, such as a Universal Windows Platform (UWP) application, to see if it has the right capability.
|
The local security authority will look at the device application, such as a Universal Windows Platform (UWP) application, to see if it has the right capability.
|
||||||
If the app is not UWP, it does not matter.
|
If the app is not UWP, it does not matter.
|
||||||
But if it is a UWP app, it will look at the device capability for Enterprise Authentication.
|
But if it is a UWP app, it will look at the device capability for Enterprise Authentication.
|
||||||
If it does have that capability and if the resource that you are trying to access is in the Intranet zone in the Internet Options (ZoneMap), then the credential will be released.
|
If it does have that capability and if the resource that you are trying to access is in the Intranet zone in the Internet Options (ZoneMap), then the credential will be released.
|
||||||
|
This behavior helps prevent credentials from being misused by untrusted third parties.
|
||||||
|
|
||||||
## Intranet zone
|
## Intranet zone
|
||||||
|
|
||||||
@ -68,9 +69,26 @@ The username should also include a domain that can be reached over the connectio
|
|||||||
|
|
||||||
If the credentials are certificate-based, then the elements in the following table need to be configured for the certificate templates to ensure they can also be used for Kerberos client authentication.
|
If the credentials are certificate-based, then the elements in the following table need to be configured for the certificate templates to ensure they can also be used for Kerberos client authentication.
|
||||||
|
|
||||||
| TEmplate element | Configuration |
|
| Template element | Configuration |
|
||||||
|------------------|---------------|
|
|------------------|---------------|
|
||||||
| SubjectName | The user’s distinguished name (DN) where the domain components of the distinguished name reflects the internal DNS namespace when the SubjectAlternativeName does not have the fully qualified UPN required to find the domain controller. </br>This requirement is particularly relevant in multi-forest environments as it ensures a domain controller can be located. |
|
| SubjectName | The user’s distinguished name (DN) where the domain components of the distinguished name reflects the internal DNS namespace when the SubjectAlternativeName does not have the fully qualified UPN required to find the domain controller. </br>This requirement is particularly relevant in multi-forest environments as it ensures a domain controller can be located. |
|
||||||
| SubjectAlternativeName | The user’s fully qualified UPN where a domain name component of the user’s UPN matches the organizations internal domain’s DNS namespace.</br>This requirement is particularly relevant in multi-forest environments as it ensures a domain controller can be located when the SubjectName does not have the DN required to find the domain controller. |
|
| SubjectAlternativeName | The user’s fully qualified UPN where a domain name component of the user’s UPN matches the organizations internal domain’s DNS namespace.</br>This requirement is particularly relevant in multi-forest environments as it ensures a domain controller can be located when the SubjectName does not have the DN required to find the domain controller. |
|
||||||
| Key Storage Provider (KSP) | If the device is joined to Azure AD, a discrete SSO certificate is used. This certificate must be issued using the PassportForWork CSP. |
|
| Key Storage Provider (KSP) | If the device is joined to Azure AD, a discrete SSO certificate is used. |
|
||||||
| EnhancedKeyUsage | One or more of the following EKUs is required: </br>- Client Authentication (for the VPN) </br>- EAP Filtering OID (for PassportForWork)</br>- SmartCardLogon (for Azure AD joined devices)</br>If the domain controllers require smart card EKU either:</br>- SmartCardLogon</br>- id-pkinit-KPClientAuth (1.3.6.1.5.2.3.4)</br>Otherwise:</br>- TLS/SSL Client Authentication (1.3.6.1.5.5.7.3.2) |
|
| EnhancedKeyUsage | One or more of the following EKUs is required: </br>- Client Authentication (for the VPN) </br>- EAP Filtering OID (for Windows Hello for Business)</br>- SmartCardLogon (for Azure AD joined devices)</br>If the domain controllers require smart card EKU either:</br>- SmartCardLogon</br>- id-pkinit-KPClientAuth (1.3.6.1.5.2.3.4)</br>Otherwise:</br>- TLS/SSL Client Authentication (1.3.6.1.5.5.7.3.2) |
|
||||||
|
|
||||||
|
## NDES server configuration
|
||||||
|
|
||||||
|
The NDES server is required to be configured so that incoming SCEP requests can be mapped to the correct template to be used.
|
||||||
|
For more information, see [Configure certificate infrastructure for SCEP](https://docs.microsoft.com/en-us/intune/deploy-use/Configure-certificate-infrastructure-for-scep).
|
||||||
|
|
||||||
|
## Active Directory requirements
|
||||||
|
|
||||||
|
You need IP connectivity to a DNS server and domain controller over the network interface so that authentication can succeed as well.
|
||||||
|
|
||||||
|
The domain controllers will need to have appropriate KDC certificates for the client to trust them as domain controllers, and since phones are not domain-joined, the root CA of the KDC’s certificate must be in the Third-Party Root CA or Smart Card Trusted Roots store.
|
||||||
|
|
||||||
|
The domain controllers must be using certificates based on the updated KDC certificate template Kerberos Authentication.
|
||||||
|
This is because Windows 10 Mobile requires strict KDC validation to be enabled.
|
||||||
|
This requires that all authenticating domain controllers run Windows Server 2016, or you'll need to enable strict KDC validation on domain controllers that run previous versions of Windows Server.
|
||||||
|
For more information, see [Enabling Strict KDC Validation in Windows Kerberos](https://www.microsoft.com/download/details.aspx?id=6382).
|
||||||
|
|
||||||
|
BIN
windows/keep-secure/images/atp-add-intune-policy.png
Normal file
After Width: | Height: | Size: 66 KiB |
Before Width: | Height: | Size: 116 KiB |
BIN
windows/keep-secure/images/atp-mdm-onboarding-package.png
Normal file
After Width: | Height: | Size: 75 KiB |
BIN
windows/keep-secure/images/wip-select-column.png
Normal file
After Width: | Height: | Size: 5.7 KiB |
BIN
windows/keep-secure/images/wip-taskmgr.png
Normal file
After Width: | Height: | Size: 43 KiB |
@ -24,6 +24,7 @@ Microsoft Intune and System Center Configuration Manager helps you create and de
|
|||||||
|[Create a Windows Information Protection (WIP) policy using Microsoft Intune](create-wip-policy-using-intune.md) |Intune helps you create and deploy your WIP policy, including letting you choose your protected apps, your WIP-protection level, and how to find enterprise data on the network. |
|
|[Create a Windows Information Protection (WIP) policy using Microsoft Intune](create-wip-policy-using-intune.md) |Intune helps you create and deploy your WIP policy, including letting you choose your protected apps, your WIP-protection level, and how to find enterprise data on the network. |
|
||||||
|[Create and deploy a Windows Information Protection (WIP) policy using System Center Configuration Manager](create-wip-policy-using-sccm.md) |System Center Configuration Manager helps you create and deploy your WIP policy, including letting you choose your protected apps, your WIP-protection level, and how to find enterprise data on the network. |
|
|[Create and deploy a Windows Information Protection (WIP) policy using System Center Configuration Manager](create-wip-policy-using-sccm.md) |System Center Configuration Manager helps you create and deploy your WIP policy, including letting you choose your protected apps, your WIP-protection level, and how to find enterprise data on the network. |
|
||||||
|[Create and verify an Encrypting File System (EFS) Data Recovery Agent (DRA) certificate](create-and-verify-an-efs-dra-certificate.md) |Steps to create, verify, and perform a quick recovery using a Encrypting File System (EFS) Data Recovery Agent (DRA) certificate. |
|
|[Create and verify an Encrypting File System (EFS) Data Recovery Agent (DRA) certificate](create-and-verify-an-efs-dra-certificate.md) |Steps to create, verify, and perform a quick recovery using a Encrypting File System (EFS) Data Recovery Agent (DRA) certificate. |
|
||||||
|
|[Determine the Enterprise Context of an app running in Windows Information Protection (WIP)](wip-app-enterprise-context.md) |Use the Task Manager to determine whether an app is considered work, personal or exempt by Windows Information Protection (WIP). |
|
||||||
|
|
||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>Help to make this topic better by providing us with edits, additions, and feedback. For info about how to contribute to this topic, see [Contributing to TechNet content](https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md).
|
>Help to make this topic better by providing us with edits, additions, and feedback. For info about how to contribute to this topic, see [Contributing to TechNet content](https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md).
|
@ -93,3 +93,6 @@ Topic | Description
|
|||||||
[Troubleshoot Windows Defender Advanced Threat Protection](troubleshoot-windows-defender-advanced-threat-protection.md) | This topic contains information to help IT Pros find workarounds for the known issues and troubleshoot issues in Windows Defender ATP.
|
[Troubleshoot Windows Defender Advanced Threat Protection](troubleshoot-windows-defender-advanced-threat-protection.md) | This topic contains information to help IT Pros find workarounds for the known issues and troubleshoot issues in Windows Defender ATP.
|
||||||
[Review events and errors on endpoints with Event Viewer](event-error-codes-windows-defender-advanced-threat-protection.md)| Review events and errors associated with event IDs to determine if further troubleshooting steps are required.
|
[Review events and errors on endpoints with Event Viewer](event-error-codes-windows-defender-advanced-threat-protection.md)| Review events and errors associated with event IDs to determine if further troubleshooting steps are required.
|
||||||
[Windows Defender compatibility](defender-compatibility-windows-defender-advanced-threat-protection.md) | Learn about how Windows Defender works in conjunction with Windows Defender ATP.
|
[Windows Defender compatibility](defender-compatibility-windows-defender-advanced-threat-protection.md) | Learn about how Windows Defender works in conjunction with Windows Defender ATP.
|
||||||
|
|
||||||
|
## Related topic
|
||||||
|
[Windows Defender ATP helps detect sophisticated threats](https://www.microsoft.com/itshowcase/Article/Content/854/Windows-Defender-ATP-helps-detect-sophisticated-threats)
|
||||||
|
@ -18,7 +18,7 @@ author: jasesso
|
|||||||
Windows Defender in Windows 10 is a built-in antimalware solution that provides security and antimalware management for desktops, portable computers, and servers.
|
Windows Defender in Windows 10 is a built-in antimalware solution that provides security and antimalware management for desktops, portable computers, and servers.
|
||||||
This topic provides an overview of Windows Defender, including a list of system requirements and new features.
|
This topic provides an overview of Windows Defender, including a list of system requirements and new features.
|
||||||
|
|
||||||
For more important information about running Windows Defender on a server platform, see [Windows Defender Overview for Windows Server Technical Preview](https://technet.microsoft.com/library/dn765478.aspx).
|
For more important information about running Windows Defender on a server platform, see [Windows Defender Overview for Windows Server](https://technet.microsoft.com/windows-server-docs/security/windows-defender/windows-defender-overview-windows-server).
|
||||||
|
|
||||||
Take advantage of Windows Defender by configuring settings and definitions using the following tools:
|
Take advantage of Windows Defender by configuring settings and definitions using the following tools:
|
||||||
- Microsoft Active Directory *Group Policy* for settings
|
- Microsoft Active Directory *Group Policy* for settings
|
||||||
|
55
windows/keep-secure/wip-app-enterprise-context.md
Normal file
@ -0,0 +1,55 @@
|
|||||||
|
---
|
||||||
|
title: Determine the Enterprise Context of an app running in Windows Information Protection (WIP) (Windows 10)
|
||||||
|
description: Use the Task Manager to determine whether an app is considered work, personal or exempt by Windows Information Protection (WIP).
|
||||||
|
keywords: WIP, Windows Information Protection, EDP, Enterprise Data Protection, WIP and Task Manager, app context, enterprise context
|
||||||
|
ms.prod: w10
|
||||||
|
ms.mktglfcycl: explore
|
||||||
|
ms.sitesec: library
|
||||||
|
ms.pagetype: security
|
||||||
|
localizationpriority: high
|
||||||
|
---
|
||||||
|
|
||||||
|
# Determine the Enterprise Context of an app running in Windows Information Protection (WIP)
|
||||||
|
**Applies to:**
|
||||||
|
|
||||||
|
- Windows 10, version 1607
|
||||||
|
- Windows 10 Mobile
|
||||||
|
|
||||||
|
>Learn more about what features and functionality are supported in each Windows edition at [Compare Windows 10 Editions](https://www.microsoft.com/en-us/WindowsForBusiness/Compare).
|
||||||
|
|
||||||
|
Use Task Manager to check the context of your apps while running in Windows Information Protection (WIP) to make sure that your organization's policies are applied and running correctly.
|
||||||
|
|
||||||
|
## Viewing the Enterprise Context column in Task Manager
|
||||||
|
You need to add the Enterprise Context column to the **Details** tab of the Task Manager.
|
||||||
|
|
||||||
|
1. Make sure that you have an active WIP policy deployed and turned on in your organization.
|
||||||
|
|
||||||
|
2. Open the Task Manager (taskmgr.exe), click the **Details** tab, right-click in the column heading area, and click **Select columns**.
|
||||||
|
|
||||||
|
The **Select columns** box appears.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
3. Scroll down and check the **Enterprise Context** option, and then click **OK** to close the box.
|
||||||
|
|
||||||
|
The **Enterprise Context** column should now be available in Task Manager.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
## Review the Enterprise Context
|
||||||
|
The **Enterprise Context** column shows you what each app can do with your enterprise data:
|
||||||
|
|
||||||
|
- **Domain.** Shows the employee's work domain (such as, corp.contoso.com). This app is considered work-related and can freely touch and open work data and resources.
|
||||||
|
|
||||||
|
- **Personal.** Shows the text, *Personal*. This app is considered non-work-related and can't touch any work data or resources.
|
||||||
|
|
||||||
|
- **Exempt.** Shows the text, *Exempt*. WIP policies don't apply to these apps (such as, system components).
|
||||||
|
|
||||||
|
>[!IMPORTANT]
|
||||||
|
>Enlightened apps can change between Work and Personal, depending on the data being touched. For example, Microsoft Word 2016 shows as **Personal** when an employee opens a personal letter, but changes to **Work** when that same employee opens the company financials.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|