<h2>Vulnerability Response Discovered Item Source Data not updating</h2><br/><div style="overflow-x:auto"><article><div ><h3 >Issue </h3><section><ul style="list-style-position: inside;"><li>In Qualys integration or Rapid7 integration, if the host info (Qualys) or asset (Rapid7) is updated for a given asset ID in the incoming payload, it is expected that the source_data of corresponding Discovered Item is updated to reflect this change. This allows us to reapply CI Lookup Rules to re-map that DI to a different CI. <ul style="list-style-position: inside;"><li>This support article explains this process: <a href="https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0998706#mcetoc_1fj5hopce20">https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0998706#mcetoc_1fj5hopce20</a></li></ul> </li><li>For some Discovered items the source_data is not being updated.</li></ul></section></div><div ><h3 >Cause</h3><section><ul style="list-style-position: inside;"><li>For an existing CI source OOTB source data is only updated from the Qualys Host List Import or from the Rapid7 Asset List integration import.</li><li>In the instance the Discovered Item record was updated by another Qualys or Rapid7 integration besides Qualys Host List or Rapid7 Asset List.</li></ul></section></div><div ><h3 >Resolution</h3><section><ul style="list-style-position: inside;"><li>OOTB you will need to run the Qualys Host List integration or the Rapid7 Asset List integration in order to update the source data on the Discovered Item record.</li><li>Alternatively you can customise the ImportHost script include to update source_data from host detection. <ul style="list-style-position: inside;"><li>This customisation is out of scope for technical support.</li></ul> </li></ul></section></div></article></div>