Changes in Qualys not reflected in ServiceNow - Asset Groups and Scanner Appliances

Jkelley
Tera Contributor

Hello All

 

We are receiving some errors on Rescan attempts from ServiceNow, for just some specific IPs.

 

Error code: 999. A virtual or physical scanner appliance is needed

 

As a result of the error message, we have mapped some specific asset groups that contain these IPs to scanner appliances within Qualys, and have rerun the imports into ServiceNow. But, we are not seeing these changes reflect in SN, and still receive the same error messages for these specific IPs. I'm thinking that there is something missing here on the Qualys side - since we have been utilizing ServiceNow rescan and asset groups, host tags, appliances, etc for quite some time without issue.

 

What does it take for ServiceNow to recognize this change in Qualys configuration? Is anybody able to provide any advice/guidance here? It would be greatly appreciated!

1 ACCEPTED SOLUTION

Martin Dewit
Kilo Sage

Have you tried to mimic the api requests outside of ServiceNow? Have you confirmed that the Asset Group integration runs before the Appliance integration and that they have completed successfully? In your scan requests can you confirm that the IP that is attempting to be rescanned is part of an asset group (in servicenow) with a default appliance (in servicenow)?

View solution in original post

2 REPLIES 2

Martin Dewit
Kilo Sage

Have you tried to mimic the api requests outside of ServiceNow? Have you confirmed that the Asset Group integration runs before the Appliance integration and that they have completed successfully? In your scan requests can you confirm that the IP that is attempting to be rescanned is part of an asset group (in servicenow) with a default appliance (in servicenow)?

Thank you Martin. The IP is not part of an asset group in ServiceNow - since that is imported from Qualys and this IP is being ignored for some reason. Thank you for the other info - will look into that!