Muokkaa

Jaa


Holm Security Asset Data (using Azure Functions) connector for Microsoft Sentinel

The connector provides the capability to poll data from Holm Security Center into Microsoft Sentinel.

This is autogenerated content. For changes, contact the solution provider.

Connector attributes

Connector attribute Description
Log Analytics table(s) net_assets_CL
web_assets_CL
Data collection rules support Not currently supported
Supported by Holm Security

Query samples

All low net assets

net_assets_CL
         
| where severity_s  == 'low'

All low web assets

web_assets_CL
         
| where severity_s  == 'low'

Prerequisites

To integrate with Holm Security Asset Data (using Azure Functions) make sure you have:

Vendor installation instructions

Note

This connector uses Azure Functions to connect to a Holm Security Assets to pull its logs into Microsoft Sentinel. This might result in additional data ingestion costs. Check the Azure Functions pricing page for details.

(Optional Step) Securely store workspace and API authorization key(s) or token(s) 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.

STEP 1 - Configuration steps for the Holm Security API

Follow these instructions to create an API authentication token.

STEP 2 - Use the below deployment option to deploy the connector and the associated Azure Function

IMPORTANT: Before deploying the Holm Security connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the Holm Security API authorization Token, readily available.

Azure Resource Manager (ARM) Template Deployment

Option 1 - Azure Resource Manager (ARM) Template

Use this method for automated deployment of the Holm Security connector.

  1. Click the Deploy to Azure button below.

    Deploy To Azure

  2. Select the preferred Subscription, Resource Group and Location.

  3. Enter the Workspace ID, Workspace Key, API Username, API Password, 'and/or Other required fields'.

Note: If using Azure Key Vault secrets for any of the values above, use the@Microsoft.KeyVault(SecretUri={Security Identifier})schema in place of the string values. Refer to Key Vault references documentation for further details. 4. Mark the checkbox labeled I agree to the terms and conditions stated above. 5. Click Purchase to deploy.

Next steps

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