Resilience: It’s Everyone’s Business, So It’s Nobody’s
summary
This talk explains cyber-resilience as a cross-functional responsibility beyond just Dev and Ops, arguing it involves product managers, security architects, directors, HR and community managers. It presents practical, role-by-role measures—such as software architecture practices, code reviews, mental models, Conway’s Law considerations, experiments (including Chaos Engineering where allowed), incident analysis and diversity—to improve the resilience of services, systems and organizations.
AI-written summary · about
chapters (11)
- 0:00Resilience introduction
- 1:51Resilience definition and stakes
- 3:54Failure cycle and strategies
- 8:30Solutions and design patterns
- 13:04Progressive systemic levels
- 19:19Cyber resilience and ransomware
- 25:52Specific vs systemic resilience
- 29:27Community incidentology
- 35:14Diversity as resilience source
- 39:11Summary and conclusion
- 41:21Q&A
related talks
40mWhy Resilience Has Become A Cybersecurity Superpower
40mCyber Resilience: Say What?
43mCyber Resilience Starts Within: A Mental Health Perspective
40mThe Resilience Business Case: Three Case Studies
24mResilient Systems Require Resilient People
36mResilience in Action
24mNational Cyber-Resiliency
34mResilience Isn’t a Buzzword