Data Loss Prevention (beta)
With Cloudflare Data Loss Prevention (DLP) and Secure Web Gateway, you can inspect HTTP traffic for the presence of sensitive data such as social security numbers and credit card numbers. DLP scans the entire HTTP body, which may include uploaded or downloaded Microsoft Office documents (Office 2007 and later), chat messages, forms, and other web content. Visibility varies depending on the site or application. DLP does not scan non-HTTP traffic such as email, nor does it scan any traffic that bypasses Cloudflare Gateway (for example, traffic that matches a rule).
To perform DLP filtering, first configure a DLP Profile with the data patterns you want to detect, and then build a Gateway HTTP policy to allow or block the sensitive data from leaving your organization. Gateway will parse and scan your HTTP traffic for strings matching the keywords or regexes specified in the DLP profile.
1. Configure a DLP Profile
- In the , go to Gateway > DLP Profiles.
- Choose a and select Configure.
- Enable one or more Detection entries according to your preferences. The DLP Profile matches using the OR logical operator — if multiple entries are enabled, your data needs to match only one of the entries.
- Select Save profile.
2. Create a DLP policy
Select Create a policy.
Policy name Only allow SSN uploads to Workday Selector Operator Value DLP Profiles in
U.S. Social Security Numbers
Application not in
Select Create policy.
DLP scanning is now enabled.
3. View DLP logs
- In the , go to Settings > Network.
- Verify that Activity logging is turned on, and check that Gateway HTTP logs is set to capture traffic.
- Next, go to Logs > Gateway > HTTP.
- Select Filter.
- Choose an item under one of the following filters:
- DLP Profiles - shows the requests which matched a specific DLP profile.
- Policy - shows the requests which matched a specific DLP policy.
You can expand an individual row to view details about the request.
Policy configuration tips
If you configured a DLP policy with a Block action, false positives may cause some pages to not load properly. Adding additional conditions to your policy will limit the scope of the DLP scan and can help reduce false positives.
play.google.com is a common source of noise in the DLP logs. These detections clutter your logs with junk data and could cause issues for the end user if they are blocked. To exempt these sites from DLP scanning, you can manually create a of hostnames or URLs. Then, exclude the list from your DLP policy as shown in the example below:
|Block SSN uploads to file sharing apps|
|Domain||not in list|