Collect DigitalArts i-Filter logs

Supported in:

This document explains how to ingest DigitalArts i-Filter logs to Google Security Operations using the Bindplane agent.

DigitalArts i-Filter is a web filtering and URL categorization solution that controls and monitors web access across an organization. It generates logs for web access events, blocked URLs, and policy violations.

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 DigitalArts i-Filter server
  • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
  • Privileged access to the DigitalArts i-Filter 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/digitalarts_ifilter:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: DIGITALARTS_IFILTER
        raw_log_field: body
        ingestion_labels:
            env: production

service:
    pipelines:
        logs/ifilter_to_chronicle:
            receivers:
                - udplog
            exporters:
                - chronicle/digitalarts_ifilter

Configuration parameters

Replace the following placeholders:

  • Receiver configuration:

    • udplog: The receiver type based on protocol:
      • udplog for UDP syslog
      • tcplog for TCP 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:

    • digitalarts_ifilter: Descriptive name for the exporter
    • 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 from the previous step
    • 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
    • DIGITALARTS_IFILTER: Log type exactly as it appears in Chronicle
    • ingestion_labels: Optional labels in YAML format (for example, env: production)

  • Pipeline configuration:

    • ifilter_to_chronicle: Descriptive name for the pipeline

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 DigitalArts i-Filter syslog forwarding

  1. Sign in to the DigitalArts i-Filter management console with administrator credentials.
  2. Go to System Settings > Log Output Settings.
  3. Enable Syslog Output.
  4. Provide the following configuration details:
    • Syslog Server Address: Enter the IP address of the Bindplane agent host (for example, 192.168.1.100).
    • Port: Enter 514 (must match the Bindplane agent receiver port).
    • Protocol: Select UDP.
    • Format: Select Syslog (RFC 3164).
  5. Select the log types to forward:
    • Web access logs
    • Block logs (filtered URL requests)
    • Policy violation logs
  6. Click Apply to save the configuration.

  7. Verify that syslog messages are being received by checking the Bindplane agent logs.

UDM mapping table

Log Field UDM Mapping Logic
map_field additional.fields Merged
inter_host intermediary.hostname Directly mapped
inter_host_data intermediary.ip Merged
access_time metadata.event_timestamp Parsed as dd/MMM/yyyy:HH:mm:ss Z
request_method network.http.method Directly mapped
user_agent network.http.parsed_user_agent Renamed/mapped
referral_url network.http.referral_url Directly mapped
response_code network.http.response_code Directly mapped
user_agent network.http.user_agent Directly mapped
response_bytes network.received_bytes Directly mapped
request_bytes network.sent_bytes Directly mapped
request_version network.tls.version_protocol Directly mapped
client_name principal.hostname Directly mapped
client_ip principal.ip Merged
src_ip principal.nat_ip Merged
process_id principal.process.product_specific_process_id Directly mapped
group_name principal.user.group_identifiers Merged
user_name principal.user.userid Directly mapped
sec_result security_result Merged
target_ip target.ip Merged
target_port target.port Directly mapped
key target.resource.attribute.labels Mapped: webservice_id → map_field
map_field target.resource.attribute.labels Merged
request_url target.url Directly mapped
N/A metadata.description Constant: i-FILTER proxy
N/A metadata.event_type Constant: NETWORK_CONNECTION
N/A metadata.product_name Constant: i-FILTER
N/A metadata.vendor_name Constant: DigitalArts Inc.
N/A network.ip_protocol Constant: TCP
N/A target.hostname Constant: unspecified

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