The 10 Container Security Tricks That (...)
summary
Containers improve security by making deployments reproducible and short lived and by using concrete controls not vague policies. Practical prescriptions: avoid --privileged and running as root, prefer read-only images and recent official bases like Alpine or Debian stretch, never commit keys — use Docker secrets or Vault, run automated CI builds with image scanning, sign images with Notary/docker trust, roll frequently (reverse uptime), prefer minimal container OSes and add static analysis and fuzzing to catch real vulnerabilities.
AI-written summary · about
chapters (16)
- 0:00Start
- 2:07Ten things?
- 2:42Containers do make security a little easier
- 4:28No silos
- 5:32Teamwork
- 7:49Don't use privileged and capabilities
- 10:01Use read only images
- 10:41Use official images where possible
- 13:23Use the secrets API
- 15:20Always be updating
- 17:28Use an image scanning service
- 20:51Don't try to keep containers running forever
- 22:21Sign your containers
- 23:38Use a minimal underlying OS
- 24:34Fuzz test
- 25:11Test based on your code
related talks
05mContainer Security Best Practices
47mContainer Security, Are You Doing It Wrong?
35mThe 10 steps of Container Security: It's not that hard !
30mMaster the Container Security Model with
35mDocker Security
27mContainer Security Best Practices
34mHow to Contain Security in your Containers
40mSecuring Containers on the High Seas