Collect Endpoint Protector DLP logs

Parser Version: 2.0

Supported in:

Google SecOps SIEM

This document explains how to ingest Netwrix Endpoint Protector DLP logs to Google Security Operations using the Bindplane agent.

Netwrix Endpoint Protector is a Data Loss Prevention (DLP) solution that generates syslog messages for device control, content-aware protection, and file transfer events. The parser extracts fields using grok patterns and maps them to the Unified Data Model (UDM).

Before you begin

Make sure you have the following prerequisites:

• A Google SecOps instance
• Windows Server 2016 or later, or Linux host with systemd
• Network connectivity between the Bindplane agent and the Endpoint Protector server
• If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
• Privileged access to Netwrix Endpoint Protector

Get Google SecOps credentials for the Bindplane agent

To authenticate the Bindplane agent to Google SecOps, choose one of the following methods:

• New deployments: Use the Chronicle API (Option 1).
• Legacy deployments: Continue using the ingestion authentication file (Option 2) until the Ingestion API is discontinued on July 20, 2027.

Option 1: Create a service account for the Chronicle API (recommended)

1. Sign in to the Google Cloud console and select the Google Cloud project that is linked to your Google SecOps instance.
2. Go to IAM & Admin > Service Accounts.
3. Click Create service account.
4. Provide the following configuration details:
   • Service account name: Enter a name for the account (for example, bindplane-ingest).
   • Service account description: Enter a description (for example, Bindplane agent log ingestion).
5. Click Create and continue.
6. In the Grant this service account access to project section, click Select a role and select Chronicle Editor.
7. Click Continue, and then click Done.
8. Click the service account you created, and then go to the Keys tab.
9. Click Add key > Create new key.
10. Select JSON and click Create. The key file is downloaded to your computer.
11. Save the key file as ingestion-auth.json in the Bindplane collector directory (/opt/observiq-otel-collector/ingestion-auth.json on Linux or C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json on Windows), or update creds_file_path in config.yaml to match the path where you save it.
12. Go to IAM & Admin > Settings and copy the Project number. You'll need it for the exporter configuration.

Note: The JSON key is a credential. Restrict access to the file on the Bindplane host and rotate the key according to your organization's policy.

Option 2: Download the ingestion authentication file (legacy)

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 the Bindplane agent will be installed.

Note: This file authenticates the agent to the legacy Ingestion API (malachiteingestion-pa.googleapis.com), which Google has scheduled for end of life on July 20, 2027. Plan to move to Option 1 before that date.

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 ID from the Organization Details section.

   Note: The customer ID is required for configuring the Bindplane agent exporter.

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 Prompt or PowerShell as an administrator.

2. Run the following command:

   msiexec /i "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 root or sudo privileges.

2. Run the following command:

   sudo sh -c "$(curl -fsSlL 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).

Additional installation resources

For additional installation options and troubleshooting, see the Bindplane agent installation guide.

Note: The Chronicle API exporter configuration requires Bindplane collector v1.106.0 or later. The previous commands install the latest release. If you're updating an existing installation, upgrade the collector before changing the configuration.

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

Locate the configuration file

• Linux:

  sudo nano /opt/observiq-otel-collector/config.yaml
  

• Windows:

  notepad "C:\Program Files\observIQ OpenTelemetry Collector\config.yaml"
  

Edit the configuration file

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

  receivers:
    udplog:
      listen_address: "0.0.0.0:514"
  
  exporters:
    chronicle/endpoint_protector_dlp:
      protocol: https
      # Region of your instance, for example us, europe, asia-southeast1
      location: <LOCATION>
      # Project number of the Google Cloud project linked to the instance
      project: '<PROJECT_NUMBER>'
      compression: gzip
      creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
      customer_id: '<customer_id>'
      endpoint: chronicle.googleapis.com
      log_type: ENDPOINT_PROTECTOR_DLP
      raw_log_field: body
  
  service:
    pipelines:
      logs/endpoint_protector_dlp_to_chronicle:
        receivers:
          - udplog
        exporters:
          - chronicle/endpoint_protector_dlp
  

Configuration parameters

Replace the following placeholders:

• Receiver configuration:

  • listen_address: IP address and port to listen on:
    • 0.0.0.0 to listen on all interfaces (recommended)
    • Port 514 is the standard syslog port (requires root on Linux; use 1514 for non-root)

• Exporter configuration:

  • creds_file_path: Full path to the service account JSON key file (Option 1):
    • Linux: /opt/observiq-otel-collector/ingestion-auth.json
    • Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
  • customer_id: Customer ID copied from the Google SecOps console
  • location: Replace <LOCATION> with the region of your Google SecOps instance (for example, us, europe, or asia-southeast1). The exporter prefixes chronicle.googleapis.com with this value. See Regional Endpoints for the complete list.
  • project: Replace <PROJECT_NUMBER> with the project number from IAM & Admin > Settings.
  • endpoint: Keep set to chronicle.googleapis.com.

Legacy ingestion API exporter

• If you use the ingestion authentication file from Option 2, replace the exporters block with the following. Set creds_file_path to the path to the ingestion authentication file, and if your instance is outside the US, replace malachiteingestion-pa.googleapis.com with your regional endpoint (for example, europe-malachiteingestion-pa.googleapis.com).

  exporters:
    chronicle/endpoint_protector_dlp:
      compression: gzip
      creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
      customer_id: '<customer_id>'
      endpoint: malachiteingestion-pa.googleapis.com
      log_type: ENDPOINT_PROTECTOR_DLP
      raw_log_field: body
  

