Secure Applications, By Design
summary
Claims a repeatable process: threat modeling + partitioning + defense in depth with concrete outcomes. Shows a hotel card-authorization system on AWS that replaces faxed forms with a third-party tokenization service, adds CI static analysis, continuous monitoring, minimized stored data, and compartmentalized IAM. Uses Microsoft Threat Modeling Tool 2016 and mentions Threat Dragon. Cites concrete failures—2012 trading bug $440M—and treats mitigations as iterated, prioritized tickets until risks are marked mitigated.
AI-written summary · about
chapters (19)
- 0:00Start
- 23:25COMPREHENSIVITY
- 24:52COMPARTMENTALIZATION Is this made of distinct parts with limited interactions?
- 26:38BUSINESS PROBLEM
- 29:24NAÏVE SOLUTION, REVISITED
- 33:20DESIGNED INTO PROCESS
- 34:49TRAINING
- 36:40Opportunity PATCH ALL OF THE THINGS
- 37:54Rigor STATIC ANALYSIS
- 39:12MINIMIZE ATTACK SURFACE (and everything else)
- 40:08Minimization STORE LESS
- 41:35DOUBLE EDGED SWORD
- 42:30LEAST PRIVILEGE
- 43:09COMPARTMENTALIZE IT!
- 44:00FAULT TOLERANCE
- 45:58PROPORTIONALITY
- 47:14LATHER, RINSE, REPEAT
- 48:24FURTHER READING
- 49:44CREDITS
related talks
43mSecurity By Design
57mUnlocking Threat Modeling
50mSecure and Privacy by Design Converge with Threat Modeling
29mThreat Modelling 101
48mSecurity Practices for Developers
43mThreat modeling
51mApplication Threat Modeling Implementation Tips and Tricks
18mCommit Secure AI: Embedding Security in Code, Pipelines, and Production