Collect BlueCat DDI logs

Parser Version: 1.0

This document explains how to ingest BlueCat DDI logs to Google Security Operations using Bindplane. BlueCat DDI is an integrated DNS, DHCP, and IP Address Management (IPAM) solution that provides centralized management and automation of core network services. It helps organizations manage DNS zones, DHCP scopes, and IP address allocations across complex enterprise environments.

Before you begin

Make sure you have the following prerequisites:

• A Google SecOps instance.
• A Windows 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 BlueCat Address Manager administration console.

Get Google SecOps ingestion authentication file

1. Sign in to the Google SecOps console.
2. Go to SIEM Settings > Collection Agent.
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

Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.

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 is in the /observiq-otel-collector/ 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:
           listen_address: "0.0.0.0:514"
   
   exporters:
       chronicle/bluecat_ddi:
           compression: gzip
           creds_file_path: '/path/to/ingestion-authentication-file.json'
           customer_id: '<customer_id>'
           endpoint: malachiteingestion-pa.googleapis.com
           log_type: BLUECAT_DDI
           raw_log_field: body
           ingestion_labels:
   
   service:
       pipelines:
           logs/bluecat_ddi:
               receivers:
                   - udplog
               exporters:
                   - chronicle/bluecat_ddi
   

• Replace the port and IP address as required in your infrastructure.
• Replace <customer_id> with the actual customer ID.
• 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:

1. Run the following command:

   sudo systemctl restart observiq-otel-collector
   

2. Verify the service is running:

   sudo systemctl status observiq-otel-collector
   

3. Check logs for errors:

   sudo journalctl -u observiq-otel-collector -f
   

To restart the Bindplane agent in Windows:

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

2. Verify the service is running:

   sc query observiq-otel-collector
   

3. Check logs for errors:

   type "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log"
   

Configure BlueCat DDI syslog forwarding

Configure syslog on BlueCat Address Manager

1. Sign in to the BlueCat Address Manager web interface.
2. From the configuration drop-down menu, select a configuration.
3. Select the Servers tab.
4. Under Servers, click the name of the BDDS (BlueCat DNS/DHCP Server) that you want to configure.
5. Click the Syslog tab.
6. Under Syslog, click New.
7. 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 (or your configured Bindplane agent port).
   • Transport: Select UDP.
8. Click Add to save the syslog redirection entry.
9. Click Deploy to push the updated configuration to the BDDS appliance.

Configure syslog on BlueCat DNS/DHCP Server (BDDS) via CLI

If you prefer to configure syslog forwarding directly on the BDDS appliance instead of through Address Manager:

1. Connect to the BDDS appliance via SSH.
2. Sign in with administrative credentials.

3. Edit the syslog-ng configuration file:

   sudo vi /etc/syslog-ng/syslog-ng.conf
   

4. Add the following destination and log statements:

   destination d_bindplane {
       udp("<BINDPLANE_IP>" port(514));
   };
   
   log {
       source(s_local);
       destination(d_bindplane);
   };
   

5. Replace <BINDPLANE_IP> with the IP address of the Bindplane agent host.

6. Save the file and restart the syslog-ng service:

   sudo systemctl restart syslog-ng
   

7. Verify that logs are being forwarded by checking the Bindplane agent logs.

UDM mapping table

Change Log

View the Change Log for this parser

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