Is your feature request related to a problem? Please describe.
Tenable recently introduced a "/hosts/download::POST" endpoint for exporting Host Assets.
This feature is not (yet) available in pyTenable.
https://docs.tenable.com/tenablesc/api/Changelog.htm
Describe the solution you'd like
Build a class in pyTenable which uses this new endpoint.
Revise the current functions in other classes to check if we can directly export assetID's (although I'm not sure Tenable supports this, I don't think they introduced this yet)
Describe alternatives you've considered
At the moment we calculate our own ID (md5 hash) based on the parameters within "hostUniqueness" which is exported via the endpoint analysis/vulns/vulndetails. This ensures we copy the uniqueness logic from Tenable.
Since Tenable now introduced this in their API, it makes more sense to copy the same value rather than calculating it ourselves.
Is your feature request related to a problem? Please describe. Tenable recently introduced a "/hosts/download::POST" endpoint for exporting Host Assets. This feature is not (yet) available in pyTenable. https://docs.tenable.com/tenablesc/api/Changelog.htm
Describe the solution you'd like Build a class in pyTenable which uses this new endpoint. Revise the current functions in other classes to check if we can directly export assetID's (although I'm not sure Tenable supports this, I don't think they introduced this yet)
Describe alternatives you've considered At the moment we calculate our own ID (md5 hash) based on the parameters within "hostUniqueness" which is exported via the endpoint analysis/vulns/vulndetails. This ensures we copy the uniqueness logic from Tenable. Since Tenable now introduced this in their API, it makes more sense to copy the same value rather than calculating it ourselves.
Additional context /