--- title: How to collect Windows Information Protection (WIP) audit event logs description: How to collect & understand Windows Information Protection audit event logs via the Reporting configuration service provider (CSP) or Windows Event Forwarding. author: aczechowski ms.author: aaroncz manager: aaroncz ms.topic: conceptual ms.date: 02/26/2019 ms.reviewer: --- # How to collect Windows Information Protection (WIP) audit event logs **Applies to:** - Windows 10, version 1607 and later Windows Information Protection (WIP) creates audit events in the following situations: - If an employee changes the File ownership for a file from **Work** to **Personal**. - If data is marked as **Work**, but shared to a personal app or webpage. For example, through copying and pasting, dragging and dropping, sharing a contact, uploading to a personal webpage, or if the user grants a personal app provides temporary access to a work file. - If an app has custom audit events. ## Collect WIP audit logs by using the Reporting configuration service provider (CSP) Collect the WIP audit logs from your employee's devices by following the guidance provided by the [Reporting configuration service provider (CSP)](/windows/client-management/mdm/reporting-csp) documentation. This topic provides info about the actual audit events. >[!Note] >The **Data** element in the response includes the requested audit logs in an XML-encoded format. ### User element and attributes This table includes all available attributes for the **User** element. |Attribute |Value type |Description | |----------|-----------|------------| |UserID |String |The security identifier (SID) of the user corresponding to this audit report. | |EnterpriseID |String |The enterprise ID corresponding to this audit report. | ### Log element and attributes This table includes all available attributes/elements for the **Log** element. The response can contain zero (0) or more **Log** elements. |Attribute/Element |Value type |Description | |----------|-----------|------------| |ProviderType |String |This is always **EDPAudit**. | |LogType |String |Includes:| |TimeStamp |Int |Uses the [FILETIME structure](/windows/win32/api/minwinbase/ns-minwinbase-filetime) to represent the time that the event happened. | |Policy |String |How the work data was shared to the personal location: | |Justification |String |Not implemented. This will always be either blank or NULL.

**Note**
Reserved for future use to collect the user justification for changing from **Work** to **Personal**. | |Object |String |A description of the shared work data. For example, if an employee opens a work file by using a personal app, this would be the file path. | |DataInfo |String |Any additional info about how the work file changed: | |Action |Int |Provides info about what happened when the work data was shared to personal, including: | |FilePath |String |The file path to the file specified in the audit event. For example, the location of a file that's been decrypted by an employee or uploaded to a personal website. | |SourceApplicationName |String |The source app or website. For the source app, this is the AppLocker identity. For the source website, this is the hostname. | |SourceName |String |A string provided by the app that's logging the event. It's intended to describe the source of the work data. | |DestinationEnterpriseID |String |The enterprise ID value for the app or website where the employee is sharing the data.

