Vulnerable software in Vulnerability response

GTSNOW
Giga Guru

i can see Vulnerability software table is keep on updating daily however i thought it shows data after qualys integration scan. I checked existing integration however it dows not have any other integration. What can be the possible cause.

1 ACCEPTED SOLUTION

andy_ojha
ServiceNow Employee
ServiceNow Employee

Hey there,

The functionality here would be to use the Vulnerable Software as reference data.  This has no relationship you Qualys scan / vulnerability detection data, and would not create a Vulnerable Item.

Given you have the Qualys integration in place, you want Qualys host detections to create VIs through the integration.

A VI would be tied to a CI from the CMDB and a Vulnerability from the Third-party library - in the case of Qualys, this would be a QID-xxxxx.   

A Vulnerability from Qualys (e.g. QID-12345) - may be associated to one or more CVEs.  Each CVE, may be associated to one or more Vulnerable Software.

However.... There is an optional configuration for Software Asset Management (SAM), where VIs would be created if you had CIs with Software populated.  The dependency here would be having rich software data on your CIs.

Since you are integrating with Qualys, you would likely not want to turn this on.

View solution in original post

4 REPLIES 4

andy_ojha
ServiceNow Employee
ServiceNow Employee

Hey there - this data originates from the NVD integration.  

Check out this table -> sn_vul_m2m_entry_software

This holds the association between CVE and Vulnerable Software.

Thanks but why it is not creating VI automatically. If i have data in Vulnerable software , is it possible to create VI automatically.

andy_ojha
ServiceNow Employee
ServiceNow Employee

Hey there,

The functionality here would be to use the Vulnerable Software as reference data.  This has no relationship you Qualys scan / vulnerability detection data, and would not create a Vulnerable Item.

Given you have the Qualys integration in place, you want Qualys host detections to create VIs through the integration.

A VI would be tied to a CI from the CMDB and a Vulnerability from the Third-party library - in the case of Qualys, this would be a QID-xxxxx.   

A Vulnerability from Qualys (e.g. QID-12345) - may be associated to one or more CVEs.  Each CVE, may be associated to one or more Vulnerable Software.

However.... There is an optional configuration for Software Asset Management (SAM), where VIs would be created if you had CIs with Software populated.  The dependency here would be having rich software data on your CIs.

Since you are integrating with Qualys, you would likely not want to turn this on.

Syam4
Kilo Contributor

One source could be data being imported as part of 'NIST National Vulnerability Database Integration - API (CVE and CPE)' OOTB Scheduled Job.