Configuration Items details are not getting updated by Qualys Integration - Support and Troubleshooting

Configuration Items details are not getting updated by Qualys Integration Issue  Symptoms Once the Qualys integration for the Vulnerability module is configured, if the "Qualys Host Detection Integration" is executed, newly matched CI's are not consistently updated with the Qualys Asset specific data as expected, and values for Qualys ID, Qualys Host ID ,Qualys Host tag and Fully Qualified Domain Name (if available) remain blank on the matched CI.

Cause This is expected behaviour. CI information is supposed to be updated by Discovery tool but not Qualys.

Resolution This is by design. All information related to a CI will be stored in the associated Discovered Items record for that CI (sn_sec_cmn_src_ci). Note: For customers, if this functionality is extremely important and you need assistance implementing it, please reach out to your SAM so that our Customer Outcomes (Previously known as "Professional Services") team can provide further assistance. Keep in mind that this is a chargeable service.

Updating the CI information in CMDB can be done in two approaches .One approach is to just update the tags information of CI in CMDB and the other approach is to update tags information along with other fields(Qualys Id, Qualys Host Id, fqdn, ip, os, netbios) of CI in CMDB.They are discussed in detail in subsequent sections

The table sn_sec_cmn_src_cmdb_map contains the mapping between the fields in Qualys response and columns of CI in CMDB

1. Updating the tags information along with other fields(Qualys Id, Qualys Host Id, fqdn, ip, os, netbios) on CI

a. Add the additional boolean parameter to the below method as shown

File: QualysHostImportReportProcessor

var matchResult = new sn_vul.ImportHost().hostImport(sourceInstance, host, "ID", integrationRun, true);

b. Re-run the Qualys Host Detection Integration

This will update the CI information in CMDB.

2. Updating just the tags information of matched CI's in CMDB

This can be done by following the below two steps in order

a.Add a schedule job that runs once and update all the existing matched CI's in CMDB with their host data present in sn_vul_qualys_m2m_ci_host_tag. Attached the scheduled job( sysauto_script_66e4c7bf53320010a3b7ddeeff7b12a6.xml ) which can be imported on the instance and run.

b.Add a business rule on table sn_vul_qualys_m2m_ci_host_tag which will run on insert/update/delete and update the tags data for every newly matched CI on imports.Attached the business rule ( sys_script_707072b253fe0010a3b7ddeeff7b12db.xml ) which can be imported on the instance.

Ref. documentation pages related to Discovered Items: https://docs.servicenow.com/csh?topicname=secops-vuln-resp-rn.html&version=latest https://docs.servicenow.com/csh?topicname=cj-discovered-items.html&version=latest#discovered-items