Qualys Cloud Agent Application Release 2.2

June 09, 2025

With this release, we are introducing the following new features and enhancements for the Qualys Cloud Agent application.

Updates for Agent Version Control

We have made the following updates to the Agent Version Control.

Warning Message while Downloading Lower Cloud Agent Versions

Cloud Agents that are already upgraded to the latest version can not be downgraded to lower versions. When you create an AVC profile with a lower agent version, it does not affect the existing Cloud Agents that are already upgraded to the latest version.

To clearly convey this message, we now display the warning message when a lower agent version is selected in the AVC profile.

Warning Message while selecting lower agent version in AVC Profile.

AVC Profile Name for Affected Agents Report

We have updated the Affected Agents Report name to display the AVC profile name. This update helps you associate the Affected Agents report with the respective AVC profile. Earlier, we used the AVC profile ID in the affected agents report name.

Older Affected Agents Report name format: AffectedAgents_<avc_profile_id>.csv

New Affected Agents Report name format: AffectedAgents_<avc_profile_name>.csv

To download the Affected Agents report, navigate to Configuration > Agent Version Control Profile. Select a profile for which you want to download the report, and click Download Affected Agents from the Quick Actions menu.

Issues Addressed

The following important and notable issues are fixed in this release.

Category / Component	Description
Database Authentication	When deleting a Database Assessment profile, the warning message displayed an incorrect count of impacted Cloud Agents. To fix this issue, we have updated the confirmation message to display the database instance count.
Application Configuration	In some cases, the option to enable the File Integrity Monitoring (FIM) application was not displayed while creating or editing a configuration profile in the Cloud Agent user interface. We fixed this issue with suitable code changes to display the option to enable FIM when the users have a valid license.