HavocLabAll scenarios →
SEV-2Caching

Time To Leave (TTL)

To speed up logins, the security team set the RBAC cache to an infinite TTL, and the Identity Database has never been happier. Then HR fired Ron over Zoom and IT revoked his credentials. The database knows he's gone. The cache does not. Ron is at the Starbucks across the street, still pulling company data at 2ms latency. The Job: A revoked credential has to stop working almost immediately, with no stale "still allowed" reads surviving, and the database can't melt under the load of staying fresh. Lock Ron out before he finds HR's home addresses.

Free to play, no account needed. A deterministic engine grades your design against this scenario's SLA - error rate, latency, and cost.