Prepare Endpoint DLP
Endpoint data loss prevention (Endpoint DLP) extends the activity monitoring and protection capabilities of DLP to sensitive items on Windows devices. Once devices are onboarded into the Microsoft Purview compliance portal, the information about what activities (like copying to USB devices or printing) users perform on sensitive items is visible to those who have access to activity explorer in the Microsoft Purview compliance portal. You can also take the extra step of auditing or restricting those activities via data loss prevention policies.
This unit walks you through the additional steps required to use Endpoint DLP:
- Confirm your devices meet requirements
- Onboard devices
- Configure global Endpoint DLP settings
Confirm devices meet requirements
Windows devices that you plan on monitoring with Endpoint DLP must meet the system requirements. Review the requirements before you onboard devices.
Before you can include Windows devices in DLP policies, you need to onboard them, or enable data collection.
To enable data collection from a device, the account onboarding the device must be a member of any of these roles:
- Global admin
- Security admin
- Compliance admin
Use the following steps to add an account to a role:
- In the Microsoft 365 admin center, select Roles.
- In the Azure AD tab, select Show all roles.
- Select one of the roles and add the user account.
Give users only the access they need by assigning the least-permissive role.
Onboarding and offboarding are handled via scripts you download from the Device onboarding center. The center has custom scripts for each of these deployment methods:
- Local script (up to 10 machines)
- Group policy
- Microsoft Endpoint Configuration Manager
- Mobile Device Management/Microsoft Intune
- VDI onboarding scripts for non-persistent machines
In the Microsoft Purview compliance portal, select Settings, then select Device Onboarding to view a list of monitored devices and download the packages used to onboard or offboard devices using your preferred deployment method.
Onboarding using local script
We'll use the Local script (for up to 10 machines) script to onboard devices. The local script is meant for testing purposes - you can see how Endpoint DLP will affect your devices and environments before you roll it out in your production environment.
Here are the instructions for onboarding a Windows device using a local script.
- On the Device onboarding page in the compliance portal, select Onboarding.
- Select Local script (for up to 10 machines) under Deployment method.
- Select Download package, and then save the DeviceComplianceOnboardingPackage.zip file.
- Extract the DeviceComplianceOnboardingPackage.zip file to a location accessible from the device you want to onboard, like a network share or the local device's Desktop. (You may need to bypass any messages or errors stating that downloading the file may harm your device and is not safe.)
- In the Windows Explorer or wherever you extracted the files, right-click DeviceComplianceLocalOnboardingScript.cmd, then select Run as Administrator.
- If a User Account Control window appears, select Yes.
- Follow the prompts on the screen to onboard the device.
Configure global Endpoint DLP settings
Global Endpoint DLP settings apply to all existing and new DLP policies that protect content on Windows devices. But these settings only apply to content impacted by DLP policies, not every item in, for example, the user's Documents folder.
In the Microsoft Purview compliance portal left menu, go to Data loss prevention > Endpoint DLP settings to configure global settings.
Here are the settings available to you:
File path exclusions: Exclude specific paths from DLP monitoring, alerting, and policy enforcement. Use the setting for file paths that are too active or that don't contain files you want to protect. You can use wildcards, system variables, and other options to refine which file paths you include or exclude. You can see in the following image an exclusion for the
C:\Tempfolder and all subfolders. All other folders on the device will be monitored.
Unallowed apps: Prevent specific applications from accessing files protected by your policies. You can use the Access by unallowed apps setting to define what happens when one of your users tries to access protected data by using one of the specified apps. You can choose to allow the activity, allow but audit, block, or block the activity but let the user override the restriction. In this example, we've blocked Microsoft WordPad from opening any file that is protected by DLP policy. Other apps, like Microsoft Word, can open the same file.
The following image shows a notification a user will see when they try to access the data with WordPad. The app isn't entirely blocked, so the user can select Allow to override the policy.
Unallowed browsers: Prevent browsers from accessing files protected by your policies. When you configure this setting, users will be prompted to access protected files using Microsoft Edge. You can block any of the 10 browsers included in the policy, or you can add your own. Although you can block a single browser, consider blocking all web browsers that do not respect Endpoint DLP policies.
The image below shows the notification the user will receive if they try to upload protected content using a blocked browser. Notice the suggestion to access the file using Microsoft Edge.
Service domain restrictions: Even if you've prevented all unsupported browsers from accessing sensitive data, sometimes you might also want to block supported browsers, like Microsoft Edge, from uploading protected content to specific web services. Service domain restrictions control whether sensitive files protected by your policies are allowed or blocked from accessing specific service domains from Microsoft Edge. Choose Block to prevent certain domains from accessing these files or Allow to specify safe domains. For example, the setting in the image below blocks users from uploading protected content to Dropbox even when using Microsoft Edge.
This is the notification that a user gets when they try to upload protected content into Dropbox. Notice that the user can override the restriction because the policy was configured with the option to allow override. The policy could as easily have been configured to prevent it from being overridden.
Unless you've added other browsers to the Unallowed browsers list, user can still upload the protected content by using a different browser. Be sure to add the other browsers in use in your organization to the unallowed browsers list if you want service domain restrictions to work correctly.