Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | ExtraHop |
| Publisher | ExtraHop |
| Used in Solutions | ExtraHop |
| Collection Method | Azure Function |
| Connector Definition Files | ExtraHop_FunctionApp.json |
| Ingestion API | Log Ingestion API — Sibling ARM template declares DCR / Log Ingestion API resources |
| Microsoft Learn | View on Learn |
The ExtraHop Detections Data Connector enables you to import detection data from ExtraHop RevealX to Microsoft Sentinel through webhook payloads. Data is ingested using the Azure Monitor Log Ingestion API via a Data Collection Rule (DCR).
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
ExtraHop_Detections_CL |
✓ | ✓ | ✓ |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Resource Provider Permissions:
Custom Permissions:
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
NOTE: This connector uses Azure Functions to receive ExtraHop webhook payloads and ingest them into Microsoft Sentinel using the Azure Monitor Log Ingestion API (DCR-based ingestion). This replaces the legacy Log Analytics HTTP Data Collector API. This might result in additional data ingestion costs. Check the Azure Functions pricing page for details.
(Optional Step) Securely store API credentials in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. Follow these instructions to use Azure Key Vault with an Azure Function App.
NOTE: This data connector depends on a parser based on a Kusto Function to work as expected which is deployed as part of the solution. To view the function code in Log Analytics, open Log Analytics/Microsoft Sentinel Logs blade, click Functions and search for the alias ExtraHopDetections and load the function code or click here. The function usually takes 10-15 minutes to activate after solution installation/update.
2. Configuration:
STEP 1 - App Registration steps for the Application in Microsoft Entra ID
This integration requires an App registration in the Azure portal. Follow the steps in this section to create a new application in Microsoft Entra ID:
ExtraHopSentinelConnector).Reference link: https://learn.microsoft.com/azure/active-directory/develop/quickstart-register-app
STEP 2 - Add a client secret for application in Microsoft Entra ID
Sometimes called an application password, a client secret is a string value required for the execution of ExtraHop Data Connector. Follow the steps in this section to create a new Client Secret:
Reference link: https://learn.microsoft.com/azure/active-directory/develop/quickstart-register-app#add-a-client-secret
STEP 3 - Get Object ID of your application in Microsoft Entra ID
After creating your app registration, follow the steps in this section to get Object ID:
STEP 4 - Deploy ExtraHop Data Connector
IMPORTANT: Before deploying the ExtraHop Data connector, have the Microsoft Entra ID App Registration details (Client ID, Client Secret, Tenant ID, and Object ID) readily available.
6. Deploy the ExtraHop Detections Data Connector:
Use this method for automated deployment of the ExtraHop Detections Data connector.
Click the Deploy to Azure button below.
Select the preferred Subscription, Resource Group and Region.
Enter the below information :
a. FunctionName - Enter the Function App name (used to name all related resources). Must be 1-11 characters. Default: ExtraHop
b. Location - The location in which the data collection rules and data collection endpoints should be deployed
c. WorkspaceName - Enter Microsoft Sentinel Workspace Name of Log Analytics workspace
d. AzureClientId - Enter Azure Client ID that you have created during app registration
e. AzureClientSecret - Enter Azure Client Secret that you have created during creating the client secret
f. AzureEntraObjectID - Enter Object id of your Microsoft Entra App
g. TenantId - Enter Tenant ID of your Microsoft Entra ID
h. DetectionsTableName - Enter name of the table used to store ExtraHop Detections logs. Default is 'ExtraHop_Detections'
i. LogLevel - Select log level or log severity value from Debug, Info, Error, Warning. By default it is set to Info
j. AppInsightsWorkspaceResourceID - Migrate Classic Application Insights to Log Analytic Workspace which is retiring by 29 Febraury 2024. Use 'Log Analytic Workspace-->Properties' blade having 'Resource ID' property value. This is a fully qualified resourceId which is in format '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/{workspaceName}'
k. HostingPlanType - Select the Function App hosting plan: FlexConsumption (recommended, required if you choose Private storage below) or LinuxConsumption (legacy, only supports Public storage, and retires 30 September 2028). Default is FlexConsumption
l. StorageAccountAccessType - Select Public (default, matches historical connector behavior) or Private to lock the storage account down behind private endpoints (blob/file/queue/table). Private requires HostingPlanType = FlexConsumption
m. NetworkDeploymentMode - Only used when StorageAccountAccessType is Private. Existing (default) uses subnet/private DNS zone resource IDs you already have; New has this template create its own VNet, subnets, and private DNS zones automatically
n. VNetAddressPrefix - Only used when NetworkDeploymentMode is New. Address space for the VNet this template creates. Default 10.42.0.0/24
o. FunctionAppOutboundSubnetPrefix - Only used when NetworkDeploymentMode is New. Subnet prefix for the Function App's outbound VNet integration. Default 10.42.0.0/27
p. StoragePrivateEndpointSubnetPrefix - Only used when NetworkDeploymentMode is New. Subnet prefix for the storage account's private endpoints. Default 10.42.0.32/27
q. FunctionAppOutboundSubnetId - Required when StorageAccountAccessType is Private and NetworkDeploymentMode is Existing. Resource ID of an empty subnet delegated to Microsoft.App/environments, used for the Function App's regional VNet integration
r. StoragePrivateEndpointSubnetId - Required when StorageAccountAccessType is Private and NetworkDeploymentMode is Existing. Resource ID of the subnet where the storage account's blob/file/queue/table private endpoints will be created
s. CreatePrivateDnsZoneLinks - Only used when NetworkDeploymentMode is Existing. If true, links StorageVNetId (below) to the private DNS zones below. If false (default), your VNet must already be linked to these zones
t. StorageVNetId - Required only when CreatePrivateDnsZoneLinks is true. Resource ID of the VNet that contains the subnets above, to link to the private DNS zones below
u. BlobPrivateDnsZoneId - Required when StorageAccountAccessType is Private and NetworkDeploymentMode is Existing. Resource ID of an existing private DNS zone for Blob storage (privatelink.blob)
v. FilePrivateDnsZoneId - Required when StorageAccountAccessType is Private and NetworkDeploymentMode is Existing. Resource ID of an existing private DNS zone for File storage (privatelink.file)
w. QueuePrivateDnsZoneId - Required when StorageAccountAccessType is Private and NetworkDeploymentMode is Existing. Resource ID of an existing private DNS zone for Queue storage (privatelink.queue)
x. TablePrivateDnsZoneId - Required when StorageAccountAccessType is Private and NetworkDeploymentMode is Existing. Resource ID of an existing private DNS zone for Table storage (privatelink.table)
Mark the checkbox labeled I agree to the terms and conditions stated above.
Click Purchase to deploy.
STEP 5 - Post Deployment
After successful deployment, configure the webhook connection from ExtraHop RevealX to Microsoft Sentinel.
8. 1) Get the Function App endpoint
9. 2) Configure a connection to Microsoft Sentinel and specify webhook payload criteria from RevealX
From your ExtraHop system, configure the Microsoft Sentinel integration to establish a connection between Microsoft Sentinel and ExtraHop RevealX and to create detection notification rules that will send webhook data to Microsoft Sentinel. For detailed instructions, refer to Integrate ExtraHop RevealX with Microsoft Sentinel SIEM.
After notification rules have been configured and Microsoft Sentinel is receiving webhook data, the Function App is triggered and you can view ExtraHop detections from the Log Analytics workspace custom table. Use the ExtraHopDetections parser function for a normalized view of the data.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