Collect BloxOne Threat Defense logs

This document explains how to ingest BloxOne Threat Defense logs to Google Security Operations using Bindplane. The Logstash parser extracts fields from BLOXONE DNS logs received in SYSLOG or JSON format. It first normalizes the log message into a JSON object and then maps the extracted fields to the Unified Data Model (UDM), enriching the data with geolocation and DNS details for security analysis.

Before you begin

Make sure you have the following prerequisites:

• Google SecOps instance
• Windows 2016 or later, or a Linux host with systemd
• If running behind a proxy, firewall ports are open
• Privileged access to Infoblox BloxOne

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. 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

Windows installation

1. Open the 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
   

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
   

Additional installation resources

For additional installation options, consult the installation guide.

Configure the Bindplane agent to ingest Syslog and send to Google SecOps

1. Access the Configuration File:
   • Locate the config.yaml file. Typically, it's in the /etc/bindplane-agent/ directory on Linux or in the installation directory on Windows.
   • Open the file using a text editor (for example, nano, vi, or Notepad).

2. Edit the config.yaml file as follows:

   receivers:
       udplog:
           # Replace the port and IP address as required
           listen_address: "0.0.0.0:514"
   
   exporters:
       chronicle/chronicle_w_labels:
           compression: gzip
           # Adjust the path to the credentials file you downloaded in Step 1
           creds: '/path/to/ingestion-authentication-file.json'
           # Replace with your actual customer ID from Step 2
           customer_id: <customer_id>
           endpoint: malachiteingestion-pa.googleapis.com
           # Add optional ingestion labels for better organization
           ingestion_labels:
               log_type: 'BLOXONE'
               raw_log_field: body
   
   service:
       pipelines:
           logs/source0__chronicle_w_labels-0:
               receivers:
                   - udplog
               exporters:
                   - chronicle/chronicle_w_labels
   

3. Replace the port and IP address as required in your infrastructure.

4. Replace <customer_id> with the actual customer ID.

5. Update /path/to/ingestion-authentication-file.json to the path where the authentication file was saved in the Get Google SecOps ingestion authentication file section.

Restart the Bindplane agent to apply the changes

• To restart the Bindplane agent in Linux, run the following command:

  sudo systemctl restart bindplane-agent
  

• To restart the Bindplane agent in Windows, you can either use the Services console or enter the following command:

  net stop BindPlaneAgent && net start BindPlaneAgent
  

Configure Syslog in Infoblox BloxOne

1. Sign in to the Infoblox Portal.
2. Go to Configure > Administration > Data Connector.
3. Select Destination Configuration tab.
4. Click Create > Syslog.
5. Provide the following configuration details:
   • Name: Provide a descriptive name (for example, Google SecOps collector).
   • Description: Provide a brief description.
   • State: Select Enable.
   • Tags: Click Add and specify the following to associate a key with the destination:
     • KEY: Enter a descriptive name for the key.
     • VALUE: Enter your value for the key.
   • Format: Select CEF.
   • Protocol: Select UDP or TCP (depending on your Bindplane agent configuration).
   • FQDN/IP: Enter the Bindplane agent IP address.
   • Port: Enter the Bindplane agent port (default is set to 514 for UDP).
6. Click Save & Close.

UDM mapping table

Note: This table only includes fields that are mapped to the UDM. Some fields from the raw log might be used internally by the parser but are not directly reflected in the final UDM output.

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