Collect HPE BladeSystem c7000 logs

This document explains how to ingest HPE BladeSystem C7000 logs to Google Security Operations using Bindplane. The parser code extracts fields from HPE BladeSystem c7000 syslog messages using regular expressions, then maps those fields to a Unified Data Model (UDM) while enriching the data with additional context like severity levels and descriptive labels. It handles various log message structures, providing consistent representation for security monitoring and analysis.

Before you begin

Make sure you have the following prerequisites:

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

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

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

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_file_path: '/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
           log_type: 'HPE_BLADESYSTEM_C7000'
           raw_log_field: body
           ingestion_labels:
   
   service:
       pipelines:
           logs/source0__chronicle_w_labels-0:
               receivers:
                   - udplog
               exporters:
                   - chronicle/chronicle_w_labels
   

   • Replace the port and IP address as required in your infrastructure.
   • Replace <customer_id> with the actual customer ID.
   • 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

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

   sudo systemctl restart bindplane-agent
   

2. 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 directly in HPE BladeSystem

1. Sign in to the BladeSystem UI.
2. Go to Configuration > System Log.
3. Click Log Options tab.
4. Select the Enable remote system logging checkbox.
5. Provide the following configuration details:
   • Syslog Server Address: Enter the Bindplane agent IP address.
   • Port: Enter the Bindplane agent port number (default port is 514).
   • Protocol: The protocol is always UDP.
6. Click Test Remote Log and verify logs are received.
7. Click Apply to save.

Configure Syslog in StorageGRID Software

You can configure both the audit message levels within StorageGRID and set up external Syslog servers for forwarding these messages.

Configure StorageGRID Audit Message Levels

1. Sign in to the GRID Manage web UI.
2. Go to Configuration > Monitoring > Audit and syslog server.
3. For each category of audit message, select the Normal audit level from the list.
4. Click Save.

Configure StorageGRID External Syslog Server

1. From the Audit and syslog server page, click Configure external syslog server.
2. Provide the following configuration details:
   • Enter syslog info: Enter the Bindplane agent IP address.
   • Enter the Bindplane agent port number (default port is 514).
   • Select the UDP or TCP protocol, depending on your Bindplane agent configuration.
3. Click Continue.

Configure Syslog Events

1. From the Manage syslog content step of the wizard, select each type of audit information you want to send to the external syslog server.
   • Send audit logs
   • Send security events
   • Send application logs
   • Send access logs
2. For Severity, select Passthrough or 7 (Informational).
3. For Facility, select Passthrough.
4. Click Continue.

UDM mapping table

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