Note: Support for this Pack was moved to Partner starting October 15, 2025. In case of any issues arise, please contact the Partner directly at support@infoblox.com or https://support.infoblox.com/.
Infoblox NIOS
The Infoblox NIOS integration enables network security and DNS based controls through the Infoblox NIOS platform. This integration provides capabilities for IP information retrieval, DNS firewall management via Response Policy Zones (RPZs), and network infrastructure monitoring within your Cortex environment.
DNS Security & Firewall
- Manages DNS Firewall by configuring Response Policy Zones (RPZs) to control DNS resolution behavior
- Blocks DNS resolution for malicious or unauthorized hostnames to prevent access to harmful destinations
- Redirects clients to walled gardens by substituting DNS responses for enhanced security control
- Provides comprehensive rule management including creation, updates, enabling/disabling, and deletion
- Supports multiple substitute record types (A, AAAA, MX, NAPTR, PTR, SRV, TXT, IPv4, IPv6) for advanced DNS response control
- Enables rule searching and object field inspection for detailed policy management
- Retrieves detailed metadata about IP addresses including status, network associations, and device information
- Provides comprehensive IP address information for both IPv4 and IPv6 addresses
- Supports network information lookup and related object searches
- Enables DHCP lease lookups for network troubleshooting and analysis
Host Record Management
- Creates new host records with IPv4 and IPv6 address assignments
- Lists and retrieves existing host records with detailed configuration information
- Supports host record configuration including DNS settings, aliases, and extended attributes
- Manages host record associations with network views and DNS zones
Network Infrastructure Integration
- Integrates with Infoblox NIOS appliances for DNS and network security management
- Provides API access to manage DNS security policies through Response Policy Zones
- Enables integration with security workflows for policy management
Pack Use-cases
- Retrieve detailed IP address information and network metadata for security investigations
- Create and manage Response Policy Zones (RPZs) for DNS based threat blocking
- Configure DNS firewall rules to block, redirect, or allow specific domains and IP addresses
- Create advanced substitute records (A, AAAA, MX, NAPTR, PTR, SRV, TXT) for sophisticated DNS response control
- Update existing RPZ rules and policies to adapt to changing security requirements
- Enable, disable, search, and delete RPZ rules for comprehensive policy lifecycle management
- Monitor network infrastructure and retrieve IP address status information
- Create new host records for DNS management and network asset tracking
- List and manage existing host records with comprehensive configuration details
- Integrate DNS security policy management with security workflows and automation
- Implement DNS based security controls as part of a layered defense strategy
- Perform DHCP lease lookups for network troubleshooting and security analysis
Support
This pack includes XSIAM content.
Sample XQL Queries
The following XQL Queries demonstrate the XDM modeling for the ingested Infoblox syslog messages:
DNS Queries
config timeframe = 1H
| datamodel dataset = infoblox_infoblox_raw
| filter xdm.event.type = "DNS Query"
| fields xdm.source.process.name, xdm.source.process.pid, xdm.alert.severity, xdm.event.log_level, xdm.event.type, xdm.event.description, xdm.source.ipv4, xdm.source.port, xdm.intermediate.ipv4, xdm.network.dns.dns_question.name, xdm.network.dns.dns_question.type, xdm.network.dns.dns_question.class, xdm.event.outcome, xdm.event.outcome_reason, xdm.network.ip_protocol
DNS Responses
config timeframe = 1H
| datamodel dataset = infoblox_infoblox_raw
| filter xdm.event.type = "DNS Response"
| fields xdm.source.process.name, xdm.source.process.pid, xdm.alert.severity, xdm.event.log_level, xdm.event.type, xdm.event.description, xdm.source.ipv4, xdm.source.port, xdm.network.dns.authoritative, xdm.network.dns.dns_question.name, xdm.network.dns.dns_question.class, xdm.network.dns.dns_question.type, xdm.network.dns.is_response,xdm.network.dns.is_truncated, xdm.network.dns.response_code, xdm.network.dns.dns_resource_record.name, xdm.network.dns.dns_resource_record.value, xdm.network.dns.dns_resource_record.type, xdm.network.dns.dns_resource_record.class, xdm.target.host.ipv4_addresses, xdm.target.host.ipv6_addresses, xdm.target.ipv4, xdm.target.ipv6, xdm.network.ip_protocol, xdm.event.outcome, xdm.event.outcome_reason
DHCP Events
config timeframe = 1H
| datamodel dataset = infoblox_infoblox_raw
| filter xdm.event.type = "DHCP" and xdm.network.dhcp.message_type != null
| fields xdm.source.process.name, xdm.source.process.pid, xdm.alert.severity, xdm.event.log_level, xdm.event.type, xdm.event.description, xdm.network.dhcp.message_type, xdm.source.host.mac_addresses, xdm.source.host.device_id, xdm.source.interface, xdm.source.ipv4, xdm.intermediate.ipv4, xdm.network.dhcp.giaddr, xdm.target.ipv4, xdm.network.dhcp.siaddr, xdm.network.dhcp.chaddr, xdm.network.dhcp.ciaddr, xdm.network.dhcp.client_hostname, xdm.network.dhcp.lease, xdm.network.dhcp.requested_address, xdm.network.dhcp.yiaddr, xdm.event.operation_sub_type, xdm.session_context_id, xdm.event.outcome, xdm.event.outcome_reason
Configuration on Server Side
This section describes the configuration steps that need to be done on your Infoblox NIOS appliance for sending event logs to Cortex XSIAM Broker VM via syslog.
Login to the Infoblox NIOS appliance.
From the Grid tab, Navigate to Grid Manager → Members, and then click Grid Properties → Edit from the Toolbar.
In the Grid Properties editor, select the Monitoring tab, and then complete the following:
- Select Log to External Syslog Servers to enable the appliance to send messages to a specified syslog server.
- Click the Add icon to add a new syslog server configuration and complete the following:
| Parameter |
Value |
Address |
Enter the IP address of the Cortex XSIAM Broker VM Syslog server. |
Transport |
Select whether the appliance should use UDP, TCP, or Secure TCP to connect to the Cortex XSIAM Broker VM. |
Server Certificate |
To transport the logs over Secure TCP, upload a self-signed or a CA-signed server certificate. |
Interface |
Select the interface through which the appliance should send the syslog messages to the Cortex XSIAM Broker VM. |
Source |
Select whether the appliance should send only Internal messages, External messages, or both (Any). |
Node ID |
Specify the host or node identification string that would be used in the syslog message header to identify the appliance from which the syslog messages originated. |
Port |
Enter the port number that the Cortex XSIAM Broker VM is listening on for receiving syslog messages from the Infoblox appliance. |
Severity |
Select the severity level of which messages from this level and above should be sent to Cortex XSIAM. |
Logging Category |
Select Send selected categories and use the arrows to move the requested logging categories from the Available table to the Selected table and vice versa. |
- Click Add to add the external syslog server information.
- Optionally, click the Test button to test the connection to the Cortex XSIAM syslog server.
If you want Audit logs to be forwarded to Cortex XSIAM Broker VM as well, select Copy Audit Log Messages to Syslog and select the facility that determines the processes and daemons from which the log messages are generated.
Save the configuration and click Restart if it appears at the top of the screen.
Timestamp Parsing for syslog messages sent from Infoblox to Cortex XSIAM is supported in GMT time zone. The time zone configured on the grid member should be set accordingly. See Using a Syslog Server and Viewing the Syslog Infoblox docs for additional details.
Collect Events from Vendor
In order to use the collector, use the Broker VM option.
Broker VM
You will need to use the information described here.
You can configure the specific vendor and product for this instance.
Navigate to Settings → Configuration → Data Broker → Broker VMs.
Go to the APPS column under the Brokers tab and add the Syslog app for the relevant broker instance. If the Syslog app already exists, hover over it and click Configure.
Click Add New.
When configuring the Syslog Collector, set the following parameters:
| Parameter |
Value |
Protocol |
Select UDP, TCP, or Secure TCP, in accordance with the selected syslog transport method configured on the Infoblox appliance. |
Port |
Enter the syslog service port that Cortex XSIAM Broker VM should listen on for receiving forwarded events from the Infoblox appliance. |
Vendor |
Enter Infoblox. |
Product |
Enter Infoblox. |
Pack Contributors:
Contributions are welcome and appreciated. For more info, visit our Contribution Guide.