It's late on a Thursday afternoon when Dana, an IT lead at a mid-sized insurance firm, spots it: a folder of customer records sitting on a server it never should have touched.
The technical next steps are clear. Everything else isn't.
Who does she tell first? Her manager is in a board meeting. Legal is "someone in another building." Customer service will start getting calls the minute word gets out, and nobody has told them what to say. Within an hour, three different people have written three different versions of what happened. Within a day, one of them reached a customer.
The systems got fixed quickly but trust took months to rebuild.
Knowing your breach response plan and following it under pressure are two different skills. A plan covers the process, but practice prepares people for the pressure.
Breaches are getting more common, and harder to spot
Breaches aren't rare events anymore. Verizon's 2026 Data Breach Investigations Report analyzed more than 22,000 confirmed breaches, nearly double the year before, the largest set in the report's history.
They're also getting harder to see coming. Attackers now use AI to move faster and to make phishing more convincing. More and more attacks also come in through trusted vendors and partners. No checklist can predict every version.
This, as a fact, changes what preparation entails. Technical defenses still matter, but when a breach looks new, the response depends on people: making sound judgment calls with incomplete information, and communicating clearly while the situation is still moving. Those are human skills, and they take real practice.
People are already at the center of the problem. The same Verizon report found that 62% of breaches involved the human element: one click, stolen credentials, a simple mistake. That's why most security training focuses on prevention. Spot the suspicious email or use a stronger password.
But people matter just as much once a breach has already happened. The response runs on judgment, coordination and hard conversations, often between colleagues who have never had to work together under pressure. Few teams ever practice that part.
What a breach response plan quietly asks of your people
The Federal Trade Commission's Data Breach Response: A Guide for Business appears as a standard technical checklist, but if you look closer, much of it is about people. It asks companies to:
- Pull together a response team that can span forensics, legal, IT, HR, communications and management.
- Build a communications plan that reaches everyone (employees, customers, investors and partners).
- Avoid misleading statements, without holding back details people need to protect themselves.
- Anticipate all the questions people will ask, and answer them in simplified language.
- Name one key person to share information.
But each of these pieces of advice requires human skill.
Knowing the plan isn't the same as following it under pressure
Most response teams know what they're supposed to do. The plan is written down. A few people have even read it.
Then the pressure hits. A leader wants answers in five minutes. Messages pile up. Nobody wants to be the person who made it worse. In that moment, the steps don't disappear. They just get much harder to reach.
That's the gap between knowing and doing, and it's mostly an emotional gap, not a knowledge gap. Dana knows customers need to be told. What she hasn't done is say it out loud to a worried customer, or tell her manager "we don't know yet" while he's pushing for a yes or no.
Why simulation prepares people for the pressure, not just the process
Crisis scenario exercises are a good start. They walk a team through the process: who calls whom, which system gets shut down, when legal steps in. But most of these excercises happen in environments that don’t layer on the realistic pressure.
Simulation adds the part a checklist can't: the emotional pressure. In a realistic simulation, the customer on the other end is angry. The executive wants certainty you don't have. The reporter asks the question you hoped to avoid. You have to find the words while it feels real.
That's what makes it stick. When the real moment comes, it isn't the first time you've said "here's what we know, and here's what we don't." It's the fifth. Good breach simulations rehearse moments like:
- Delivering bad news to a leader who wants a clear answer
- Calming an anxious customer without overpromising
- Disagreeing with a colleague about what to say next, quickly and respectfully
AI conversation simulations let people rehearse these moments on their own schedule, as many times as it takes, without waiting for the next company-wide drill.
How to build breach-response skills before you need them
- Drill the conversations, not just the systems: Next time your team runs a crisis scenario, include the human moments too: telling the CEO, briefing customer service, answering a reporter.
- Name the point person (and a backup) now: Decide who speaks for the company before anything happens, so nobody improvises once in the moment.
- Write the plain-language answers in advance: Draft short answers to the five questions customers will ask first: what happened, what was taken, what you're doing, what they should do, and where to get updates.
- Practice "here's what we know, and here's what we don't.": It's one of the hardest sentences to say under pressure. Rehearse it out loud, ideally in a simulation where someone pushes back, and with someone whose style is different from yours.
- Map your team's styles to response roles: Know who will want to act fast and who will want more facts. Then decide in advance who keeps the pace and who guards the details.
Practice before the pressure
A response plan helps your team discover what to do. Simulation is where they practice doing it, with the pressure turned on. And the transformation shows up on the worst afternoon of the year, when the gap between knowing and doing has already closed and the team stays calm, clear and honest. The systems will always need fixing. The trust is up to your people.




