Cloud Native Security: A New Paradigm for a New World
summary
Perimeter defenses fail as humans, third‑party packages and sprawling clusters bypass static controls; CVE counts spike dramatically since May after kernel.org reclassification, making manual patching impossible. The new posture enforces zero-trust between services, shift-left scanning (SAST/DAST, SBOMs) and continuous runtime checks. Practical stack examples: image scanners like Trivy and Grype, registry integration (Harbor), kube-bench/kube-score for cluster checks, Falco/KSPT-style runtime detection and Cilium for mesh encryption and microsegmentation.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:26Old World security flaws
- 9:29Cloud native security shift
- 15:10DevOps and automation
- 20:07Zero trust architecture
- 22:13Security tools in pipelines
- 25:51Observability and DevSecOps
- 27:19Collaboration is key
- 28:45Q&A session
related talks
40mCloud Native Security: A New Paradigm for a New World
34mCloud Native Security 101: Building Blocks, Patterns and Best Practices
35mCloud Native Security for the Rest of Us
41mCloud Native Security For The Rest Of Us
37mCloud Native Security 101 - Introduction, Workflows and Best practices
23mCloud Native Security for the Rest of Us
52mSecurity in Cloud-Native
39mThe Art of (Cloud Native) Defense: Pillars of Kubernetes Security