Merged PR 7806: WIP Learning
New for WIP Learning
@ -51,4 +51,5 @@
|
|||||||
#### [Unenlightened and enlightened app behavior while using Windows Information Protection (WIP)](windows-information-protection\app-behavior-with-wip.md)
|
#### [Unenlightened and enlightened app behavior while using Windows Information Protection (WIP)](windows-information-protection\app-behavior-with-wip.md)
|
||||||
#### [Recommended Enterprise Cloud Resources and Neutral Resources network settings with Windows Information Protection (WIP)](windows-information-protection\recommended-network-definitions-for-wip.md)
|
#### [Recommended Enterprise Cloud Resources and Neutral Resources network settings with Windows Information Protection (WIP)](windows-information-protection\recommended-network-definitions-for-wip.md)
|
||||||
#### [Using Outlook Web Access with Windows Information Protection (WIP)](windows-information-protection\using-owa-with-wip.md)
|
#### [Using Outlook Web Access with Windows Information Protection (WIP)](windows-information-protection\using-owa-with-wip.md)
|
||||||
|
### [Fine-tune Windows Information Protection (WIP) with WIP Learning](windows-information-protection\wip-learning.md)
|
||||||
|
|
||||||
|
@ -256,6 +256,7 @@ Where the text, `O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US` is the
|
|||||||
For this example, we’re going to add an AppLocker XML file to the **Allowed apps** list. You’ll use this option if you want to add multiple apps at the same time. For more info about AppLocker, see the [AppLocker](https://technet.microsoft.com/itpro/windows/keep-secure/applocker-overview) content.
|
For this example, we’re going to add an AppLocker XML file to the **Allowed apps** list. You’ll use this option if you want to add multiple apps at the same time. For more info about AppLocker, see the [AppLocker](https://technet.microsoft.com/itpro/windows/keep-secure/applocker-overview) content.
|
||||||
|
|
||||||
**To create a list of Allowed apps using the AppLocker tool**
|
**To create a list of Allowed apps using the AppLocker tool**
|
||||||
|
|
||||||
1. Open the Local Security Policy snap-in (SecPol.msc).
|
1. Open the Local Security Policy snap-in (SecPol.msc).
|
||||||
|
|
||||||
2. In the left blade, expand **Application Control Policies**, expand **AppLocker**, and then click **Packaged App Rules**.
|
2. In the left blade, expand **Application Control Policies**, expand **AppLocker**, and then click **Packaged App Rules**.
|
||||||
|
After Width: | Height: | Size: 215 KiB |
After Width: | Height: | Size: 103 KiB |
After Width: | Height: | Size: 510 KiB |
After Width: | Height: | Size: 406 KiB |
After Width: | Height: | Size: 127 KiB |
After Width: | Height: | Size: 326 KiB |
After Width: | Height: | Size: 256 KiB |
After Width: | Height: | Size: 250 KiB |
After Width: | Height: | Size: 105 KiB |
@ -7,7 +7,7 @@ ms.prod: w10
|
|||||||
ms.mktglfcycl: explore
|
ms.mktglfcycl: explore
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.pagetype: security
|
ms.pagetype: security
|
||||||
author: eross-msft
|
author: coreyp-at-msft
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.date: 09/11/2017
|
ms.date: 09/11/2017
|
||||||
---
|
---
|
||||||
@ -120,7 +120,7 @@ WIP currently addresses these enterprise scenarios:
|
|||||||
|
|
||||||
- Your employees won't have their work otherwise interrupted while switching between personal and enterprise apps while the enterprise policies are in place. Switching environments or signing in multiple times isn’t required.
|
- Your employees won't have their work otherwise interrupted while switching between personal and enterprise apps while the enterprise policies are in place. Switching environments or signing in multiple times isn’t required.
|
||||||
|
|
||||||
### WIP-protection modes
|
### <a href="" id="bkmk-modes"></a>WIP-protection modes
|
||||||
Enterprise data is automatically encrypted after it’s loaded on a device from an enterprise source or if an employee marks the data as corporate. Then, when the enterprise data is written to disk, WIP uses the Windows-provided Encrypting File System (EFS) to protect it and associate it with your enterprise identity.
|
Enterprise data is automatically encrypted after it’s loaded on a device from an enterprise source or if an employee marks the data as corporate. Then, when the enterprise data is written to disk, WIP uses the Windows-provided Encrypting File System (EFS) to protect it and associate it with your enterprise identity.
|
||||||
|
|
||||||
Your WIP policy includes a list of trusted apps that are allowed to access and process corporate data. This list of apps is implemented through the [AppLocker](/windows/device-security/applocker/applocker-overview) functionality, controlling what apps are allowed to run and letting the Windows operating system know that the apps can edit corporate data. Apps included on this list don’t have to be modified to open corporate data because their presence on the list allows Windows to determine whether to grant them access. However, new for Windows 10, app developers can use a new set of application programming interfaces (APIs) to create *enlightened* apps that can use and edit both enterprise and personal data. A huge benefit to working with enlightened apps is that dual-use apps, like Microsoft Word, can be used with less concern about encrypting personal data by mistake because the APIs allow the app to determine whether data is owned by the enterprise or if it’s personally owned.
|
Your WIP policy includes a list of trusted apps that are allowed to access and process corporate data. This list of apps is implemented through the [AppLocker](/windows/device-security/applocker/applocker-overview) functionality, controlling what apps are allowed to run and letting the Windows operating system know that the apps can edit corporate data. Apps included on this list don’t have to be modified to open corporate data because their presence on the list allows Windows to determine whether to grant them access. However, new for Windows 10, app developers can use a new set of application programming interfaces (APIs) to create *enlightened* apps that can use and edit both enterprise and personal data. A huge benefit to working with enlightened apps is that dual-use apps, like Microsoft Word, can be used with less concern about encrypting personal data by mistake because the APIs allow the app to determine whether data is owned by the enterprise or if it’s personally owned.
|
||||||
|
@ -0,0 +1,101 @@
|
|||||||
|
---
|
||||||
|
title:
|
||||||
|
# Fine-tune Windows Information Policy (WIP) with WIP Learning
|
||||||
|
description: How to access the WIP Learning report to monitor and apply Windows Information Protection in your company.
|
||||||
|
ms.assetid: 53db29d2-d99d-4db6-b494-90e2b4872ca2
|
||||||
|
keywords: WIP, Windows Information Protection, EDP, Enterprise Data Protection, WIP Learning
|
||||||
|
ms.prod: w10
|
||||||
|
ms.mktglfcycl:
|
||||||
|
ms.sitesec: library
|
||||||
|
ms.pagetype: security
|
||||||
|
author: coreyp-at-msft
|
||||||
|
ms.localizationpriority: medium
|
||||||
|
ms.date: 04/18/2018
|
||||||
|
---
|
||||||
|
|
||||||
|
# Fine-tune Windows Information Protection (WIP) with WIP Learning
|
||||||
|
**Applies to:**
|
||||||
|
|
||||||
|
- Windows 10, version 1703 and later
|
||||||
|
- Windows 10 Mobile, version 1703 and later
|
||||||
|
|
||||||
|
With WIP Learning, you can intelligently tune which apps and websites are included in your WIP policy to help reduce disruptive prompts and keep it accurate and relevant. WIP Learning generates two reports: The **App learning report** and the **Website learning report**. Both reports are accessed from Microsoft Azure Intune, and you can alternately access the App learning report from Microsoft Operations Management Suite (OMS).
|
||||||
|
|
||||||
|
The **App learning report** monitors your apps, not in policy, that attempt to access work data. You can identify these apps using the report and add them to your WIP policies to avoid productivity disruption before fully enforcing WIP with [“Hide overrides”](protect-enterprise-data-using-wip.md#bkmk-modes) mode. Frequent monitoring of the report will help you continuously identify access attempts so you can update your policy accordingly.
|
||||||
|
|
||||||
|
In the **Website learning report**, you can view a summary of the devices that have shared work data with websites. You can use this information to determine which websites should be added to group and user WIP policies. The summary shows which website URLs are accessed by WIP-enabled apps so you can decide which ones are cloud or personal, and add them to the resource list.
|
||||||
|
|
||||||
|
## Access the WIP Learning reports
|
||||||
|
|
||||||
|
1. Open the [Azure portal](http://https://portal.azure.com/). Choose **All services**. Type **Intune** in the text box filter.
|
||||||
|
|
||||||
|
2. Choose **Intune** > **Mobile Apps**.
|
||||||
|
|
||||||
|
3. Choose **App protection status**.
|
||||||
|
|
||||||
|
4. Choose **Reports**.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
5. Finally, select either **App learning report for Windows Information Protection**, or **Website learning report for Windows Information Protection**.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
Once you have the apps and websites showing up in the WIP Learning logging reports, you can decide whether to add them to your app protection policies. Next, we'll look at how to do that in Operations Management Suite (OMS).
|
||||||
|
|
||||||
|
## View the WIP app learning report in Microsoft Operations Management Suite
|
||||||
|
|
||||||
|
From Intune, you can open OMS by choosing **WIP in the OMS console**. Then you can view the WIP App learning blade to monitor access events per app, and devices that have reported WIP access events:
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
If you don't have OMS linked to your Microsoft Azure Account, and want to configure your environment for Windows Analytics: Device Health, see [Get Started with Device Health](https://docs.microsoft.com/windows/deployment/update/device-health-get-started) for more information.
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>Intune has a 14 day data retention capacity, while OMS offers better querying capabilities and longer data retention.
|
||||||
|
|
||||||
|
Once you have WIP policies in place, by using the WIP section of Device Health, you can:
|
||||||
|
|
||||||
|
- Reduce disruptive prompts by adding rules to allow data sharing from approved apps.
|
||||||
|
- Tune WIP rules by confirming that certain apps are allowed or denied by current policy.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
The **APP LEARNING** tile shows details of app statistics that you can use to evaluate each incident and update app policies by using WIP AppIDs.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
In this chart view, you can see apps that have been used on connected devices which, when clicked on, will open additional details on the app, including details you need to adjust your WIP Policy:
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
Here, you can copy the **WipAppid** and use it to adjust your WIP protection policies.
|
||||||
|
|
||||||
|
## Use OMS and Intune to adjust WIP protection policy
|
||||||
|
|
||||||
|
1. Click the **APP LEARNING** tile in OMS, as described above, to determine which apps are being used for work so you can add those you choose to your WIP policy.
|
||||||
|
|
||||||
|
2. Click the app you want to add to your policy and copy the publisher information from the app details screen.
|
||||||
|
|
||||||
|
3. Back in Intune, click **App protection policies** and then choose the app policy you want to add an application to.
|
||||||
|
|
||||||
|
4. Click **Protected apps**, and then click **Add Apps**.
|
||||||
|
|
||||||
|
5. In the **Recommended apps** drop down menu, choose either **Store apps** or **Desktop apps**, depending on the app you've chosen (for example, an executable (EXE) is a desktop app).
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
6. In **NAME** (optional), type the name of the app, and then in **PUBLISHER** (required), paste the publisher information that you copied in step 2 above.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
7. Type the name of the product in **PRODUCT NAME** (required) (this will probably be the same as what you typed for **NAME**).
|
||||||
|
|
||||||
|
8. Back in OMS, copy the name of the executable (for example, snippingtool.exe) and then go back to Intune and paste it in **FILE** (required).
|
||||||
|
|
||||||
|
9. Go back to OMS one more time and note the version number of the app and type it in **MIN VERSION** in Intune (alternately, you can specify the max version, but one or the other is required), and then select the **ACTION**: **Allow** or **Deny**
|
||||||
|
|
||||||
|
When working with WIP-enabled apps and WIP-unknown apps, it is recommended that you start with **Silent** or **Allow overrides** while verifying with a small group that you have the right apps on your allowed apps list. After you're done, you can change to your final enforcement policy, **Hide overrides**. For more information about WIP modes, see: [Protect enterprise data using WIP: WIP-modes](protect-enterprise-data-using-wip.md#bkmk-modes)
|
||||||
|
|
||||||
|
>[!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).
|