It’s 8:15 a.m. and a Vendor Says They’ve Been Breached. What Do You Do First?

A vendor reports a breach. What happens next? Run a 25-minute tabletop to practice verifying alerts, assigning response roles, assessing exposure, and making decisions under uncertainty.

A breach notification from a vendor creates an immediate problem: you need to make decisions before you have complete information. The vendor may still be investigating. Your operations team needs the service. Customers may expect answers you cannot yet provide.

Your first move is to activate your response process while independently verifying the notification. Assign an incident lead, preserve the message, and begin assessing your exposure. Do not wait for the vendor’s final report to organize your own response.

The FTC’s data breach response guidance recommends promptly mobilizing a multidisciplinary team, preserving evidence, and examining a breached service provider’s access privileges. Those responsibilities belong to your organization even when the intrusion happened somewhere else.

The following tabletop turns that principle into a practical test. It is not a technical investigation or a test of who knows the most terminology. It is a rehearsal for making defensible decisions under uncertainty.

Set Up a 25-Minute Tabletop

Invite security or IT, the vendor’s business owner, legal or privacy, operations, and communications. Assign a facilitator and a note-taker. In a smaller organization, participants can cover multiple roles, but decision-making authority must remain explicit.

NIST’s incident-response guidance includes relevant suppliers in planning, response, and recovery activities. This exercise tests whether those relationships work when an incident moves beyond a procurement questionnaire.

Preparation Checklist

  • Have the incident-response plan and escalation contacts available.
  • Locate the vendor contract, including security and notification provisions.
  • Bring a summary of the customer data the vendor holds and the systems it can access.
  • Identify where relevant access and integration logs are stored.
  • Prepare a decision log using: Decision | Owner | Rationale | Unknowns | Next review time.

Exercise rules: Discuss actions only. Do not change production systems, disable real accounts, or contact actual customers. Reveal each development only at its scheduled exercise minute. The scenario clock advances faster than the meeting clock; the timestamps represent simulated events.

Opening Scenario: 8:15 a.m. — Exercise Minute 0

HYPOTHETICAL BREACH NOTIFICATION — EXERCISE ONLY

Your customer-support software vendor emails your account owner:

“We detected unauthorized access to our support environment. Your organization may be affected. We are investigating whether customer records were accessed. Our service remains available. We will provide another update within two hours.”

This notification and every subsequent development are fictional exercise material, not reports of an actual incident.

For this scenario, the vendor holds customer names, email addresses, and support-ticket contents. An integration credential also allows it to read selected records from your customer database.

Give the team five minutes to answer:

  • Who leads? Name the incident lead, the person setting initial severity, and the person authorized to interrupt the service.
  • How will you verify the message? Use a previously established vendor contact or an independently accessed support channel, rather than relying on links or phone numbers in the email.
  • What is known? Distinguish what the vendor reports from what your organization has independently established. Your exposure remains unconfirmed.
  • What do you need? Request affected systems, the incident window and time zone, tenant-specific findings, data categories, potentially exposed credentials, containment status, and a named response contact.
  • What will you preserve? Assign responsibility for the original message, relevant logs, and the timestamped decision record.

Required output: A named incident lead, an initial exposure hypothesis, and a next-update time.

A useful exposure hypothesis is specific without claiming certainty: support-ticket data may be affected, and the integration credential creates a possible path into selected customer records. That gives investigators a direction without turning suspicion into fact.

Timed Development 1: 8:25 a.m. — Exercise Minute 5

HYPOTHETICAL DEVELOPMENT — EXERCISE ONLY

The vendor confirms that integration credentials may have been exposed. Your team finds an unusual bulk read using the vendor integration credential shortly before the notification. Operations says disabling the integration will delay customer support.

Give the team seven minutes to decide:

  • Will you suspend the integration, revoke its credential, restrict permissions, or take another containment action? Who approves and executes the choice?
  • What does the unusual read establish, and what evidence would help determine whether it was unauthorized?
  • Which logs and records must be retained while containment proceeds?
  • What manual workaround will operations use, and who owns it?
  • What evidence and approval will be required before reconnecting?

