Building in cyber resilience
summary
Claims that software ecology has 25,000 critical vulnerabilities (2025) and causes ~$10.5 trillion/year, with 70% of CVEs being memory‑safety bugs (Chromium: 38% pointer, 34% use‑after‑free, ~20% control flow). Proposes DARPA‑born CHERI as a concrete fix: CHERI compartmentalization plus pointer sealing, 300‑instruction provable boot, formal verification (Oxford), Microsoft/Google adoption, Rust/C/C++ support, and US procurement now requiring a pathway to memory safety — built to shrink blast radius and make Cat‑1 systemic bugs nearly impossible.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:50Cybersecurity challenges today
- 3:40Permissive architectures flaws
- 4:45Memory safety bugs impact
- 7:37DARPA CRASH and CHERI
- 9:42Formal verification in systems
- 13:57Compartmentalization blast radius
- 16:25Self-healing systems secrets
- 18:12CHERI capabilities adoption
- 19:37CRA timeline realities
- 21:03Security by design incentives
- 23:36CRA compliance measuring
- 24:17Proving secure design handling
- 27:11ISA security certification
- 28:14US mandates memory safety
- 28:56Incident impact insurance
- 30:00Vulnerability reporting patching
- 30:41Summary
related talks
18mWhat’s next for memory safety?
23mHardware security for critical national infrastructure
31mMemory Safety: The Pernicious Challenge
57mFinding, Managing, Preventing Vulnerabilities: An Automotive Perspective
25mLightning Talk: Protecting Zephyr Against Memory Safety Vulnerabilities With the New CHERI Hardware Architecture
20mMaking CHERI Accessible- 25mLightning Talk: Protecting Zephyr Against Memory Safety Vulnerabilities With the New CHERI Hardware Architecture
50mSmashing the Stack: Let’s Make It Less Fun And Unprofitable!