Collect Claroty CTD logs

This document explains how to ingest Claroty Continuous Threat Detection (CTD) 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 CTD.

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

Install the Bindplane agent

Windows installation

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

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
   

Additional installation resources

• For additional installation options, consult this installation guide.

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

1. 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).

2. 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_CTD
               raw_log_field: body
   
   service:
       pipelines:
           logs/source0__chronicle_w_labels-0:
               receivers:
                   - udplog
               exporters:
                   - chronicle/chronicle_w_labels
   

3. Replace the port and IP address as required in your infrastructure.

4. Replace <customer_id> with the actual customer ID.

5. 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 Continuous Threat Detection (CTD)

1. Sign in to the Claroty CTD Web UI.
2. Go to Menu > Integrations > Syslog.
3. Repeat the following steps for each syslog message content type:
   • Alerts
   • Events
   • Health Monitoring
   • Insights
   • Activity Logs
   • Vulnerabilities
4. Click + to add a new configuration.
5. In the Message Content menu, select the required content to export.
6. Provide the following configuration details:
   • Category: select All.
   • Type: select Select All types.
   • Format: select CEF (Latest).
   • System URL: do not update the system URL/IP, unless you're behind a proxy server.
   • Send to: select External Syslog server (e.g SIEM, SOAR systems).
   • Vendor: select Other.
   • Syslog Server IP: enter the Bindplane agent IP address.
   • Port: enter the Bindplane agent port (for example, 514).
   • Protocol: select UDP (other options include TCP, TLS, or mTLS, depending on your Bindplane configuration).
7. Click Save.

UDM Mapping Table

Changes

2024-12-04

• Added additional mappings for logs when eventclass is Event , Alert , HealthCheck , and Insight.

2024-11-13

• Added Grok patterns to parse the hostname and the IP address from the syslog header and map it to observer.hostname and observer.ip respectively.
• Added support for unparsed logs.

2024-10-07

• Added support to parse new format of unparsed KV logs.

2024-08-28

• Newly created parser.

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