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.

Tenable has updated the permissions required for a number of Tenable.io Container Security API endpoints (both v1 and v2). The affected endpoints are listed in the tables below.

If configured to use Nessus Plugin ID 45590, Tenable.io scans identify software applications installed on an asset, and log that information to a new attribute in the asset record. This attribute, installed_software, contains a list of Common Platform Enumeration (CPE) values in the CPE 2.2 format. For more information, see the "Component Syntax" section of the CPE Specification, Version 2.2.

Tenable.io Container Security API v2 is now available. It replaces the deprecated Tenable.io Container Security API v1.