Qualys Container Security (CS), an integral part of TotalCloud 2.0, provides a comprehensive view of the security posture of containerized applications. Operationalizing a new technology tool in an enterprise often presents its own challenges. This blog seeks to help the operations team familiarize themselves with a few important processes and configure key parameters early in the rollout. Please note this is not a definitive guide; instead, it highlights a few points to consider. Here are some of the best practices to follow when using Qualys Container Security. Maintaining Sensor Version It's always recommended that the Qualys CS sensor be updated to the newer version to take advantage of new features, bug fixes and to remediate sensor vulnerabilities. When a newer sensor version is available than the one deployed, you’ll see “Update Available” next to the sensor name. Update Strategy: It's always advised to use the latest Qualys CS sensor and review the release notes for every update. The status of the platform and scheduled maintenance windows are published at status.qualys.com. There is also an option to "Subscribe to Updates" for a specific platform and component. Example: US Platform 2, Container Security (CS). Review the release notes at www.qualys.com/documentation/release-notes with "Filters" as Container Security (CS). Container Security Sensor Image is available on dockerhub and is released regularly, almost every month. The sensor is also available as a…Read More