Collect Fortra Digital Guardian DLP (formerly Digital Guardian DLP) logs

Supported in:

This document explains how to ingest Fortra Digital Guardian DLP (formerly known as Digital Guardian DLP) logs to Google Security Operations using Bindplane.

Fortra Digital Guardian DLP is a data loss prevention platform that monitors, detects, and prevents unauthorized data transfers across endpoints, networks, and cloud applications. The platform provides visibility into sensitive data movement through policy-based controls, content inspection, and contextual classification, helping organizations protect intellectual property and comply with regulatory requirements.

Before you begin

Make sure you have the following prerequisites:

  • A Google SecOps instance.
  • A host running Windows Server 2016 or later, or a Linux host with systemd .
  • Network connectivity between the Bindplane agent and Fortra Digital Guardian DLP.
  • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements.
  • Privileged access to the Fortra Digital Guardian Management Console.

Get Google SecOps ingestion authentication file

  1. Sign in to the Google SecOps console.
  2. Go to SIEM Settings > Collection Agents.
  3. Download the Ingestion Authentication File.
  4. Save the file securely on the system where Bindplane will be installed.

Get Google SecOps customer ID

  1. Sign in to the Google SecOps console.
  2. Go to SIEM Settings > Profile.
  3. Copy and save the Customer IDfrom the Organization Detailssection.

Install the Bindplane agent

Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.

Windows installation

  1. Open Command Promptor PowerShellas an administrator.
  2. Run the following command:

      msiexec 
      
     / 
     i 
      
     "[https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi](https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi)" 
      
     / 
     quiet 
     
    
  3. Wait for the installation to complete.

  4. Verify the installation by running:

     sc query observiq-otel-collector 
    

The service should show as RUNNING.

Linux installation

  1. Open a terminal with rootor sudoprivileges.
  2. Run the following command:

     sudo  
    sh  
    -c  
     " 
     $( 
    curl  
    -fsSlL  
     [ 
    https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh ]( 
    https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh ) 
     )" 
      
    install_unix.sh 
    
  3. Wait for the installation to complete.

  4. Verify the installation by running:

     sudo  
    systemctl  
    status  
    observiq-otel-collector 
    

The service should show as active (running).

Configure the Bindplane agent to ingest syslog and send to Google SecOps

Locate the configuration file

  • Linux: sudo systemctl status observiq-otel-collector
  • Windows: C:\Program Files\observIQ OpenTelemetry Collector\config.yaml

Edit the configuration file

  • Replace the entire contents of config.yaml with the following configuration:

      receivers 
     : 
     tcplog 
     : 
      
     listen_address 
     : 
      
     "0.0.0.0:514" 
     exporters 
     : 
     chronicle/dg_dlp 
     : 
      
     compression 
     : 
      
     gzip 
      
     creds_file_path 
     : 
      
     '/path/to/ingestion-authentication-file.json' 
      
     customer_id 
     : 
      
     '<customer_id>' 
      
     endpoint 
     : 
      
     malachiteingestion-pa.googleapis.com 
      
     log_type 
     : 
      
     DIGITALGUARDIAN_DLP 
      
     raw_log_field 
     : 
      
     body 
      
     ingestion_labels 
     : 
      
     env 
     : 
      
     production 
     service 
     : 
     pipelines 
     : 
      
     logs/digitalguardian_dlp 
     : 
      
     receivers 
     : 
      
     - 
      
     tcplog 
      
     exporters 
     : 
      
     - 
      
     chronicle/dg_dlp 
     
    

Configuration parameters

Replace the following placeholders:

  • tcplog : TCP syslog receiver. TCP is recommended for Fortra Digital Guardian DLPto prevent truncation of events exceeding 1024 bytes.
  • creds_file_path : Full path to the ingestion authentication file.
  • <customer_id> : Your Customer ID from the previous step.
  • endpoint : Your regional endpoint URL (e.g., malachiteingestion-pa.googleapis.com ).

Restart the Bindplane agent to apply the changes

To restart the Bindplane agent in Linux:

  1. Run the following command:

     sudo  
    systemctl  
    restart  
    observiq-otel-collector 
    
  2. Verify the service is running:

     sudo  
    systemctl  
    status  
    observiq-otel-collector 
    
  3. Check logs for errors:

     sudo  
    journalctl  
    -u  
    observiq-otel-collector  
    -f 
    

To restart the Bindplane agent in Windows:

  1. Choose one of the following options:

    • Command Prompt or PowerShell as administrator:
     net stop observiq-otel-collector && net start observiq-otel-collector 
    
    • Services console:
      1. Press Win+R , type services.msc , and press Enter.
      2. Locate observIQ OpenTelemetry Collector.
      3. Right-click and select Restart.
  2. Verify the service is running:

     sc query observiq-otel-collector 
    
  3. Check logs for errors:

      type 
      
     "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log" 
     
    

Configure Fortra Digital Guardian syslog export

  1. Sign in to the Digital Guardian Management Console.
  2. Go to Workspace > Data Export > Create Export.
  3. Select Alertsor Eventsas the data source.
  4. Select Syslogas the Export Type.
  5. From the Typelist, select TCP.
  6. In the Serverfield, enter the IP address of the Bindplane agenthost.
  7. In the Portfield, enter 514 .
  8. Select a severity level and ensure the Is Activecheckbox is selected.
  9. Click Next.
  10. Add AllAlert and Event fields for the data export.
  11. Complete the wizard by testing the query and clicking Save.

UDM mapping table

Log Field UDM Mapping Logic
Agent Version
observer.platform_version Directly mapped.
Application
principal.process.command_line Mapped if not empty.
Command Line
target.process.command_line Directly mapped.
Company Name
principal.user.company_name Directly mapped.
Computer Name
principal.hostname Directly mapped.
DNS Hostname
target.asset.hostname Directly mapped.
Destination File Path
target.file.full_path Directly mapped.
Email Sender
network.email.from Mapped if not empty.
Email Subject
network.email.subject Mapped if Sender is not empty.
Event Time
metadata.event_timestamp Converted to timestamp format.
MAC Address
target.mac Mapped if not empty.
MD5 Hash
target.process.file.md5 Lowercased and mapped.
Network Direction
network.direction Mapped to INBOUNDor OUTBOUND.
Process Path
target.process.file.full_path Directly mapped.
SHA256 Hash
target.process.file.sha256 Lowercased and mapped.
URL Path
target.url Directly mapped.
User
principal.user.userid Directly mapped.
Was Detail Blocked
security_result.action BLOCKif Yes, ALLOWif No.
N/A
metadata.log_type Set to DIGITALGUARDIAN_DLP .
N/A
metadata.vendor_name Set to DigitalGuardian .

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

Create a Mobile Website
View Site in Mobile | Classic
Share by: