Home/Glossary/Container Registry

Container Registry

A repository for storing, managing, and distributing container images, providing version control and access management.

DevSecOpsAlso called: "image registry", "docker registry", "artifact registry"

Container registries store and serve container images, acting as the distribution hub for containerized applications.

Registry types

  • Public registries: Docker Hub, GitHub Container Registry, Quay.io.
  • Cloud-managed: AWS ECR, Azure ACR, Google Artifact Registry.
  • Self-hosted: Harbor, Nexus Repository, GitLab Container Registry.

Security features

  • Authentication: Control who can push/pull images.
  • Authorization: Role-based access to repositories.
  • Vulnerability scanning: Automatic CVE detection.
  • Image signing: Verify image authenticity.
  • Immutable tags: Prevent tag overwrites.
  • Geo-replication: Distribute images globally.

Cloud registry comparison

FeatureAWS ECRAzure ACRGCP Artifact Registry
ScanningInspectorDefenderArtifact Analysis
SigningSignerNotary v2Binary Authorization
ReplicationCross-regionGeo-replicationMulti-region

Best practices

  1. Enable vulnerability scanning on push.
  2. Implement image retention policies.
  3. Use immutable tags for production images.
  4. Require image signing for deployment.
  5. Restrict push access to CI/CD pipelines only.
  6. Enable audit logging for compliance.

Registry security checklist

  • Authentication required for all operations.
  • Network access restricted (VPC endpoints, private links).
  • Vulnerability scanning enabled and enforced.
  • Image signing implemented.
  • Retention policies configured.
  • Audit logs exported to SIEM.