Host Uniqueness Criteria Update in Tenable SC 6.4Issue Changes in Host Uniqueness Criteria for Tenable SC 6.4 OverviewWith the release of Tenable SC version 6.4, a significant change was implemented in how hosts are uniquely identified during vulnerability scanning and reporting. Previous Configuration Prior to version 6.4, host uniqueness was defined by three parameters:- repositoryID- IP address- DNS name Current ConfigurationStarting with Tenable SC 6.4, host uniqueness has been simplified to use:- repositoryID- hostUUID ImpactThis change provides more accurate host identification by:- Reducing duplicate asset entries- Improving consistency in vulnerability tracking- Ensuring more reliable asset management- Better handling of dynamic IP environments ReleaseVulnerability Response Integration with Tenable and Tenable SC version 6.4.CauseThe new "host_uniqueness" field, intended to contain "repositoryID,hostUUID", is missing the hostUUID component because the system property "glide.import_set_row.dynamically_add_fields" is disabled.ResolutionImplementationTo properly implement this change, ensure that:- The hostUUID field is properly populated during imports- System property "glide.import_set_row.dynamically_add_fields" is temporarily enabled- Existing vulnerability records are properly mapped to their corresponding CIsRelated LinksSystem property "glide.import_set_row.dynamically_add_fields" may be disable in order to control the fields being populated during import jobs. Import sets propertieshttps://www.servicenow.com/docs/csh?topicname=r_ImportSetsProperties.html&version=latest