Collect Endpoint Protector DLP logs

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 ingestion authentication file

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

Note: This JSON file contains credentials for authenticating the Bindplane agent to Google SecOps.

Get Google SecOps customer ID

Sign in to the Google SecOps console.
Go to SIEM Settings > Profile.
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

Open Command Prompt or PowerShell as an administrator.

Run the following command:

msiexec /i "https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi" /quiet

Wait for the installation to complete.
Verify the installation by running:
```
sc query observiq-otel-collector
```
The service should show as RUNNING.

Linux installation

Open a terminal with root or sudo privileges.

Run the following command:

sudo sh -c "$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)" install_unix.sh

Wait for the installation to complete.
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.

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

Locate the configuration file

Linux:

sudo nano /etc/bindplane-agent/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:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.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 ingestion authentication file:
  - Linux: /etc/bindplane-agent/ingestion-auth.json
  - Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
- customer_id: Customer ID copied from the Google SecOps console
- endpoint: Regional endpoint URL:
  - US: malachiteingestion-pa.googleapis.com
  - Europe: europe-malachiteingestion-pa.googleapis.com
  - Asia: asia-southeast1-malachiteingestion-pa.googleapis.com
  - See Regional Endpoints for complete list

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

Verify the service is running:

sudo systemctl status observiq-otel-collector

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

Sign in to the Endpoint Protector web UI.
Go to Appliance > SIEM Integration.
Click Add New.
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.
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.

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