Container Image Scanning
Also called Image vulnerability scanning.
Inspecting container images for known vulnerabilities and exposed secrets.
What it is
The automated analysis of a container image's layers and packages to surface known vulnerabilities, embedded secrets, and risky configuration before or after deployment. It examines the image contents rather than the running workload.
Why it matters
Scanning catches inherited flaws and accidentally baked-in credentials early, and during an incident the scan history helps determine whether a deployed image carried a known exploitable vulnerability.
In practice
A responder confirms the exploited service shipped from an image flagged weeks earlier for a critical library flaw that was never patched.
What to look for
- Critical vulnerabilities in base images that are still deployed.
- Secrets baked into image layers.
- Images pulled from public registries without review.
Common mistake
Scanning only at build time. New vulnerabilities appear after the image ships, so rescan what is running.
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
- Registry Security: Protecting the store of container images from tampering and unauthorized access.
- Image Provenance and Signing: Cryptographically proving where a container image came from and that it is unaltered.
- Cloud Workload Protection Platform: Runtime protection and visibility for VMs, containers, and serverless workloads.