Registry Security
Also called Container registry hardening.
Protecting the store of container images from tampering and unauthorized access.
What it is
The controls that protect a container image registry, including access restrictions, signing enforcement, vulnerability gating, and audit logging of pushes and pulls. The registry is the distribution chokepoint for what runs in an environment.
Why it matters
A compromised registry can poison every downstream deployment, so its access and integrity controls are a critical supply-chain defense and a key place to look when malicious images appear.
In practice
A responder discovers a stolen push credential let the attacker overwrite a trusted image tag with a backdoored build for everyone pulling it.
What to look for
- Pushes from unexpected identities or locations.
- Public repositories that should be private.
- Images overwritten under an existing tag.
Common mistake
Locking down pulls but not pushes. Whoever can push can replace what everyone else deploys.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Trivy Open source
Scans images, file systems and code for known vulnerabilities and secrets.
-
Falco Open source
Detects suspicious behavior inside running containers and Kubernetes.
-
Sigstore Open source
Signs and verifies software artifacts so you can prove where a build came from.
-
CrowdStrike Falcon Cloud Security Commercial
Protects cloud workloads and containers, from build to runtime.
Read next
- Image Provenance and Signing: Cryptographically proving where a container image came from and that it is unaltered.
- Container Image Scanning: Inspecting container images for known vulnerabilities and exposed secrets.
- Secrets Management: Centralized, controlled storage and delivery of credentials and keys.