Tenable.sc

Version 2.6.0 (View all)
Managed integration release status GA
Subscription level
What's this?
Basic
Developed by
What's this?
Elastic
Ingestion method(s) API
Minimum Kibana version(s) 9.1.4
9.0.7
8.19.4
Important - Managed integrations on Elastic Cloud Hosted

You can use this integration as an Elastic Managed integration on Elastic Cloud Hosted deployments running this version or later.

The Tenable Security Center integration collects and parses data from the Tenable Security Center APIs.

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.

This module has been tested against Tenable.sc version 5.23 and Tenable.sc version 6.4.0.

In order to ingest data from the Tenable.sc you must have the Access key and Secret Key.

Enable API keys to allow users to perform API key authentication.

See Tenable's documentation for more information on:

Note

The default value is the recommended value for a batch size by Tenable. It can be found under Advanced Options and can be configured as per requirements. A very large value might not work as intended depending on the API and instance limitations.

This is the asset dataset.

Asset documents use a stable tenable_sc.asset.custom_hash (computed in the asset ingest pipeline from the export field values named in the Tenable export property uniqueness, stored as tenable_sc.asset.uniqueness) and an ingest _id derived from that identity, mutable scan state (scores, severity counts, MAC address, policy, plugin set, and scan timestamps), and the collection day. The asset input requests only assets whose Tenable lastSeen time falls after the previous poll, so an asset is indexed again only when Tenable reports it again. Repeat reports on the same day with unchanged state deduplicate on _id. A change in scan state indexes a new document. A later Tenable report on a new collection day also indexes a new document, even if the scan state has not changed. The package installs a latest transform that copies the newest document per asset into logs-tenable_sc_latest.asset, keyed on tenable_sc.asset.custom_hash and data_stream.namespace. The latest index removes a document when its @timestamp is older than 90 days, so assets that Tenable has not reported for 90 days drop out of logs-tenable_sc_latest.asset.

Upgrading to version 2.6.0 or later installs and starts this transform. Clusters need a transform node, transform privileges, and access to source and destination indices. Asset data is stored in both the source data stream and the latest destination index; plan storage accordingly. See Transform setup for details.

This is the plugin dataset.

This is the vulnerability 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.