Release 1.1.1

July 02, 2025 (Updated on 17th July 2025)

 

Container Runtime Sensor (CRS) 1.1.1 release includes multiple bug fixes aiming to improve the accuracy of the event capture and to ensure more reliable monitoring and performance in your environment.

Enhanced Security with No Persistent Storage

Earlier, the Persistent Storage was enabled by default with the help of the Helm chart. This saved the data locally on disk.
With this release, the Persistent Storage is disabled to align with your customized configurations. This has also added security and operational simplicity as CRS does not save the data locally.

Behavioral Change

With persistent storage disabled by default, the runtime-sensor generates a new UUID upon each reprovisioning or upgrade. Consequently, any sensor profile assignments associated with the previous UUID will not persist. You must manually re-assign the sensor to the appropriate sensor profile after each reprovisioning or upgrade to maintain consistent configurations.

Best Practices

Qualys recommends the following best practices for smooth functioning of the CRS.

• After reprovisioning or upgrading the runtime sensor, promptly re-assign it to the appropriate sensor profile to ensure continued adherence to your security policies.
• Consider enabling persistent storage only if automatic retention of sensor profile assignments is preferred.

Issues Addressed

The following issues have been fixed with this release.

Category	Issue
Port 8080	The CRS was binding to port 8080 for metrics, leading to conflicts with other services utilizing the same port. Now, the metrics have been disabled by setting the port value to '0' in the configuration, ensuring the runtime-sensor no longer listens on port 8080.
Persistent Storage	The CRS had persistent storage enabled by default, which was not aligned with desired configurations. Now, the persistent storage has been disabled by default in the Helm chart.

 

To know more about Container Runtime Sensor, refer to CRS Online Help.