Collect Xcitium Endpoint Security logs

Parser Version: 2.0

Supported in:

Google SecOps SIEM

This document explains how to ingest Xcitium Endpoint Security (formerly Comodo) logs to Google Security Operations using the Bindplane agent.

Xcitium Endpoint Security is an endpoint protection platform that combines antivirus, firewall, intrusion prevention, and containment technologies to protect endpoints from known and unknown threats. It uses a default-deny approach with auto-containment to isolate unrecognized files and processes, preventing them from causing damage while they are analyzed.

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 Xcitium-managed endpoints
• If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
• Privileged access to the Xcitium Endpoint Manager console (formerly Comodo ITSM / ITarian)
• Administrator role in Xcitium Endpoint Manager to modify configuration profiles and portal settings

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.

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 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/comodo_av:
      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: '/path/to/ingestion-authentication-file.json'
      customer_id: 'your-customer-id'
      endpoint: chronicle.googleapis.com
      log_type: COMODO_AV
      raw_log_field: body
      ingestion_labels:
  
  service:
    pipelines:
      logs/comodo_to_chronicle:
        receivers:
          - udplog
        exporters:
          - chronicle/comodo_av
  

Configuration parameters

Replace the following placeholders:

• Receiver configuration:

  • listen_address: The IP address and port to listen on. Use 0.0.0.0 to listen on all interfaces. Default syslog port is 514.

• 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 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/comodo_av:
      compression: gzip
      creds_file_path: '/path/to/ingestion-authentication-file.json'
      customer_id: 'your-customer-id'
      endpoint: malachiteingestion-pa.googleapis.com
      log_type: COMODO_AV
      raw_log_field: body
      ingestion_labels:
  

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 Xcitium Endpoint Security syslog forwarding

Xcitium Endpoint Manager provides two levels of syslog forwarding. Configure both to ensure comprehensive log coverage.

Configure endpoint-level syslog forwarding (Xcitium Client - Security logs)

1. Sign in to the Xcitium Endpoint Manager console.
2. Go to Configuration Templates > Profiles.
3. Click the Windows profile you want to modify, or create a new profile.
4. Click Add Profile Section > Logging Settings.
5. In the Xcitium Client - Security section, enable Write to Syslog Server.
6. Provide the following configuration details:
   • Host: Enter the IP address or hostname of the Bindplane agent host.
   • Port: Enter the port number configured in the Bindplane agent (for example, 514).
7. Optionally, enable Write to Log File (CEF Format) to keep a local copy of logs in Common Event Format.
8. In the Communication Client section, enable Write to Syslog Server.
9. Provide the following configuration details:
   • Host: Enter the IP address or hostname of the Bindplane agent host.
   • Port: Enter the port number configured in the Bindplane agent (for example, 514).
10. Select the event types for which logs are collected:
    • Monitoring logs
    • Script logs
    • OS patch logs
    • Third party application update logs
    • Application installation logs
    • Uninstall logs
    • Event Detection and Response (EDR) agent communication logs
    • Xcitium Client - Security (XCS) communication logs
    • Remote Control Communication Logs
    • Operational Logs
11. Click Save.

Configure portal-level syslog forwarding (audit logs)

1. Sign in to the Xcitium Endpoint Manager console.
2. Go to Settings > Portal Set-Up > Logging Settings.
3. Click Edit.
4. Enable Write to syslog server.
5. Provide the following configuration details:
   • Host: Enter the IP address or hostname of the Bindplane agent host.
   • Port: Enter the port number configured in the Bindplane agent (for example, 514).

6. Click Save.

   Note: The portal-level logging settings feature may need to be enabled by your Xcitium account manager. Contact Xcitium support if the option is not available.

For more information, see the Xcitium Endpoint Manager Logging Settings documentation and Configure Audit Log Settings.

UDM mapping table

Log Field	UDM Mapping	Logic
event_type	metadata.event_type	Renamed/mapped
data5	principal.application	Directly mapped
data3	principal.asset.platform_software.platform_version	Directly mapped
dvchost	principal.hostname	Directly mapped
dvc	principal.ip	Merged
data4	principal.user.product_object_id	Directly mapped
filePath	target.file.full_path	Directly mapped
fname	target.process.parent_process.file.full_path	Directly mapped
suser	target.user.userid	Directly mapped
N/A	metadata.product_name	Constant: COMODO_AV
N/A	metadata.vendor_name	Constant: COMODO
N/A	principal.ip	Constant: dvc

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