Changelog

In Tenable.io API you can now cancel an asset or vulnerability export job, as well as view a list of current export jobs for your Tenable.io instance.

The following changes have been made to the POST /vulnerabilities request message:

We now provide the links for viewing and downloading the OpenAPI specifications published in the Tenable API Explorer.

The Scan Export Filters documentation now describes commonly-used filter query parameters for scan export data.

The API now supports associating connectors with Tenable.io networks by adding the network_id field to the connector object.

You can now use these API endpoints to get a list of available scan and scan history filters:

Added new content describing the GET /scanners/{scanner_id}/agent-groups/{agent_group_id}/agents endpoint for listing agents for an agent group. See List agents for agent group.

You can now configure Tenable.io scans to target assets based on one or more tags you have assigned to the assets. For example, you might want to run more frequent scans of assets running a Windows operating system. Rather than manually configuring a scan to target a static group of Windows assets, you can configure Tenable.io to automatically apply a tag to any asset that a scan identifies as running Windows. Then, you can configure a scan to evaluate any asset with that tag on an appropriate frequency.

Tenable API Explorer now provides client request code samples in PowerShell and Kotlin.

Tenable.io now returns a 400 response message if you submit a request to create or update a dynamic tag rule using an invalid parameter.