Qualys Cloud Platform 3.0.1.0 (WAS) API notification 1

A new release of Qualys Cloud Platform 3.0.1.0 (WAS) includes an updated API which is targeted for release in May 2020. The specific day will differ depending on the platform. See platform release dates on the Qualys Status page. This API notification provides an early preview into the coming API, allowing you to identify use cases that can leverage this updated API.

What’s newWAS API: Set a Default DNS Override for Web Application/qps/rest/3.0/create/was/webapp/qps/rest/3.0/update/was/webapp/<id>/qps/rest/3.0/get/was/webapp/<id> When creating or updating your web application, you can now set one of the DNS override records assigned to your web application as default using these APIs. The default DNS override setting is useful when you want to scan multiple web applications using the DNS override option. We will use the default DNS override record that you have set for your web applications to launch scan on them. This functionality is already supported from the WAS UI.

WAS API: Added a New Scan Status “PROCESSING” for WAS Scans The WAS Scan API Output will now show a new status “PROCESSING” for scans whose results are in processing in WAS. After the scan result is processed, the status of the scan is changed to Finished. This status is already used for scans launched from WAS UI.

AWS Security Hub Integration/qps/rest/2.0/add/integration/amazon/securityhub//qps/rest/2.0/add/integration/amazon/securityhub/{id}/vm/qps/rest/2.0/update/integration/amazon/securityhub/{id}/qps/rest/2.0/update/integration/amazon/securityhub/{id}/vm/qps/rest/2.0/get/integration/amazon/securityhub//qps/rest/2.0/get/integration/amazon/securityhub/vm//qps/rest/2.0/get/integration/amazon/securityhub/{id}/vm//qps/rest/2.0/delete/integration/amazon/securityhub/{id}/qps/rest/2.0/delete/integration/amazon/securityhub/{id}/vm/qps/rest/2.0/delete/integration/amazon/securityhub/{id}/vm/reg We have now introduced APIs (JSON) to fasten and simplify the integration process with AWS Security Hub. The integration process involves two quick steps: creating the Amazon Security Hub integration and configuring the Amazon Security Hub integration. Once you configure it, you can use it to fetch details, update the existing configuration of Amazon Security Hub, or delete the Amazon Security Hub integration as well.