🛑

Caution

The information contained in this changelog has been superseded. Refer to Scan Results Archived at 35 Days for the most recent information about scan result archival.

The type parameter is no longer included in the request body when creating a Tenable.io user.

Tenable.io now supports the bigfix_asset_id attribute on asset objects. The property is present on the objects returned by the following endpoints:

Tenable.io now returns a 400 error response if you submit a request to list tag categories or values with invalid or malformed query filtering parameters.

The Connectors documentation now describes the Google Cloud Platform (GCP) connector type parameter. For more information, see the POST /settings/connectors endpoint.

The Tenable.io API now provides connector error codes in the status_message property of connector objects returned by the GET /setting/connectors and GET /setting/connectors/{connector_id} endpoints. The error codes are provided to help troubleshoot connector problems (for example, caused by authentication errors or insufficient permissions).

Tenable.io can discover assets without assessing the assets for vulnerabilities (for example, via a host discovery scan, Nessus Network Monitor running in discovery mode, or connectors). Assets that have been seen but not assessed do not count towards your asset license limit.

You can use Tenable Lumin to quickly and accurately assess your Cyber Exposure risk and compare your health and remediation performance to other Tenable customers in your Salesforce industry and the larger population. Lumin correlates raw vulnerability data with asset business criticality and threat context data to support faster, more targeted analysis workflows than traditional vulnerability management tools. For more information, see Lumin in Tenable.io in the Tenable.io Vulnerability Management User Guide.

You can now upload files for use with managed credentials, using the following endpoint:

Tenable.io API now allows you manage user access authorizations. Access methods include user name and password, single sign-on (SSO) with SAML, and API.