Containerization and micro-services in real life change security and vulnerability management
summary
Microservices and containers force security to change: ephemeral containers make periodic scans useless so teams adopt continuous runtime monitoring, enforce image configuration scans at build time, and apply fine‑grained identity for every service-to-service call. Open-source image scanners and policy engines sit alongside runtime protection; network controls shift from host-level to per-connection enforcement. Expect misconfiguration to be the largest practical risk and defense-in-depth plus automated CI/CD checks to be the only realistic way to keep a dynamic fleet acceptably secure.
AI-written summary · about
chapters (9)
- 0:00Introduction to security in containers
- 1:05Microservices and security challenges
- 3:32Containerization security shifts
- 5:45Container communication risks
- 7:12Runtime security and configuration
- 9:01Tool selection and implementation
- 10:08Identity and authorization in microservices
- 11:54Defense in depth approach
- 12:36Q&A on security changes
related talks
27mContainer Security Best Practices
46mWhat Security People Want: Making DevSecOps Happen with Containers
53mSecurity And Microservices
48mContainer Security: It’s All About the Supply Chain
25mContainers. Microservices. Cloud. Open Source. Fantasy or Reality for Enterprises?
05mContainer Security Best Practices
47mContainer Security, Are You Doing It Wrong?
53mAppSec & Microservices