Cybersecurity glossary
What is an Image Registry?
Learn what a container image registry is, how tags and digests are stored, which auth and immutability controls stop supply-chain abuse, and how to promote images safely.
Definition
An image registry is a service that stores, authenticates, and distributes OCI container images (manifests, indexes, and layers) so build systems can push artifacts and runtimes can pull them by tag or digest.
Why image registries matter
If git is where source lives, the image registry is where production actually pulls software. A stolen push token, a mutable tag, or an unsigned public image can change every node that reconciles a Deployment.
Registries are therefore identity, storage, and supply-chain control—not a dumb disk for tarballs.
Push, store, pull
CI authenticates and pushes
A workload identity or robot account uploads layers and a manifest. Credentials must not be long-lived org-wide passwords.
The registry stores content-addressed blobs
Layers are keyed by digest. Two images can share a base layer; deleting one tag may not delete the blob.
Tags are pointers
v1.4 and latest name a digest. If tags are mutable, yesterday’s scan does not apply to today’s bits.
Policy can scan and sign
On-push scanning, admission of signatures, and replication to a prod project happen here.
Nodes pull at schedule time
kubelet and the runtime authenticate, verify the digest, and unpack. Network egress to unknown registries is a finding.
Registry controls that change risk
Authentication and RBAC
Separate push (CI) from pull (nodes) from admin (replication, retention).
Immutable tags
Once v1.2.3 exists, it cannot be retargeted. New bits need a new tag and digest.
Private plus cache
Internal source of truth with pull-through of approved upstreams, not ad-hoc Docker Hub.
Retention and GC
Old digests with leaked secrets or unpatched CVEs should expire on purpose.
Public, private, and promoted registries
| Pattern | Role | Risk if misused |
|---|---|---|
| Public registry as prod source | Fine for experiments | Tag hijack, rate limits, availability, unknown publishers |
| Single private registry, everyone pushes | Better than public | A stolen CI token overwrites what prod pulls |
| Dev registry → scanned/signed prod registry | Promotion pipeline | None if clusters can only pull the prod project |
| Anonymous pull enabled | Convenience for air-gapped mistakes | Anyone who can reach the endpoint can steal images and guess tags |
Image registry checklist
- Make a private registry (or a tightly controlled cloud registry) the only source production nodes may pull.
- Authenticate pushes with workload identity; rotate robot tokens and never share them across products.
- Enable tag immutability for release tags; deploy clusters by digest regardless.
- Scan on push and block promotion of failed digests; rescan stored images for new CVEs.
- Sign images and verify signatures at admission; unsigned public tags should not run.
- Split CI-writable repositories from production-readable repositories.
- Disable anonymous pull on internal registries; log pull/push and alert on unexpected identities.
- Garbage-collect untagged blobs on a policy so leaked layers do not live forever.
The practical takeaway
An image registry stores and serves OCI images. It is the distribution control plane for containers: who can push, whether tags can move, and which digests a cluster is allowed to trust.
Promote scanned, signed digests into a prod repository, pull only from there, and treat registry credentials as production IAM. The registry is not a cache of convenience—it is where your running software comes from.
Related security terms
Container Image
The artifact the registry stores as manifests and layers.
Container Image Scanning
Often runs on push and gates which digests may be pulled.
Package Repository
Language package stores; an image registry is the analog for containers.
Software Supply Chain Attack
Registries are a high-value place to swap tags or steal push credentials.
Kubernetes Admission Controller
Can restrict clusters to pull only from approved registries and signed digests.
Frequently asked questions
What is an image registry in simple terms?
It is a warehouse for container images. CI pushes a digest; Kubernetes nodes pull that digest. Authentication decides who may push, overwrite tags, or download.
Is Docker Hub the same as a registry?
Docker Hub is one public registry. ECR, GCR/Artifact Registry, ACR, GHCR, Harbor, and self-hosted registries are others. The OCI distribution API is the common protocol.
Why not pull :latest from the public internet in production?
Tags move, availability changes, and you inherit whoever pushed that name. Mirror and scan into a private registry, then deploy by digest.
What is tag immutability?
A registry setting that refuses to point an existing tag at a new digest. It prevents silent replacement of v1.2.3 after it was scanned and approved.
How do pull-through caches help?
Nodes pull from an internal cache that fetches upstream once. You keep availability, rate-limit headroom, and a place to scan—without giving every node anonymous internet pulls.
What is registry promotion?
The same digest moves from a scan/dev repo to a prod repo (or is signed) after policy passes. Production clusters cannot pull from the writable CI repository.
Are public registries a vulnerability?
They are a trust decision. Dependency confusion, deleted images, and malicious tags are real. Pin digests, verify signatures, and prefer an internal source of truth.
References
Explore authoritative guidance and frameworks related to image registry.
Explore every security definition
Return to the glossary to search by term, alias, starting letter, or security category.