Facilitator checkpoint: Require an explicit containment decision. “IT will investigate” is an activity, not a decision about continued access.

The bulk read establishes that the credential was used in an unusual way. It does not, by itself, establish who used it or whether the activity was malicious. Investigators should examine timing, source information, records accessed, and whether the activity matches an authorized business process.

That uncertainty does not require leaving access unchanged. The team should weigh plausible exposure against operational disruption and choose a proportionate action. For example, suspending the integration while support staff use an approved manual workflow may be preferable to allowing continued access.

Preserve evidence alongside containment; do not let evidence collection become an open-ended reason to leave risky access active. The FTC guidance emphasizes reviewing service-provider access, protecting forensic evidence, and verifying fixes rather than simply accepting reassurance.

Required output: A containment decision, an accountable approver, a continuity owner, and explicit reconnection criteria. Restoring service availability alone is not evidence that access is safe.

Timed Development 2: 8:45 a.m. — Exercise Minute 12

HYPOTHETICAL DEVELOPMENT — EXERCISE ONLY

The vendor confirms an unauthorized export containing some of your support tickets, but cannot yet identify every affected customer. A customer asks whether their information was stolen. The vendor suggests waiting for its final report before communicating.

Give the team six minutes to decide:

  • What can you truthfully tell the customer now? Draft two sentences separating confirmed facts from unresolved scope.
  • Who approves external statements and coordinates customer-service responses?
  • Who assesses applicable legal, regulatory, contractual, and insurance-notification requirements?
  • What additional facts does that assessment require, and when will it be revisited?
  • What will you do if the vendor misses its promised update?

Facilitator checkpoint: The vendor’s reporting schedule does not determine your obligations. Do not assume a universal notification deadline, and do not assume every communication must wait for a complete investigation.

For the customer-response exercise, the first sentence should acknowledge the confirmed unauthorized export of some support tickets. The second should explain that the organization is still determining whose information was included and when the customer can expect another update. Do not claim that this customer was affected—or unaffected—without supporting evidence.

Legal and privacy teams should assess relevant jurisdictions, information types, affected individuals, contractual commitments, and other applicable requirements. Communications should coordinate with that assessment, not substitute for it.

Required output: An approved interim response, an owner for the notification assessment, a review time, and a vendor-escalation path. Record unresolved questions rather than filling gaps with reassurance.

Debrief: Use the Final Seven Minutes to Find the Gaps

Discuss decisions, not individual blame. A tabletop is valuable when it exposes friction before an actual incident does.

  • Authority: Could everyone identify the person empowered to suspend vendor access? Was a backup available?
  • Evidence: Did the team separate confirmed facts, suspicions, and missing information throughout the exercise?
  • Containment and continuity: Did the decision address both potential exposure and the operational consequences of interruption?
  • Vendor dependence: Could you investigate using your own records? Were escalation contacts and evidence-sharing expectations usable?
  • Communication: Did anyone promise “no impact” without evidence? Could customer-facing staff explain uncertainty accurately?
  • Recovery: Were reconnection criteria concrete, documented, and assigned to an approver?

Close with three corrective actions, each with an owner, deadline, and validation method. Examples include locating and safely testing the integration shutoff procedure, confirming access to relevant logs, or updating the vendor escalation contact.

Follow the approach in CISA’s exercise guidance: document strengths and improvement areas in an after-action report, then assign corrective actions and implementation timelines. A finding is not resolved merely because it appears in meeting notes.

Your First Response Should Not Depend on the Vendor’s Final Answer

You cannot control how quickly a breached vendor understands its incident. You can control who leads your response, how you verify information, what access you permit, and how honestly you communicate.

Schedule this exercise with the team responsible for a critical vendor. Finish with named owners and testable improvements. The objective is not perfect certainty at 8:15 a.m. It is a disciplined first decision—and a clear process for making the next one.

Browse all insights · Contact Bart McDonough