Threat modeling at subsystem scale
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
model threats in a way that fits a real subsystem.
Planned topics
- Four questions: what are we building, what can go wrong, what will we do about it, did we do a good job.
- Draw a data flow diagram with trust boundaries; walk each flow and store with a prompt list such as STRIDE (spoofing, tampering, repudiation, information disclosure, denial of service, elevation of privilege).
- Adapt a checklist to the system: payments, personal data, multi-tenant data, messages, AI components.
- Keep the model alive: update on design changes.
Draft outline details
Demonstration
Data flow description: client to gateway to orders service to database and payment provider, with Kafka between services; trust boundaries at the gateway and at the provider; table of threats per boundary.
Check your understanding
What does STRIDE give you?
Show answer
A set of prompts for categories of threats to look for.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.