Qualys Deep Scan Results/Proof Missing from Vulnerability Detection Records

Martin Dewit
Mega Sage

Has anyone implemented or tested the newer Qualys Deep Scan capability with the ServiceNow Vulnerability Response Qualys integration?

We recently enabled Deep Scan in Qualys and found that the resulting vulnerability detections are successfully ingested into ServiceNow. However, the additional Results/Proof available for the Deep Scan finding in Qualys are not populated on the corresponding ServiceNow Detection record, leaving the Proof field empty.

 

From our investigation, the current ServiceNow Qualys integration uses the Host List Detection API:

/api/2.0/fo/asset/host/vm/detection/

 

Qualys also has the newer Host List Detection API:

/vmrs/api/1.0/host/list/detections

 

Has anyone else encountered this with Deep Scan findings?

I'm particularly interested in whether:

  • Deep Scan Results/Proof are currently supported by the ServiceNow Qualys integration.

  • The newer Qualys detection API is supported or planned for the integration.

  • There is a recommended configuration or workaround for bringing the Deep Scan Results/Proof into ServiceNow.

The detection itself is being ingested correctly; the issue appears limited to the additional evidence/results associated with the Deep Scan detection.

1 REPLY 1

kmohammed
Tera Guru

Your diagnosis points at the right place. An integration can only map what its source response actually returns. If the older Host List Detection response does not carry the Deep Scan Results/Proof element for that detection, no transform map or field mapping change in the current integration will create it - the field will stay empty even though the detection itself ingests fine, which is exactly the symptom you describe.

 

So the first step is to prove where the data stops, before changing anything in ServiceNow:

 

1. In a non-production environment, call the older API for one affected host/QID and inspect the raw response for the proof element. If it is absent there, the gap is in the source payload, not in the VR mapping.

2. Call the newer VMDR detection API for the same host/QID and check whether the Deep Scan Results/Proof is present there. That tells you whether a second fetch can even supply the missing evidence.

 

If the newer API does return it, the workable pattern is a separate, supplementary fetch rather than replacing the out-of-box import: an IntegrationHub REST step (or a scheduled import) that queries the newer API for Deep Scan detections, matches each result to the existing ServiceNow detection record by host + QID (and scan time where available), and writes the proof into the detection's Proof field. Keep it as an enrichment step on top of the existing import, so the standard detection ingestion keeps working unchanged, and run it in sub-production first with a small set of Deep Scan findings.

 

On your other two questions, I would not state a support or roadmap position from the thread alone - that is worth confirming against the current Qualys integration store release notes for your release, or with Support, since integration coverage changes by release. What the payload check above gives you is the evidence to take to that conversation either way: if the proof is missing from the older API response, it is a source-payload gap, not a mapping error.