Loading

Tenable Vulnerability Management

Version 4.2.1 (View all)
Compatible Kibana version(s) 8.19.0 or higher
9.1.0 or higher
Supported Serverless project types
What's this?
Security
Observability
Subscription level
What's this?
Basic
Level of support
What's this?
Elastic

The Tenable Vulnerability Management integration allows users to monitor asset, audit, plugin, scan and vulnerability activity. It provides the industry's most comprehensive vulnerability coverage with the ability to predict which security issues to remediate first. Tenable Vulnerability Management is the user's complete end-to-end vulnerability management solution.

Use the Tenable Vulnerability Management integration to collects and parses data from the REST APIs. Then visualize that data in Kibana.

The Tenable Vulnerability Management integration collects logs for five types of events: Asset, Audit, Plugin, Scan, and Vulnerability.

Asset is used to get details related to assets that belong to the user's organization. See more details in the API documentation here.

Audit is used to obtain details about when each activity occurred, the actions taken, the individuals involved, and other relevant information. See more details in the API documentation here.

Plugin is used to get detailed plugin information. See more details in the API documentation here.

Vulnerability is used to retrieve all vulnerabilities on each asset, including the vulnerability state. See more details in the API documentation here.

Scan is used to retrieve details about existing scans, including scan statuses, assigned targets, and more. See more details in the API documentation here.

This module has been tested against Tenable Vulnerability Management release December 6, 2022.

Elastic Agent must be installed. For more details, check the Elastic Agent installation instructions.

Notes:

  • In this integration, export and plugin endpoints of vulnerability management are used to fetch data.
  • The default value is the recommended value for a batch size by Tenable. Using a smaller batch size can improve performance. A very large value might not work as intended depending on the API and instance limitations.
  • If any long-running export jobs are stuck in the "PROCESSING" state and reach the user-provided timeout, the export job will be terminated, allowing for the initiation of a new export job after the specified interval.

Agentless integrations allow you to collect data without having to manage Elastic Agent in your cloud. They make manual agent deployment unnecessary, so you can focus on your data instead of the agent that collects it. For more information, refer to Agentless integrations and the Agentless integrations FAQ.

Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. This functionality is in beta and is subject to change. Beta features are not subject to the support SLA of official GA features.

  1. Create a valid user account with appropriate permissions on Tenable Vulnerability Management.
  2. Generate the API keys for the account to access all Tenable Vulnerability Management APIs.

Note:

  • For the Tenable Vulnerability Management asset and vulnerability API, ADMINISTRATOR [64] and Can View access control is required in created user's access key and secret key.
  • For the Tenable Vulnerability Management plugin, BASIC [16] user permissions are required in created user's access key and secret key.
  • For the Tenable Vulnerability Management audit, ADMINISTRATOR [64] user permissions are required in created user's access key and secret key.
  • For more details related to permissions, refer to the link here.
  1. In Kibana navigate to Management > Integrations.
  2. In the search top bar, type Tenable Vulnerability Management.
  3. Select the Tenable Vulnerability Management integration and add it.
  4. Add all the required integration configuration parameters according to the enabled input type.
  5. Save the integration.

Version 4.0.0 of the Tenable Vulnerability Management integration adds support for Elastic Cloud Security workflow. The enhancement enables the users of Tenable Vulnerability Management integration to ingest their enriched asset vulnerabilities from Tenable platform into Elastic and get insights directly from Elastic Vulnerability Findings page. This update adds Elastic Latest Transform which copies the latest vulnerability findings from source indices matching the pattern logs-tenable_io.vulnerability-* into new destination indices matching the pattern security_solution-tenable_io.vulnerability_latest-*. The Elastic Vulnerability Findings page will display vulnerabilities based on the destination indices.

For existing users of Tenable Vulnerability Management integration, before upgrading to 4.0.0 please ensure following requirements are met:

  1. Users need Elastic Security solution which has requirements documented here.
  2. To use transforms, users must have:
    • at least one transform node,
    • management features visible in the Kibana space, and
    • security privileges that:
      • grant use of transforms, and
      • grant access to source and destination indices For more details on Transform Setup, refer to the link here
  3. Because the latest copy of vulnerabilities is now indexed in two places, i.e., in both source and destination indices, users must anticipate storage requirements accordingly.

This is the asset dataset.

This is the audit dataset.

This is the plugin dataset.

This is the vulnerability dataset.

This is the scan dataset.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.