Collect Barracuda Web Filter logs

Supported in:

This document explains how to ingest Barracuda Web Filter logs to Google Security Operations using Bindplane agent.

Barracuda Web Filter (also known as Barracuda Web Security Gateway) is a web security appliance that generates syslog messages for web traffic events and web interface activity. The parser normalizes fields 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 Barracuda Web Filter
  • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
  • Firmware 10.x or later installed on the appliance
  • Privileged access to the Barracuda Web Filter web UI

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

Configure the 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/barracuda_webfilter:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: BARRACUDA_WEBFILTER
        raw_log_field: body

service:
    pipelines:
        logs/barracuda_webfilter_to_chronicle:
            receivers:
                - udplog
            exporters:
                - chronicle/barracuda_webfilter

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 for Barracuda Web Filter

  1. Sign in to the Barracuda Web Filter web UI.
  2. Go to Advanced Tab > Advanced > Syslog.
  3. In the Web Traffic Syslog section, enter the Bindplane agent IP address and port number.
  4. Click Add.
  5. In the Web Interface Syslog section, enter the Bindplane agent IP address and port number.
  6. Click Add.

UDM mapping table

Log Field UDM Mapping Logic
inter_ip intermediary.ip Merged
date_time metadata.event_timestamp Parsed as yyyy-MM-dd HH:mm:ss
app metadata.event_type Mapped: http → NETWORK_CONNECTION
has_principal metadata.event_type Mapped: true → STATUS_UPDATE
app network.application_protocol Mapped: http → HTTP
sess_id network.session_id Directly mapped
src_ip principal.asset.ip Merged
src_ip principal.ip Merged
mime principal.process.file.mime_type Directly mapped
process_id principal.process.pid Directly mapped
url principal.url Directly mapped
action_normalized security_result.action Merged
status security_result.rule_name Directly mapped
dst_ip target.asset.ip Merged
dst_ip target.ip Merged
N/A metadata.event_type Constant: NETWORK_CONNECTION
N/A network.application_protocol Constant: HTTP

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