Collect Tanium Insight logs

Supported in:

This document explains how to ingest Tanium Insight logs to Google Security Operations using the Bindplane agent.

Tanium Insight is an endpoint visibility and incident response module that generates syslog messages for endpoint events, file integrity monitoring, process execution, network connections, and registry changes. The parser extracts fields from syslog-formatted key-value logs 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 Tanium Console
  • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
  • Administrator privileges on the Tanium Console

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.

  4. 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

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 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/tanium_insight:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: TANIUM_INSIGHT
        raw_log_field: body

service:
    pipelines:
        logs/tanium_insight_to_chronicle:
            receivers:
                - udplog
            exporters:
                - chronicle/tanium_insight

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

    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 syslog forwarding on Tanium Insight

  1. Sign in to the Tanium Console with administrator privileges.
  2. Go to Modules > Connect > Overview.
  3. Select Create Connection.
  4. Provide the following configuration details:
    • Name: Enter a descriptive name (for example, Google SecOps Insight Integration).
    • Description: Optional description for this connection.
    • Source: Select a Tanium Insight source (for example, a saved report from the Insight module).
    • Destination: Select Socket (SIEM) / Syslog.
    • Host: Enter the Bindplane agent IP address.
    • Port: Enter the Bindplane agent port number (for example, 514).
    • Transport: Select UDP.
    • Format: Select Syslog RFC 5424 (KV format).
    • Timezone: Select UTC timezone for universal consistency.
  5. Recommended: In Configure Output > Columns, add Insight fields and format them as key=value pairs.
  6. Click Save to start forwarding.

UDM mapping table

Log Field UDM Mapping Logic
timestamp metadata.event_timestamp Parsed as ISO8601
Question metadata.product_name Mapped: Chronicle-Patch-Applicability → Patch
product_name metadata.product_name Directly mapped
Question metadata.vendor_name Mapped: Chronicle-Patch-Applicability → Tanium Patch
Question security_result Mapped: Chronicle-Patch-Applicability → title, Chronicle-Patch-Applicability → `last_r...
cves security_result Merged
knowledge_base security_result Merged
last_reboot security_result Merged
title security_result Merged
category security_result.category Merged
Computer-Name target.hostname Directly mapped
group_name target.user.group_identifiers Merged
userid target.user.userid Directly mapped
N/A metadata.event_type Constant: SCAN_HOST
N/A metadata.product_name Constant: Patch
N/A metadata.vendor_name Constant: Tanium Patch

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