Threat Modeling for Secure Software Design
summary
Concrete takeaways and tools not platitudes: threat modeling identifies specific flaws (Jeep Cherokee remote takeover, about 500,000 pacemakers with unauthenticated access), uncovers design errors like confused‑deputy microservice calls and config files with secrets, and recommends measurable mitigations. Use data flow diagrams to map trust boundaries, apply STRIDE to enumerate threats, score risk with FAIR or CVSS, fuzz inputs, and validate fixes. Try Microsoft Threat Modeling Tool or Threat Dragon, break large systems into clusters, and track findings as bugs or requirements.
AI-written summary · about
chapters (26)
- 0:00Intro
- 4:45Secure Software Design
- 6:14Breakdown in Secure Software
- 11:10What is threat modeling?
- 13:33Threat Modeling Vocabulary
- 14:12When? Make threat modeling first priority
- 16:10Who should do Threat Modeling?
- 19:46Threat Modeling Process
- 20:31Draw your picture
- 22:29Understand the system
- 29:24Misuse Cases help with ...
- 30:46STRIDE Framework - Data Flow Property we want
- 32:58Identity Threats - Ask Questions
- 33:27One of the best questions...
- 33:57Identify Threats - Example
- 35:25Scenario - Configuration Management
- 37:57Determine mitigations and risks
- 41:02Risk Rating - Ease of Exploitation
- 41:12Risk Rating - Business Impact
- 43:08Follow through
- 45:23Your challenge
- 46:26Resources - Books
- 47:27Resources - Tools
- 48:45Resources - OWASP Threat Model Slack Channel
- 58:34Session Survey
- 58:48Questions?
related talks
43mThreat modeling
53mThreat Modeling: uncover vulnerabilities without looking at code
57mUnlocking Threat Modeling
22mEmpowering Developers through Threat Modeling Excellence
46mThreat modeling is on the rise
51mApplication Threat Modeling Implementation Tips and Tricks
58mThreat Modeling In And For Your Organization
52mLessons From The Threat Modeling Trenches