Container Security Best Practices
summary
94% of respondents say containers raise security concerns, 60% report incidents last year, 47% run at least one vulnerable image and 46% don't know if they do. Checklist: seven concrete areas — build (verify images, use image scanning like Claire from Korres, limit allowed base images), network (default deny network policies and default deny network policies, layer‑7 rules with a service mesh and mTLS, log failed connections), host/runtime (seccomp/syscall filters, SELinux, restrict privileged containers), orchestrator audits and API RBAC, encrypt and log data access, and monitor cloud provider defaults and component versions.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:03Why Container Security
- 3:04Security shouldnt be an afterthought
- 4:26Seven Chakras
- 5:21Secure Build Type Line
- 7:48Secure Network
- 11:14Secure the Host
- 12:51Secure the Container Runtime
- 16:13Secure the Orchestrator Configuration
- 19:51Secure the Data
- 22:36Secure the Cloud
- 25:22Conclusion
related talks
05mContainer Security Best Practices
47mContainer Security, Are You Doing It Wrong?
48mContainer Security: It’s All About the Supply Chain
28mContainer Security: A Horror Story
26mThe 10 Container Security Tricks That (...)
40mSecuring Containers on the High Seas
35mThe 10 steps of Container Security: It's not that hard !
24mCracking the Code of Cloud Security