Note: This exporter will stop working when the Ingestion API is discontinued on July 20, 2027.

Save the configuration file

• After editing, save the file:
  • Linux: Press Ctrl+O, then Enter, then Ctrl+X
  • Windows: Click File > Save

Restart the Bindplane agent to apply the changes

• To restart the Bindplane agent in Linux, run the following command:

  sudo systemctl restart observiq-otel-collector
  

  1. Verify the service is running:

     sudo systemctl status observiq-otel-collector
     

  2. Check logs for errors:

     sudo journalctl -u observiq-otel-collector -f
     

• To restart the Bindplane agent in Windows, 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.

    4. Verify the service is running:

       sc query observiq-otel-collector
       

    5. Check logs for errors:

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

Configure syslog on Netwrix Endpoint Protector

1. Sign in to the Endpoint Protector web UI.
2. Go to Appliance > SIEM Integration.
3. Click Add New.
4. Provide the following configuration details:
   • SIEM Status: Toggle switch to enable the SIEM server.
   • Disable Logging: Toggle switch to enable logging.
   • Server Name: Enter a unique and meaningful server name.
   • Server Description: Add a description for this integration.
   • Server IP or DNS: Enter the Bindplane agent IP address.
   • Server Protocol: Select UDP.
   • Server Port: Enter the Bindplane agent port number (for example, 514 for UDP).
   • Exclude Headers: Toggle switch to enable log headers.
   • Log Types: Select the available logs to send to the SIEM.
5. Click Save.

UDM mapping table

Log Field	UDM Mapping	Logic
Client Computer	principal.asset.asset_id	The value of Client Computer is assigned to principal.asset.asset_id after prepending "Client Computer: ".
Client User	principal.user.userid	The value of Client User is assigned to principal.user.userid.
Content Policy	security_result.rule_name	The value of Content Policy is assigned to security_result.rule_name.
Content Policy Type	security_result.rule_id	The value of Content Policy Type is assigned to security_result.rule_id.
Destination	metadata.ingestion_labels.value	The value of Destination is assigned to the value field of an ingestion_labels object where the key is "Destination".
Destination Type	metadata.ingestion_labels.value	The value of Destination Type is assigned to the value field of an ingestion_labels object where the key is "Destination Type".
Device PID	metadata.ingestion_labels.value	The value of Device PID is assigned to the value field of an ingestion_labels object where the key is "Device PID".
Device Serial	metadata.ingestion_labels.value	The value of Device Serial is assigned to the value field of an ingestion_labels object where the key is "Device Serial". This is only done if Device Serial is not empty.
Device VID	metadata.ingestion_labels.value	The value of Device VID is assigned to the value field of an ingestion_labels object where the key is "Device VID".
File Name	target.file.full_path	The value of File Name is assigned to target.file.full_path.
File Size	target.file.size	The value of File Size is assigned to target.file.size and converted to an unsigned integer.
IP Address	principal.ip	The value of IP Address is assigned to principal.ip.
Item Details	metadata.ingestion_labels.value	The value of Item Details is assigned to the value field of an ingestion_labels object where the key is "Item Details".
Log ID	metadata.product_log_id	The value of Log ID is assigned to metadata.product_log_id.
MAC Address	principal.mac	The value of MAC Address is assigned to principal.mac after replacing all hyphens with colons.
Matched Item	metadata.ingestion_labels.value	The value of Matched Item is assigned to the value field of an ingestion_labels object where the key is "Matched Item".
Message	security_result.summary	The value of Message is assigned to security_result.summary.
OS	principal.platform	The value of OS is used to determine the value of principal.platform. If OS contains "Windows", principal.platform is set to "WINDOWS". If OS contains "Mac", principal.platform is set to "MAC". If OS contains "Lin", principal.platform is set to "LINUX".
Serial Number	principal.asset.hardware.serial_number	The value of Serial Number is assigned to principal.asset.hardware.serial_number. Extracted from the message field using grok and assigned to intermediary.hostname. Extracted from the message field using grok and assigned to metadata.description. The timestamp from the syslog message is parsed and assigned to metadata.event_timestamp. The value "SCAN_UNCATEGORIZED" is assigned to metadata.event_type. The value "ENDPOINT_PROTECTOR_DLP" is assigned to metadata.log_type. The value "ENDPOINT_PROTECTOR_DLP" is assigned to metadata.product_name. The value "ENDPOINT_PROTECTOR_DLP" is assigned to metadata.vendor_name. Extracted from the message field using grok and assigned to principal.hostname. Extracted from the message field using grok and assigned to principal.ip. The timestamp from the syslog message is parsed and assigned to the top-level timestamp field.
Destination	event.idm.read_only_udm.target.application	Mapped from changelog
Matched Item	event.idm.read_only_udm.target.file.mime_type	Mapped from changelog
intermediary_ip	event.idm.read_only_udm.intermediary.ip	Mapped from changelog
server_date	event.idm.read_only_udm.additional.fields	Mapped from changelog
client_date	event.idm.read_only_udm.additional.fields	Mapped from changelog
server_date_utc	event.idm.read_only_udm.additional.fields	Mapped from changelog
client_date_utc	event.idm.read_only_udm.additional.fields	Mapped from changelog
pid	event.idm.read_only_udm.principal.process.pid	Mapped from changelog
OS	event.idm.read_only_udm.principal.platform_version	Mapped from changelog

Change Log

View the Change Log for this parser

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