Container Image Registry Scanning

This is a conceptual overview of how Tenable scans registries.

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.

Note: Registry scanning is enabled for container images whose size is up to 2 GiB. For more information, or to change this value, Contact Support. Tenable-based scans provide additional context for container images that isn't available from scans performed by cloud providers. Container images scanned by Tenable have an additional Workload tab in the resource view, providing information about 1) software packages installed on the image, and 2) vulnerabilities detected on the image, along with relevant fixes.

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.