image scanning
Checking the packages inside an image against lists of known vulnerabilities.
In more detail
Tools such as Docker Scout or Trivy read the package list (often from an SBOM) and report CVEs with severities and fixed versions. Scan in CI so a new high or critical finding fails the build, and rescan published images, because new vulnerabilities are found in old packages every day.
Examples
Not to be confused with Flux's image scanning, which only lists available tags in a registry.docker scout cves taskapi:0.1Related terms
- base image — The image a Dockerfile starts from with FROM, which supplies the operating system files and often a language runtime.
- ImageRepository — A Flux object that tells the image reflector controller which registry image to scan for tags, and how often.
- vulnerability — A weakness in software or configuration that an attacker could use to cause harm.
- CVE — A public identifier, such as CVE-2024-21626, given to one known security vulnerability so everyone can refer to it.
- CVSS severity — A standard 0 to 10 score, grouped as low, medium, high or critical, for how dangerous a vulnerability is.
- SBOM — A list of every software package and version inside an image, like an ingredients label.
- patching — Updating software to a version that fixes known bugs or vulnerabilities.
- continuous integration — Automatically building and testing every change as soon as it is pushed, so problems are caught early.
- image — A read-only package containing a program and everything it needs to run, used as the template for containers.
- image promotion — Moving the exact same, already-tested image through environments, such as staging to production, without rebuilding it.
- Trivy — An open-source scanner that finds vulnerable packages, secrets and misconfigurations in repositories, container images, Kubernetes manifests and Terraform.
- digest — A SHA-256 hash of an image's manifest that identifies its exact content and can never be moved to other bytes.
- security gate — An automated check in a pipeline that stops a change going further when it fails, usually by exiting with a non-zero code.
Taught in
- Surviving A Hundred And Eighty Minutes — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Artifacts: Where Packages And Images Live, And Die — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Systems Manager At Fleet Scale: Compliant And Unpatched — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Remediation As Code: A Public Bucket Appears — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Pipeline Security: The Build Role That Could Do Anything — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Long-Stem Clinic: When Two Answers Both Work — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Building and Pushing Container Images — Continuous Integration & Continuous Delivery Pipelines
- Software Composition Analysis with Trivy — Cloud Security & DevSecOps Engineering
- Supply Chain Security: SBOMs & Cosign Signing — Cloud Security & DevSecOps Engineering
- ARG, ENV, LABEL, EXPOSE And VOLUME — Docker Architecture & Production Containers
- Minimal Bases, Non Root Users And Smaller Images — Docker Architecture & Production Containers
- Scan, Patch And Inspect The Software Supply Chain — Docker Architecture & Production Containers
- Packaging Into A Container — Modern Java: Virtual Threads & High-Throughput Services
- Container Security: Minimal Bases And Non Root — Application Security & Threat Modeling for Engineers
- Image Scanning And Trivy — Application Security & Threat Modeling for Engineers
References
- Dockerfile best practices
- Docker Scout
- NIST SP 800-190: Application Container Security Guide
- OWASP Docker Security Cheat Sheet
- Trivy: container image scanning