Tenable.io Web Application Scanning has added a new assessment setting to allow users to exclude DOM elements and their children. DOM element exclusions allow you to prevent scans from interacting with specific page elements like logout buttons or forms. You can configure DOM element exclusions when you create a scan configuration.

Tenable.io Web Application Scanning now supports folders for scan jobs. This feature allows you to create custom folders for organizing your scans. Additionally, there are three Tenable-provided default folders: All Scans, My Scans, and Trash.

Tenable.io previously categorized as "archived" any scan results that were older than 60 days. Tenable.io now archives scan results older than 35 days.

Two new endpoints have been added to the Tenable.io API for agent bulk operations. These endpoints allow you to create a bulk operation task to add agents to a network or remove agents from a network.

The behavior for the since filter, used in the Tenable.io vulnerability export API, will change on January 25, 2021.

There are two existing endpoints available for retrieving the filtering, sorting, and pagination capabilities available for assets and vulnerabilities. These two endpoints are GET /filters/workbenches/assets and GET /filters/workbenches/vulnerabilities.

The Tenable.io Web Application Scanning v2 API page request and response format has been updated to match the Tenable.io Vulnerability Management format. This change brings consistent pagination across the various Tenable.io APIs. The old page request and response format has been deprecated in favor of the new page request and response format.

The scan report format for the Web Application Scanning v2 API endpoint GET /was/v2/scans/{scan_id}/report has been updated from version 1.0 to version 1.1. Previously, in scan report report format version 1.0, all cross-references were returned within the xrefs object. In scan report format version 1.1, all cross-references are returned as structured references to make parsing easier for the user.

Tenable.io Vulnerability Management now limits the number of scans you can create to 10,000 scans. If you're close to the maximum limit, Tenable recommends you re-use scheduled scans instead of creating new scans. An HTTP 403 error is returned if you attempt to create a scan after you have already reached the scan limit of 10,000.

Tenable.io now offers the option to automatically delete assets in a network after a specified number of days. The assets_ttl_days body parameter can be specified when creating or updating a network. Additionally, a new endpoint has been added that allows you to return the total number of assets in a network along with the number of assets that have not been seen for a specified number of days.