Demo: threat-modeling Larkspur's checkout and payment 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
run a worked threat-modeling session on checkout; prepares ARC-028-LAB1.
Draft outline details
Step by step
- Draw the checkout data flow: browser, web app, basket service, payment provider's hosted page, order service, ERP.
- Mark trust boundaries: browser/internet, platform/provider, platform/ERP.
- Walk each boundary: skimming script, price tampering, replayed payment callback, stolen session, insider refund abuse.
- Planned mistake: jump straight to controls (a WAF, more logging) before ranking. Fix: score each threat first; the replayed callback and price tampering outrank a generic WAF rule.
- Assign controls and owners to the top threats and record accepted risks.
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.