Containers (e.g. Docker) package an app with its dependencies so it runs anywhere. They're lightweight and everywhere in modern cloud and DevSecOps — but they bring their own security concerns.
Container Security
Securing Docker images, runtime and the shared kernel.
Tap or hover a part to learn more.
Scan for CVEs.
Containers build on base images that may carry known vulnerabilities. Scan images in CI/CD and use minimal, trusted, signed base images.
Check your understanding
1. Why is a container escape serious?
2. How should containers run?
Keep learning
Key risks and controls
- Vulnerable images — containers are built from base images that may carry known CVEs; scan images in the pipeline (vulnerability management).
- Least privilege — don't run containers as root; drop unneeded capabilities.
- Image provenance — use trusted registries and signed images (a supply-chain concern).
- Runtime isolation — containers share the host kernel, so a container escape is the key threat; keep the host hardened and patched.
Container security is a DevSecOps staple — shift scanning left and enforce policy before deployment.
