This document explains how to ingest Aruba EdgeConnect SD-WAN logs to
Google Security Operations using Bindplane. The parser extracts fields from syslog
messages, handling both key-value and unstructured formats. It then maps these
extracted fields to the Unified Data Model (UDM), enriching the data with
network connection details and security results while categorizing events based
on available information.
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 Aruba Central or SD-WAN Orchestrator or both
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.
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.
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 /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).
Edit the config.yaml file as follows:
receivers:udplog:# Replace the port and IP address as requiredlisten_address:"0.0.0.0:514"exporters:chronicle/chronicle_w_labels:compression:gzip# Adjust the path to the credentials file you downloaded in Step 1creds_file_path:'/path/to/ingestion-authentication-file.json'# Replace with your actual customer ID from Step 2customer_id:<customer_id>
endpoint:malachiteingestion-pa.googleapis.com# Add optional ingestion labels for better organizationlog_type:'ARUBA_EDGECONNECT_SDWAN'raw_log_field:bodyingestion_labels:service:pipelines:logs/source0__chronicle_w_labels-0:receivers:-udplogexporters:-chronicle/chronicle_w_labels
Replace the port and IP address as required in your infrastructure.
Replace <customer_id> with the actual customer ID.
To restart the Bindplane agent in Linux, run the following command:
sudosystemctlrestartbindplane-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 Aruba Central
Sign in to the Aruba Central web UI.
Go to Manage > Devices > Gateways.
Select a Gateway under Device Name. The dashboard context for the gateway device is displayed.
In Manage, click Device. The gateway configuration page is displayed.
Click System > Logging.
Click + in the Syslog Servers section.
Provide the following configuration details:
IP address: Enter the Bindplane agent IP address.
Category: Select security (you can repeat the process later to add other categories).
Logging facility: Select Local0.
Logging level: Select Informational.
Format: Select cef.
Click Save Settings.
UDM mapping table
Log Field
UDM Mapping
Logic
Action
security_result.action_details
Directly mapped from the Action field.
Application
network.application_protocol
If the Application field contains "dhcp" (case-insensitive), the value is set to "DHCP".
Application
intermediary.application
Directly mapped from the Application field.
Direction
network.direction
Directly mapped from the Direction field, converted to uppercase. If the value is not "INBOUND", "OUTBOUND", or "BROADCAST", it's set to "UNKNOWN_DIRECTION".
DstAddr
target.ip
Directly mapped from the DstAddr field.
DstPort
target.port
Directly mapped from the DstPort field, converted to an integer.
Flow-ID
metadata.id
Directly mapped from the Flow-ID field.
FromZone
target.resource.attribute.labels
Creates a label with key "FromZone" and value from the FromZone field.
Host
intermediary.hostname
Directly mapped from the Host field.
Protocol
network.ip_protocol
Directly mapped from the Protocol field, converted to uppercase, and then parsed using an include file (parse_ip_protocol.include) to get the protocol name.
Reason
security_result.category_details
Directly mapped from the Reason field.
Reason
security_result.category
If the Reason field contains "policy deny", the value is set to "POLICY_VIOLATION".
SrcAddr
principal.ip
Directly mapped from the SrcAddr field.
SrcPort
principal.port
Directly mapped from the SrcPort field, converted to an integer.
Tag
security_result.rule_name
Directly mapped from the Tag field.
ToZone
target.resource.attribute.labels
Creates a label with key "ToZone" and value from the ToZone field.
description
metadata.description
Directly mapped from the description field, which is extracted from the log message when the kv_data field is empty.
intermediary_pid
intermediary.process.pid
Directly mapped from the intermediary_pid field.
timestamp
metadata.event_timestamp
Directly mapped from the timestamp field extracted from the log message. Set to "NETWORK_CONNECTION" if both SrcAddr and DstAddr are present, otherwise set to "GENERIC_EVENT". Hardcoded to "ARUBA_EDGECONNECT_SDWAN". Hardcoded to "ARUBA_EDGECONNECT_SDWAN".
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Collect Aruba EdgeConnect SD-WAN logs\n=====================================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n| **Note:** This feature is covered by [Pre-GA Offerings Terms](https://chronicle.security/legal/service-terms/) of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the [Google SecOps Technical Support Service guidelines](https://chronicle.security/legal/technical-support-services-guidelines/) and the [Google SecOps Service Specific Terms](https://chronicle.security/legal/service-terms/).\n\nThis document explains how to ingest Aruba EdgeConnect SD-WAN logs to\nGoogle Security Operations using Bindplane. The parser extracts fields from syslog\nmessages, handling both key-value and unstructured formats. It then maps these\nextracted fields to the Unified Data Model (UDM), enriching the data with\nnetwork connection details and security results while categorizing events based\non available information.\n\nBefore you begin\n----------------\n\nMake sure you have the following prerequisites:\n\n- Google SecOps instance\n- Windows 2016 or later, or a Linux host with `systemd`\n- If running behind a proxy, firewall [ports](/chronicle/docs/ingestion/use-bindplane-agent#verify_the_firewall_configuration) are open\n- Privileged access to Aruba Central or SD-WAN Orchestrator or both\n\nGet Google SecOps ingestion authentication file\n-----------------------------------------------\n\n1. Sign in to the Google SecOps console.\n2. Go to **SIEM Settings \\\u003e Collection Agents**.\n3. Download the **Ingestion Authentication File**. Save the file securely on the system where Bindplane will be installed.\n\nGet Google SecOps customer ID\n-----------------------------\n\n1. Sign in to the Google SecOps console.\n2. Go to **SIEM Settings \\\u003e Profile**.\n3. Copy and save the **Customer ID** from the **Organization Details** section.\n\nInstall the Bindplane agent\n---------------------------\n\nInstall the Bindplane agent on your Windows or Linux operating system according\nto the following instructions.\n\n### Windows installation\n\n1. Open the **Command Prompt** or **PowerShell** as an administrator.\n2. Run the following command:\n\n msiexec /i \"https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi\" /quiet\n\n### Linux installation\n\n1. Open a terminal with root or sudo privileges.\n2. Run the following command:\n\n sudo sh -c \"$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)\" install_unix.sh\n\n### Additional installation resources\n\nFor additional installation options, consult the [installation guide](/chronicle/docs/ingestion/use-bindplane-agent#install_the_bindplane_agent).\n\nConfigure the Bindplane agent to ingest Syslog and send to Google SecOps\n------------------------------------------------------------------------\n\n1. Access the configuration file:\n - Locate the `config.yaml` file. Typically, it's in the `/etc/bindplane-agent/` directory on Linux or in the installation directory on Windows.\n - Open the file using a text editor (for example, `nano`, `vi`, or Notepad).\n2. Edit the `config.yaml` file as follows:\n\n receivers:\n udplog:\n # Replace the port and IP address as required\n listen_address: \"0.0.0.0:514\"\n\n exporters:\n chronicle/chronicle_w_labels:\n compression: gzip\n # Adjust the path to the credentials file you downloaded in Step 1\n creds_file_path: '/path/to/ingestion-authentication-file.json'\n # Replace with your actual customer ID from Step 2\n customer_id: \u003ccustomer_id\u003e\n endpoint: malachiteingestion-pa.googleapis.com\n # Add optional ingestion labels for better organization\n log_type: 'ARUBA_EDGECONNECT_SDWAN'\n raw_log_field: body\n ingestion_labels:\n\n service:\n pipelines:\n logs/source0__chronicle_w_labels-0:\n receivers:\n - udplog\n exporters:\n - chronicle/chronicle_w_labels\n\n - Replace the port and IP address as required in your infrastructure.\n - Replace `\u003ccustomer_id\u003e` with the actual customer ID.\n - Update `/path/to/ingestion-authentication-file.json` to the path where the authentication file was saved in the [Get Google SecOps ingestion authentication file](/chronicle/docs/ingestion/default-parsers/aruba#get-auth-file) section.\n\nRestart the Bindplane agent to apply the changes\n------------------------------------------------\n\n1. To restart the Bindplane agent in **Linux**, run the following command:\n\n sudo systemctl restart bindplane-agent\n\n2. To restart the Bindplane agent in **Windows** , you can either use the **Services** console or enter the following command:\n\n net stop BindPlaneAgent && net start BindPlaneAgent\n\nConfigure Syslog in Aruba Central\n---------------------------------\n\n1. Sign in to the **Aruba Central** web UI.\n2. Go to **Manage \\\u003e Devices \\\u003e Gateways**.\n3. Select a **Gateway** under **Device Name**. The dashboard context for the gateway device is displayed.\n4. In **Manage** , click **Device**. The gateway configuration page is displayed.\n5. Click **System \\\u003e Logging**.\n6. Click **+** in the **Syslog Servers** section.\n7. Provide the following configuration details:\n - **IP address**: Enter the Bindplane agent IP address.\n - **Category** : Select **security** (you can repeat the process later to add other categories).\n - **Logging facility** : Select **Local0**.\n - **Logging level** : Select **Informational**.\n - **Format** : Select **cef**.\n8. Click **Save Settings**.\n\nUDM mapping table\n-----------------\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
