Skip to content

Common policies

The following DLP policies are commonly used to secure sensitive data in uploaded and downloaded files. They are built as Gateway HTTP policies using the DLP Profile selector.

Before using these policies, complete the prerequisites for scanning HTTP traffic.

Log uploads/downloads

When you want to monitor where sensitive data is going before enforcing blocks, use the Allow action. In a Gateway HTTP policy, all matches — including Allow — are recorded in your HTTP request logs. This gives you visibility into sensitive data transfers without disrupting users.

The following example logs any upload or download that matches your enabled Financial Information DLP profile entries when users interact with file sharing applications.

SelectorOperatorValueLogicAction
DLP ProfileinFinancial InformationAndAllow
Content CategoriesinFile Sharing

Block file types

Block the upload or download of files based on their type.

SelectorOperatorValueLogicAction
Upload File TypesinMicrosoft Office Word Document (docx)AndBlock
Download File TypesinPDF (pdf)

For more information on what file formats DLP can scan, refer to Supported file types.

Block uploads/downloads for specific users

You can configure access on a per-user or group basis by adding identity-based conditions to your policies. These selectors match against user attributes from your configured identity provider.

The following example blocks only contractors from uploading/downloading Financial Information to file sharing apps. Users who are not in the Contractors group are not affected by this policy.

SelectorOperatorValueLogicAction
DLP ProfileinFinancial InformationAndBlock
Content CategoriesinFile SharingAnd
User Group NamesinContractors

Exclude Android applications

Many Android applications (such as Google Drive) use certificate pinning, which is incompatible with Gateway TLS decryption. These applications verify they are connecting directly to their own servers and will reject Gateway's inspection certificate. If needed, you can create a Do Not Inspect policy so that the app can continue to function on Android:

  1. Set up an OS version device posture check that checks for the Android operating system.

  2. Create the following HTTP policy in Gateway:

    SelectorOperatorValueLogicAction
    ApplicationinGoogle DriveAndDo Not Inspect
    Passed Device Posture ChecksinOS Version Android

Android users can now use the app, but the app traffic will bypass Gateway inspection entirely — including DLP scanning, HTTP logging, and antivirus scanning.

Exclude specific sites

In your DLP logs, you may find that certain sites routinely trigger DLP detections that do not represent actual data loss (false positives). To exempt these sites from DLP scanning:

  1. Create a list of hostnames or URLs.

  2. Exclude the list from your DLP policy using the not in list operator, which references the list you created in step 1:

    SelectorOperatorValueLogicAction
    DLP ProfileinFinancial InformationAndBlock
    ApplicationinGoogle DriveAnd
    Domainnot in listDo not DLP - SSN