Challenge 23 · intermediate · Token validation
JWT misconfiguration
An accounts API reads a JSON Web Token on every request and trusts what it says. Real users send 300 requests a second; a few of their phones have clocks up to 45 seconds out. At 10 seconds an attacker starts sending three kinds of bad token: stolen ones that expired hours ago, forged ones whose header says "alg": "none", and genuine tokens our identity provider minted for the billing service.
From 10 to 60 seconds, refuse every attacker request and accept at least 99.5% of real users' requests.
Goal · measured 00:10–01:00
0 changes · par 4- Attacker requests refused ≥ 100.0%not measured yet
- Real users' requests accepted ≥ 99.5%not measured yet
Service map
What changed
Turn on a fault or change a defence while the run plays. Its effect shows here: the 5 seconds before against 5 seconds after it settles.
This is a simulation. Its numbers come from a model of a typical system, not from measuring real servers. The same link and seed always give the same run. How the Chaos Lab works.