Infoblox Cloud Data connector for Microsoft Sentinel

The Infoblox Cloud Data Connector allows you to easily connect your Infoblox BloxOne data with Microsoft Sentinel. By connecting your logs to Microsoft Sentinel, you can take advantage of search & correlation, alerting, and threat intelligence enrichment for each log.

Connector attributes

Connector attribute	Description
Log Analytics table(s)	CommonSecurityLog (InfobloxCDC)
Data collection rules support	Workspace transform DCR
Supported by	InfoBlox

Query samples

Return all BloxOne Threat Defense (TD) security events logs

InfobloxCDC

| where DeviceEventClassID has_cs "RPZ"

Return all BloxOne Query/Response logs

InfobloxCDC

| where DeviceEventClassID has_cs "DNS"

Return all Category Filters security events logs

InfobloxCDC

| where DeviceEventClassID has_cs "RPZ"

| where AdditionalExtensions has_cs "InfobloxRPZ=CAT_"

Return all Application Filters security events logs

InfobloxCDC

| where DeviceEventClassID has_cs "RPZ"

| where AdditionalExtensions has_cs "InfobloxRPZ=APP_"

Return Top 10 TD Domains Hit Count

InfobloxCDC

| where DeviceEventClassID has_cs "RPZ" 

| summarize count() by DestinationDnsDomain 

| top 10 by count_ desc

Return Top 10 TD Source IPs Hit Count

InfobloxCDC

| where DeviceEventClassID has_cs "RPZ" 

| summarize count() by SourceIP 

| top 10 by count_ desc

Return Recently Created DHCP Leases

InfobloxCDC

| where DeviceEventClassID == "DHCP-LEASE-CREATE"

Vendor installation instructions

Important

This data connector depends on a parser based on a Kusto Function to work as expected called InfobloxCDC which is deployed with the solution.

Important

This Microsoft Sentinel data connector assumes an Infoblox Cloud Data Connector host has already been created and configured in the Infoblox Cloud Services Portal (CSP). As the Infoblox Cloud Data Connector is a feature of BloxOne Threat Defense, access to an appropriate BloxOne Threat Defense subscription is required. See this quick-start guide for more information and licensing requirements.

1. Linux Syslog agent configuration

Install and configure the Linux agent to collect your Common Event Format (CEF) Syslog messages and forward them to Microsoft Sentinel.

Notice that the data from all regions will be stored in the selected workspace

1.1 Select or create a Linux machine

Select or create a Linux machine that Microsoft Sentinel will use as the proxy between your security solution and Microsoft Sentinel this machine can be on your on-premises environment, Microsoft Sentinel or other clouds.

1.2 Install the CEF collector on the Linux machine

Install the Microsoft Monitoring Agent on your Linux machine and configure the machine to listen on the necessary port and forward messages to your Microsoft Sentinel workspace. The CEF collector collects CEF messages on port 514 TCP.

1. Make sure that you have Python on your machine using the following command: python -version.

2. You must have elevated permissions (sudo) on your machine.

Run the following command to install and apply the CEF collector:

sudo wget -O cef_installer.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/CEF/cef_installer.py&&sudo python cef_installer.py {0} {1}

2. Configure Infoblox BloxOne to send Syslog data to the Infoblox Cloud Data Connector to forward to the Syslog agent

Follow the steps below to configure the Infoblox CDC to send BloxOne data to Microsoft Sentinel via the Linux Syslog agent.

1. Navigate to Manage > Data Connector.

2. Click the Destination Configuration tab at the top.

3. Click Create > Syslog.

   • Name: Give the new Destination a meaningful name, such as Microsoft-Sentinel-Destination.
   • Description: Optionally give it a meaningful description.
   • State: Set the state to Enabled.
   • Format: Set the format to CEF.
   • FQDN/IP: Enter the IP address of the Linux device on which the Linux agent is installed.
   • Port: Leave the port number at 514.
   • Protocol: Select desired protocol and CA certificate if applicable.
   • Click Save & Close.

4. Click the Traffic Flow Configuration tab at the top.

5. Click Create.

   • Name: Give the new Traffic Flow a meaningful name, such as Microsoft-Sentinel-Flow.
   • Description: Optionally give it a meaningful description.
   • State: Set the state to Enabled.
   • Expand the CDC Enabled Host section.
   • On-Prem Host: Select your desired on-premises host for which the Data Connector service is enabled.
   • Expand the Source Configuration section.
   • Source: Select BloxOne Cloud Source.
   • Select all desired log types you wish to collect. Currently supported log types are:
     • Threat Defense Query/Response Log
     • Threat Defense Threat Feeds Hits Log
     • DDI Query/Response Log
     • DDI DHCP Lease Log
   • Expand the Destination Configuration section.
   • Select the Destination you just created.
   • Click Save & Close.

6. Allow the configuration some time to activate.

7. Validate connection

Follow the instructions to validate your connectivity:

Open Log Analytics to check if the logs are received using the CommonSecurityLog schema.

It may take about 20 minutes until the connection streams data to your workspace.

If the logs are not received, run the following connectivity validation script:

1. Make sure that you have Python on your machine using the following command: python -version

2. You must have elevated permissions (sudo) on your machine

Run the following command to validate your connectivity:

sudo wget -O cef_troubleshoot.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/CEF/cef_troubleshoot.py&&sudo python cef_troubleshoot.py {0}

4. Secure your machine

Make sure to configure the machine's security according to your organization's security policy

Learn more >

Next steps

For more information, go to the related solution in the Azure Marketplace.