Collect Aruba Central logs

Supported in:

Google SecOps SIEM

This document shows how to ingest HPE Aruba Networking Central logs to Google SecOps using the Bindplane agent. The parser extracts fields from Aruba Central syslog formatted logs. It uses grok and/or kv to parse the log message and then maps these values to the Unified Data Model (UDM). It sets default metadata values for the event source and type.

Before you begin

Make sure you have the following prerequisites:

A Google SecOps instance
A Windows 2016 or later or Linux host with systemd
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Privileged access to the Aruba Central Management console

Get Google SecOps credentials for the Bindplane agent

To authenticate the Bindplane agent to Google SecOps, choose one of the following methods:

New deployments: Use the Chronicle API (Option 1).
Legacy deployments: Continue using the ingestion authentication file (Option 2) until the Ingestion API is discontinued on July 20, 2027.

Option 1: Create a service account for the Chronicle API (recommended)

Sign in to the Google Cloud console and select the Google Cloud project that is linked to your Google SecOps instance.
Go to IAM & Admin > Service Accounts.
Click Create service account.
Provide the following configuration details:
- Service account name: Enter a name for the account (for example, bindplane-ingest).
- Service account description: Enter a description (for example, Bindplane agent log ingestion).
Click Create and continue.
In the Grant this service account access to project section, click Select a role and select Chronicle Editor.
Click Continue, and then click Done.
Click the service account you created, and then go to the Keys tab.
Click Add key > Create new key.
Select JSON and click Create. The key file is downloaded to your computer.
Save the key file as ingestion-auth.json in the Bindplane collector directory (/opt/observiq-otel-collector/ingestion-auth.json on Linux or C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json on Windows), or update creds_file_path in config.yaml to match the path where you save it.
Go to IAM & Admin > Settings and copy the Project number. You'll need it for the exporter configuration.

Option 2: Download the ingestion authentication file (legacy)

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 the Bindplane agent will be installed.

Get Google SecOps customer ID

Sign in to the Google SecOps console.
Go to SIEM Settings > Profile.
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

Open the Command Prompt or PowerShell as an administrator.

Run the following command:

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

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

Additional installation resources

For additional installation options, consult this installation guide.

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

Access the Configuration File:
- Locate the config.yaml file. Typically, it's in the /opt/observiq-otel-collector/ directory on Linux or in the installation directory on Windows.
- Open the file using a text editor (for example, nano, vi, or Notepad).

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:
    protocol: https
    # Region of your instance, for example us, europe, asia-southeast1
    location: <LOCATION>
    # Project number of the Google Cloud project linked to the instance
    project: '<PROJECT_NUMBER>'
    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: chronicle.googleapis.com
    # Add optional ingestion labels for better organization
    log_type: 'ARUBA_CENTRAL'
    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 <LOCATION> with the region of your Google SecOps instance (for example, us, europe, or asia-southeast1). The exporter prefixes chronicle.googleapis.com with this value.
Replace <PROJECT_NUMBER> with the project number from IAM & Admin > Settings.
Replace <customer_id> with the actual Customer ID.
Update /path/to/ingestion-authentication-file.json to the file path where the service account key file (Option 1) was saved in Step 1.

Legacy ingestion API exporter

If you use the ingestion authentication file from Option 2, replace the exporters block with the following. Set creds_file_path to the path to the ingestion authentication file, and if your instance is outside the US, replace malachiteingestion-pa.googleapis.com with your regional endpoint (for example, europe-malachiteingestion-pa.googleapis.com).

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: 'ARUBA_CENTRAL'
    raw_log_field: body
    ingestion_labels:

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
```
To restart the Bindplane agent in Windows, you can either use the Services console or enter the following command:
```
net stop observiq-otel-collector && net start observiq-otel-collector
```

Configure Syslog on Aruba Central

Sign in to Aruba Central web UI.
From the dashboard, locate a group that contains the devices you want to configure, or set the filter to All Devices for global settings.
Click the device or group you want to configure.
Go to Configuration > System > Logging.
Locate the Syslog Servers section and click the + button.
- Server Name: Enter a unique and descriptive name.
- Server IP: Enter the Bindplane agent IP address.
- Server Port: Enter the Bindplane agent port number.
- Logging Format: Select Syslog.
- Category and Facility: Select the categories and facilities for which you want to send logs.
- Logging Level: Select Informational.
Click Save Settings.

UDM mapping table

Log Field	UDM Mapping	Logic
`additional_amm`	`additional.fields`	Merged
`additional_nid`	`additional.fields`	Merged
`additional_setting_id`	`additional.fields`	Merged
`additional_webhook`	`additional.fields`	Merged
`dev_type_label`	`additional.fields`	Merged
`operation_label`	`additional.fields`	Merged
`datetime`	`metadata.event_timestamp`	Parsed as `RFC 3339`
`timestamp`	`metadata.event_timestamp`	Parsed as `RFC 3339`
`event_type`	`metadata.event_type`	Directly mapped
`alert_type`	`metadata.product_event_type`	Directly mapped
`event_data`	`metadata.product_event_type`	Directly mapped
`id`	`metadata.product_log_id`	Directly mapped
`details.__base_url`	`metadata.url_back_to_product`	Directly mapped
`network_ssid`	`network.session_id`	Directly mapped
`app`	`principal.application`	Directly mapped
`cluster_hostname`	`principal.asset.hostname`	Directly mapped
`host`	`principal.asset.hostname`	Directly mapped
`princ_mac`	`principal.asset.mac`	Merged
`details.group_name`	`principal.group.group_display_name`	Directly mapped
`details.group`	`principal.group.product_object_id`	Directly mapped
`cluster_hostname`	`principal.hostname`	Directly mapped
`host`	`principal.hostname`	Directly mapped
`princ_mac`	`principal.mac`	Merged
`pid`	`principal.process.pid`	Directly mapped
`cid`	`principal.user.product_object_id`	Directly mapped
`details.user`	`principal.user.userid`	Directly mapped
`device_id`	`principal.user.userid`	Directly mapped
`labels`	`security_result.about.labels`	Merged
`description`	`security_result.description`	Directly mapped
`state_label`	`security_result.detection_fields`	Merged
`severity`	`security_result.severity`	Mapped values (5 total, e.g. `"LOG_INFO", "LOG_DEBUG"` → `LOW`, `LOG_WARN` → `MEDIUM`, `LOG_...
`details.config_change`	`security_result.summary`	Directly mapped
`target_mac`	`target.asset.mac`	Merged
`target_mac`	`target.mac`	Merged
`alert_type`	`target.resource.type`	Mapped: `DEVICE_CONFIG_CHANGE_DETECTED` → `DEVICE`
`target_userid`	`target.user.userid`	Directly mapped
`userid`	`target.user.userid`	Directly mapped
N/A	`metadata.product_name`	Constant: `ARUBA_CENTRAL`
N/A	`metadata.vendor_name`	Constant: `ARUBA CENTRAL`
N/A	`security_result.severity`	Constant: `LOW`
N/A	`target.resource.type`	Constant: `DEVICE`
`nid" , "setting_id" , "details.dev_type" , "webhook" and "operation`	`additional.fields`	Mapped from changelog
`details.labels`	`security_result.about.labels`	Mapped from changelog

Change Log

View the Change Log for this parser

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