Follow an Attack

Choose a fictional attack path. Watch the missing control cross a trust boundary, then add defenses and rerun. The simulator focuses on secure design, blast radius, detection and recovery—never operational exploitation.

Choose an attack to follow
Follow an Attack: Broken Authorization
Goal: Read another customer’s invoice using a valid account.
ATTACK SUCCEEDS
  1. 01
    Valid login
    The attacker starts as an ordinary customer.
  2. 02 · TRUST CROSSING
    Change resource ID
    A client-controlled identifier selects another record.
  3. 03
    Authentication passes
    The cookie is valid; identity is known.
  4. 04 · TRUST CROSSING
    Ownership check missing
    The API loads by id without tenant/owner scope.
  5. 05
    Sensitive data returned
    A valid 200 response makes the breach quiet.
Click a defense to add it, then watch the path rerun
The attack above re-evaluates immediately. Read the trade-off before you add it.
0 of 3 added
Blast radius
Cross-user or cross-tenant invoice disclosure. Authentication logs misleadingly show a valid user.
Detection
No detection control selected: this can fail silently.
Residual risk
The asset is reached; contain the identity and scope access from logs.
All scenarios run only as conceptual state transitions inside Engineer Atlas. They contain no real targets, credential workflows, stealth or persistence.