Closed qmontal closed 6 years ago
Hey guys, Might it be that I am talking about Qualys Vulnerability Management instead of Qualys Web Applications, and that they use the same endpoint even if they use different APIs for the job? In that case, this would probably go with https://github.com/austin-taylor/VulnWhisperer/issues/51...
Closing issue as feature is on development by @pemontto , checking on it. Thanks @pemontto !
When trying to fetch the results of qualys with VulnWhisperer, I am getting the following error:
As a user of qualysapi, I understand that this is an error of Qualys API changes that have not been updated in the qualysapi library, on top of which VulnWhisperer works, although I haven't seen any Issue related to this topic. Is this an issue that other VulnWhisperer users are meeting?
As details of my deployment, I still don't have the ELK stack deployed, as I was making sure first the data fetching from the scanners, and I have tried the qualys urls at https://www.qualys.com/docs/qualys-was-api-user-guide.pdf (URL to Qualys API Server) with no luck, discarding the endpoint. No issues at all with Nessus.