Tenable has made several improvements to the View activity log endpoint that enables users to have more granular control when searching activity logs.

A new boolean body parameter is now available for the Tenable Vulnerability Management Export assets v1 endpoint that enables customers to include or exclude open port findings from info-level plugins. The new parameter is include_open_ports. If the new parameter is omitted, Tenable Vulnerability Management uses a default value of false to exclude open port findings from the asset export.

The user permissions requirement for the Import assets endpoint has been reduced from ADMINISTRATOR [64] to SCAN MANAGER [40]. For more information about permissions and roles, see Permissions.

On January 4, 2024, Tenable Vulnerability Management will change how it processes fully qualified domain names (FQDNs) for assets. All FQDNs will be normalized to lowercase and then the duplicates will be merged.

Tenable has added the query parameter fileType to the Tenable Vulnerability Management Upload credentials file endpoint.

Tenable has deployed a new Tenable Vulnerability Management host URL - https://sensor.cloud.tenablecloud.cn - along with the Cloudflare China Network, which provides Tenable with better visibility for troubleshooting and monitoring purposes. The legacy host URL for sensors in mainland China - http://sensor.cloud.tenable-cn.com - will be deprecated on January 31, 2024.

Documentation is now available for new report endpoints. The new endpoints enable customers to programmatically generate reports of vulnerabilities affecting their assets. The reports are generated in PDF format. You can use the following templates when generating a report:

On December 5, 2023, customers that enabled the Relocate Open Port Findings setting in the user interface will begin to see open port data for info-level findings in their asset export data.

New filters are now available for the Tenable Vulnerability Management Export vulnerabilities endpoint. These new filter parameters are:

Tenable reorganized some of the content in the Tenable API Explorer. The content was reorganized to match functional areas of the user interface and to split categories that contained a large number of endpoints into multiple categories depending on the functional area.