Challenge 34 · starter · Secrets handling
Secrets exposure
A payments service loads its database password and a payment provider key from a secret manager at startup. It logs every request in full, its framework debug endpoints are reachable from the internet, and its error pages show stack traces. At 10 seconds an attacker starts scanning for debug endpoints and sending malformed requests. This is a fictional, self-contained simulation.
From 10 to 60 seconds, expose no secrets at all, and keep at least 90% of your ability to debug from logs.
Goal · measured 00:10–01:00
0 changes · par 3- Secret copies exposed ≤ 1 copiesnot measured yet
- Debugging ability from logs ≥ 90%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.