marketplace
CDS Tenable One Platform - IO - Vulnerability Overview
CDS Tenable One Platform - IO - Asset Overview
CDS Tenable One Platform - IO - Plugins Overview
CDS Tenable One Platform - SC - Vulnerability Overview
CDS Tenable One Platform - SC - Asset Overview
CDS Tenable One Platform - SC - Plugins Overview
This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project,
feel free to reach out to us!Overview
Tenable is a cybersecurity company that offers a variety of products and services to assist organizations in managing and reducing their cyber risk.
This integration supports Tenable.io and Tenable.sc.
Tenable.io is a cloud-based platform that offers continuous visibility and monitoring of an organization’s assets, both on-premises and in the cloud. It combines vulnerability management, web application scanning, container security, and other capabilities to provide comprehensive security monitoring and risk assessment.
Tenable.sc is a comprehensive vulnerability management platform that provides continuous network monitoring, vulnerability assessment, and reporting capabilities. It helps organizations identify, assess, and prioritize vulnerabilities across their IT infrastructure, enabling effective remediation efforts.
This integration collects the following data:
- Vulnerabilities
- Assets
- Plugins
Upgrade Integration
- Take the backup of your existing ‘conf.yaml’ file from your Datadog Agent’s
crest_data_systems_tenable_one_platform.d directory under conf.d directory. - Uninstall the current version of
crest_data_systems_tenable_one_platform and install the latest version from the Datadog platform. - This latest version of the integration has more configuration parameters that give you more control over data collection and hence would need reconfiguration of conf.yaml for data collection to resume after the upgrade. You can refer to the example of
conf.yaml from the Set up conf.yaml section that is mentioned above.
NOTE:
- Make sure your
conf.yaml has all the parameters mentioned in the above Set up conf.yaml section. - Create a separate instance in order to collect data for each data type i.e. (vulns/assets/plugins) and make sure ‘io_collect_assets’ for IO and ‘sc_collect_assets’ for SC have been enabled in order to continue the other types of data collection.
- For instance, if you want to collect IO data, update your
conf.yaml as shown below, where there are different instances for different data types.- Older Version 1.0.5:
init_config:
instances:
- is_io_enabled: True
io_access_key: <io-access-key>
io_secret_key: <io-secret-key>
is_sc_enabled: False
min_collection_interval: 7200
- Newer Version 1.1.0:
init_config:
instances:
- is_io_enabled: True
io_access_key: <io-access-key>
io_secret_key: <io-secret-key>
is_sc_enabled: False
io_collect_assets: True
min_collection_interval: 7200
- is_io_enabled: True
io_access_key: <io-access-key>
io_secret_key: <io-secret-key>
is_sc_enabled: False
io_collect_vulns: True
min_collection_interval: 7200
- is_io_enabled: True
io_access_key: <io-access-key>
io_secret_key: <io-secret-key>
is_sc_enabled: False
io_collect_plugins: True
min_collection_interval: 7200
NOTE: Checkpoint will be reset after the upgrade.
Support
For support or feature requests, please contact Crest Data through the following channels:
This application is made available through the Datadog Marketplace and is supported by a Datadog Technology Partner. To use it, purchase this application in the Marketplace.
