DevSecOps·DevSecOps essentials

Threat modelling

Model assets, trust boundaries and threats before coding.

Intermediate 10 min read Lesson 1 of 150 Challenge included
What you will be able to do
  • Draw data flows.
  • Name assets and actors.
  • Prioritise mitigations.

In plain English

Model assets, trust boundaries and threats before coding.

  • Draw data flows.
  • Name assets and actors.
  • Prioritise mitigations.
threats.txtText
asset: learner data
trust boundary: browser -> API
threat: session theft
mitigation: HttpOnly cookies + rotation
Your turn

Explain it back

Easy

Answer from memory: When should threat modelling happen?

TEXT · starter
Your answer…
Check your understanding before moving on.
Knowledge checkQuestion 1

When should threat modelling happen?

Select an answer to continue
Study tools

Make it yours.

Keep a private note for this lesson, then turn the key ideas into flashcards you can revisit.

Sign in to save notes and flashcards.Both are private to your account and stay with your progress.
Sign in
Finished reading?

Lock in what you just learned.

Mark this lesson complete to save your place and move one step closer to the certificate.

Next: Dependency scanning
Lesson 1 of 150 · 0% of course