[Deprecated] Infoblox SOC Insight Data Connector via AMA

Workspace Keys

In order to use the playbooks as part of this solution, find your **Workspace ID** and **Workspace Primary Key** below for your convenience.

Workspace ID

Workspace Key

Parsers

>This data connector depends on a parser based on a Kusto Function to work as expected called [**InfobloxCDC_SOCInsights**](https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/Infoblox%20SOC%20Insights/Parsers/InfobloxCDC_SOCInsights.yaml) which is deployed with the Microsoft Sentinel Solution.

SOC Insights

>This data connector assumes you have access to Infoblox BloxOne Threat Defense SOC Insights. You can find more information about SOC Insights [**here**](https://docs.infoblox.com/space/BloxOneThreatDefense/501514252/SOC+Insights).

Infoblox Cloud Data Connector

>This data connector assumes an Infoblox Data Connector host has already been created and configured in the Infoblox Cloud Services Portal (CSP). As the [**Infoblox Data Connector**](https://docs.infoblox.com/display/BloxOneThreatDefense/Deploying+the+Data+Connector+Solution) is a feature of BloxOne Threat Defense, access to an appropriate BloxOne Threat Defense subscription is required. See this [**quick-start guide**](https://www.infoblox.com/wp-content/uploads/infoblox-deployment-guide-data-connector.pdf) for more information and licensing requirements.

Follow the steps below to configure this data connector

A. Configure the Common Event Format (CEF) via AMA data connector

_Note: CEF logs are collected only from Linux Agents_ 1. Navigate to your **Microsoft Sentinel workspace > Data connectors** blade. 2. Search for the **Common Event Format (CEF) via AMA** data connector and open it. 3. Ensure there is no existing DCR configured to collect required facility of logs as it may cause log duplication. Create a new **DCR (Data Collection Rule)**. _Note: It is recommended to install the AMA agent v1.27 at minimum. [Learn more](https://learn.microsoft.com/azure/azure-monitor/agents/azure-monitor-agent-manage?tabs=azure-portal ) and ensure there is no duplicate DCR as it can cause log duplication._ 4. Run the command provided in the **Common Event Format (CEF) via AMA** data connector page to configure the CEF collector on the machine.

B. Within the Infoblox Cloud Services Portal, configure Infoblox BloxOne to send CEF 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 **Service Instance** section. - **Service Instance**: Select your desired Service Instance for which the Data Connector service is enabled. - Expand the **Source Configuration** section. - **Source**: Select **BloxOne Cloud Source**. - Select the **Internal Notifications** Log Type. - Expand the **Destination Configuration** section. - Select the **Destination** you just created. - Click **Save & Close**. 6. Allow the configuration some time to activate.

C. 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:

2. Secure your machine

Make sure to configure the machine's security according to your organization's security policy [Learn more >](https://aka.ms/SecureCEF)