Chapter 2 of 6 · 4 practices · 5 min · 4-question quiz
What are we working on: diagrams and trust boundaries
A shared picture of the system is the foundation. This chapter covers data flow diagrams, trust boundaries, scope, and keeping the model where the team can update it.
Start: Draw a data flow diagram with the standard elements4 practices in this chapter
- 1Draw a data flow diagram with the standard elementsThe OWASP cheat sheet calls data flow diagrams (DFDs) the most common way to model a system for threat modeling. A DFD shows what talks to what and where data goes, using a small set of elements…
- 2Mark every trust boundary and look hardest where flows cross themA trust boundary is any place where data or a request moves between parts of the system that trust each other differently. Crossing one is where you must ask: who is really sending this, can it be…
- 3Set the scope, and list assets and entry points before hunting threatsA threat model that tries to cover everything finishes nothing. The Manifesto suggests iterations scoped to manageable portions of the system. Before looking for threats, write down three short…
- 4Keep the model where the team works, and use more than one viewOWASP's cheat sheet says to store the model where the team can update it. A diagram in someone's laptop or an expired whiteboard photo cannot be maintained.
Check yourself on this chapter
4 questions, right here once you are signed in. Your progress is saved as you read.