Collect HPE iLO logs

This document explains how to ingest the HPE iLO (Hewlett Packard Enterprise Integrated Lights-Out) logs to Google Security Operations using Bindplane. The parser code first attempts to parse the raw log message as JSON. If that fails, it uses regular expressions (grok patterns) to extract fields from the message based on common HP iLO log formats.

Before you begin

Ensure that you have the following prerequisites:

• Google SecOps instance
• Windows 2016 or later or Linux host with systemd
• If running behind a proxy, firewall ports are open
• Privileged access to HPE iLO

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 ID from the Organization Details section.

Install the Bindplane agent

Windows installation

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

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
   

Additional installation resources

For additional installation options, consult the installation guide.

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

1. Access the configuration file:

   • Locate the config.yaml file. Typically, it's in the /etc/bindplane-agent/ directory on Linux or in the installation directory on Windows.
   • Open the file using a text editor (for example, nano, vi, or Notepad).

2. Edit the config.yaml file as follows:

           receivers:
               udplog:
                   # Replace the port and IP address as required
                   listen_address: "0.0.0.0:514"
   
           exporters:
               chronicle/chronicle_w_labels:
                   compression: gzip
                   # Adjust the path to the credentials file you downloaded in Step 1
                   creds: '/path/to/ingestion-authentication-file.json'
                   # Replace with your actual customer ID from Step 2
                   customer_id: <customer_id>
                   endpoint: malachiteingestion-pa.googleapis.com
                   # Add optional ingestion labels for better organization
                   ingestion_labels:
                       log_type: HPE_ILO
                       raw_log_field: body
   
           service:
               pipelines:
                   logs/source0__chronicle_w_labels-0:
                       receivers:
                           - udplog
                       exporters:
                           - chronicle/chronicle_w_labels
   

3. Replace the port and IP address as required in your infrastructure.

4. Replace <customer_id> with the actual customer ID.

5. Update /path/to/ingestion-authentication-file.json to the path where the authentication file was saved in the Get Google SecOps ingestion authentication file section.

Restart the Bindplane agent to apply the changes

• To restart the Bindplane agent in Linux, run the following command:

  sudo systemctl restart bindplane-agent
  

• To restart the Bindplane agent in Windows, you can either use the Services console or enter the following command:

  net stop BindPlaneAgent && net start BindPlaneAgent
  

Configure Syslog in HP iLO

1. Sign in to the HPE iLO web UI.
2. Go to Management > Remote Syslog tab.
3. Click Enable iLO Remote Syslog.
4. Provide the following configuration details:
   • Remote Syslog Port: Enter the Bindplane port number (for example, 514).
   • Remote Syslog Server: Enter the Bindplane IP address.
5. Click Send Test Syslog and validate it was received in Google SecOps.
6. Click Apply.

UDM mapping table

Changes

2023-11-27

Bug fix:

• Set metadata.event_type to USER_LOGIN if logs are of Browser Login type.
• Set metadata_event_type to STATUS_UPDATE if principal.hostname is present.

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