Keynote: The Cloud Native Chasm
summary
Argues that cloud native projects need project-specific security choices, not generic checklists, and gives concrete practices: use security reviews and CNCF catalogs, tag and track the single functions that protect data, and require optional components (example: embedded web server explicitly enabled) to enforce secure by default behavior. Warns against cargo‑culting supply‑chain fixes, urges continuous iteration and participation in SIG/TAG reviews so projects can actually cross the chasm.
AI-written summary · about
chapters (6)
- 0:00Keynote: The Cloud Native Chasm Emily Fox, Security Engineer, Apple
- 0:28It's a jungle out there...
- 2:22and everything is on fire
- 4:15What does success look like?
- 5:43A bridge to nowhere is useless.
- 7:42Expect the worst, design it to be the best
related talks
05mKeynote: Crossing the Chasm with Cloud Native
01h 26mKeynote Presentation Software Defined Security Governance
39mCloud Native Security Landscape: Myths, Dragons, and Real Talk
20mKeynote: What is Cloud Native and Why Should I Care?
30mHow to beat an existential crisis by becoming Cloud Native.
08mKeynote: Security of the Open Source Supply Chain, a Call to Action
38mShift Down Security! How Platform Teams Can Help Break the Logjam
21mGrowing up in a cloud native org