Bank Tabletop Exercise: Customer Data Breach and Fraud Spike

A generic, reusable tabletop exercise template for banks, credit unions, and other financial institutions. Run it on paper in about 90 minutes. Replace bracketed details to fit your organization. No real organization names are used.

This exercise is aligned to FFIEC information-security and incident-response guidance and designed to support Gramm-Leach-Bliley Act (GLBA) Safeguards expectations. It does not by itself satisfy any regulation or ensure compliance.

Scenario summary

A contact at a cyber task force tells the institution that a dataset matching its customers is being advertised for sale on a criminal forum. The institution's own monitoring shows no alert. Over the following hours the team confirms the data is genuine, traces how it left, weighs a request to delay public notice against a rising fraud signal, and manages notification, the contact center, regulators, and the press — all while the full scope and whether the access is still open remain uncertain.

Exercise objectives

  1. Confirm or rule out a breach from an external tip within a target time, using internal data rather than the tipster's word alone.
  2. Identify the exfiltration path and determine whether unauthorized access is still active, with a defined containment decision point.
  3. Make and document a notification-timing decision that weighs an investigative hold against customer harm.
  4. Scale the contact center and customer-facing teams to a surge, with accurate scripts and identity-verification safeguards.
  5. Coordinate consistent communication across customers, regulators, and media through single owners.
  6. Track the fraud signal and tie customer-protection actions (holds, re-issues, monitoring) to it.

Participants and roles

  • Incident commander — senior risk or operations executive who runs the response.
  • Security / IT team — forensics, containment, and the technical timeline.
  • Fraud operations — account-takeover monitoring and customer protection.
  • Legal / compliance — notification obligations, regulator engagement, privilege.
  • Communications / PR — customer, media, and public messaging.
  • Contact center leadership — surge staffing, scripts, and escalation.
  • Executive sponsor — approves cross-functional trade-offs and external statements.
  • Facilitator — delivers injects, keeps time, captures decisions (not a participant).

Injects

T+0 — A call from outside. Delivered to: security team → incident commander. A cyber task-force contact reports a dataset advertised for sale that appears to contain the institution's customers — names, account numbers, balances, and phone numbers. Internal monitoring has shown nothing.

  • How do you verify whether this is real without relying only on the tip?
  • Who needs to be in the room in the first hour, and who decides that?
  • What do you preserve now in case this becomes an investigation?

T+20m — It's genuine. Delivered to: security team + fraud operations. The sample matches live records exactly, assembled in a way only one internal reporting system produces. That system's logs show an unusual account running queries for months.

  • What does confirmation change about containment and who you notify internally?
  • How do you find out whether the access is still active right now?
  • What is the first customer-protection action, if any, before scope is known?

T+45m — A request to wait. Delivered to: incident commander + legal. The task force asks the institution to hold public disclosure for about two weeks to protect an operation against the seller, and wants an answer today. Separately, fraud reports a small uptick in account-takeover attempts.

  • How do you weigh an investigative hold against potential customer harm?
  • Who owns that decision, and how is the reasoning recorded?
  • What would change your answer as the fraud signal moves?

T+1h15 — The way in. Delivered to: security team. Forensics identifies the entry point — a vendor support access path that stayed within normal thresholds for months. It now appears closed, but the data is already gone, and the exposed records include details used to verify identity by phone.

  • What does a third-party access path mean for vendor risk and for other systems?
  • How do you protect against callers who can now pass standard identity checks?
  • How do you confirm the access is truly closed?

T+2h — Notification day. Delivered to: communications + contact center. The institution notifies customers. Within the hour the contact center is overwhelmed — call volume many times normal — and representatives are improvising answers the scripts do not cover.

  • How do you scale and script the contact center for a surge, fast?
  • What is the single, accurate message customers should hear everywhere?
  • How do you keep identity verification tight while volume spikes?

T+4h — Regulators and the record. Delivered to: legal / compliance + executive sponsor. A regulator asks for a briefing on the handling and timeline. A reporter asks, on the record, how long the institution knew before telling anyone.

  • What do you tell the regulator, and who owns that relationship?
  • How do you answer the "how long did you know" question honestly and consistently?
  • What internal record do you need so the timeline holds up later?

T+6h — The delay becomes the story. Delivered to: communications + executive sponsor. A leaked internal email suggests the institution confirmed exposure before it notified customers, and that framing is spreading faster than the facts.

  • How do you respond when the narrative is about the delay, not the breach?
  • What can you say about the investigative hold without blaming others?
  • Who speaks for the institution now?

Contingency — A second listing. Delivered to: incident commander. A second dataset appears from the same seller, time-stamped after the access was believed closed. It may be a reseller exploiting the headlines, or the intruder may never have left.

  • How do you reconcile "we closed it" with evidence of fresh data?
  • What do you tell customers and regulators while you re-investigate?

After-action checklist

  • Time from tip to confirmed/ruled-out breach, measured against target.
  • Containment decision point reached and documented, including "is access still active."
  • Notification-timing decision recorded with its reasoning and owner.
  • Contact-center surge handled: staffing, scripts, and identity-verification integrity.
  • Fraud signal tracked and tied to customer-protection actions taken.
  • Regulator and media engagement run through single, consistent owners.
  • Third-party/vendor access path reviewed as a root-cause and a recurring risk.
  • Internal timeline and decision record complete enough to withstand later scrutiny.

Frequently asked questions

How long does this bank tabletop exercise take?

About 90 minutes, from the first outside tip through containment, the notification-timing decision and the contact-center surge.

Does it work for credit unions and smaller institutions?

Yes. Replace the bracketed details with your own systems, vendors and team. A smaller institution may have one person covering several roles, and that's worth testing too.

Is this exercise aligned to FFIEC guidance?

It's aligned to FFIEC information-security and incident-response guidance and designed to support GLBA Safeguards expectations. It doesn't by itself satisfy any regulation.

What decisions does it test?

Confirming a breach from an outside tip, whether attacker access is still active, whether to hold public notice at law enforcement's request while fraud rises, and how to protect customers when stolen data can pass phone identity checks.

READINESS STARTS BEFORE THE CRISIS.

Put your team to the test.

Build your first scenario and turn preparation into measurable progress.

Explore pricing →Request a demo →