Collect Claroty xDome logs

Supported in:

Google SecOps SIEM

This document explains how to ingest Claroty xDome logs to Google Security Operations by using Bindplane.

Before you begin

Ensure that you have a Google Security Operations instance.
Ensure that you are using Windows 2016 or later, or a Linux host with systemd.
If running behind a proxy, ensure firewall ports are open.
Ensure that you have privileged access to Claroty xDome.

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.

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.

Install the Bindplane agent

Windows installation

Open the 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

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

Additional installation resources

For additional installation options, consult this installation guide.

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

Access the configuration file:
1. Locate the config.yaml file. Typically, it's in the /etc/bindplane-agent/ directory on Linux or in the installation directory on Windows.
2. Open the file using a text editor (for example, nano, vi, or Notepad).

Edit the config.yaml file as follows:

receivers:
    udplog:
        # Replace the port and IP address as required
        listen_address: "0.0.0.0:514"

exporters:
    chronicle/chronicle_w_labels:
        compression: gzip
        # Adjust the path to the credentials file you downloaded in Step 1
        creds: '/path/to/ingestion-authentication-file.json'
        # Replace with your actual customer ID from Step 2
        customer_id: <customer_id>
        endpoint: malachiteingestion-pa.googleapis.com
        # Add optional ingestion labels for better organization
        ingestion_labels:
            log_type: CLAROTY_XDOME
            raw_log_field: body

service:
    pipelines:
        logs/source0__chronicle_w_labels-0:
            receivers:
                - udplog
            exporters:
                - chronicle/chronicle_w_labels

Replace the port and IP address as required in your infrastructure.
Replace <customer_id> with the actual customer ID.
Update /path/to/ingestion-authentication-file.json to the path where the authentication file was saved in the Get Google SecOps ingestion authentication file section.

Restart the Bindplane agent to apply the changes

To restart the Bindplane agent in Linux, run the following command:
```
sudo systemctl restart bindplane-agent
```
To restart the Bindplane agent in Windows, you can either use the Services console or enter the following command:
```
net stop BindPlaneAgent && net start BindPlaneAgent
```

Configure Syslog on Claroty xDome

Sign in to the Claroty xDome Web UI.
Click the Settings tab in the navigation bar.
Select System Settings from the drop-down menu.
Click My Integrations in the Integrations section.
Click + Add Integration.
Select Internal Services from the Category menu.
Select SIEM and Syslog from the Integration menu.
Click Add.
Enter the following configuration details:
1. Destination IP: enter the Bindplane agent IP address.
2. Transport Protocol: select UDP (you can also select TCP, or TLS depending on your Bindplane configuration).
3. If you select the TLS security protocol, do the following:
  - Select Check Hostnames to verify if the server's hostname matches any of the names present in the X. 509 certificate.
  - Select Use Custom Certificate Authority to use a custom Certificate Authority (CA) instead of the default CA. Upload the custom certificate file or insert the certificate (in PEM format) into the space provided.
4. Destination Port: the default value for TCP, TLS, and UDP is 514 (hold your pointer over the field to use the clickable arrows to select a different destination port).
5. Advanced Options: enter the Advanced Options settings:
  - Message Format: select CEF (other options include JSON, or LEEF format).
  - Syslog Protocol Standard: select RFC 5424 or RFC 3164.
6. Integration Name: enter a meaningful name for the integration; for example, Google SecOps syslog.
7. Deployment options: select Run from the collection server or Run from the cloud option depending on your xDome configuration.
Go to the Integration Tasks parameters.
Turn on the Export Claroty xDome Communication Events Using Syslog option to enable exporting Claroty xDome communication events.
From the Event Types Selection menu, click Select All.
Choose the device conditions to export: select All Devices to export the communication event data of all affected devices.

Note: To receive OT Activity events through Syslog, it's necessary to create and enable OT Activity Alerts for the relevant event types. This is because xDome only sends events related to alerts for OT Activity.
Turn on the Export Claroty xDome Device Changes Alerts Change Log to Syslog option to export Claroty xDome change events.
In the Change Event Types Selection menu, select the change event types you want to export.
Choose the device conditions you want to export: select All Devices to export the change event data of all the affected devices.
Turn on the Export Claroty xDome Alert Information for Affected Devices Using Syslog option to export alert information for any alert type, including custom alerts.
From alert types, click Select All.
Turn on the Export Claroty xDome Vulnerability Information for Affected Devices Using Syslog option to export Claroty xDome vulnerability types.
In the Vulnerability Types Selection menu, select the vulnerability types you want to export.
Specify the CVSS Threshold number.
- This parameter lets you set a CVSS threshold to send a vulnerability using Syslog.
- Only vulnerabilities greater or equal to this threshold are exported.
- The threshold will revert to the CVSS V3 Base Score by default and CVSS V2 Base Score if the CVSS V3 score is unknown.
Choose the device conditions to export: Select All Devices to export the data of all affected devices.
Turn on the Export Claroty xDome Server Incidents Information to Syslog option to export Claroty xDome server incidents.
Select the collection server types you want to export from the Collection Server Selection menu.
Select the server incidents you want to export on the Server Incidents Selection menu.
Click Apply to save the configuration settings.

Changes

2025-01-29

Newly created parser

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