Collapsology: Why your biggest threat isn’t exposed RDP
summary
Argument: organizational collapse follows predictable cultural failure not just unpatched services. Evidence: Neo‑Assyrian turf wars and Roman 1,700‑year longevity show politics and high‑reliability behaviors matter. Tools described: competing security cultures framework, a 25‑statement survey plus metrics in the security force behavioral model, and a 10‑question security culture diagnostic survey. Case: Code Spaces 2014 EC2 compromise illustrates what happens when resilience is missing. Outcome claim: these instruments surface political, logistical, emotional and bias threats so teams can measure change, not just virtue‑signal.
AI-written summary · about
chapters (12)
- 0:00Intro
- 2:05REASON FOR COLLPASE
- 2:58IN THE MODERN DAY
- 5:59SECURITY TOOL #1
- 6:57CASE STUDY #1
- 8:44REASON FOR SUCCESS
- 11:46SECURITY TOOL #2
- 14:29CASE STUDY #2
- 17:22IN THE MODERN DAT
- 22:29SECURITY TOOL #3
- 24:30CASE STUDY #3
- 25:21TYING IT ALL TOGETHER
related talks
33mLearning from Past Security Breaches: Strengthening AppSec Efforts and Focus
20mCalcifying Crisis Readiness
37mSecurity Culture Hacking: Disrupting the Security Status Quo
50mSecurity's Social Problem
34mThe Epistemology of Trust (Mike Wilkes)
40mCulture Matters—Put People at the Heart of Security
46mCultivating a Security-First Culture in Tech Organizations
40mRebels & Resilience—Why It Pays Off to Break Your Patterns!
