The Tenable.io API now supports compliance data exports. The compliance export API can be used to export data that is an aggregation or summary of all compliance scan data. The summary is updated with the latest audit results as new compliance scans are run. The compliance export API does not return results for individual scans.
A new field has been added to allow customers to filter export results and observe the specific time a document has been indexed into the Tenable.io datastore. The new filter is indexed_at.
You can now use the Tenable.io Web Application Scanning v2 API to get vulnerability details by vuln ID.
The details.response and details.request response attributes are deprecated. These response attributes will be retired from the the Web Application Scanning v2 API on 2021/11/26 and will no longer be returned in responses. Please update any existing integrations that your organization has.
In the Tenable.io Web Application Scanning v2 API, the limit query parameter is used to specify the number of records to retrieve. The maximum value you can specify for the limit parameter is now 200. If you need to retrieve more than 200 records, use the offset parameter to iterate through page responses.
A new scan status has been added in Tenable.io Web Application Scanning. This new status is called Processing. Processing indicates that the scan has completed but the results are still being processed. For example, the scanner is processing vulnerability findings, attachments, notes, and other metadata.
Tag values cannot exceed 50 characters in length.
The filter limit for the GET /workbenches/vulnerabilities endpoint has changed. You cannot specify more than 10 filters or 50 filter values per filter. A 400 Bad Request error is returned if you exceed this limit.
The Get plugin output endpoint is deprecated. Tenable recommends that you use the Export scan endpoint instead. Please update any existing integrations that your organization has since this endpoint will be removed.
Vulnerability management remediation scans allow you to validate whether your vulnerability remediation actions on scan targets have succeeded. If a remediation scan cannot identify a vulnerability on targets where the vulnerability was previously identified, the system changes the status of the vulnerability to Fixed.
