What’s In Your Burrito?
summary
Chipotle’s appsec team maps CIS-style controls into SDLC pipelines and proves it works: a two-person team scales by shipping developer golden paths and templates, blocks ~350+ public misconfigurations found in research by forcing clusters behind VPN/bastions, enforces image signing (Notation) and SBOM/EOL checks (Grype, Xeol), refuses deploys with critical/high vulns and validates ACR scans, applies Gatekeeper/rego admission controls, and runs eBPF sensor (Falco) plus Namespacehound, Kubescape and network policies (Cilium/Calico) for runtime and posture assurance.
AI-written summary · about
chapters (17)
- 0:00Kubernetes security at Chipotle
- 1:48Restaurant vs Kubernetes security
- 3:32Kubernetes threat matrix
- 5:22Software supply chain protection
- 7:08Security architecture planning
- 8:54Threat modeling best practices
- 12:48Securing build pipeline
- 16:26Identity management in Kubernetes
- 18:09Admission controllers
- 20:19Risk profiles for workloads
- 22:03Image verification scanning
- 23:46Runtime monitoring validation
- 26:53Kubernetes posture compliance
- 29:04Prioritizing security controls
- 32:16Kubernetes security tools
- 35:51Developer golden paths
- 36:55Q&A
related talks
48mAppSec++ Take the best of Agile, DevOps and CI/CD into your AppSec Program
29mSecuring Your Web Application Pipeline From Intruders
19mFrom Code to Cloud: Embedding Security
48mSecuring Your Pipes with a TACO
57mWhat’s in an AppSec program?
32mIntroduction to CDD and Security Centric System Design
57mShift Left Security with the Security Test Pyramid
55mAh mom, why do I need to eat my vegetables?
