Release 1.2.0
July 07, 2025
Qualys Container Runtime Sensor (CRS) 1.2.0 release introduces key enhancements that focus on improving event monitoring and management capabilities. It introduces the following features.
Added Support for ARM64 Architecture
The Qualys Container Runtime Sensor now supports ARM64 (aarch64) platforms, in addition to existing AMD64 support. This enables deployment on a wider range of hardware, including modern cloud-native environments and ARM-based infrastructure like AWS Graviton.
Added Support for Threat detection
We’ve introduced process event monitoring to detect suspicious behavior in real time. This helps you proactively identify and respond to potential threats during container runtime, improving your overall security posture.
Kubernetes Metadata in Process Events
CRS process events now include Kubernetes metadata, such as pod and pod owner references. This provides better visibility and traceability, making it easier to investigate incidents and correlate events with specific workloads.
Increased Memory Allocation for CRS Pods
The Helm chart has been updated with increased default CPU and memory allocations for CRS pods. This ensures the sensor performs optimally under high workloads, reducing the risk of missed events or performance bottlenecks.
More Resilient Sensor Startup
We’ve increased the retry limit and wait time for establishing a connection to the eBPF agent. This improves startup reliability, especially in environments with delayed service availability, ensuring consistent monitoring.
Expanded AWS ARN Support
The CRS sensor now recognizes ARNs across all AWS partitions, as follows
- aws (Standard)
- aws-cn (China)
- aws-us-gov (GovCloud)
This allows seamless integration and monitoring across all AWS regions, including restricted and government environments.
Added Support to Configure Process Allowlist
You can now configure a process allowlist directly through the Helm chart’s values.yaml file. This gives you greater control over what processes are allowed, reducing false positives and aligning runtime policies with your security requirements.
Issues Addressed
The following issues have been fixed with this release:
| Category | Issue |
|---|---|
| File Event | No event generated for any file operations execution from its working directory. |
To know more about Container Runtime Sensor, refer to CRS Online Help.