Token Leak: Customer Data Exposure on a B2B SaaS Platform
Technology tabletop exercise scenario · SaaS Data Breach
It starts with a polite email from a stranger: a security researcher found your internal API token in a public repository. It's been there five weeks. It still works. And your logs only go back 30 days.
This scenario captures the modern SaaS breach in miniature: not a Hollywood intrusion, but an exposed credential, an evidence gap you can't close, notification clocks that start at different times for different customers, a disclosure deadline set by someone outside your company — and a sales pipeline that suddenly intersects with your incident response.
Your security, legal, and go-to-market leaders will practice the discipline that separates trusted vendors from cautionary tales: saying what you know, exactly when you should, no more and no less.
1 hr 30 minIntermediate
TechnologySOC 2GDPRISO 27001
What this scenario tests
- Whether your team can scope a breach honestly when the logs don't cover the exposure window
- How you sequence notifications across GDPR, contracts, and state laws with different clocks
- How your company works with a researcher who controls the disclosure timeline
- Whether sales and security can share the truth without breaking either the deal or the law
Who it's for
IT & Security Team · Legal & Compliance · Executive / C-Suite · Communications / PR