I'm trying to figure out if there is a Qualys API to obtain and update list of excluded hosts. I can't seem to find it, but not having an API call for this does not seem to be logical.
Am I missing something?
There is no API available to get the list of the excluded hosts, but you can copy/paste the list of the hosts that are excluded in looking at the history. Open the last entry by clicking on the info icon, and the IPs section contains the list. Just copy/past it.
You can also import the updated list by copy paste.
Thank you Eric! That's what I was afraid of. Unfortunately the copy/paste won't work too well for us, we have a big network and excluded hosts change frequently, while scans are launched by many independent teams.
Is there a way to have that API call for excluded hosts reading/manipulation implemented during future API enhancements?
I understand, I will bring this point internally and I'll figure what could be done. In the mean while would you please send a email at support (at) qualys.com so we can officaly track this request ? Just mention in the body of the email that per this discussion the ticket should be assigned to myself.
Thank you Eric! Just sent an email to support.
As of today (v6.22 released in the US), you can do this via API -- (and more)
With the new Exclude Hosts per Scan feature in QualysGuard 6.22, a new excluded hosts list V2 API (api/2.0/fo/asset/excluded_ip/?action=list) has been added that allows API users to request a list of excluded hosts.
With the new Exclude Hosts per Scan feature in QualysGuard 6.22, a new excluded hosts change history V2 API (api/2.0/fo/asset/excluded_ip/history/?action=list) has been added that allows API users to request the change history for excluded hosts in the user’s subscription.
Thank you Paul! I'll try to implement it asap.
Were these APIs depreciated or replaced? These URLs no longer work:
They redirect to the help pages: https://qualysguard.qualys.com/qwebhelp/fo_help/index.htm
The format is what is referred to above and in the API User Guide, but it's odd because there's a question mark after the slash. I would expect the syntax of the URLs to be similar to other APIs such as:
...would be to this:
Hey Bill, thanks for bringing this up. The calls work for me using the Chrome app POSTMAN.
If you are still having issues, please contact support and message me the case #:
How to Contact Qualys Support
Retrieving data ...