Ewance
← All challenges Security Engineer

Threat Model a HealthTech Patient-Portal Web App

Duration
3 weeks
Level
Advanced
Type
Design
Team
1 to 5 people

The situation

The HealthTech (Series-B at USD 35M raised, around 240,000 monthly active patients) is being held to a SOC 2 Type II + HIPAA risk assessment by its largest hospital-system customer — a credible threat model is part of the contract renewal.

Your task

Run a STRIDE threat model on a HealthTech patient-portal redesign and produce a defensible launch-blocking decision list.

The brief

You start with

Read the 25-page redesign architecture document (auth via Clerk, Next.js front-end, FastAPI backend, Postgres, S3 for documents, webhook integration with EMRs).

What you do

  1. Build data-flow diagrams (Level 0 + Level 1) showing trust boundaries.
  2. Run a STRIDE threat-modeling session with 6 participants (you + tech lead + security engineer + product manager + privacy officer + EMR-integration lead).
  3. Identify 35-50 raw threats, then rank top-20 using a likelihood × impact scoring including HIPAA breach magnification.
  4. Author mitigations per threat (control type: prevention / detection / response) and tag which mitigations must ship before launch vs can ship after.
  5. Build a 1-page launch-blocking decision memo with the 5 must-ship items.

You deliver

DFDs, threat list, mitigation plan, and launch memo.

What you will practice

  • Apply STRIDE methodology to a real web-app architecture
  • Draw data-flow diagrams with explicit trust boundaries
  • Rank threats including regulatory-magnification factors
  • Communicate launch-blocking decisions to a product audience

A suggested way in

  1. Adam Shostack's 'Threat Modeling: Designing for Security' is the canonical reference
  2. STRIDE-per-element is more thorough than STRIDE-per-interaction for a focused 6-component app
  3. HIPAA breach magnification turns a Medium into a Critical — never skip the regulatory weighting

Skills you will practice

Threat modeling, Stride, Secure design, Data flow diagrams, Hipaa, Risk management

Where it leads

Product Manager

How it is assessed

  • DFD quality20%

    DFDs show trust boundaries explicitly and survive review by a system architect.

  • Threat identification30%

    Top-20 covers all 6 STRIDE categories with concrete attack chains.

  • Mitigation realism30%

    Mitigations are implementable in the launch window and named per type.

  • Launch-memo clarity20%

    Launch memo defines 5 must-ship items unambiguously.

Resources

  • Microsoft Threat Modeling ToolTool

    STRIDE-based threat enumeration with DFD support.

  • draw.ioTool

    Data-flow diagrams with explicit trust boundaries.

  • MermaidTool

    DFDs as code, embeddable in documentation.

  • NotionTool

    Author threat list and mitigation plan.

  • LinearTool

    Track mitigation items as launch-blocking issues.

  • Google DocsTool

    Launch-blocking decision memo with product + security comments.

Sample Ewance certificate of completion, verified by LearnCoin
Sample certificate
Your proof

Finish it. Earn this.

A verified certificate with your name. Anyone can check it.

Time to practice.

Solve this challenge
Related challenges

More like this.