Collect LogonBox logs

This document explains how to ingest LogonBox logs to Google Security Operations using Bindplane.

LogonBox is a self-service password management and identity verification platform. It generates audit logs for password resets, identity verification events, and admin actions. The parser maps LogonBox audit data to the Unified Data Model (UDM), capturing user identity, authentication events, resource modifications, and group management operations.

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 LogonBox server
• If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
• Privileged access to the LogonBox administration 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. 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 Bindplane agent installation guide .

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

Locate the configuration file

• Linux:

   sudo  
  systemctl  
  status  
  observiq-otel-collector 
  

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

Configuration parameters

Replace the following placeholders:

• Receiver configuration:

  • udplog : The receiver type based on protocol:
    • udplog for UDP syslog
    • tcplog for TCP syslog
    • syslog for RFC 3164/5424 syslog
  • 0.0.0.0 : IP address to listen on:
    • 0.0.0.0 to listen on all interfaces (recommended)
    • Specific IP address to listen on one interface
  • 514 : Port number to listen on (for example, 514 , 1514 , 6514 )

• Exporter configuration:

  • <customer_id> : Customer ID from the earlier step
  • malachiteingestion-pa.googleapis.com : 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
  • Adjust the creds_file_path depending on the platform:
    • Linux: /etc/bindplane-agent/ingestion-auth.json
    • Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json

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:

1. Run the following command:

    sudo  
   systemctl  
   restart  
   observiq-otel-collector 
   

2. Verify the service is running:

    sudo  
   systemctl  
   status  
   observiq-otel-collector 
   

3. Check logs for errors:

    sudo  
   journalctl  
   -u  
   observiq-otel-collector  
   -f 
   

To restart the Bindplane agent in Windows:

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

2. Verify the service is running:

    sc query observiq-otel-collector 
   

3. Check logs for errors:

     type 
     
    "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log" 
    
   

Configure LogonBox syslog forwarding

1. Sign in to the LogonBoxadministration console as an administrator.
2. Navigate to Reports > Audit Log.
3. Configure the syslog export settings:
   • Syslog Server: Enter the IP address of the Bindplane agent host (for example, 192.168.1.100 ).
   • Port: Enter 514 (must match the Bindplane receiver port).
   • Protocol: Select UDP(must match the Bindplane receiver type).
4. Select the event categories to forward (for example, password resets, identity verifications, user and group management).
5. Click Save.

UDM mapping table

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