Updating CI class for unmatched cloud assets
Starting with Vulnerability Response v20.0, you can categorize the unmatched cloud assets from Qualys, Rapid7 and Tenable scanners into Unclassed Hardware by using the sn_sec_cmn.unmatched_cloud_resource_enabled system property.
This system property with false as a default value is shipped with the base system. It classifies the unmatched cloud assets into a Unclassed hardware (cmdb_ci_unclassed_hardware) or Cloud Resource (cmdb_ci_cmp_resource) class for the integrations that bring in both infrastructure and cloud assets.
Starting with Vulnerability Response v20.0, the Asset Type column is added in the Third-party Integrations (sn_sec_int_integration) table to identify the integrations that support both infrastructure and cloud assets. The Asset
Type column has the value, Hybrid for the scanners that bring in both infrastructure and cloud assets. For example, Qualys, Rapid7, and Tenable integrations have the value as Hybrid in the Asset Type column.
- For new installation of Vulnerability Response v20.0 and above, all the unmatched cloud assets are categorized into:
- Unclassed Hardware class by default.
- Cloud Resources class, if you change the sn_sec_cmn.unmatched_cloud_resource_enabled system property to true.
- For upgrades to Vulnerability Response v20.0:
- If there are any assets in the Cloud Resource class, the sn_sec_cmn.unmatched_cloud_resource_enabled system property is set to true so that the unmatched cloud assets continue to add to the Cloud Resource (cmdb_ci_cmp_resource) class.
- Otherwise, the sn_sec_cmn.unmatched_cloud_resource_enabled system property is set to false so that the unmatched cloud assets are categorized into Unclassed Hardware class.