Console
    Start free

    Collect Wallix Bastion logs

    Supported in:

    This document explains how to ingest Wallix Bastion logs to Google Security Operations using the Bindplane agent.

    Wallix Bastion is a privileged access management (PAM) platform that generates syslog messages for session recordings, authentication events, password management, and administrative 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 Wallix Bastion appliance
    • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
    • Privileged access to the Wallix Bastion web UI

    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 IDfrom the Organization Detailssection.

    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 Promptor PowerShellas 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/wallix_bastion 
 : 
  
 compression 
 : 
  
 gzip 
  
 creds_file_path 
 : 
  
 '/etc/bindplane-agent/ingestion-auth.json' 
  
 customer_id 
 : 
  
 '<customer_id>' 
  
 endpoint 
 : 
  
 malachiteingestion-pa.googleapis.com 
  
 log_type 
 : 
  
 WALLIX_BASTION 
  
 raw_log_field 
 : 
  
 body 
 service 
 : 
  
 pipelines 
 : 
  
 logs/wallix_bastion_to_chronicle 
 : 
  
 receivers 
 : 
  
 - 
  
 udplog 
  
 exporters 
 : 
  
 - 
  
 chronicle/wallix_bastion

    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 in Wallix Bastion

    1. Sign in to the Wallix Bastionweb UI.
    2. Go to Configuration > Syslog.
    3. Click Addto add a new syslog server.
    4. Provide the following configuration details:
      • Server Address: Enter the Bindplane agent IP address.
      • Port: Enter 514 .
      • Protocol: Select UDP.
      • Facility: Select Local0.
    5. Click Activate.

    UDM mapping table

    Log Field UDM Mapping Logic
    status_label
    		additional.fields Merged
    type_label
    		additional.fields Merged
    infos
    		extensions.auth.type Mapped: (Authentication started/Authentication success) → AUTHTYPE_UNSPECIFIED , `Closed ...
    hostname
    		intermediary.hostname Directly mapped
    infos
    		metadata.description Directly mapped
    msg
    		metadata.description Directly mapped
    ts
    		metadata.event_timestamp Parsed as RFC 3339
    event_type
    		metadata.event_type Directly mapped
    event_details
    		metadata.product_event_type Directly mapped
    uid
    		metadata.product_log_id Directly mapped
    total_bytes_recv
    		network.received_bytes Renamed/mapped
    total_bytes_send
    		network.sent_bytes Renamed/mapped
    client_ip
    		principal.asset.ip Merged
    ip
    		principal.asset.ip Merged
    src_ip
    		principal.asset.ip Merged
    client_ip
    		principal.ip Merged
    ip
    		principal.ip Merged
    src_ip
    		principal.ip Merged
    src_port
    		principal.port Directly mapped
    action
    		security_result.action_details Directly mapped
    process
    		target.application Directly mapped
    dest_ip
    		target.asset.ip Merged
    dest_ip
    		target.ip Merged
    dest_port
    		target.port Directly mapped
    pid
    		target.process.pid Directly mapped
    user
    		target.user.userid Directly mapped
    N/A
    		 extensions.auth.type Constant: AUTHTYPE_UNSPECIFIED
    N/A
    		 metadata.product_name Constant: Wallix Bastion
    N/A
    		 metadata.vendor_name Constant: WALLIX_BASTION
    N/A
    		 network.ip_protocol Constant: TCP

    Change Log

    View the Change Log for this parser

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

    Create a Mobile Website
    View Site in Mobile | Classic
    Share by: