Page Comparison

...

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.	`vuln.tenable.io.agents`
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: Version 1.1.2 and before: Using directly the `assets` endpoints (and `vulns` endpoint for enrichment). However, this method is not suggested for big amounts of data; for this see the next option. Version 1.2.0 and above: Using exports endpoint to get `assets` (and `vulns` for enrichment). Running one single pull cycle of this collector could take hours, depending on the amount of assets of the customer and the current load of Tenable’s servers, so it’s recommended to configure this service to run a maximum of 1 or 2 times per day. This service takes snapshots of all the assets.	`vuln.tenable.io.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.	`vuln.tenable.io.audit_log`
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.	`vuln.tenable.io.plugins`
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.	`vuln.tenable.io.scanners`
Scans	Retrieves scans.	`vuln.tenable.io.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.	`vuln.tenable.io.vulnerabilities`

Working with API credentials

...

The Basic permission applied for the X-ApiKeys would be enough to extract necessary data safely.

Name	Value	Description
`Basic`	16	Users with this role can view and configure scan results.

Note
You’ll need the `Administrator[64]` permission in order to request Audit_log data.

...

Rw ui tabs macro

Rw tab

title	Cloud collector

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.

Rw tab

title	On-premise collector

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.

Structure

The following directory structure should be created for being used when running the Tenable.io collector:

Code Block

<any_directory>
└── devo-collectors/
    └── tenable/
        ├── certs/
        │   ├── chain.crt
        │   ├── <your_domain>.key
        │   └── <your_domain>.crt
        └── config/ 
            └── config-tenable.yaml

Devo credentials

In Devo, go to Administration → Credentials → X.509 Certificates, download the Certificate, Private key and Chain CA and save them in <any directory>/devo-collectors/tenable/certs. Learn more about security credentials in Devo here.

Editing the config.yaml file

In the config.yaml file, replace the <short_unique_identifier>, <x_api_key>.crt, and <secret_key> values and enter the ones that you got in the previous steps. In the <short_unique_identifier> placeholder, enter the value that you choose.

Code Block

globals:
  debug: false                                                    # Setup as True or False for debugging mode
  id: not_used
  name: tenable-io
  persistence:                                                    # Persistence setup filesystem
    type: filesystem
    config:
      directory_name: state                                       # Persistence directory
outputs:
  devo_1:
    type: devo_platform
    config:
      address: collector-eu.devo.io                               # Devo platform address EU (for US use: collector-us.devo.io)
      port: 443
      type: SSL
      chain: chain.crt
      cert: <your_domain>.crt                                     
      key: <your_domain>.key
inputs:
  tenable_io:
    id: <1>                                                       # The value of this field will be used internally for having independent persistence areas
    enabled: true
    debug: true
    credentials:
      access_key: <access_key>                                    # Tenable access key
      secret_key: <secret_key>                                    # Tenable secret key
    services:
      agents:
        request_period_in_seconds: 43200                          # 12 hours - Setting up request period in seconds.
      export_assets:
        request_period_in_seconds: 86400                          # 24 hours
      audit_log:
        request_period_in_seconds: 60                             
        start_time: "2021-03-10"                                  # Start time for pulling data from - format date YYYY-MM-DD
      plugins:
        request_period_in_seconds: 60   86400                          # 124 minhours
        start_time: "2021-03-15"                                  # Start time for pulling data from
      scanners:
        request_period_in_seconds: 43200       
      scans:
        request_period_in_seconds: 43200
      export_vulnerabilities:
        request_period_in_seconds: 43200                          # 12 hours
        since_epoch: 0
        severities:
          - critical
          - high
          - medium
          #- low
          #- info
        statuses:
          - open
          - 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
collector-tenable-docker-image-1.23.50.tgz	`758bb31bb9a4820fac65aea63ab2d1c71cb11ad3da074ac83305fcc71263aea9a5e6ff3846fd7f67f9c7b6e021282a3113650a001810173705c32757da720e6e`

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 "`<version>`" with a proper value.

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 `<version>` with the required value.

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:
      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
      - ./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 `<version>` with the required value.

Change log

...

Release

...

Released on

...

Release type

...

Details

...

 up -d

Note
Replace `<version>` with the required value.

Change log

Release

Released on

Release type

Details

Recommendations

v1.3.0

13 Oct 2023

Status

colour	Green
title	NEW FEATURE

Status

colour	Yellow
title	IMPROVEMENT

New features:

Added new data source export_vulnerabilities as new service

Improvements:

Upgrade DC SDK to the latest version 1.9.2

Recommended version

v1.2.5

05 Apr 2023

Status

colour	Yellow
title	IMPROVEMENTS

Improvements:

Upgrade DC SDK to the latest version 1.7.2.dev1 to avoid errors in the sender module. Those errors made the collector restart constantly.
Upgrade DC SDK to the latest version 1.7.2.dev1:
- Added a lock to enhance sender object.

Recommended version

v1.2.0

22 Mar 2023

Status

colour	Green
title	NEW FEATURE

Status

colour	Red
title	BUG FIXING

New features:

A new export_assets service has been created to allow massive data ingestion, enriched with vulnerabilities information. This data is collected through a different endpoint called exports, whose purpose is exporting big amounts of data. This service takes snapshots of all the assets available and it is recommended to configure it to run a maximum of 1-2 times per day.
The underlaying Devo Collector SDK has been upgraded from v1.1.4 to v1.6.4.dev1.

Bug fixing:

The collector was using a standard assets endpoint to get a lot of data and this was resulting in constant 500-level errors. The new service export_assets solves this.

Upgrade

Versions Compared

Old Version 11

New Version 12

Key

Working with API credentials

Structure

Devo credentials

Editing the config.yaml file

Download the Docker image

Docker

Docker Compose

Change log

Change log