**NULL**, **Personal**, or **blank** means there's no enterprise ID because the work data was shared to a personal location. Because we don't currently support multiple enrollments, you'll always see one of these values. | |DestinationApplicationName |String |The destination app or website. For the destination app, this is the AppLocker identity. For the destination website, this is the hostname. | |DestinationName |String |A string provided by the app that's logging the event. It's intended to describe the destination of the work data. | |Application |String |The AppLocker identity for the app where the audit event happened. | ### Examples Here are a few examples of responses from the Reporting CSP. #### File ownership on a file is changed from work to personal ```xml 110SyncHdr200212Replace200314Get200414./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logsxml Protection removed NULL C:\Users\TestUser\Desktop\tmp\demo\Work document.docx ``` #### A work file is uploaded to a personal webpage in Edge ```xml 110SyncHdr200212Replace200314Get200414./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logsxml CopyPaste NULL NULL NULL mail.contoso.com C:\Users\TestUser\Desktop\tmp\demo\Work document.docx ``` #### Work data is pasted into a personal webpage ```xml 110SyncHdr200212Replace200314Get200414./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logsxml CopyPaste NULL O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT OFFICE 2016\WINWORD.EXE\16.0.8027.1000 NULL mail.contoso.com EnterpriseDataProtectionId|Object Descriptor|Rich Text Format|HTML Format|AnsiText|Text|EnhancedMetafile|Embed Source|Link Source|Link Source Descriptor|ObjectLink|Hyperlink ``` #### A work file is opened with a personal application ```xml 110SyncHdr200212Replace200314Get200414./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logsxml NULL C:\Users\TestUser\Desktop\tmp\demo\Work document.docx 1 O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT® WINDOWS® OPERATING SYSTEM\WORDPAD.EXE\10.0.15063.2 Personal O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT® WINDOWS® OPERATING SYSTEM\WORDPAD.EXE\10.0.15063.2 O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT® WINDOWS® OPERATING SYSTEM\WORDPAD.EXE\10.0.15063.2 ``` #### Work data is pasted into a personal application ```xml 110SyncHdr200212Replace200314Get200414./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logsxml CopyPaste NULL O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT OFFICE 2016\WINWORD.EXE\16.0.8027.1000 NULL EnterpriseDataProtectionId|Object Descriptor|Rich Text Format|HTML Format|AnsiText|Text|EnhancedMetafile|Embed Source|Link Source|Link Source Descriptor|ObjectLink|Hyperlink ``` ## Collect WIP audit logs by using Windows Event Forwarding (for Windows desktop domain-joined devices only) Use Windows Event Forwarding to collect and aggregate your Windows Information Protection audit events. You can view your audit events in the Event Viewer. **To view the WIP events in the Event Viewer** 1. Open Event Viewer. 2. In the console tree under **Application and Services Logs\Microsoft\Windows**, click **EDP-Audit-Regular** and **EDP-Audit-TCB**. ## Collect WIP audit logs using Azure Monitor You can collect audit logs using Azure Monitor. See [Windows event log data sources in Azure Monitor.]() **To view the WIP events in Azure Monitor** 1. Use an existing or create a new Log Analytics workspace. 2. In **Log Analytics** > **Advanced Settings**, select **Data**. In Windows Event Logs, add logs to receive: ```console Microsoft-Windows-EDP-Application-Learning/Admin Microsoft-Windows-EDP-Audit-TCB/Admin ``` >[!NOTE] >If using Windows Events Logs, the event log names can be found under Properties of the event in the Events folder (Application and Services Logs\Microsoft\Windows, click EDP-Audit-Regular and EDP-Audit-TCB). 3. Download Microsoft [Monitoring Agent](/azure/azure-monitor/platform/agent-windows#install-the-agent-using-dsc-in-azure-automation). 4. To get MSI for Intune installation as stated in the Azure Monitor article, extract: `MMASetup-.exe /c /t:` Install Microsoft Monitoring Agent to WIP devices using Workspace ID and Primary key. More information on Workspace ID and Primary key can be found in **Log Analytics** > **Advanced Settings**. 5. To deploy MSI via Intune, in installation parameters add: `/q /norestart NOAPM=1 ADD_OPINSIGHTS_WORKSPACE=1 OPINSIGHTS_WORKSPACE_AZURE_CLOUD_TYPE=0 OPINSIGHTS_WORKSPACE_ID= OPINSIGHTS_WORKSPACE_KEY= AcceptEndUserLicenseAgreement=1` >[!NOTE] >Replace & received from step 5. In installation parameters, don't place & in quotes ("" or ''). 6. After the agent is deployed, data will be received within approximately 10 minutes. 7. To search for logs, go to **Log Analytics workspace** > **Logs**, and type **Event** in search. ***Example*** ```console Event | where EventLog == "Microsoft-Windows-EDP-Audit-TCB/Admin" ``` ## Additional resources - [How to deploy app via Intune](/intune/apps-add) - [How to create Log workspace](/azure/azure-monitor/learn/quick-create-workspace) - [How to use Microsoft Monitoring Agents for Windows](/azure/azure-monitor/platform/agents-overview)