Collect Sangfor Proxy logs

Supported in:

This document explains how to ingest Sangfor Proxy logs to Google Security Operations using the Bindplane agent.

Sangfor IAG (Internet Access Gateway), listed in Chronicle as Sangfor Proxy, is a web security gateway providing URL filtering, threat protection, and internet access control. The parser extracts fields from Sangfor Proxy log entries and maps them to the Unified Data Model (UDM), capturing network connections, user identity, DNS answers, and security metadata.

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 Sangfor IAG appliance
  • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
  • Privileged access to the Sangfor IAG management console 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/sangfor_proxy:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: SANGFOR_PROXY
        raw_log_field: body

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

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 the 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 Sangfor IAG syslog forwarding

  1. Sign in to the Sangfor IAG management console.
  2. Go to System > Log Settings > Syslog.
  3. Enable Syslog forwarding.
  4. Provide the following configuration details:
    • Server Address: Enter the IP address of the Bindplane agent host (for example, 192.168.1.100).
    • Port: Enter 514 (must match the Bindplane receiver port).
    • Protocol: Select UDP (must match the Bindplane receiver type).
  5. Select the log categories to forward (for example, URL filtering, threat protection, traffic logs).
  6. Click Save.

UDM mapping table

Log Field UDM Mapping Logic
log_type,serv,net_action,url,title,snapshot,risk_level,identify,category,family,nProtocol,ioc_id additional.fields Merged with labels containing key and string_value from each source field
record_time metadata.event_timestamp Converted using date match RFC3339
metadata.event_type Set to "NETWORK_CONNECTION" if has_principal and has_target, else "STATUS_UPDATE" if has_principal, else "USER_UNCATEGORIZED" if has_user, else "GENERIC_EVENT"
metadata.product_name Set to "SANGFOR_PROXY"
metadata.vendor_name Set to "SANGFOR_PROXY"
dns network.dns.answers Merged with dns_answers containing data from dns
down_flux network.received_bytes Converted to uinteger
up_flux network.sent_bytes Converted to uinteger
host principal.asset.hostname Value copied directly
host_ip principal.asset.ip Value copied directly
group principal.group.group_display_name Value copied directly
host principal.hostname Value copied directly
host_ip principal.ip Value copied directly
src_port principal.port Converted to integer
username principal.user.userid Value copied directly
virus security_result.detection_fields Merged with virus_field containing key "virus" and value from virus
app target.application Value copied directly
dst_ip target.asset.ip Value copied directly
dst_ip target.ip Value copied directly
tm_type target.platform Set to "WINDOWS" if matches "Win", "MAC" if "Mac", "LINUX" if "Linux"
port target.port Converted to integer
file_name target.process.file.full_path Value copied directly
file_type target.process.file.mime_type Value copied directly
site target.resource.attribute.labels Merged with site_label containing key "site" and value from site

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