Fueling The Future: Building Robust Engines
summary
Argues that software must be treated as safety‑critical engineering, not just bug hunting, and backs that with history (Triangle Shirtwaist 140 deaths, 19 11? no) and numbers: 27 US elevator deaths last year with 14 worker fatalities, the $1.4B crypto theft likely via phishing vector, and current bug markets (zerodium prices: desktop/server ~$500k, virtualization ~$1M, mobile zero‑clicks in the millions). Shows CVE trends 2002–2024 where SQL injection and memory bugs persist, notes AFL fuzzers and recent VPN vuln discoveries, and commits to releasing the dataset for reproducible defensive work.
AI-written summary · about
chapters (10)
- 0:00Introduction and cyber threats
- 3:14Industrial revolutions and safety
- 8:51Cyber security industry flaws
- 12:08Lift safety analogy
- 14:14Transistors and ENIAC history
- 16:43Defensive security challenges
- 19:51Bugs with real-world impact
- 23:06Espionage and surveillance era
- 24:51Web application vulnerabilities
- 28:44Current software weakness trends
related talks
57mFinding, Managing, Preventing Vulnerabilities: An Automotive Perspective
33m40,000 CVEs and Counting: What 60 Years of AppSec Tells Us About 2026
23mSecure Code, Safe Future: Mastering Security in Critical Software Development
50mSmashing the Stack: Let’s Make It Less Fun And Unprofitable!
23mKeynote: Fireside Chat with Window Snyder & Katherine Druckman
39mSoftware Security Engineering (Learnings from the past to fix ...)
14mKeynote: The Human Cost of Security in the AI Era
51mPreventing Security Bugs through Software Design