Qualys Cloud Platform 3.6 (AM/WAS) API notification 1

Jeff Leggett

A new release of Qualys Cloud Platform 3.6 (AM/WAS) includes an updated API which is targeted for release in May 2021. 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 New

AM API: VNet Details for Azure Assets
/qps/rest/2.0/get/am/hostasset/
We now fetch details and provide information about the virtual network (VNet) for your Microsoft Azure assets. Assets are returned when they are visible to the user (i.e. in the user’s scope).

WAS API: Findings Output to Show the History of Findings
/qps/rest/3.0/get/was/finding/
/qps/rest/3.0/search/was/finding

With this release, we will now show in the Get and Search Findings API output the history of findings and each history will include the scan reference ID, scan ID and scan launch date.

WAS API: “From Address” Support Added for sending emails on scan completion
/qps/rest/3.0/get/was/wasscanschedule/
/qps/rest/3.0/create/was/wasscanschedule
/qps/rest/3.0/update/was/wasscanschedule/

We support “from address” as support@qualys.com or the owner’s name like for example user@qualys.com from the Create/Update Schedule Scan > Settings tab for sending emails from UI. This same functionality is now supported from API.

WAS API: Assign System and Dynamic tags from the UI and API for the WAS module (FORMAL DEPRECATION NOTICE)
In the WAS module, you can now assign system and dynamic tags from the UI and API again. However, this is in violation of the defined Qualys Platform Tag behavior. Consider this as a formal deprecation notice. 60 days on, you will no longer be able to assign system and dynamic tags in the WAS module either from the UI or using the API.

Share your Comments

Comments

Your email address will not be published. Required fields are marked *