Collect Radware Web Application Firewall logs

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

Radware Web Application Firewall (AppWall) is an application security solution that generates syslog messages for web attack detection, policy violations, bot mitigation events, and access control decisions. The parser extracts fields from syslog-formatted logs using grok patterns and maps them 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 Radware AppWall or Vision Reporter
• If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
• Administrative access to the Radware AppWall or Vision Reporter management console

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

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 Radware AppWall to forward logs to Bindplane

You can configure syslog forwarding from AppWall standalone, integrated AppWall in Alteon, or Vision Reporter.

Option 1: AppWall standalone using Vision Reporter

1. Sign in to the AppWall management console.
2. Go to Configuration > Services > Vision Support > Vision Reporter.
3. Enable Send events to Vision Reporter.
4. Set the Server IP to the Vision Reporter IP address.
5. Set the Port (for example, 514).
6. Set the Protocol to UDP.
7. Optional: Enable Send replies to forward response data.
8. Click Save.

Option 2: Integrated AppWall in Alteon

1. Sign in to the Alteon management console.
2. Go to Configuration > Security > Web Security > Vision Reporter.
3. Enable the Vision Reporter integration.
4. Set the Server IP to the Vision Reporter IP address.
5. Set the Port (for example, 514).
6. Set the Protocol to UDP.
7. Click Save.

Option 3: Vision Reporter forwarding to Bindplane

1. Sign in to the Vision Reporter management console.
2. Go to Configuration > SIEM & External Logging.
3. Click + Add New SIEM Destination.
4. Provide the following configuration details:
   • Name: Enter a name (for example, Google SecOps Forwarder).
   • Log Export Type: Select Syslog RFC 5424.
   • Remote Syslog Server: Enter the Bindplane agent IP address.
   • Port: Enter 514.
   • Protocol: Select UDP.
5. Click Save.

UDM mapping table

Change Log

View the Change Log for this parser

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