Collect Infoblox DNS logs

This document explains how to ingest Infoblox DNS logs to Google Security Operations using the Bindplane agent.

The parser extracts fields from Infoblox DNS SYSLOG and CEF formatted logs. It uses grok and/or kv to parse the log message and then maps these values to the Unified Data Model (UDM). It also sets default metadata values for the event source and type.

Before you begin

Make sure you have the following prerequisites:

• A Google SecOps instance
• Windows Server 2016 or later, or Linux host with systemd
• If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
• Privileged access to the Infoblox Grid Manager web interface

Get a 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 a 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/chronicle_w_labels:
          compression: gzip
          creds_file_path: '/path/to/ingestion-authentication-file.json'
          customer_id: 'YOUR_CUSTOMER_ID'
          endpoint: malachiteingestion-pa.googleapis.com
          log_type: 'INFOBLOX_DNS'
          raw_log_field: body
          ingestion_labels:
  
  service:
      pipelines:
          logs/source0__chronicle_w_labels-0:
              receivers:
                  - udplog
              exporters:
                  - chronicle/chronicle_w_labels
  

Configuration parameters

Replace the following placeholders:

• Receiver configuration:

  • udplog: Use udplog for UDP syslog or tcplog for TCP syslog
  • 0.0.0.0: IP address to listen on (0.0.0.0 to listen on all interfaces)
  • 514: Port number to listen on (standard syslog port)

• Exporter configuration:

  • creds_file_path: Full path to ingestion authentication file:
    • Linux: /opt/observiq-otel-collector/ingestion-auth.json
    • Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
  • YOUR_CUSTOMER_ID: Customer ID from the Get customer ID section
  • 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
  • log_type: Log type exactly as it appears in Chronicle (INFOBLOX_DNS)

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 forwarding on Infoblox DNS

Use this section for on-premises Infoblox NIOS. For Infoblox BloxOne (cloud) deployments, use the Configure Infoblox BloxOne (Data Connector) section that follows instead.

1. Sign in to the Infoblox Grid Manager web interface.
2. Go to Grid > Grid Manager > Members.
3. Select the member to configure and click Edit.
4. Go to the Monitoring tab.
5. Under Syslog, click Add to add a new syslog server.
6. Provide the following configuration details:
   • Address: Enter the IP address of the Bindplane agent host.
   • Port: Enter 514.
   • Transport: Select UDP.
   • Node ID: Select the Infoblox node (for HA pairs).
   • Severity: Select Info (or your preferred severity level).
   • Facility: Select local0 (or your preferred facility).
7. Enable the following log categories:
   • DNS queries: Check Log DNS Queries under Grid DNS Properties > Logging.
   • DNS responses: Check Log DNS Responses.
   • DHCP: Enable DHCP logging under Grid DHCP Properties.
   • Audit: Enable audit logging under Grid Properties > Monitoring.
8. Click Save & Close.
9. Restart the DNS service if required.
10. Verify syslog messages are being sent by checking the Bindplane agent logs.

Configure Infoblox BloxOne (Data Connector) to forward DNS logs

For Infoblox BloxOne (cloud) deployments, use the Infoblox Data Connector to forward DNS query and response logs as CEF over syslog to the Bindplane agent you configured earlier.

1. Deploy the Infoblox Data Connector if you have not already, following the Deploying the Data Connector Solution guide.
2. Sign in to the Infoblox Portal.
3. Go to Integrations > Data Connectors.
4. On the Destination Configuration tab, from the Create drop-down list, select Syslog.
5. In the Create Syslog Destination Configuration wizard, provide the following configuration details:
   • Name: Enter a name that distinguishes this destination (for example, secops-bindplane).
   • State: Enable the destination using the slider.
   • Format: Select CEF.
   • FQDN/IP: Enter the IP address of the Bindplane agent host.
   • Port: Enter the port that your Bindplane syslog receiver listens on (for example, 514).
   • Protocol: Select the protocol that matches your Bindplane syslog receiver (UDP or TCP).
6. Click Save & Close.
7. Select the Source tab and confirm a DNS query and response source is available. Infoblox Threat Defense is pre-configured and needs no setup. For Universal DDI or on-prem NIOS DNS sources, configure the source here first, following the Configuring Sources guide.
8. Select the Traffic Flow Configuration tab, click Create, and provide the following configuration details:
   • Name: Enter a descriptive name (for example, dns-to-secops).
   • Source: Select the DNS query and response source (Infoblox Threat Defense Query/Response Log, or Universal DDI DNS Query/Response Log).
   • Destination: Select the syslog destination you created.
   • Service Instance: Select the Data Connector service instance (optionally add a secondary instance for failover).
   • State: Enable the traffic flow using the slider.
9. Click Save & Close.

UDM mapping table

Change Log

View the Change Log for this parser

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