Qualys TruRisk™ Eliminate 4.2 API Notification

Anushka Damle

A new release of Qualys TruRisk™ Eliminate 4.2, which was released in September 2026, introduces new APIs and includes updates to several existing APIs. This API notification highlights recently released changes, enabling you to identify use cases that can benefit from the new and updated APIs.

Block Unwanted Patches Before Deployment

New API: Get All Patch Blocking Rules

GET /pm/v1/blocking/rules

DTD or XSD changes: Not Applicable

We have introduced this API to fetch the list of patch blocking rules. The API supports both Windows and Linux platforms. If you do not specify the platform, the API returns the blocking rules configured for the Windows platform.

New API: Create Patch Blocking Rule

POST /pm/v1/blocking/rules

DTD or XSD changes: Not Applicable

We have introduced this API to create patch blocking rules that prevent unwanted patches from being deployed. You can define the patches to be blocked using a patch QQL query in the criteria parameter and apply the rule to all assets (GLOBAL scope) or only to assets included in specific tags (TAG_BASED scope). The API request includes the ruleName, ruleReason, criteria, platform, scope, and includeTagIds parameters. You can create a maximum of 10 blocking rules per platform.

New API: Get Patch Blocking Rule by ID

GET /pm/v1/blocking/rules/{id}

DTD or XSD changes: Not Applicable

We have introduced this API to fetch a specific patch blocking rule by its rule ID and view its details. The API supports both Windows and Linux platforms.

New API: Update Patch Blocking Rule by ID

PUT /pm/v1/blocking/rules/{id}

DTD or XSD changes: Not Applicable

We have introduced this API to update an existing patch blocking rule using its rule ID. The API supports both Windows and Linux platforms.

New API: Delete Patch Blocking Rule by ID

DELETE /pm/v1/blocking/rules/{id}

DTD or XSD changes: Not Applicable

We have introduced this API to delete a patch blocking rule using its rule ID. The API supports both Windows and Linux platforms.

Approve Deployment Jobs Before They Run

New API: Get Approval Status for a Deployment Job

GET /pm/v1/deploymentjobs/{jobId}/approval

DTD or XSD changes: Not Applicable

We have introduced this API to check the approval status of a deployment job, along with the history of approval actions and the comments provided by the job approver.

New API: Perform an Approval Action on a Deployment Job

POST /pm/v1/deploymentjobs/{jobId}/approval

DTD or XSD changes: Not Applicable

We have introduced this API to perform an approval action on a deployment job. The job approver can approve or reject a pending job, and the job owner can send a job for approval or revoke a pending approval request. The API request includes the action parameter (APPROVED or REJECTED for the job approver, and PENDING_APPROVAL or REVOKED for the job owner) and an optional comment parameter.

Updated API: Create Deployment Job

POST /pm/v2/deploymentjob

DTD or XSD changes: Not Applicable

We have enhanced this API to validate the job approval workflow. When the job approval workflow is enabled for a platform, the API rejects a create job request unless the job is submitted with the status parameter set to Disabled.

Updated API: Change Status of Deployment Job

POST /pm/v1/deploymentjobs/update/status/{action}

DTD or XSD changes: Not Applicable

We have enhanced this API to honor the job approval workflow. A job with the approval workflow turned on cannot be bulk-enabled until it is approved. The API response provides a failure reason for each job that is still pending approval, rejected, or revoked.

Track Job Approval Status for Deployment and Rollback Jobs

We have enhanced the following APIs with a new parameter, approvalStatus, in the API request and response. This parameter indicates the approval status of the job across the job execution flow. When a job is created in the disabled state with the approval status as Pending Approval, the job is executed only after it is approved. The job approval workflow is supported for Windows deployment , mitigation and rollback jobs, and is also supported for the Linux platform.

Create Deployment Job (Windows)

POST /pm/v2/deploymentjob
DTD or XSD changes: Not Applicable

Update Deployment Job (Windows)

PATCH /pm/v2/deploymentjob/update/{deploymentJobId}
DTD or XSD changes: Not Applicable

Create Deployment Rollback Job (Windows)

POST /pm/v2/deploymentjob
DTD or XSD changes: Not Applicable

Updated API: Create Mitigation Job (Windows)

PATCH /pm/v2/deploymentjob/update/{deploymentJobId}
DTD or XSD changes: Not Applicable

Update Deployment Rollback Job (Windows)

PATCH /pm/v2/deploymentjob/update/{deploymentJobId}
DTD or XSD changes: Not Applicable

Please refer to the detailed release notes here:https://docs.qualys.com/en/pm/release-notes/patch_management/release_4_2_api.htm



Share your Comments

Comments

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