Container image scanning meaning, in plain words

Container image scanning checks the parts inside a container for known holes. What OWASP's Docker guidance and Top 10 A06 say, and what a clean scan can't show.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

Container image scanning is a check for holes in the parts inside an app's container. An image is the full set from which a container is made, holding OS parts, libraries and the app itself. OWASP's Docker Security Cheat Sheet explains that scanning tools can find known vulnerabilities, secrets and configuration flaws in an image.

How does container image scanning work?

It resembles a food factory that, before shipping, checks its list of raw materials to confirm that no material under recall is included. The scan builds a list of the parts in an image, matches it against published vulnerability information, and reports the parts that match.

OWASP's Docker material recommends building this check into the automated flow from development to release (CI/CD). If a hole is found before release, the image does not have to run with the hole still in it.

A06 of the OWASP Top 10:2021 lists keeping a continuous inventory of the versions of the parts you use, watching public sources such as CVE and NVD, and obtaining parts from official sources. The results are fixed in order, starting with the ones with the biggest impact. The idea of holes in parts is organized on the vulnerable dependencies page. How your site looks from outside can be checked with the free URL check.

Why does container image scanning matter?

If an old part remains in a container, the same hole is copied as many times as the container is started. If you stop checking after release, you also miss holes that are newly found. Scanning is repeated on a schedule, not only at release time.

What a scan finds is limited to what is already known. Even when the result is empty, that does not settle that there are no holes.

The fix is to build a new image with the parts updated, and to check it again. For a part that cannot be updated, you decide whether to keep using it or replace it with another part, after looking at the impact. To discuss how to proceed with checks, contact us.

Related terms

  • Container security: keeping the app's container and its runtime environment safe.
  • SCA: a check that looks for holes in the parts you use.
  • SBOM: a list of the parts used in a piece of software.
  • Vulnerable dependencies: the state in which a part you use has a known hole.

Next step

How to find and fix parts with holes is on the vulnerable dependencies page. How your own site looks from outside is covered by the free URL check, and we take questions about how to proceed with checks through a free consultation.

Frequently asked questions

If a scan finds nothing, can we call the container safe?

No. What the OWASP material describes is the ability to find known vulnerabilities, secrets and configuration flaws. Holes that are not yet public, and problems in how the app itself is built, need other checks.

How often should we scan?

Scan before every release, and repeat on a schedule after release. New vulnerabilities are published later, so the result can change over time even for a container that has not changed.

Frequently asked questions

If a scan finds nothing, can we call the container safe?

No. What the OWASP material describes is the ability to find known vulnerabilities, secrets and configuration flaws. Holes that are not yet public, and problems in how the app itself is built, need other checks.

How often should we scan?

Scan before every release, and repeat on a schedule after release. New vulnerabilities are published later, so the result can change over time even for a container that has not changed.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.