Release 3.3

January 20, 2025 (Updated on February 21, 2025)

What's New?

Add Success Conditions When Automating Testing and Production-chained Jobs

With this release, you can select another job (a parent job) that includes post-actions during the Select Patches step for Windows, Linux, and Mac jobs. By doing so, you can control the execution of the child job based on the successful percentage completion of post-actions in the parent job.

This successful completion percentage of the post-actions is decided based on the condition you add while creating or updating the child job. In the Add Condition section, select the Post Actions are successfully executed condition, select the required post-actions, and provide the percentage of successful post-actions.

 While adding a condition, you can provide the percentage based on the post-actions you select. For example, if you select three post actions, you can specify the percentage as 33, 66, or 100. If one post-action is successful, the success rate will be 33. If two are successful, the success rate will be 66; if all three are successful, the success rate will be 100.

Support Rollback Jobs for Linux Assets

You can create a rollback job to roll back the patches from the Linux assets. Until this release, it was possible to create rollback jobs for Windows assets.

 Linux Cloud Agent version 7.1 or later is the prerequisite for Linux rollback job creation. 

You can create a Linux rollback job by navigating to Jobs > Linux > Create Job and clicking Rollback Job. For more information, refer to the Online Help.

Show Deployment Completion Message Regardless of Patch Deployment Status

You can show the patch job deployment completion pop-up message on patched machines for Windows deployment jobs irrespective of whether the patches are failed, skipped, or successfully deployed. As a result, you get better control over deployment job completion notifications.

 Windows Cloud Agent version 6.1.x or later is the prerequisite to show the patch job deployment completion pop-up message.

To do so, you must switch on the newly introduced Always Show Patch Job Deployment Completion Pop-Up Window toggle while creating or editing the Windows job.

This toggle is added to the Options page of the Windows deployment job page under the Deployment messages section.

Abort Job Before Patches are Deployed Based on Pre-condition

With this release, we introduced a capability to cancel or abort the Windows and Linux deployment jobs. This capability enables you to abort the job under specific conditions.

To do so, you must include a specific run script pre-action in the deployment job, which returns code 12. Upon receiving this return code, the deployment job is aborted. For more information, refer to the Online Help.

  Windows Cloud Agent version 6.1.x and later and Linux Cloud Agent version 7.1.x and later are prerequisites for initiating this job cancellation.

Support for ARM: Ubuntu 20, Ubuntu 24, and Amazon Linux 2023

We have provided patching support for ARM: Ubuntu 20, Ubuntu 24, and Amazon Linux 23 assets.

 The value noarch is shown under the Archt column as there is no specific architecture for Linux Ubuntu.

Extended Security Update (ESU) Patching Support for Windows 

With this release, the ESU patching is supported for Windows Server 2012 and Windows Server 2012 R2 operating systems. A new patch QQL search token, isEsuPatch, is introduced on the Patches > Windows tab, letting you find the ESU Patches.

 ESU patching is feasible only when the ESU license is enabled. Contact your Technical Account Manager (TAM) for the ESU license enablement.

Enhanced User Interface (UI 4.0) of the Qualys Cloud Platform

Introducing the new and improved UI with the following key upgrades. This new interface is designed to make your platform experience faster, and smoother. 

Check out our blog for insights to discover the key enhancements designed to improve your experience. 

Watch this video to explore the new UI and discover the key enhancements designed to improve your experience! 

Enhanced Navigation for a Streamline User ExperienceEnhanced Navigation for a Streamline User Experience

Refreshed DashboardRefreshed Dashboard

Standardized UI Elements for Seamless NavigationStandardized UI Elements for Seamless Navigation

Enhanced UI Rollout Starting January 2025

The enhanced user interface will be rolled out in phases starting January 2025. You will receive in-platform notifications and email updates to guide you through the transition. Compatibility is seamless, with no additional setup required.

• You can update your preference by switching between the Old and New UI using the toggle option until Day 90.

  

• If no preference is set, the platform will default to the New UI after the 30-day transition period. For more information on the rollout phase, refer to the Frequently Asked Questions.

Explore the full details of these updates! Check out our blog for insights.

Platform Name Change Update

We are renaming the Qualys Cloud Platform to the Qualys Enterprise TruRisk™ Platform. This change highlights Qualys' commitment to empowering CISOs, cybersecurity professionals, and risk stakeholders to effectively measure and mitigate the impact of cyber risk on their organizations. 

The Qualys Enterprise TruRisk Platform is the only cybersecurity and risk management solution that enables you to measure, communicate, and eliminate cyber risk across the extended enterprise with precise remediation and mitigation actions. 

This update does not affect the platform’s functionality or features. Starting in January 2025, the name change will be implemented in phases across all product interfaces. 

For more information, check out this blog.

New Token

Refer to the following table to learn more about the token added in this release.

Token	Tab	Description
isEsuPatch	Patches	To find the Extended Security Update (ESU) patches. Supported values: true and false.

Issues Addressed

The following reported and notable customer issues have been fixed in this release.

Component/Category	Description
PM - Job Windows	We fixed the issue wherein the patch job was not sent to assets because extensive tags were in the user scope.
PM - Job Windows	We fixed the issue where some assets were stuck in the pending state while the patching was completed on other assets from the job.
PM - Job Windows	We fixed the issue where users were unable to add more than 150 tags for the Patch Management license.
PM - Job Windows	We fixed the issue where the job status was changed to Asset Responded despite the job being in the Disabled state.
PM-Licensing	We fixed the issue where zero licenses were shown as available for consumption despite having the active Patch Management full subscription.
PM-UI	We fixed the issue observed related to an unexpected decrease in the license tag limit from the earlier limit.
PM - Job Windows	We fixed the issue for the on-demand job rerun. Despite the job being sent and scans running on assets, the job was stuck in the Prepared state and the asset in the Pending state.
PM - Job Windows	We fixed the issue where the job was not executed when sub-users had fewer than 10 tags in their scope.
PM - Job Windows	We fixed the issue where the QQL-based jobs were not referring to the latest patches; instead, the previous month's patches were considered.
PM - Reports	We fixed the issue where the Linux Install Job & Windows Rollback Job Progress Reports couldn't be downloaded because the Download icon was not visible.
PM-UI	We fixed the issue where the Patch Management application crashed while accessing the job progress from the New User Interface (UI 4.0) for a specific case.