Description
The ExtraHop supported Azure integration delivers unparalleled visibility into real-time IT operations that help you make the most of Microsoft Azure and gain control over your cloud and hybrid IT environments. While ExtraHop delivers insights from all data in flight observed on your network, by integrating with Azure Monitor and Activity Logs, you get a centralized view of all IT assets in a way that's never been possible before.
This integration includes visibility over your entire Azure subscription for Virtual Machines, Storage Accounts, SQL Server Databases, Load Balancers, and Activity Logs. From resource utilization to performance, access changes to Azure Security Center events, we surface the information that matters.
Bundle Contents
- (5) Dashboards
- Azure: Activity Log
- Azure: Databases
- Azure: Load Balancers
- Azure: Storage
- Azure: Virtual Machines
- (1) Record Formats
- Azure Activity Log
- (5) Triggers
- Azure: Activity Log
- Azure: Databases
- Azure: Load Balancers
- Azure: Storage Accounts
- Azure: Virtual Machines
Requirements
ExtraHop version 7.4 or laterInstallation Instructions
Here is an overview of the steps you must complete to integrate Azure with ExtraHop:
- Deploy an ExtraHop EDA and EXA in Azure
- Create an Azure Virtual Machines Device Group on the EDA
Install the ExtraHop Azure Integration bundle on the EDA
Enable Open Data Context on the EDA
Deploy the Azure Integration
a. Set up the VNET Integration
b. Grant read permission to the App Service
c. Tag the Azure resources that you want to monitor
d. Send wire data from all tagged Azure Virtual Machines
Add Azure Virtual Machines to the device group on the EDA
1. Deploy an ExtraHop EDA and EXA in Azure
If you don't already have an EDA and EXA deployed in Azure, you must complete the following steps:
Log into Azure and complete the instructions in the following topic: Deploy the ExtraHop Discover Appliance in Azure.
Log into Azure and complete the instructions in the following topic: Deploy the ExtraHop Explore Appliance in Azure.
2. Create an Azure Virtual Machines Device Group on the EDA
- Create a static device group named Azure Virtual Machines.
3. Install the ExtraHop Azure Integration bundle on the EDA
Download the bundle on this page.
Log into the ExtraHop Web UI on your EDA and complete the instructions in the following topic: Upload and Apply the Bundle. Be sure to enable each of the Azure triggers.
4. Enable Open Data Context on the EDA
Log into the ExtraHop Admin UI on your EDA and complete the instructions in the following topic: Enable Open Data Context.
Note: For this integration, you only need to enable default TCP port 11211.
5. Deploy the Azure Integration
Click the Deploy to Azure button to begin the Azure Integration deployment.
Sign into your Azure account.
In the Basics section, complete the following steps:
a. In the Subscription field, select the subscription where the EDA is deployed.
b. In the Resource group field, select Use existing and then select the resource group where the EDA is deployed.
c. In the Location field, select a desired region.
In the Settings section, fill out each of the required fields. Hover over the ( i ) on each field to see an explanation about the field.
Accept the terms and conditions.
Click Purchase.
The deployment will take approximately 30 minutes. After the deployment is complete, continue onto the next step.
Setup the VNET Integration
Before the deployed Function App can communicate with the EDA, you must configure a Point-to-Site VPN, which Azure refers to as a VNET integration.
Navigate to Function Apps.
Select the Function App Name that was specified in the deployment.
Click Platform features.
Click Networking.
In the VNET Integration section, click Setup.
Select the Virtual Network that was specified in the deployment.
If the operation fails due to a timeout (such as in the figure below), you must sync the network through the following steps before proceeding to the next section:
a. In the Function App Platform features section, click App Service plan.
b. In the App Service plan Settings section, click Networking.
c. In the VNET Integration section, click Click here to manage.
d. Select the Virtual Network that was specified in the deployment.
e. Click Sync Network.
Wait until all of the sync operations are complete and then verify that they were successful.
If any of the sync operations were unsuccessful, wait a few minutes and click Sync Network again. Repeat this process until all of the sync operations complete successfully.
Grant read permission to the App Service
Before the deployed Function App can access metrics from all of the resources in the subscription, you must add a reader permission on the subscription level.
Navigate to Subscriptions.
Select the subscription specified in the deployment.
Click Access Control (IAM).
Click + Add.
Configure the permission with the following configuration steps:
a. In the Role field, select Reader.
b. In the Assign access to field, select Function App.
c. In the subscription field, ensure that the subscription specified in the deployment is selected.
d. Select the Function App Name that was specified in the deployment.
Tag the Azure resources that you want to monitor
You must go through each of the following Azure services supported by this integration and bulk assign a tag to the specific resources that you are interested in having Azure monitor metrics.
- Virtual machines
- Storage accounts
- Load balancers
- SQL databases
You must complete the following steps for each Azure Service above.
Navigate to the service within Azure.
Select all of the resources that you would like to monitor.
Click Assign tags.
In the Name field, type extrahop-azure-integration.
In the Value field, type true.
Click Assign
Note: If you would like to add all resources within a particular resource group, complete the following steps:
Navigate to the Resource Group.
Check Select All.
Click Assign Tags.
Enter the tag information from above.
Send wire data from all tagged Azure Virtual Machines
Before the Azure Integration can properly correlate virtual machine metrics with the associated devices within the EDA, you must be receiving wire data from those virtual machines.
You can either complete the steps in the Packet Forwarding with RPCAP guide or use Azure virtual network TAP by completing the steps in the Work with a virtual network TAP using the Azure CLI guide.
6. Add Azure Virtual Machines to the device group on the EDA
The source for the Virtual Machines dashboard on the EDA depends on a device group that contains all of the tagged Azure Virtual Machine devices that are sending wire data.
- Add devices to the Azure Virtual Machines group for each of the tagged Azure Virtual Machines that are sending wire data to the EDA.
Note: The time it takes for the EDA to discover the L3 devices for each of the Azure Virtual Machines can vary depending on how active the devices are and how much traffic is generated.