CyberGuard dictionary / Cloud Security
Container Image
A container image is a packaged filesystem and configuration used to start a containerized application.
In simple terms
The image includes application code and dependencies. If it contains vulnerable software or secrets, every deployment of that image can inherit the problem.
Technical explanation
Images are built from layers and distributed through registries. Security review includes base image provenance, pinned versions, vulnerability updates, secret scanning, and runtime permissions; an image scan does not assess the whole deployed system.
An image packages application code and dependencies into layers. Provenance, update cadence, scanning, and runtime configuration matter because a clean scan cannot prove safe behavior.
Examples in practice
A team rebuilds its API image after a vulnerable base library is fixed and redeploys the verified new digest.
A build pins a trusted base image digest and scans it before release. When a dependency advisory appears, the team rebuilds the image and verifies that production uses the new digest.
Why it matters
Controlling image origin and updates reduces repeatable exposure across many workloads.
VERIFY & LEARN MORE
Sources and further reading
Published 2026-10-15 · Last updated 2026-10-15 · CyberGuard editorial content. Source links provide context; they do not imply endorsement.