Tenable Vulnerability Management (using Azure Functions) connector for Microsoft Sentinel

Članak
10/15/2024

The TVM data connector provides the ability to ingest Asset and Vulnerability data into Microsoft Sentinel using TVM REST APIs. Refer to API documentation for more information. The connector provides the ability to get data which helps to examine potential security risks, get insight into your computing assets, diagnose configuration problems and more

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

Connector attributes

Connector attribute	Description
Application settings	TenableAccessKey TenableSecretKey WorkspaceID WorkspaceKey logAnalyticsUri (optional)
Azure function app code	https://aka.ms/sentinel-TenableVMAzureSentinelConnector-functionapp
Log Analytics table(s)	Tenable_VM_Assets_CL Tenable_VM_Vuln_CL
Data collection rules support	Not currently supported
Supported by	Tenable

Query samples

Tenable VM Report - All Assets

Tenable_VM_Assets_CL

| sort by TimeGenerated desc

Tenable VM Report - All Vulns

Tenable_VM_Vuln_CL

| sort by TimeGenerated desc

Select unique vulnerabilities by a specific asset.

Tenable_VM_Vuln_CL

| where asset_fqdn_s has "one.one.one.one"

| summarize any(asset_fqdn_s, plugin_id_d, plugin_cve_s) by plugin_id_d

Select all Azure assets.

Tenable_VM_Assets_CL

| where isnotempty(azure_resource_id_s) or isnotempty(azure_vm_id_g)

Prerequisites

To integrate with Tenable Vulnerability Management (using Azure Functions) make sure you have:

Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. See the documentation to learn more about Azure Functions.
REST API Credentials/permissions: Both a TenableAccessKey and a TenableSecretKey is required to access the Tenable REST API. See the documentation to learn more about API. Check all requirements and follow the instructions for obtaining credentials.

Vendor installation instructions

Note

This connector uses Azure Durable Functions to connect to the TenableVM API to pull assets and vulnerabilities at a regular interval 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.

Note

This data connector depends on a TenableVM parser for vulnerabilities and a TenableVM parser for assets based on a Kusto Function to work as expected which is deployed with the Microsoft Sentinel Solution.

STEP 1 - Configuration steps for TenableVM

Follow the instructions to obtain the required API credentials.

STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function App

Before deploying the Workspace data connector, have the Workspace ID and Workspace Primary Key (can be copied from the following).

Option 1 - Azure Resource Manager (ARM) Template

Use this method for automated deployment of the TenableVM Vulnerability Management Report data connector using an ARM Template.

Click the Deploy to Azure button below.
Select the preferred Subscription, Resource Group, and Location.
Enter the TenableAccessKey and TenableSecretKey and deploy.
Mark the checkbox labeled I agree to the terms and conditions stated above.
Click Purchase to deploy.

Option 2 - Manual Deployment of Azure Functions

Use the following step-by-step instructions to deploy the TenableVM Vulnerability Management Report data connector manually with Azure Functions (Deployment via Visual Studio Code).

1. Deploy a Function App

You will need to prepare VS code for Azure function development.

Download the Azure Function App file. Extract archive to your local development computer.
Start VS Code. Choose File in the main menu and select Open Folder.
Select the top level folder from extracted files.
Choose the Azure icon in the Activity bar, then in the Azure: Functions area, choose the Deploy to function app button. If you aren't already signed in, choose the Azure icon in the Activity bar, then in the Azure: Functions area, choose Sign in to Azure If you're already signed in, go to the next step.
Provide the following information at the prompts:

a. Select folder: Choose a folder from your workspace or browse to one that contains your function app.

b. Select Subscription: Choose the subscription to use.

c. Select Create new Function App in Azure (Don't choose the Advanced option)

d. Enter a globally unique name for the function app: Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. (e.g. TenableVMXXXXX).

e. Select a runtime: Choose Python 3.11.

f. Select a location for new resources. For better performance and lower costs choose the same region where Microsoft Sentinel is located.
Deployment will begin. A notification is displayed after your function app is created and the deployment package is applied.
Go to Azure Portal for the Function App configuration.

2. Configure the Function App

In the Function App, select the Function App Name and select Configuration.
In the Application settings tab, select New application setting.
Add each of the following application settings individually, with their respective string values (case-sensitive):
- TenableAccessKey
- TenableSecretKey
- WorkspaceID
- WorkspaceKey
- logAnalyticsUri (optional)
- Use logAnalyticsUri to override the log analytics API endpoint for dedicated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format: https://<WorkspaceID>.ods.opinsights.azure.us.
Once all application settings have been entered, click Save.

Next steps

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

Dijelite putem