Cloud Native Security: A New Paradigm for a New World
summary
Claims that matter: a move to zero-trust identity and encryption everywhere, concrete shift-left practices, and continuous automation. Cites 233,000 CVEs last year and kernel.org retroactively opening ~700 CVEs in a week, notes containerD was patched within hours and images (flatcar, Ubuntu) rolled days later. Recommends automated image scanning, lifecycle restarts for pods (often >100 days), and tools like FAL Cod, Ceno and KS GPT to detect and enforce policies.
AI-written summary · about
chapters (13)
- 0:00Cloud Native Security intro
- 2:10Traditional security limits
- 8:18CVE inflation impact
- 12:31Pets to cattle shift
- 15:46Why Zero Trust matters
- 18:39DevOps culture
- 21:31Shift Left with SuS and DuS
- 25:03Zero Trust architecture
- 27:36Automating Kubernetes security
- 31:57Observability in security
- 33:04DevSecOps and platform engineering
- 35:50Security team collaboration
- 38:42Encryption costs and gains
related talks
34mCloud Native Security: A New Paradigm for a New World
34mCloud Native Security 101: Building Blocks, Patterns and Best Practices
37mCloud Native Security 101 - Introduction, Workflows and Best practices
35mCloud Native Security for the Rest of Us
41mCloud Native Security For The Rest Of Us
52mSecurity in Cloud-Native
23mCloud Native Security for the Rest of Us
32mHow cloud-native applications are helping orgs stay ahead of cybersecurity threats