Enterprise TruRisk™ Platform Release 10.33 API 

April 2, 2025

Before understanding the API release highlights, learn more about the API server URL to be used in your API requests by referring to the Know Your Qualys API Server URL section. For this API Release Notes, <qualys_base_url> is mentioned in the sample API requests.

We have implemented versioning for APIs. For more information on API versioning, refer to the Introducing API Versioning: A Strategic Upgrade for Enhanced Stability and Control for API Integrations blog.

Qualys Vulnerability Management (VM)

Added MITRE ATT&CK in Scan Template and Host Detection List API

With this release, we have added MITRE ATT&CK Tactics and Technique details in the scan template and host detection list API. Previously, it was available on the Prioritization tab of Qualys Vulnerability Management, Detection, and Response (VMDR), which is now extended to the API. This helps to prioritize vulnerabilities and detections based on the associated MITRE techniques, enabling more effective remediation strategies.

  • Scan Template API: Availability of MITRE ATT&CK in the Scan Template

    New or Updated API Updated
    API Endpoint (deprecation Timeline - September 2025)

     /api/2.0/fo/report/template/scan/

    API Endpoint
    (New Version)

     /api/3.0/fo/report/template/scan/

    Method GET, POST
    DTD or XSD changes No

    With this release, you can now create, update, delete, and export scan templates for MITRE ATT&CK details (MITRE Tactic and Technique Details). This enhances threat detection accuracy by aligning scans with known adversary tactics and techniques.

  • Host Detection List API: Display of MITRE ATT&CK Details

    New or Updated API Updated
    API Endpoint (deprecation Timeline - September 2025)

    /api/3.0/fo/asset/host/vm/detection/ 

    API Endpoint
    (New Version)

    /api/4.0/fo/asset/host/vm/detection/

    Method GET
    DTD or XSD changes Yes

    With this release, we have introduced the following 4 new tags in the response:

    • MITRE_TACTIC_NAME 
    • MITRE_TECHNIQUE_NAME 
    • MITRE_TACTIC_ID
    • MITRE_TECHNIQUE_ID

    This displays the MITRE ATT&CK details associated with QID. This enables more informed decision-making in threat detection, response, and mitigation and also validates your organization’s adherence to MITRE compliance.

Cloud Perimeter Scans API: Simplified Load Balancer DNS Names Detection for Azure

New or Updated API Updated
API Endpoint (deprecation Timeline - September 2025)

/api/2.0/fo/scan/cloud/perimeter/job/

API Endpoint
(New Version)
/api/3.0/fo/scan/cloud/perimeter/job/
Method POST
DTD or XSD changes No

With this release, we have added two new input parameters - include_app_gateway_lb_from_connector and include_lb_from_connector to simplify the process of adding load balancer DNS names when performing a Cloud Perimeter Scan for the cloud provider Microsoft Azure. Once these parameters are specified as 1, the system automatically retrieves the load balancer DNS names list and displays the total count.

The new parameters can be accessed by users having the Vulnerability Management Scan Process (VMSP) subscription enabled and access to the TotalCloud (TC) module.

Users API: Contact Number now made Optional

New or Updated API Updated
API Endpoint /msp/user.php/
Method GET, POST
DTD or XSD changes No

With this release, when you add/edit a user account defined in the API user subscription, the contact number is now made optional, which was mandatory earlier. The value of the input parameter phone is now optional for both add and edit request. This helps you to safeguard your security.  

Issues Addressed

The following reported and notable customer API issue are fixed in this release:

Component/Category Application
 
Description
VM - Asset API Vulnerability management When the users used the API script to add the scanner appliance to the asset group using the scanner ID parameter, the scanner appliance was not getting updated in the asset group list. Relevant code changes have been made to fix the issue.
VM - Host List Detection API Vulnerability management When user executed HLD API by including the input parameter Exclude Supersede QIDs on multiple hosts, incorrect QIDS were getting excluded from API result. Relevant code changes have been made to fix the issue.
Documentation Vulnerability management When the users tried to create a scheduled map scan using the API /msp/scheduled_scans.php?, they were unable to find the details in the latest API User Guide. Now we have updated the API User guide with relevant information. For details Refer to Qualys API (VM/PC) Guide. 
VM - Host List Detection API Vulnerability Management When the users were calling the 'vm_processed_before' parameter in the Host List Detection (v2.0 and v3.0) and the Host List (v2.0, v3.0, and v4.0) APIs , they were not receiving the expected results. Relevant code changes have been made to fix the issue. The issue persisted because of the way the query handled date conditions. We have now documented this behavior in the Host List Detection and the Host List APIs section in the Qualys API (VM/PC) User Guide.