Nuclear powered software security
summary
Maps actionable safety techniques onto web security and shows concrete mitigations: use fault tree analysis to trace “steal customer data” to login, CS rep and DB routes; harden customer service accounts with two‑factor authentication; encrypt database fields and protect keys with hardware security modules or isolated backend keys; apply defense-in-depth, network zoning and isolate backups, remove single points like shared admin credentials, enforce HSTS and disable HTTP fallbacks to fail secure.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:42Nuclear safety
- 2:00Nuclear bomb
- 3:10Nuclear power plant
- 6:04Loss of cooling
- 6:55Loss of power
- 7:35Inhibit gate
- 8:58E-Commerce
- 10:48How to use your diagram
- 13:27A big firewall
- 15:10Defense in depth
- 16:45Database Access
- 17:55Adding encryption
- 20:50United Airlines Flight 232
- 24:09Zonal analysis for security
- 28:26Zonal analysis for data
- 31:50Chernobyl accident
- 34:02Passive safety
related talks
59mPractical Security for Web Applications
30mWeb Security Engineering - Protect all layers of your project
01h 24mCode Red: Navigating the Minefield of Security Programming Blunders
46mThe Path of Secure Software
29mGraphQL Security Best Practices and Hardening
01h 03mTen Key Steps for Enhanced Web App Security
51mSecure Applications, By Design
01h 00mDefense-in-depth engineering