Collect Zscaler Email DLP logs

This document describes how you can export Zscaler Email DLP logs by setting up a Google Security Operations feed and how log fields map to Google SecOps Unified Data Model (UDM) fields.

For more information, see Data ingestion to Google SecOps overview .

A typical deployment consists of Zscaler Email DLP and the Google SecOps Webhook feed configured to send logs to Google SecOps. Each customer deployment can differ and might be more complex.

The deployment contains the following components:

• Zscaler Email DLP: The platform from which you collect logs.

• Google SecOps feed: The Google SecOps feed that fetches logs from Zscaler Email DLP and writes logs to Google SecOps.

• Google SecOps: Retains and analyzes the logs.

An ingestion label identifies the parser which normalizes raw log data to structured UDM format. The information in this document applies to the parser with the ZSCALER_EMAIL_DLP ingestion label.

Before you begin

Ensure you have the following prerequisites:

• Access to Zscaler Internet Access console. For more information, see Secure Internet and SaaS Access ZIA Help .
• Zscaler Email DLP 2026 or later
• All systems in the deployment architecture are configured with the UTC time zone.
• The API key which is needed to complete feed setup in Google Security Operations. For more information, see Setting up API keys .

Set up feeds

There are two different entry points to set up feeds in the Google SecOps platform:

• SIEM Settings > Feeds
• Content Hub > Content Packs

Set up feeds from SIEM Settings > Feeds

To configure multiple feeds for different log types within this product family, see Configure feeds by product .

To configure a single feed, follow these steps:

1. Go to SIEM Settings > Feeds.
2. Click Add New Feed.
3. On the next page, click Configure a single feed.
4. In the Feed namefield, enter a name for the feed; for example, Zscaler Email DLP Logs.
5. Select Webhookas the Source Type.
6. Select Zscaler Email DLPas the Log Type.
7. Click Next.
8. Optional: Enter values for the following input parameters:
   1. Split delimiter: The delimiter that is used to separate the logs lines. Leave blank if a delimiter is not used.
   2. Asset namespace: The asset namespace.
   3. Ingestion labels: The label to be applied to the events from this feed.
9. Click Next.
10. Review your new feed configuration, and then click Submit.
11. Click Generate Secret Keyto generate a secret key to authenticate this feed.

Set up feeds from the Content Hub

Specify values for the following fields:

• Split delimiter: The delimiter that is used to separate log lines, such as \n .

Advanced options

• Feed Name: A prepopulated value that identifies the feed.
• Source Type: Method used to collect logs into Google SecOps.
• Asset namespace: The asset namespace .
• Ingestion labels: The label applied to the events from this feed.
• Click Next.
• Review the feed configuration in the Finalizescreen, and then click Submit.
• Click Generate Secret Keyto generate a secret key to authenticate this feed.

Set up Zscaler Email DLP

1. In the Zscaler Internet Access console, click Administration > Nanolog Streaming Service > Cloud NSS Feedsand then click Add Cloud NSS Feed.
2. The Add Cloud NSS Feedwindow appears. In the Add Cloud NSS Feedwindow, enter the details.
3. Enter a name for the feed in the Feed Namefield.
4. Select NSS for Webin NSS Type.
5. Select the status from the Statuslist to activate or deactivate the NSS feed.
6. Keep the value in the SIEM Ratedrop-down as Unlimited. To suppress the output stream due to licensing or other constraints, change the value.
7. Select Otherin the SIEM Typelist.
8. Select Disabledin the OAuth 2.0 Authenticationlist.
9. Enter a size limit for an individual HTTP request payload in Max Batch Size. Configure this value to 512 KB, as this is the recommended best practice for optimal SIEM ingestion. (Note: Lower batch sizes can sometimes reduce latency at the cost of more frequent HTTP requests).

10. Enter the HTTPS URL of the Chronicle API endpoint in the API URL in the following format:

     https://<CHRONICLE_REGION>-chronicle.googleapis.com/v1alpha/projects/<GOOGLE_PROJECT_NUMBER>/locations/<LOCATION>/instances/<CUSTOMER_ID>/feeds/<FEED_ID>:importPushLogs 
    

    • CHRONICLE_REGION : Region where your Chronicle instance is hosted. For example, US.
    • GOOGLE_PROJECT_NUMBER : BYOP project number. Obtain this from C4.
    • LOCATION : Chronicle region. For example, US.
    • CUSTOMER_ID : Chronicle customer ID. Obtain from C4.
    • FEED_ID : Feed ID shown on Feed UI on the new webhook created
    • Sample API URL:

     https://us-chronicle.googleapis.com/v1alpha/projects/12345678910/locations/US/instances/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/feeds/yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy:importPushLogs 
    

