Collect Radware Alteon logs

Supported in:

This document explains how to ingest Radware Alteon logs to Google Security Operations using the Bindplane agent.

Radware Alteon is an application delivery controller (ADC) that provides load balancing, SSL offloading, and DDoS protection for enterprise applications. The parser extracts fields from Alteon log entries and maps them to the Unified Data Model (UDM), capturing authentication events, principal and target identifiers, and security results.

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 Radware Alteon appliance
  • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
  • Privileged access to the Radware Alteon appliance with administrator permissions

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 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 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

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

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

Locate the configuration file

  • Linux:

    sudo nano /opt/observiq-otel-collector/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/radware_alteon:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: RADWARE_ALTEON
        raw_log_field: body

service:
    pipelines:
        logs/radware_alteon:
            receivers:
                - udplog
            exporters:
                - chronicle/radware_alteon

Configuration parameters

Replace the following placeholders:

  • Receiver configuration:

    • udplog: The receiver type based on protocol:
      • udplog for UDP syslog
      • tcplog for TCP syslog
      • syslog for RFC 3164/5424 syslog
    • 0.0.0.0: IP address to listen on:
      • 0.0.0.0 to listen on all interfaces (recommended)
      • Specific IP address to listen on one interface
    • 514: Port number to listen on (for example, 514, 1514, 6514)

  • Exporter configuration:

    • <customer_id>: Customer ID from the earlier step
    • malachiteingestion-pa.googleapis.com: 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
    • Adjust the creds_file_path depending on the platform:
      • Linux: /etc/bindplane-agent/ingestion-auth.json
      • Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json

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 Radware Alteon syslog forwarding

Via CLI

  1. Connect to the Alteon appliance via SSH or serial console.

  2. Run the following commands to configure syslog forwarding:

    /cfg/sys/syslog/hst1
    ip <BINDPLANE_AGENT_IP>
    severity info
    port 514
/apply
/save

Via GUI

  1. Sign in to the Alteon web management interface.
  2. Go to Configuration > System > Logging and Alerts.
  3. Add a remote syslog server with the following details:
    • IP Address: Enter the IP address of the Bindplane agent host.
    • Port: Enter 514 (must match the Bindplane receiver port).
    • Severity: Select Info or higher.
  4. Click Apply.
  5. Click Save.

UDM mapping table

Log Field UDM Mapping Logic
extensions.auth.type Authentication type
description metadata.description Description of the event
timestamp metadata.event_timestamp Timestamp of the event
metadata.event_type Type of event
product_event_type metadata.product_event_type Product-specific event type
principal_application principal.application Application used by the principal
src_ip principal.asset.ip IP address of the principal's asset
src_ip principal.ip IP address of the principal
severity security_result.severity Severity level of the security result
severity security_result.severity_details Additional details about the severity
dst_ip target.asset.ip IP address of the target's asset
dst_ip target.ip IP address of the target
user_id target.user.userid User ID of the target user

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