Qualys Cloud Agent for Linux Intel Release 7.0.3

Limited Customer Release

April 22, 2025

New Features

There are no new features for this release.

Cloud Agent Enhancements

Updated Default Folder for Cloud Agent Installation

With this release, we have updated the default folder for Cloud Agent installation to /opt. Earlier, /usr/local/ was the default folder for Cloud Agent installation. This enhancement makes Cloud Agent File System Hierarchy Standard (FHS) compliant.

Use the following commands to manage the Cloud Agents installed in the /opt folder:

• Installation command: rpm -ivh qualys-cloud-agent.rpm
• Provisioning command:
  /opt/qualys/cloud-agent/bin/qualys-cloud-agent.sh ActivationId=xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx CustomerId=dxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx ServerUri=<platform_url>/CloudAgent/ 
• Upgrade command:
  rpm -Uvh qualys-cloud-agent-7.0.3-8.x86_64.rpm
  
  The upgraded Cloud Agent is installed in the/opt folder.

   When you upgrade a Cloud Agent installed in /usr/local, new directories are created in the /opt folder, but directories present in the /usr/local folder are not deleted. If required, you can delete these directories manually.

Limitations of Installing Cloud Agent in /opt Folder

The following are the limitations for Cloud Agents installed in the /opt folder: 

• The following Qualys applications are not supported for Cloud Agents installed in the /opt folder:
  • Endpoint Protection Platform (EPP)
  • Extended Detection and Response (XDR)
  • Mitigation
• Cloud Agent installed in the /opt folder does not support auto-upgradation.

   We recommend you do not upgrade Cloud Agents installed in the /opt folder to the /usr/local folder.

• Cloud Agent does not delete the directories present in the /usr/local folder automatically. You have to delete these directories manually.

Use Cases for Upgrading Cloud Agents

The following table illustrates the different scenarios when a Cloud Agent installed in /usr/local is upgraded using the upgrade command:

Cloud Agent Version	Installation Location	Installation Type	Manual Upgrade
Newly installed Cloud Agent 6.2 and lower versions relocated to /opt	/opt/qualys	Symlinks are present in /usr/local/qualys	YES
Cloud Agents 6.2 and lower versions upgraded to v6.4	/opt/qualys	Symlinks are present in /usr/local/qualys	YES
Newly installed Cloud Agent v6.4	/opt/qualys	No symlinks are available	YES

Behavior Changes

The following behavior changes are observed for a Cloud Agent when you upgrade it to version 7.0.3.

• The default installation path for Cloud Agent has changed from /usr/local to /opt.
• We recommend installing a new Cloud Agent in the /opt folder instead of upgrading an existing agent. However, if you want to upgrade an existing agent, take note of the following changes:
  • The upgraded Cloud Agent is re-provisioned to the respective assets.
  • The temporary data of a Cloud Agent present in the /usr/local is not deleted. If required, you can delete this data manually.

Platform Coverage Support

There is no new platform coverage added in this release.

Issue Addressed

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

Category/Component	Description
Agent Uninstallation	We fixed an issue where the /run/qualys folder was not deleted after uninstalling the Cloud Agent. Now the /run/qualys folder is deleted when a Cloud Agent is uninstalled.
UDC Scans	Cloud Agent caused higher CPU usage during UDC scans. We fixed this issue by limiting the CPU throttle to 30% for the UDC scan.
Cloud Agent UI	We fixed an issue where data for the SwCA was not populated in the Cloud Agent and CyberSecurity Asset Management (CSAM) user interfaces due to a missing CDN certificate for the SwCA application.
Agent Upgrade	The manual upgrade of Cloud Agent to a higher version using the -Uvh (upgrade command) without the relocation parameter was failing. Now, we have fixed this issue.

Known Issues, Limitations, and Workarounds

For the initial OS platforms, such as CentOS, RHEL, and OEL versions 6.10, the Linux Cloud Agent does not restart automatically after upgrades. We recommend you manually restart the agent to resolve this issue.