Skip navigation

A new release of Qualys Cloud Platform v8.21 (VM/PC) includes an updated API which is targeted for release in August 2019. 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
API Support for New Vault Types for Cisco and Checkpoint
/api/2.0/fo/auth/unix/
We now support few more vault types as part of authentication record settings for Unix Subtypes: Cisco and Checkpoint Firewall. Newly supported vault types for Cisco authentication records are Azure Key and HashiCorp vaults and newly supported vault type for Checkpoint Firewall is HashiCorp vault. These vaults are already supported for these authentication types in the UI.

A new release of Qualys Cloud Platform v2.40 (WAS) includes an updated API which is targeted for release in August 2019. 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
WAS API: Option to choose all Detections in Option Profile
/qps/rest/3.0/get/was/optionprofile/<id>
/qps/rest/3.0/create/was/optionprofile
/qps/rest/3.0/update/was/optionprofile/<id>
You can now configure the option profile for you scan so that it could include all the WAS related detections. We have now introduced a new option named "Everything" for detection scope of Option Profile that includes every WAS related detection during the scan.

 

WAS API: Unique ID for Findings
/qps/rest/3.0/get/was/finding/<id>
/qps/rest/3.0/search/was/finding
/qps/rest/3.0/count/was/finding
/qps/rest/3.0/ignore/was/finding
/qps/rest/3.0/activate/was/finding
/qps/rest/3.0/editSeverity/was/finding
/qps/rest/3.0/restoreSeverity/was/finding
/qps/rest/3.0/retest/was/finding
We have now introduced 36-bit unique ID (uniqueId) for each finding. The ID would be unique for every finding. Earlier, the combination of three fields namely: finding ID, finding type and finding category would make a finding unique. Now, with the implementation of uniqueId, you can easily distinguish every finding

Filter Blog

By date: By tag: