Skip to content
Free · Pro export · Incident response · Template

Customer Database Breach Lab

Your customer database is for sale on a forum. Verify the sample, scope 2.1 million records, decide when the clocks started, choose between notifying now or waiting for forensics, handle an extortion email and write the customer notice. Ten scored decisions, with branches.

Template & sample only — a structured starting point with sample content, not legal, audit, certification or investment advice.Customise it with your own details for free; exporting the generated document is part of Pro.

No download, no card
Template & sample scenario. A fictional rehearsal built on common real-world patterns, not a record of any real organisation, audit or deal. Generated from a PlayCISO template as a starting point: it is not legal, audit, certification, investment or professional advice. Review, adapt and validate it for your organisation before you rely on it.

A seller on a criminal forum is offering what they say is Lumen Home Goods's customer database. You are the CISO. Verify the claim, scope what was taken, decide when the notification clocks started, handle an extortion email and write the customer notice. Ten decisions, each scored with feedback on why it matters and what it costs.

Make it yours

Replace the sample names so the scenario and the debrief you export are about your organisation.

TL;DR

What this template gives you

  • Ten decisions from the first threat-intel alert to the post-incident review, each scored 0–10 with feedback on why it matters, what it costs and what it does to the notification clock.
  • Branches change the story: ignore the tip and customers are phished first; wait for forensics and the regulator calls you; pay the extortionist and the data appears anyway.
  • Realistic artefacts: the forum listing, a database audit-log line showing the export, the extortion email, residency splits for the US state deadlines.
  • Rename the organisation and roles so the debrief reflects your own team.

Frequently asked questions

When does the GDPR 72-hour clock start after a database leak?

When the controller becomes aware — has a reasonable degree of certainty that a security incident has compromised personal data. Confirming that a leaked sample matches your production data is usually that point. Record the time and the reasoning. Confirm with counsel.

Should we wait for the forensic report before notifying?

Generally no. GDPR allows information in phases, and many other regimes expect an initial notice followed by updates. A late complete notice is usually worse than an on-time partial one.

Does paying an extortionist remove the duty to notify?

No. Payment buys a promise from a criminal, not deletion, and the duty to notify depends on the risk to the people affected, which payment does not change.

Is this a finished document I can rely on?

No. Every tool in this suite is a template with sample content. It gives you a structured, editable starting point and generates a document from your own answers, but it is not legal, audit, certification, investment or professional advice. Review and adapt the output, and have it checked by the appropriate specialist before you rely on it.

Who can use it?

Anyone. Using it and customising it with your own details is free, and your work is saved in your own browser. Exporting the generated document (Word, PDF, Markdown, CSV) is part of any PlayCISO paid plan.

The tools people use most on PlayCISO.

All tools
🎉 New here? Use code WELCOME10 for 10% off any plan at checkout
Customer Database Breach Lab: Free Scenario · PlayCISO