Collect BMC Client Management logs

Supported in:

Google secops SIEM

This document explains how to ingest BMC Client Management logs to Google Security Operations using the Bindplane agent.

BMC Client Management is an IT endpoint management platform used for software deployment, patch management, asset management, and compliance reporting. It generates logs for endpoint operations, software installations, configuration changes, and compliance checks.

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 BMC Client Management server
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Privileged access to the BMC Client Management server with administrator permissions

Get a Google SecOps ingestion authentication file

Sign in to the Google SecOps console.
Go to SIEM Settings > Collection Agents.
Download the Ingestion Authentication File.
Save the file securely on the system where Bindplane will be installed.

Note: This JSON file contains credentials for authenticating the Bindplane agent to Google SecOps.

Get a Google SecOps customer ID

Sign in to the Google SecOps console.
Go to SIEM Settings > Profile.
Copy and save the Customer IDfrom the Organization Detailssection.

Note: The customer ID is required for configuring the Bindplane agent exporter.

Install the Bindplane agent

Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.

Windows installation

Open Command Promptor PowerShellas an administrator.

Run the following command:

  msiexec 
  
 / 
 i 
  
 "https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi" 
  
 / 
 quiet

Wait for the installation to complete.
Verify the installation by running:
```
 sc query observiq-otel-collector 
```
The service should show as RUNNING.

Linux installation

Open a terminal with root or sudo privileges.

Run the following command:

 sudo  
sh  
-c  
 " 
 $( 
curl  
-fsSlL  
https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh ) 
 " 
  
install_unix.sh

Wait for the installation to complete.
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/bmc_client_mgmt 
 : 
  
 compression 
 : 
  
 gzip 
  
 creds_file_path 
 : 
  
 '/etc/bindplane-agent/ingestion-auth.json' 
  
 customer_id 
 : 
  
 '<customer_id>' 
  
 endpoint 
 : 
  
 malachiteingestion-pa.googleapis.com 
  
 log_type 
 : 
  
 BMC_CLIENT_MANAGEMENT 
  
 raw_log_field 
 : 
  
 body 
  
 ingestion_labels 
 : 
  
 env 
 : 
  
 production 
 service 
 : 
  
 pipelines 
 : 
  
 logs/bmc_to_chronicle 
 : 
  
 receivers 
 : 
  
 - 
  
 udplog 
  
 exporters 
 : 
  
 - 
  
 chronicle/bmc_client_mgmt

Configuration parameters

Replace the following placeholders:

Receiver configuration:
- udplog : The receiver type based on protocol:
  - udplog for UDP syslog
  - tcplog for TCP 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:
- bmc_client_mgmt : Descriptive name for the exporter
- 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 from the previous step
- 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
- BMC_CLIENT_MANAGEMENT : Log type exactly as it appears in Chronicle
- ingestion_labels : Optional labels in YAML format (for example, env: production )
Pipeline configuration:
- bmc_to_chronicle : Descriptive name for the pipeline

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

Verify the service is running:

 sudo  
systemctl  
status  
observiq-otel-collector

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 BMC Client Management syslog forwarding

Sign in to the BMC Client Managementadministration console with administrator credentials.
Go to Configuration > Server Settings > Logging.
Enable External Syslog Forwarding.
Provide the following configuration details:
- Syslog Server: Enter the IP address of the Bindplane agent host (for example, 192.168.1.100 ).
- Port: Enter 514 (must match the Bindplane agent receiver port).
- Protocol: Select UDP.
- Log Level: Select Informationor lower to capture all operational events.
Select the log categories to forward:
- Software deployment events
- Patch management events
- Asset inventory changes
- Compliance check results
Click Saveto apply the configuration.
Verify that syslog messages are being received by checking the Bindplane agent logs.

Note: BMC Client Management stores log files on the server file system. The default log directory depends on the installation path. Consult your BMC Client Management documentation for the exact log file locations in your environment.

UDM mapping table

Log Field	UDM Mapping	Logic
`processing_label`	`additional.fields`	Merged
`reading_label`	`additional.fields`	Merged
`writing_label`	`additional.fields`	Merged
`msg`	`metadata.description`	Directly mapped
`timestamp`	`metadata.event_timestamp`	Parsed as `dd/MMM/yyyy:HH:mm:ss`
`has_principal`	`metadata.event_type`	Mapped: `true` → `STATUS_UPDATE`
`req_method`	`network.http.method`	Directly mapped
`useragent`	`network.http.parsed_user_agent`	Directly mapped
`status_code`	`network.http.response_code`	Directly mapped
`useragent`	`network.http.user_agent`	Directly mapped
`prin_host`	`principal.asset.hostname`	Directly mapped
`prin_ip`	`principal.asset.ip`	Merged
`prin_host`	`principal.hostname`	Directly mapped
`prin_ip`	`principal.ip`	Merged
`prin_port`	`principal.port`	Directly mapped
`pid`	`principal.process.pid`	Directly mapped
`url_data`	`principal.url`	Directly mapped
N/A	`extensions.auth.type`	Constant: `MACHINE`
N/A	`metadata.event_type`	Constant: `USER_LOGIN`
N/A	`metadata.product_name`	Constant: `BMC_CLIENT_MANAGEMENT`
N/A	`metadata.vendor_name`	Constant: `BMC_CLIENT_MANAGEMENT`
N/A	`network.http.parsed_user_agent`	Constant: `parseduseragent`

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