Container Image Scanning
**
Use Tenable One Cloud Exposure to scan your container images for software vulnerabilities. Gain pre-production visibility into your containers to identify potential risks in containerized applications before deployment. Give your DevOps teams the information they need to remediate vulnerabilities in container images and registries quickly, and as early in the process as possible.
You can implement Container Image Scanning at any, or all, of the following three stages, ensuring ongoing security throughout the container lifecycle:
| Scan | LifeCycle Stage | Description | Supported |
|---|---|---|---|
| CI/CD Scanning | Build | Scan your container images and address vulnerabilities before deployment. Initiating at the CI/CD pipeline, this stage involves automated scans during the build process, ensuring that container images are free from vulnerabilities before deployment. | Windows- and Linux-based containers |
| Registry Scanning | Storage | Detect and alert on vulnerable container images stored in container registry repositories. This stage focuses on scanning container images stored in registries, systematically identifying and addressing potential risks. | Windows- and Linux-based containers |
| Workload Scanning | Runtime | The final stage deals with ongoing monitoring and scanning of running containers in production environments, allowing swift detection and mitigation of vulnerabilities and threats. | Linux-based containers only |
- (CI/CD Scanning) Each container repository to which the container is pushed as part of the build process
- (Registry Scanning) Each scanned container repository