Zennoxa Shield
Application Security Glossary

Container Scanning

Container scanning is a method that inspects container images layer by layer to inventory installed OS packages and application dependencies, matching them against vulnerability databases and checking for misconfigurations, outdated base images, and embedded secrets.

A container image bundles an application together with its operating-system packages, libraries, and configuration. Container scanning analyzes that full image, examining each filesystem layer to enumerate the OS packages (via the distro package manager metadata) and language dependencies it ships.

The scanner matches those components against vulnerability feeds such as the NVD and distro-specific advisories to report known CVEs, and it commonly checks for related risks: end-of-life or outdated base images that no longer receive patches, insecure Dockerfile practices (running as root, exposed ports), and secrets baked into layers. Results are tied to specific packages and fixed versions where available.

For developers shipping containers, scanning fits into the image-build pipeline and registry, catching vulnerable dependencies before images are deployed. Because it works from image metadata and advisories, coverage depends on the scanner understanding the base OS and package formats present in the image.

Frequently asked questions

What is container scanning?
Container scanning is the analysis of a container image to find known vulnerabilities in its OS packages and application dependencies, along with misconfigurations, outdated base images, and embedded secrets, before the image is deployed.
How does container scanning work?
Container scanning unpacks an image's layers to inventory installed OS and language packages, then matches each against vulnerability databases like the NVD and distro advisories, while also checking the base image age and Dockerfile configuration.
Container scanning vs SCA?
SCA focuses on the application's declared open-source dependencies, while container scanning covers the entire image including the operating-system packages, base image, and configuration. Container scanning includes dependency risk but extends to the full runtime environment.

Related terms

Container Scanning — Zennoxa Glossary — Zennoxa Shield