Demo: threat-modeling the checkout flow
On This Lesson 3 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 checkout end to end and leave with tests and tickets. Prepares MID-052-LAB1.
Draft outline details
Step by step
- Draw the DFD: browser, gateway, orders, payments (external), PostgreSQL, Kafka; mark trust boundaries.
- Apply STRIDE to each flow; list threats in a table.
- Planned mistake: list only technical threats (SQL injection, XSS). Fix: add business abuse cases (coupon reuse, price tampering in the request body, double charge by retry).
- Rank the top five and write the mitigation for each.
- Write one test per threat (price in body is ignored; coupon unique per customer) and file the rest as backlog items.
Check your understanding
Where should the price come from at checkout?
Show answer
The server's catalog, never the client request.
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.