Overview
Managed in the cloud and powered by Nessus technology, Tenable.io provides the industry's most comprehensive vulnerability coverage with the ability to predict which security issues to remediate first. It’s a complete end-to-end vulnerability management solution that provides a risk-based view of your entire attack surface—from IT to cloud to containers—so you can quickly identify, investigate and prioritize vulnerabilities.
Data source description
Tenable.io data will be stored in the Devo platform in different tables according to its type. All these tables will follow this format:
vuln.tenable.io.{resource_name}
Tenable exposes REST APIs resources to extract data such as:
Resource type | Definition | Devo data tables |
|---|---|---|
Agents | Nessus Agents are lightweight, low-footprint programs that you install locally on hosts to supplement traditional network-based scanning or to provide visibility into gaps that are missed by traditional scanning. Nessus Agents collect vulnerability, compliance, and system data, and report that information back to Tenable.io for analysis. |
|
Assets | Assets are defined as network entities that potentially represent security risks. Assets can include laptops, desktops, servers, routers, mobile phones, virtual machines, software containers, and cloud instances. Tenable.io allows you to track assets that belong to your organization, helping to eliminate potential security risks, identify under-utilized resources, and support compliance efforts. There are two approaches to download assets:
|
|
Audit_log | The audit log records events taking place in your organization's Tenable.io account. For each event, the log includes information about what action was taken, when the action was taken, the ID of the user, and the ID of the target entity. The audit log provides visibility into the actions that users in your organization are taking in Tenable.io, and can be helpful for identifying security issues and other potential problems. |
|
Plugins | Tenable.io plugins are programs for detecting vulnerabilities written in the Nessus Attack Scripting Language (NASL). Plugins contain vulnerability information, solution information, and the algorithm to test for the presence of the security issue. |
|
Scanners | By default, Tenable.io is configured with a region-specific cloud scanner. In addition to using the default cloud scanner, you can also link Nessus scanners, NNM scanners, and Nessus Agents to Tenable.io. |
|
Scans | Retrieves scans. |
|
Working with API credentials
To set up access to the Tenable.io API:
Verify that you have a valid user account with appropriate permissions by logging into Tenable.io.
Generate the API keys for the account. For more information, see Generate API Keys in the Tenable.io Vulnerability Management User Guide.
Tenable.io generates a unique set of API keys for each user account. These keys allow your application to authenticate to the Tenable.io API without creating a session.
To authorize your application to use the Tenable.io API, you must include the X-ApiKeys header element in your HTTP request messages.
Authorize user role permissions
The Basic permission applied for the X-ApiKeys would be enough to extract necessary data safely.
Name | Value | Description |
|---|---|---|
| 16 | Users with this role can view and configure scan results. |
You’ll need the Administrator[64] permission in order to request Audit_log data.
Run the collector
Once the data source is configured, you can either send us the required information if you want us to host and manage the collector for you (Cloud collector), or deploy and host the collector in your own machine using a Docker image (On-premise collector).
Change log
Release | Released on | Release type | Details | Recommendations |
|---|---|---|---|---|
| IMPROVEMENTS | Improvements:
|
| |
| NEW FEATURE | New features:
Bug fixing:
|
|