2024 Security BSides // Juliet Okafor
summary
Built a resilience program by boarding ships, interviewing every person tied to engines and reviewing docs, which finds a vendor monitoring breach that allows remote hacks; that program scales to 100 ships in 40 languages and uses OT assessments, SIEM/SIM logs, BIAs and threat TTP analysis. Claims a five‑step ID R A framework (Investigate Declare Respond Recover Adapt) and insists on RTO/RPO/MTD metrics; contrasts a Cayman response that fixes primary issues in ~2 months with Columbus where 70% systems still down months later.
AI-written summary · about
chapters (12)
- 0:00Introduction and background
- 3:17From security to resilience
- 8:39Security culture at scale
- 13:19Security vs. resilience
- 18:44Introducing the ID R A framework
- 22:37Protecting customers before breaches
- 27:17Investigate and declare phases
- 33:04Respond and recover phases
- 38:43Case study: Cayman Islands vs. Columbus
- 43:37Culture over awareness
- 48:17Building adaptive security culture
- 52:20Q&A session
related talks
52mContinuous Security
33mLearning from Past Security Breaches: Strengthening AppSec Efforts and Focus
17mA Resilient Journey
45mBuilding Your Roadmap to Cyber Resilience – Five Things You Can Do Today
24mBeing secure by design: Engineer-led security
11mIT Security Conference 2025 | Olivier Bailiez | Rapid7
29mBuilding a Security Operations Program
20mCalcifying Crisis Readiness