Qualys scan from Servicenow -
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2020 03:24 PM
Hello,
While initiating scans from Servicenow to Qualys, I get the below error. I am using the "rescan vulnerable items" UI action from the VUL record.
Error: Unsuccessful response from server. Status code: 400
I have already default_scan_appliance and default_scan_appliance in Qualys configuration
can someone please let me know what this error about ?
Thanks
.
- Labels:
-
Vulnerability Response

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2020 10:09 AM
good to start testing that.
Thakns,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2020 12:02 PM
I've seen this problem as well and can confirm that it can occur with IPv6 addresses being included in VSCAN scan job. Is there a property to disable sending IPv6 addresses when initiating Qualys scan from vulnerability response scan (VSCAN)? I'm on Paris edition.
FWIW: Here are the three most common errors I see with VSCAN initiating qualys scans:
Error code 400: I see these when IPv6 addresses are in the list of ci IP addresses and are included in the vuln scan.
Error code 999: Concurrency issue: too many concurrent scans running. This can be from existing Qualys initiated scans as well as SN initiated scans.
Error message “Error: No default scanner appliance defined": I see this when SN discovery finds IP addresses that are not registered in Qualys and thus mapped to an existing scanner. Remedy this by researching IP addresses that trigger this error, and add that IP address (or range or CIDR) to Qualys and map to scanner appliance and scheduled scan.