receivers:
tcplog:
# Replace the below port <54525> and IP <0.0.0.0> with your specific values
listen_address: "0.0.0.0:54525"
exporters:
chronicle/chronicle_w_labels:
compression: gzip
# Adjust the creds location below according the placement of the credentials file you downloaded
creds: '{ json file for creds }'
# Replace <customer_id> below with your actual ID that you copied
customer_id: <customer_id>
endpoint: malachiteingestion-pa.googleapis.com
# You can apply ingestion labels below as preferred
ingestion_labels:
log_type: SYSLOG
namespace: bluceat_ddi
raw_log_field: body
service:
pipelines:
logs/source0__chronicle_w_labels-0:
receivers:
- tcplog
exporters:
- chronicle/chronicle_w_labels
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[[["\u003cp\u003eThis guide outlines the process for collecting BlueCat DDI logs (DNS, DHCP, IPAM) for analysis in Google Security Operations (SecOps), supporting both LEEF and non-LEEF formatted syslog messages.\u003c/p\u003e\n"],["\u003cp\u003eThe Bindplane Agent is used to ingest syslog data from BlueCat DDI and forward it to Google SecOps after proper configuration and authentication file setup.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring syslog on BlueCat DDI involves setting the Bindplane server's IP address and port, along with the preferred transport protocol (TCP or UDP), and adding these configurations in the logging section of the BlueCat interface.\u003c/p\u003e\n"],["\u003cp\u003eThe parser utilizes grok patterns and conditional logic to extract and map fields from various BlueCat DDI log types to the Unified Data Model (UDM), setting fields for DNS, DHCP, user activity, and other relevant data.\u003c/p\u003e\n"],["\u003cp\u003eThe logs that are extracted from the Bluecat DDI platform can be categorized by \u003ccode\u003eevent_type\u003c/code\u003e and include: NETWORK_DNS, NETWORK_DHCP, USER_LOGIN, USER_LOGOUT, USER_UNCATEGORIZED, GENERIC_EVENT, STATUS_UPDATE, and NETWORK_CONNECTION.\u003c/p\u003e\n"]]],[],null,["# Collect BlueCat DDI logs\n========================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n| **Note:** This feature is covered by [Pre-GA Offerings Terms](https://chronicle.security/legal/service-terms/) of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the [Google SecOps Technical Support Service guidelines](https://chronicle.security/legal/technical-support-services-guidelines/) and the [Google SecOps Service Specific Terms](https://chronicle.security/legal/service-terms/).\n\nThis parser handles both LEEF and non-LEEF formatted syslog messages from Bluecat DDI (DNS, DHCP, IPAM). It extracts fields from various log types (for example, named, dhcpd, audit, and CRON) using grok patterns and conditional logic, mapping them to the UDM based on the log type and populating DNS, DHCP, or user-related fields accordingly.\n\nBefore you begin\n----------------\n\n- Ensure that you have a Google Security Operations instance.\n- Ensure that you are using Windows 2016 or later, or a Linux host with systemd.\n- If running behind a proxy, ensure firewall [ports](/chronicle/docs/ingestion/use-bindplane-agent#verify_the_firewall_configuration) are open.\n- Ensure that you have privileged access to Bluecat.\n\nGet Google SecOps ingestion authentication file\n-----------------------------------------------\n\n1. Sign in to the Google SecOps console.\n2. Go to **SIEM Settings \\\u003e Collection Agents**.\n3. Download the **Ingestion Authentication File**.\n\nGet Google SecOps customer ID\n-----------------------------\n\n1. Sign in to the Google SecOps console.\n2. Go to **SIEM Settings \\\u003e Profile**.\n3. Copy and save the **Customer ID** from the **Organization Details** section.\n\nInstall Bindplane Agent\n-----------------------\n\n1. For **Windows installation** , run the following script: \n `msiexec /i \"https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi\" /quiet`\n2. For **Linux installation** , run the following script: \n `sudo sh -c \"$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)\" install_unix.sh`\n3. Additional installation options can be found in this [installation guide](/chronicle/docs/ingestion/use-bindplane-agent#install_the_bindplane_agent).\n\nConfigure Bindplane Agent to ingest Syslog and send to Google SecOps\n--------------------------------------------------------------------\n\n1. Access the machine where Bindplane is installed.\n2. Edit the `config.yaml` file as follows:\n\n receivers:\n tcplog:\n # Replace the below port \u003c54525\u003e and IP \u003c0.0.0.0\u003e with your specific values\n listen_address: \"0.0.0.0:54525\" \n\n exporters:\n chronicle/chronicle_w_labels:\n compression: gzip\n # Adjust the creds location below according the placement of the credentials file you downloaded\n creds: '{ json file for creds }'\n # Replace \u003ccustomer_id\u003e below with your actual ID that you copied\n customer_id: \u003ccustomer_id\u003e\n endpoint: malachiteingestion-pa.googleapis.com\n # You can apply ingestion labels below as preferred\n ingestion_labels:\n log_type: SYSLOG\n namespace: bluceat_ddi\n raw_log_field: body\n service:\n pipelines:\n logs/source0__chronicle_w_labels-0:\n receivers:\n - tcplog\n exporters:\n - chronicle/chronicle_w_labels\n\n3. Restart the Bindplane Agent to apply the changes:\n\n sudo systemctl restart bindplane\n\nConfigure Syslog on Bluecat DDI\n-------------------------------\n\n1. Sign in to the Bluecat Address Manager (BAM).\n2. From the **configuration** menu, select a configuration.\n3. Select the **Servers** tab.\n4. Under **Servers** , click the name of a **BDDS**.\n5. The **Details** tab for the server should open.\n6. Click the **server name** menu.\n7. Select **Service Configuration**.\n8. Click **Service Type \\\u003e Syslog** (the Address Manager queries the server and returns the current values).\n9. In **General** , set the following values:\n - **Syslog Server**: the IP address of your Syslog server (Bindplane).\n - **Syslog Port**: the port of your Syslog server (Bindplane).\n - **Syslog Transport** : select either **TCP** or **UDP** (depending on your Bindplane configuration).\n10. Click **Add** .\n - The newly added syslog server will appear in the list.\n11. Click **Update**.\n\nConfigure Syslog Settings in BlueCat DDI\n----------------------------------------\n\n1. Sign in to the BlueCat Address Manager.\n2. Go to **Configuration \\\u003e System Settings \\\u003e Logging**.\n3. In the **Logging Settings** , locate the **Syslog Servers** section.\n4. Click **Add Syslog Server**.\n5. Provide the required values:\n - **Server Name** : a unique name for the syslog server (for example, **BindplaneServer**).\n - **IP Address**: the IP address or hostname of the syslog server.\n - **Protocol** : select **TCP** , **UDP** (default), or **TLS** (based on your syslog configuration).\n - **Port**: specify the port for syslog communication (default: 514 for UDP/TCP, 6514 for TLS).\n6. Configure **Logging Level** . Choose the appropriate level based on your needs. Options include:\n - **Emergency**: critical issues that require immediate attention\n - **Alert**: alerts that need prompt action\n - **Critical**: critical conditions\n - **Error**: error events\n - **Warning**: warning events\n - **Notice**: normal but significant events\n - **Info**: informational messages\n - **Debug**: detailed debug information\n7. Optional: Add a custom Syslog facility to categorize logs (for example, **local0** or **local1**).\n8. Save the configuration.\n\nApply Syslog Settings to DDI Appliances\n---------------------------------------\n\n1. Navigate to **Servers \\\u003e Manage Servers**.\n2. Select the DNS/DHCP servers where the syslog should be enabled.\n3. Click **Edit Server**.\n4. In the **Logging** section:\n - Select the syslog server you configured earlier.\n - Enable logging for specific services (For example, **DNS queries** or **DHCP leases**).\n - Save the changes.\n\nUDM Mapping Table\n-----------------\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]