Collect Comforte SecurDPS logs

Supported in:

Google secops SIEM

This document explains how to ingest Comforte SecurDPS logs to Google Security Operations using the Bindplane agent.

Comforte SecurDPS is a data protection platform that provides tokenization and encryption for sensitive data in payment and transaction processing environments. It generates audit logs for data protection operations, access events, and policy enforcement actions.

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 Comforte SecurDPS server
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Privileged access to the Comforte SecurDPS server with administrator permissions

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 Bindplane 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 /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/comforte_securdps:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: COMFORTE_SECURDPS
        raw_log_field: body
        ingestion_labels:
            env: production

service:
    pipelines:
        logs/securdps_to_chronicle:
            receivers:
                - udplog
            exporters:
                - chronicle/comforte_securdps

Configuration parameters

Replace the following placeholders:

Receiver configuration:
- udplog: The receiver type based on protocol:
  - udplog for UDP syslog
  - tcplog for TCP syslog
- 0.0.0.0: IP address to listen on:
  - 0.0.0.0 to listen on all interfaces (recommended)
  - Specific IP address to listen on one interface
- 514: Port number to listen on (for example, 514, 1514, 6514)
Exporter configuration:
- comforte_securdps: Descriptive name for the exporter
- 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 from the previous step
- 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
- COMFORTE_SECURDPS: Log type exactly as it appears in Chronicle
- ingestion_labels: Optional labels in YAML format (for example, env: production)
Pipeline configuration:
- securdps_to_chronicle: Descriptive name for the pipeline

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 Comforte SecurDPS syslog forwarding

Sign in to the Comforte SecurDPS administration console with administrator credentials.
Go to System > Configuration > Logging.
Enable Syslog Forwarding for audit logs.
Provide the following configuration details:
- Syslog Server: Enter the IP address of the Bindplane agent host (for example, 192.168.1.100).
- Port: Enter 514 (must match the Bindplane agent receiver port).
- Protocol: Select UDP.
- Facility: Select local0 or the appropriate facility for your environment.
- Severity: Select Informational or lower to capture all audit events.
Select the log categories to forward:
- Data protection operations (tokenization, encryption)
- Access and authentication events
- Policy changes and administrative actions
- Error and warning events
Click Save to apply the configuration.
Verify that syslog messages are being received by checking the Bindplane agent logs.

Note: Comforte SecurDPS stores audit log files on the server file system. Consult the Comforte SecurDPS administration guide for exact log file locations and syslog configuration options specific to your deployment.

UDM mapping table

Log Field	UDM Mapping	Logic
record.index, record.cribl_pipe	additional.fields	Merged with labels created from record.index and record.cribl_pipe
record.msg_data, description	metadata.description	Value from record.msg_data if in JSON branch, else from description
metadata_event_type	metadata.event_type	Set based on flags: NETWORK_CONNECTION if principal_mid_present and target_mid_present, else USER_UNCATEGORIZED if target_user_present, else STATUS_UPDATE if principal_mid_present, else GENERIC_EVENT
record.sourcetype, prod_event_type	metadata.product_event_type	Value from record.sourcetype if in JSON branch, else from prod_event_type
	metadata.product_name	Set to "Comforte SecureDPS"
	metadata.vendor_name	Set to "COMFORTE_SECURDPS"
host	principal.asset.hostname	Value from host if not IP
validated_host, principal_ip	principal.asset.ip	Value from validated_host if host is IP in JSON branch, else from principal_ip
host	principal.hostname	Value from host if not IP
validated_host, principal_ip	principal.ip	Value from validated_host if host is IP in JSON branch, else from principal_ip
principal_port	principal.port	Value from principal_port, converted to integer
record.facility, record.facilityName, _STRATEGY, _PROTECTS, _DENIEDPROTECTS, _REVEALS, _DENIEDREVEALS, _LOOKUPS, _INTERVAL	security_result.detection_fields	Merged with labels created from record.facility, record.facilityName, _STRATEGY, _PROTECTS, _DENIEDPROTECTS, _REVEALS, _DENIEDREVEALS, _LOOKUPS, _INTERVAL
sec_description	security_result.description	Value from sec_description
record.severityName, severity	security_result.severity	Set to INFORMATIONAL if matches (?i)(info), WARNING if matches (?i)(warn), ERROR if matches (?i)(error)
record.severity, severity	security_result.severity_details	Value from record.severity if in JSON branch, else from severity
app, _APPLICATION	target.application	Value from _APPLICATION if not empty, else from app
_IPADDRESS	target.asset.ip	Value from _IPADDRESS
sha_256_value	target.file.sha256	Value from sha_256_value if matches hex pattern
_IPADDRESS	target.ip	Value from _IPADDRESS
pid	target.process.pid	Value from pid
sha256	target.resource.attribute.labels	Merged with sha256_label if sha_256_value does not match hex pattern
_ZOSUSER	target.user.userid	Value from _ZOSUSER

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