Threat Modeling

by Adam Shostack
Threat Modeling cover

On this page

Highlights

Chapter 1 Dive In and Threat Model!

My note: .h1

Threat modeling is about using models to find security problems.
Using a model means abstracting away a lot of details to provide a look at a bigger picture, rather than the code itself. You model because it enables you to find issues in things you haven't built yet, and because it enables you to catch a problem before it starts.
Lastly, you threat model as a way to anticipate the threats that could affect you.
Learning to Threat Model

My note: .h2

You begin threat modeling by focusing on four key questions: What are you building? What can go wrong? What should you do about those things that can go wrong? Did you do a decent job of analysis?
In addressing these questions, you start and end with tasks that all technologists should be familiar with: drawing on a whiteboard and managing bugs.
Threats tend to cluster around trust boundaries. This may seem obvious: The trust boundaries delineate the attack surface between principals.
a PIA “is a systematic process that identifies and evaluates, from the perspectives of all stakeholders, the potential effects on privacy of a project, initiative, or proposed system or scheme, and includes a search for ways to avoid or mitigate negative privacy impacts.”

9 highlights, exported from my Kindle via Readwise.

Subscribe to Ishan Girdhar newsletter and stay updated.

Don't miss anything. Get all the latest posts delivered straight to your inbox. It's free!
Great! Check your inbox and click the link to confirm your subscription.
Error! Please enter a valid email address!