All tabletop exercises
DevSecOps / supply chain·Advanced·Technical audience
A tenant-isolation bug shows customers each other's data
The prompt — read this to the room
A customer of your 400-person HR software company opens a support ticket with a screenshot: their dashboard search returned salary records belonging to another customer's employees. Engineering traces it to a caching change deployed nine days ago that sometimes keys results by query text instead of by tenant. Logs show the faulty path ran at least 6,000 times, but nobody yet knows how many of those responses held another tenant's data, or which tenants saw what. You process data for 1,100 business customers, most of them in the EU and UK. The fix is ready. Do you ship it now?
Total duration
2 h 30 min
People to involve
7
Best fit
Saas
Who to involve
Most important first.
- Incident response lead
- Developer / DevOps
- Cloud engineer
- CISO / Head of security
- Privacy officer / DPO
- Legal counsel
- Customer support
What it tests
- Fix the bug while preserving the evidence needed to scope cross-tenant exposure
- Reconstruct which tenant saw which other tenant's data, with stated confidence levels
- Meet processor duties to notify controllers without undue delay, with consistent facts
- Decide what each customer is told, and in which order
Outline of activities
- 1The screenshot and the caching change
- 2Ship the fix, keep the evidence
- 3Exposure reconstruction from logs
- 4Processor notifications to controllers
- 5Customer conversations and engineering follow-up
Run sheet (Pro)
The facilitator's timeline of execution, the detailed steps for running the session and the questions to ask each person.
Loading…