improved
Vulnerability Management: FQDNs in Asset Responses
about 1 year ago by Lance Duvall
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.
For example, where asset1 would previously have three FQDNs: ["VeryImportantAsset.local", "veryimportantasset.local", "externalimportantasset.local"], after the change asset1 will have two FQDNs: ["veryimportantasset.local", "externalimportantasset.local"].
This change streamlines the Host Assets view in the Assets Workbench in the user interface, prevents assets from registering as duplicates, and enables users to better focus on the assets that need their attention.
This change affects the following endpoints:
| Endpoint | Name | Affected Property |
|---|---|---|
| GET /assets | List assets | The assets.fqdn property in the response. |
| GET /assets/{asset_uuid} | Get asset details | The fqdn property in the response. |
| GET /assets/export/{export_uuid}/chunks/{chunk_id} | Download assets chunk | The fqdns and network_interfaces.fqdns properties in the response. |
| GET /workbenches/assets | List assets | The assets.fqdn property in the response. |
| GET /workbenches/assets/vulnerabilities | List assets with vulnerabilities | The assets.fqdn property in the response. |
| GET /workbenches/assets/{asset_id}/info | Get asset information | The info.fqdn property in the response. |