--- title: "Integrating NDR with InfoBlox" slug: "integrating-ndr-with-infoblox-1" tags: ["Install and Get Started", "NDR 4.x", "Customer", "Network Security"] updated: 2026-11-17T09:23:23Z published: 2026-11-17T09:23:23Z canonical: "docs.trellix.com/integrating-ndr-with-infoblox-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Integrating NDR with InfoBlox The Trellix NDR Console provides a unified capability to configure and ingest DNS events from Infoblox BloxOne Cloud Services, enabling the solution to parse and correlate DNS metadata for the detection of malicious activities. This integration supports the seamless operation of existing detection engines within NDRC that includes DGA (Domain Generation Algorithm) Detection, DNS tunneling, Fast Flux, and rogue DNS, to generate high-fidelity alerts based on identified attack patterns. Designed for operational efficiency, this integration ensures that high-volume Infoblox DNS events are normalized and transformed into actionable security intelligence. ### How the integration works - **Log generation and S3 delivery** Infoblox BloxOne Cloud Services export DNS query, response, and security logs in Parquet format. These logs are delivered as compressed files to dedicated Amazon S3 buckets. - **Automated event triggering** The arrival of a new Infoblox DNS file in S3 triggers an S3 event notification to a central Amazon SQS queue. The SQS message invokes the Worker Lambda, which identifies the source as Infoblox by inspecting the S3 object key prefix (for example, `/dns_enriched/`). - **Parsing and normalization** The Lambda parses the Infoblox DNS data and transforms it into a standardized JSON format compatible with Trellix NDR. Events are hashed by Source IP to ensure consistent load balancing and accurate stateful correlation in the NDR Console. Vendor-specific Infoblox fields, such as `qip` and `tcode`, are mapped to standard Trellix attributes during normalization. - **NDRC ingestion and detection** The Lambda sends gzipped batches of normalized Infoblox events to the Trellix NDR Console using a KMS-encrypted token for authentication. The NDR Console validates the client and routes the events to the detection engines, which continuously analyze the DNS activity to identify malicious attack behaviors. - **Alerting and triage** Upon detection of malicious DNS activity, the Trellix NDR Console generates events and alerts in the UI. Security analysts can review these alerts in the UI with associated risk scores, affected assets, and MITRE ATT&CK context to support rapid investigation and response. ### Configure InfoBlox BloxOne integration **Before you begin** - You must have an active Infoblox Threat Defense or BloxOne subscription. - Ensure you have access to the Infoblox Cloud Services portal ([https://csp.infoblox.com](https://csp.infoblox.com)) to configure log exports. - Ensure that you have access to the AWS Management Console with administrative privileges. - You have deployed an NDR Console instance in the AWS environment and have access to `client_group_token` for authentication. Refer to [*AWS (Amazon Web Services) deployment*](https://docs.trellix.com/network-and-platform/docs/aws-amazon-web-services-deployment) in the *NDR 4.x Deployment Guide* for more information. - Make sure you have a valid NDR Core or NDR Enterprise license. See the License Management section for NDR license activation and verification. **Infoblox BloxOne integration checklist** - Prepare Amazon S3 for log storage - Configure log export on Infoblox portal - Update Lambda and configure SQS notification - Identify and analyse Infoblox DNS events in NDR Console ##### Step 1: Prepare Amazon S3 for log storage Logs must be delivered to a regional S3 bucket before the NDRC can ingest them. You can create a new bucket or reuse an existing one by defining a unique prefix. **Create the S3 bucket** - Create a regional **Amazon S3** bucket with a unique name, such as `ndrc-infoblox-logs-target`. See the *Prepare Amazon S3 for log storage* topic in the *Configure Amazon Route 53 integration* section in *NDR Console 4.x Product Guide*. **Add a bucket policy for Infoblox access** To allow Infoblox to deliver logs to your bucket, you must authorize their service via a custom bucket policy using a vendor-provided Principal ID. 1. Obtain the AWS Principal ID for your account from the InfoBlox portal. 2. In your newly created S3 bucket, click on the **Permissions** tab. 3. Under **Bucket policy**, click **Edit**. Add a statement granting `s3:PutObject` and `s3:ListBucket` permissions to the Principal ID. > [!NOTE] > Note > > The Principal ID acts as a client secret ensuring only your authorized Infoblox account can write logs to this bucket. ##### Step 2: Configure log export on Infoblox portal 1. On the Infoblox portal, go to **Configure** > **Administration** > **Log Export**. 2. Check the boxes for logs you want to receive, such as **DNS Response logs** or **Security logs**. 3. Enter your S3 bucket name in the format: `s3://[bucketname]/`. 4. Click **Export** to start the data stream. ##### Step 3: Update Lambda and configure SQS notification Infoblox automatically creates a folder structure. The Worker Lambda uses this as a prefix to differentiate these logs from other sources. ###### Update Lambda configuration The lambda function configuration steps are similar to ones described in the *Integrate Lambda function for SQS and NDR Console* topic of the *Configure Amazon Route 53 integration* section in the *NDR Console 4.x Product Guide*. In the `NDRC_CONFIG_JSON`, specify `infoblox_log_config` and set the `log_prefix_key` for `infoblox_log_config` to match the exact vendor-generated folder name (e.g., `dns_enriched`). > [!WARNING] > Important > > Infoblox exports typically use the prefix `dns_enriched`. ```plaintext {  "log_level": "DEBUG",  "appliances": [    {      "ip": "YOUR_NDRC_IP_ADDRESS",      "client_group_token": "YOUR_NDRC_CLIENT_GROUP_TOKEN"    }  ],  "infoblox_log_config": {    "log_prefix_key": "dns_enriched",    "log_type": "parquet",    "enable_ib_logging": true,    "hosts_to_trace": [      "all"    ]  } }         ``` ###### Configure SQS notification In S3, create an **event notification** for **All object create event** and point it to the required NDRC SQS queue, using the Infoblox prefix. See the *Set up the event-driven SQS pipeline* topic of the *Configure Amazon Route 53 integration* section in the *NDR Console 4.x Product Guide*. This completes the Infoblox integration configuration workflow. Events will not populate in the Trellix NDR Web UI search page immediately after configuration. To optimize storage usage, `aws-flows` is disabled by default and must be manually toggled. To enable it: 1. Log in to the Trellix NDR CLI. 2. Type `enable`. 3. Type `configure system`. 4. Navigate to `aws-flows` and set it to `enable`. > [!NOTE] > Note > > Disabling aws-flows only blocks event visibility on the search page. Any alerts associated with these events will still be detected and displayed in the Trellix NDR Web UI. ##### Step 4: Identify and analyse Infoblox DNS events in NDR Console 1. Log in to the NDR Console UI. 2. Go to the Main Menu, and select **Search** under **Investigation**. 3. Isolate your DNS traffic coming via Infoblox using specific search filters and specifying time period of the events. 4. Look for `doc_values_type` as `dns` and `device-type` as `AWS_infoblox`. 5. Locate the DNS events in the results. Identify the event details for further investigation, such as source IP, destination IP, ports etc. 6. Switch to the **Investigation** > **Alerts** page and filter using the IP addresses you identified. This enables you to find alerts that got triggered due to these specific DNS events. 7. If there are alerts present, you can investigate further using the **Alert Details** and **Asset details** pages. For more information, see *Viewing the details of the alert* and *Investigate assets* sections in *NDR Console 4.x Product Guide*.