...
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. |
|
Vulnerabilities | Tenable.io allows you to centralize data for vulnerabilities that scans detect on your network assets. Use the API to import vulnerability data from both Tenable scans and scans by third-party applications. |
|
Working with API credentials
...
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.
...
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. |
Note |
---|
You’ll need the |
...
Rw ui tabs macro | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
We use a piece of software called Collector Server to host and manage all our available collectors. If you want us to host this collector for you, get in touch with us and we will guide you through the configuration.
This data collector can be run in any machine that has the Docker service available because it should be executed as a docker container. The following sections explain how to prepare all the required setup for having the data collector running. StructureThe following directory structure should be created for being used when running the Tenable.io collector:
Devo credentialsIn Devo, go to Administration → Credentials → X.509 Certificates, download the Certificate, Private key and Chain CA and save them in Editing the config-tenable-io.yaml fileIn the config-tenable.yaml file, replace the Code Block | To enable the collector for a customer:
Editing the JSON configuration
This data collector can be run in any machine that has the Docker service available because it should be executed as a docker container. The following sections explain how to prepare all the required setup for having the data collector running. StructureThe following directory structure should be created for being used when running the Tenable.io collector:
Devo credentialsIn Devo, go to Administration → Credentials → X.509 Certificates, download the Certificate, Private key and Chain CA and save them in Editing the config.yaml fileIn the config.yaml file, replace the
Download the Docker imageThe collector should be deployed as a Docker container. Download the Docker image of the collector as a .tgz file by clicking the link in the following table: | ||||||||||||||||||||||||
Collector Docker image | SHA-256 hash | ||||||||||||||||||||||||
|
Code Block |
---|
$ gunzip -c collector-tenable-docker-image-<version>.tgz | docker load |
Note |
---|
Once the Docker image is imported, it will show the real name of the Docker image (including version info). Replace " |
The Docker image can be deployed on the following services:
Docker
Execute the following command on the root directory- reopened |
Download the Docker image
The collector should be deployed as a Docker container. Download the Docker image of the collector as a .tgz file by clicking the link in the following table:
Collector Docker image | SHA-256 hash |
---|---|
|
Use the following command to add the Docker image to the system:
Code Block |
---|
$ gunzip -c collector-tenable-docker-image-<version>.tgz | docker load |
Note |
---|
Once the Docker image is imported, it will show the real name of the Docker image (including version info). Replace " |
The Docker image can be deployed on the following services:
Docker
Execute the following command on the root directory <any_directory>/devo-collectors/tenable/
Code Block |
---|
docker run \
--name collector-tenable-io \
--volume $PWD/certs:/devo-collector/certs \
--volume $PWD/config:/devo-collector/config \
--volume $PWD/state:/devo-collector/state \
--env CONFIG_FILE=config-tenable-io.yaml \
--rm -it docker.devo.internal/collector/tenable-io:<version> |
Note |
---|
Replace |
Docker Compose
The following Docker Compose file can be used to execute the Docker container. It must be created in the <any_directory>/devo-collectors/tenable//
directory.
Code Block |
---|
docker run \ --nameversion: '3' services: collector-tenable-io: \ --volume $PWD/certs:/devo-collector/certs \ --volume $PWD/config:/devo-collector/config \ --volume $PWD/state:/devo-collector/state \ --env CONFIG_FILE=config-tenable-io.yaml \ --rm -it docker.devo.internal/collector/tenable-io:<version> |
Note |
---|
Replace |
Docker Compose
The following Docker Compose file can be used to execute the Docker container. It must be created in the <any_directory>/devo-collectors/tenable/
directory.
Code Block |
---|
version: '3' services: collector-tenable-io: build: build: context: . dockerfile: Dockerfile image: docker.devo.internal/collector/tenable-io:${IMAGE_VERSION:-latest} container_name: tenable-io-collector volumes: - ./certs:/devo-collector/certs - ./config:/devo-collector/config - context: ../state:/devo-collector/state environment: dockerfile: Dockerfile image: docker.devo.internal/collector/tenable-io:${IMAGE_VERSION:-latest} container_name: tenable-io-collector volumes: - ./certs:/devo-collector/certs - ./config:/devo-collector/config - ./state:/devo-collector/state environment: - CONFIG_FILE=${CONFIG_FILE:-config-tenable-io.yaml} |
To run the container using docker-compose, execute the following command from the <any_directory>/devo-collectors/tenable/
directory:
Code Block |
---|
IMAGE_VERSION=<version> docker-compose up -d |
Note |
---|
Replace |
Change log
...
Release
...
Released on
...
Release type
...
Details
...
Recommendations
To run the container using docker-compose, execute the following command from the
|
Change log
Release | Released on | Release type | Details | Recommendations | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
| |||||||||||||
|
| New features:
Improvements:
|
| |||||||||||||
|
| Improvements:
|
| |||||||||||||
|
| New features:
Bug fixing:
|
Recommended version
|