Collect HP Linux logs

Supported in:

Google secops SIEM

This document explains how to ingest HP-UX operating system logs to Google Security Operations using the Bindplane agent.

HP-UX is an enterprise UNIX operating system for HP Integrity and PA-RISC servers. HP-UX system logs capture authentication events, process execution, security audit data, and general system activity. Syslog files are stored locally under /var/adm/syslog/ .

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 HP-UX server
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Privileged (root) access to the HP-UX server

Get 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 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/hp_linux 
 : 
  
 compression 
 : 
  
 gzip 
  
 creds_file_path 
 : 
  
 '/etc/bindplane-agent/ingestion-auth.json' 
  
 customer_id 
 : 
  
 '<customer_id>' 
  
 endpoint 
 : 
  
 malachiteingestion-pa.googleapis.com 
  
 log_type 
 : 
  
 HP_LINUX 
  
 raw_log_field 
 : 
  
 body 
  
 ingestion_labels 
 : 
  
 env 
 : 
  
 production 
 service 
 : 
  
 pipelines 
 : 
  
 logs/hpux_to_chronicle 
 : 
  
 receivers 
 : 
  
 - 
  
 udplog 
  
 exporters 
 : 
  
 - 
  
 chronicle/hp_linux

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:
- hp_linux : 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
- HP_LINUX : Log type exactly as it appears in Chronicle
- ingestion_labels : Optional labels in YAML format (for example, env: production )
Pipeline configuration:
- hpux_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 HP-UX syslog forwarding

Sign in to the HP-UX server with root privileges.
Edit the syslog configuration file:
```
 vi  
/etc/syslog.conf 
```
Add the following line to forward all syslog messages to the Bindplane agent:
```
 *.* @<BINDPLANE_AGENT_IP> 
```
- Replace <BINDPLANE_AGENT_IP> with the IP address of the Bindplane agent host.
- The @ prefix sends logs via UDP. HP-UX syslog uses UDP by default.

To forward specific facilities only, use individual lines:

 auth.*  @<BINDPLANE_AGENT_IP>
kern.*  @<BINDPLANE_AGENT_IP>
*.err   @<BINDPLANE_AGENT_IP>

Save and close the file.

Restart the syslog daemon to apply the changes:

 /sbin/init.d/syslogd  
stop
/sbin/init.d/syslogd  
start

Verify that syslog messages are being received by checking the Bindplane agent logs.

Note: HP-UX stores syslog data in files such as /var/adm/syslog/syslog.log , /var/adm/syslog/mail.log , and rotated log files under /var/adm/syslog/ . The /var/adm/btmp and /var/adm/wtmp files capture failed login attempts and login/logout records respectively.

UDM mapping table

Log Field	UDM Mapping	Logic
`audit_type_label`	`additional.fields`	Merged
`auth_failures_label`	`additional.fields`	Merged
`ctladdr_label`	`additional.fields`	Merged
`da_instance_label`	`additional.fields`	Merged
`delay_label`	`additional.fields`	Merged
`dsn_label`	`additional.fields`	Merged
`event_code_label`	`additional.fields`	Merged
`mailer_label`	`additional.fields`	Merged
`msg_id_label`	`additional.fields`	Merged
`pri_label`	`additional.fields`	Merged
`raw_severity_label`	`additional.fields`	Merged
`ssh_version_label`	`additional.fields`	Merged
`stat_label`	`additional.fields`	Merged
`suite_label`	`additional.fields`	Merged
`syslog_priority_label`	`additional.fields`	Merged
`to_label`	`additional.fields`	Merged
`tty_label`	`additional.fields`	Merged
`xdelay_label`	`additional.fields`	Merged
`process`	`extensions.auth.type`	Mapped: `"sshd", "login"` → `AUTHTYPE_UNSPECIFIED`
`msg`	`metadata.description`	Directly mapped
`ts`	`metadata.event_timestamp`	Parsed as `MMM d HH:mm:ss`
`utc`	`metadata.event_timestamp`	Parsed as `UNIX_MS`
`event_type`	`metadata.event_type`	Directly mapped
`action_type`	`metadata.product_event_type`	Directly mapped
`centrifyEventID`	`metadata.product_log_id`	Directly mapped
`version`	`metadata.product_version`	Directly mapped
`message`	`network.application_protocol`	Mapped: `(?i)ssh` → `SSH`
`proto`	`network.ip_protocol`	Mapped: `tcp` → `TCP`
`DASessID`	`network.session_id`	Directly mapped
`process`	`principal.application`	Directly mapped
`host`	`principal.asset.hostname`	Directly mapped
`src_ip`	`principal.asset.ip`	Merged
`host`	`principal.hostname`	Directly mapped
`src_ip`	`principal.ip`	Merged
`src_port`	`principal.port`	Directly mapped
`p_id`	`principal.process.pid`	Directly mapped
`principal_user`	`principal.user.userid`	Directly mapped
`user`	`principal.user.userid`	Directly mapped
`security_result_action`	`security_result.action`	Merged
`ruleset`	`security_result.rule_name`	Directly mapped
`log_level`	`security_result.severity`	Mapped: `INFO` → `INFORMATIONAL`
`sev`	`security_result.severity`	Mapped: `(?i)ERROR` → `ERROR`
`log_level`	`security_result.severity_details`	Directly mapped
`t_domain`	`target.administrative_domain`	Directly mapped
`t_app`	`target.application`	Directly mapped
`t_hostname`	`target.asset.hostname`	Directly mapped
`target_hostname`	`target.asset.hostname`	Directly mapped
`t_hostname`	`target.hostname`	Directly mapped
`target_hostname`	`target.hostname`	Directly mapped
`target_user`	`target.user.userid`	Directly mapped
`user`	`target.user.userid`	Directly mapped
N/A	`extensions.auth.type`	Constant: `AUTHTYPE_UNSPECIFIED`
N/A	`metadata.product_name`	Constant: `HP Linux`
N/A	`metadata.vendor_name`	Constant: `HP Linux`
N/A	`network.application_protocol`	Constant: `SSH`
N/A	`network.ip_protocol`	Constant: `TCP`
N/A	`security_result.severity`	Constant: `INFORMATIONAL`

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