11. Click Add HTTP Header, and then add HTTP headers in the following format:

    • Header 1 : Key1: X-goog-api-key and Value1:API Key generated on Google Cloud BYOP's API Credentials.
    • Header 2 : Key2: X-Webhook-Access-Key and Value2:API secret key generated on webhook's "SECRET KEY".

12. Select Email DLPin the Log Typeslist.

13. Select JSONin the Feed Output Typelist.

14. Disable JSON Array Notation.

15. Set Feed Escape Characterto , \ " .

16. To add a new field to the Feed Output Format,select Customin the Feed Output Typelist.

17. Copy-paste the Feed Output Formatand add new fields. Ensure the key names match the actual field names.

18. Following is the default Feed Output Format:

       
     \ 
     { 
     "sourcetype" 
     : 
      
     "zscalernss-emaildlp" 
     , 
      
     "event" 
     : 
      
     \ 
     { 
     "mailsenttime" 
     : 
      
     "%s{mail_sent_time}" 
     , 
      
     "scantime" 
     : 
      
     "%u{scan_time}" 
     , 
      
     "recordid" 
     : 
      
     "%llu{recordid}" 
     , 
      
     "company" 
     : 
      
     "%s{company}" 
     , 
      
     "tenant" 
     : 
      
     "%s{tenant}" 
     , 
      
     "user" 
     : 
      
     "%s{username}" 
     , 
      
     "dept" 
     : 
      
     "%s{departmentname}" 
     , 
      
     "filenames" 
     : 
      
     "%s{ac_names}" 
     , 
      
     "filemd5s" 
     : 
      
     "%s{ac_md5s}" 
     , 
      
     "doctypes" 
     : 
      
     "%s{ac_doctypes}" 
     , 
      
     "filesizes" 
     : 
      
     "%s{ac_sizes}" 
     , 
      
     "filetypes" 
     : 
      
     "%s{ac_filetypes}" 
     , 
      
     "dlpdictnames" 
     : 
      
     "%s{dlpdictnames}" 
     , 
      
     "dlpdictcnts" 
     : 
      
     "%s{dlpdictcnts}" 
     , 
      
     "dlpengnames" 
     : 
      
     "%s{dlpengnames}" 
     , 
      
     "dlpidentifier" 
     : 
      
     "%llu{dlpidentifier}" 
     , 
      
     "triggeredrcpts" 
     : 
      
     "%s{trigg_rcpts}" 
     , 
      
     "severity" 
     : 
      
     "%s{severity}" 
     , 
      
     "action" 
     : 
      
     "%s{action}" 
     , 
      
     "rulename" 
     : 
      
     "%s{rulelabels}" 
     , 
      
     "otherrcpts" 
     : 
      
     "%s{other_rcpts}" 
     , 
      
     "subject" 
     : 
      
     "%s{subject}" 
     , 
      
     "msgid" 
     : 
      
     "%s{msgid}" 
     \ 
     } 
     \ 
     } 
     
    

19. Select the timezone for the Timefield in the output file in the Timezonelist. By default, the timezone is set to your organization's time zone.

20. Review the configured settings.

21. Click Saveto test connectivity. If the connection is successful, a green tick accompanied by the message Test Connectivity Successful: OK (200)appears.

For more information about Google SecOps feeds, see Google SecOps feeds documentation . For information about requirements for each feed type, see Feed configuration by type .

If you encounter issues when you create feeds, contact Google SecOps support .

Supported Zscaler Email DLP log formats

The Zscaler Email DLP parser supports logs in JSON format.

Supported Zscaler Email DLP Sample Logs

• JSON

   {
      "sourcetype": "zscalernss-emaildlp",
      "event": {
          "mailsenttime": "Wed Feb 4 04:11:09 2026",
          "scantime": "25",
          "recordid": "7602857773514883073",
          "company": "Sample Company",
          "tenant": "sample.com",
          "user": "dummyuser@sample.com",
          "dept": "Default Department",
          "filenames": "test.xlsx",
          "filemd5s": "0d67b8287a735240724384f293ee364f",
          "doctypes": "None",
          "filesizes": "8824",
          "filetypes": "xlsx",
          "dlpdictnames": "Credit Cards: Detect leakage of credit card information",
          "dlpdictcnts": "10",
          "dlpengnames": "",
          "dlpidentifier": "7602857773514883076",
          "triggeredrcpts": "test2@sample.com",
          "severity": "High Severity",
          "action": "Block",
          "rulename": "DLP_Rule_7",
          "otherrcpts": "None",
          "subject": "Test Subject",
          "msgid": "863fcac3-4040-495f-9ec6-b41abd054ca7@sample.com"
      }
  } 
  

Field mapping reference

The following table lists common fields of the ZSCALER_EMAIL_DLP log type and their corresponding UDM fields.

Need more help? Get answers from Community members and Google SecOps professionals.