Integrating Cloud Native Security into the SRE culture
summary
Claims a concrete workflow: install Trivy operator (or CLI in CI), export security reports as Kubernetes resources, and feed metrics into Grafana/Prometheus/Loki for dashboards. Demonstrates a real cluster dashboard showing 175 vulnerabilities and gives mitigation rules: prioritize criticals, filter by fixes, assign ownership, and add runbooks and ownership for alerts. Lists tools used (Helm, GitLab CI/CD, Jaeger, Tempo) and warns about automation noise and privilege risks when scanners run inside clusters.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:39Integrate Cloud Native Security with SRE
- 5:11SRE culture principles
- 7:00DevSecOps and shared ownership
- 8:45SRE versus Cloud Native Security
- 12:14Practical steps for security
- 14:45Security needs and factors
- 21:06Choosing a security scanner
- 22:31Trivy setup for Kubernetes
- 26:24Security dashboards in Grafana
- 27:04Avoiding vulnerability fatigue
- 29:08Why alerts matter for security
- 31:13Tips for security integration
- 32:41Runtime tools beyond scanning
- 33:45Resources and Q&A
related talks
31mIntegrating Cloud Native Security into the SRE culture
30mIntegrating cloud native security into the SRE culture
32mClimbing high — getting started with cloud native security through open source
01h 21mFirst Steps to Full Lifecycle Security with Open Source Tools
16mContinuous CVE Scanning with Trivy Operator
32mStrengthening Kubernetes Security
26mBoost your security and resiliency in Kubernetes
22mGitOps - The Magic Key to Cloud Native Security