Console
    Start free

    Collect Aruba EdgeConnect SD-WAN logs

    Supported in:

    This document explains how to ingest Aruba EdgeConnect SD-WAN logs to Google Security Operations using the Bindplane agent.

    The Aruba EdgeConnect SD-WAN platform generates syslog messages for network traffic flows, security events, and system operations. The parser handles both key-value and unstructured syslog formats and maps extracted fields to the Unified Data Model (UDM).

    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 Aruba EdgeConnect appliance
    • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
    • Privileged access to Aruba Central or SD-WAN Orchestrator

    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.

    4. Save the file securely on the system where the Bindplane agent 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 IDfrom the Organization Detailssection.

    Install the Bindplane agent

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

    Windows installation

    1. Open Command Promptor PowerShellas an administrator.

    2. Run the following command:

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

    3. Wait for the installation to complete.

    4. Verify the installation by running:

       sc query observiq-otel-collector

      The service should show as RUNNING.

    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

    3. Wait for the installation to complete.

    4. 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 Bindplane agent installation guide .

    Configure Bindplane agent to ingest syslog and send to Google SecOps

    Locate the configuration file

    • Linux:

       sudo  
nano  
/etc/bindplane-agent/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/aruba_edgeconnect_sdwan 
 : 
  
 compression 
 : 
  
 gzip 
  
 creds_file_path 
 : 
  
 '/etc/bindplane-agent/ingestion-auth.json' 
  
 customer_id 
 : 
  
 '<customer_id>' 
  
 endpoint 
 : 
  
 malachiteingestion-pa.googleapis.com 
  
 log_type 
 : 
  
 ARUBA_EDGECONNECT_SDWAN 
  
 raw_log_field 
 : 
  
 body 
 service 
 : 
  
 pipelines 
 : 
  
 logs/aruba_edgeconnect_to_chronicle 
 : 
  
 receivers 
 : 
  
 - 
  
 udplog 
  
 exporters 
 : 
  
 - 
  
 chronicle/aruba_edgeconnect_sdwan

    Configuration parameters

    Replace the following placeholders:

    • Receiver configuration:

      • listen_address : IP address and port to listen on:
        • 0.0.0.0 to listen on all interfaces (recommended)
        • Port 514 is the standard syslog port (requires root on Linux; use 1514 for non-root)

    • Exporter configuration:

      • 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 copied from the Google SecOps console
      • 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

    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

      1. Verify the service is running:

         sudo  
systemctl  
status  
observiq-otel-collector

      2. 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 syslog in Aruba Central

    1. Sign in to the Aruba Centralweb UI.
    2. Go to Manage > Devices > Gateways.
    3. Select a Gatewayunder Device Name. The dashboard context for the gateway device is displayed.
    4. In Manage, click Device. The gateway configuration page is displayed.
    5. Click System > Logging.
    6. Click +in the Syslog Serverssection.
    7. 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.
    8. 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".

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

    Create a Mobile Website
    View Site in Mobile | Classic
    Share by: