Container Image Registry Scanning
This is a conceptual overview of how Tenable scans registries.
- For an integration guide about connecting container image registries, see Connect Container Image Registries.
- For a how-to guide about viewing and managing container images, see Container Images.
Tenable scans container images stored in container registry repositories, identifying potential risks within the registry itself. Tenable scans:
-
Cloud-hosted registries:
- AWS Elastic Container Registry (ECR)
- Azure Container Registry (ACR)
- Google Container Registry (GCR)
- Alibaba Cloud Container Registry (ACR)
- Oracle Cloud Infrastructure Registry (OCIR)
-
Independent registries:
- JFrog Artifactory, including federated repositories
- Red Hat Quay
- Sonatype Nexus Repository
- Harbor
- Up to the last 10 images in the repository, and all images currently in use
- Tagged images
To view scanned images, see Container Images.
Container Registry Policies
Required License: Although Vulnerability Management as a whole is only available with the CNAPP license, this feature is available for all license types.
The following built-in Tenable One Cloud Exposure policy is used to scan your environment and alert on vulnerable container registry repositories:
- Container Image Repository has vulnerabilities that should be addressed
This policy looks at the last scanned container image in the registry, and only for tagged images. This results in a more actionable finding, as it reflects the version of the container image that you can actually replace.