Qualys Cloud Agent for Solaris Release 7.1
January 06, 2026
The following new features and enhancements are introduced in this release of Cloud Agent for Solaris.
Solaris Cloud Agent does not support auto-upgrade from its previous version 3.11.0 to 7.1.0 as the installer type is updated from .PKG to .P5P. We recommend manual installation of new Cloud Agent versions to prevent upgrade failures.
Support for Qualys Applications
We updated the Solaris Cloud Agent to support the following important applications:
File Integrity Management
Qualys File Integrity Monitoring (FIM) is a cloud-based security solution designed to monitor and detect unauthorized changes to critical files, directories, and registry settings across IT environments.
For optimal performance of FIM we recommend a host asset with 4 Core CPU and 4GB RAM.
Qualys FIM offers the following benefits:
- Real-Time Monitoring: Tracks changes to files, folders, and registry objects in real time.
- Alerting & Reporting: Sends alerts for suspicious or unauthorized changes and generates detailed reports.
- Compliance Support: Helps meet standards like PCI DSS 4.0, HIPAA, and more.
| Required Application Version | File Integrity Monitoring 4.9.0 |
To learn more about FIM, refer File Integrity Monitoring Online Help.
Custom Assessment and Remediation
Qualys Custom Assessment and Remediation (CAR) provides a proactive approach to identifying vulnerabilities and executing custom scripts for rapid remediation. By leveraging automated assessments, role-based access control, and seamless script execution, CAR enhances security posture while eliminating the need for third-party tools.
CAR offers the following benefits:
- Centralized Risk Management: CAR can help you consolidate findings from multiple sources in an unified view. It also help you identify assets with blind spots, custom configurations, and zero-day vulnerabilities.
- Custom Script Execution: CAR supports multiple script languages like Python, Shell, Lua, Perl, and so on. You can execute these scripts as per pre-defined schedules or on demand for various platform such as Windows, Linux, MacOS, AIX, and BSD.
- Automated Remediation: CAR supports specifically designed orchestrated workflows which helps in remediating vulnerabilities faster without relaying on third party remediation tools.
| Required Application Version | Custom Assessment and Remediation 2.7.1 |
To learn more about CAR, refer to Custom Assessment and Remediation Online Help.
Updated Package Signing Process
We have updated the installer type
Enhancements for Solaris Cloud Agent
We have upgraded the Solaris Cloud Agent to support the following features:
| Feature | Description |
|---|---|
| Troubleshooting | Use this feature to perform the troubleshooting actions on your Cloud Agents. The Cloud Agent for Unix has support for the following options to help you with troubleshooting:
|
| Change Activation Key | Use this feature to change the activation key assigned to a Cloud Agent directly from the user interface. Refer Change Activation Key to learn more. |
| On Demand Scan | Use this feature to instantly launch a Cloud Agent scan, directly from the Cloud Agent user interface. Refer On Demand Scan to learn more. |
You must have Enterprise TruRisk™ Platform 3.23.0.0 and higher versions to use the above-mentioned features for Solaris Cloud Agent.
Behavioral Change
The Solaris Cloud Agent cannot be auto-upgraded to the latest version 7.1.0 as we have changed its installer type to P5P. To avoid upgrade failures, disable the auto-upgrade option. We recommend installing the new Cloud Agent versions manually for seamless operations.
Platform Coverage Support
The following are the changes to platform coverage support for Solaris Cloud Agent:
- The Solaris Cloud Agent 7.1.0 now supports the Solaris OS 11.4.
- The Solaris Cloud Agent 7.1.0 does not support Solaris OS 11.3 and lower versions.
Issues Addressed
The following important and notable issues are fixed in this release:
| Category/Component | Description |
|---|---|
| Configuration Profile Status | The Solaris Cloud Agent was reporting incorrect status as Configuration Pending Download. We fixed this issue by adding the Agent Health Status support for Solaris Cloud Agent. |
| Reporting | The Agent Provisioning Rule could not merge duplicate asset records as the MAC addresses were not validated for the affected assets . We fixed this issue by updating Cloud Agent to validate the MAC addresses while merging the duplicate assets. |
Known Issues, Limitations, and Workarounds
Known Issues for Solaris Cloud Agent
- Solaris Cloud Agent does not support the auto-upgrade from it's previous versions 3.x to 7.1.0. To avoid Cloud Agent upgrade failure, install the latest Solaris Cloud Agent version manually.
To learn more about manual installation and upgradation, refer to Cloud Agent Installation Steps and Cloud Agent Upgradation. - Uninstalling Solaris Cloud Agent using system command packages such as
pkg uninstall -v qualys-cloud-agentmay not remove all the agent-related files and directories. Execute the following script to remove these remaining files and directories:
/etc/qualys/.postremove
We recommend uninstallation using the qagent_uninstall script packaged with the Cloud Agent installer.
Alternatively, you can use the following command to uninstall the Cloud Agent manually:
sudo /opt/qualys/cloud-agent/bin/qagent_uninstall.sh
Known Issues for FIM with Solaris Cloud Agent
Qualys File Integrity Monitoring Application (FIM) has the following limitations for Solaris Cloud Agent:
- FIM does not support the detection file access monitoring features for Solaris Cloud Agents.
- The FIM user interface does not display the executed full command, as the Solaris Cloud Agent does not report proctitle in Audit Records for Solaris.
- For Solaris platforms incomplete data from the Audit service can prevent the FIM event reporting. In some cases Cloud Agent may report FIM events incorrectly, due to insufficient audit data. When full audit data is available, FIM event reporting works fine.
- FIM reports the Change event when a touch command is executed for the second time on an existing file.
- For Solaris FIM
auditdservice is not restarted after everyqualys-edrprocess start/stop operation. Theauditdservice is restarted only when FIM is unable to track the audit log directory. - Solaris FIM creates a backup of existing audit configuration in
/etc/security/audit_config.bakbefore updating the required audit configuration.