After a Breach, Regulators Ask Three Questions. Most Firms Answer Late.
Archi4 min read
Contents
- The Letter That Starts the Clock
- What Regulators Actually Do First
- 1. The timeline
- 2. The scope claim
- 3. The containment story
- The Failure Pattern
- How Penalties Get Sized
- What to Build Before the Letter Arrives
- A single incident record
- A data map that survives contact with reality
- A notice template with placeholders, not prose
- A legal and technical review that happens together
- The Part Companies Underestimate
The Letter That Starts the Clock#
When a breach becomes public, the first regulator contact rarely arrives as a subpoena. It usually comes as a short written request: describe the incident, name the systems affected, and explain when you knew. Companies that answer this letter well buy themselves room. Companies that answer it badly spend the next year defending inconsistencies.
A recent case is instructive. An organization discovered unauthorized access to a customer database, contained it within days, and disclosed on schedule. It still ended up in a lengthy enforcement process. The failure was not the breach itself. It was the paper trail around the breach: what the company said it had contained, when it said it, and what its own logs showed.
What Regulators Actually Do First#
Enforcement begins with reconstruction, not punishment. Investigators typically want three things, and they want them in a defensible form.
1. The timeline#
Regulators compare four clocks: when the intrusion began, when monitoring detected it, when the company decided it was a reportable incident, and when notice went out. Gaps between detection and decision draw the most scrutiny. A three-day gap is often fine if documented. A three-day gap with no records is a problem.
2. The scope claim#
The phrase "limited number of records" has ended more negotiations than any other. Investigators test scope claims against backup logs, access logs, and data mapping. If you say 40,000 records and the data map shows 400,000, the entire disclosure becomes suspect. Understating scope is treated more harshly than the original vulnerability in many jurisdictions.
3. The containment story#
Containment is a technical claim with a legal consequence. If you tell a regulator the attacker was evicted on a given date, expect a request for the evidence: credential resets, revoked tokens, closed ingress paths, forensic images. A containment claim without evidence reads as optimism, and optimism gets fined.
The Failure Pattern#
The recent case followed a familiar shape. The security team contained the intrusion quickly. Legal drafted a notice. Communications approved the language. Nobody reconciled the notice against the incident timeline held by the engineers.
Three specific mismatches emerged: , The notice described the exposure window as four days. Logs showed eleven., The notice said no credentials were compromised. A later review found service account keys in the exfiltrated data., The notice described notification as prompt. The internal decision memo was dated nine days before the letters went out.
None of these required malice. Each required a reviewer who was not in the room. Regulators rarely allege intent in cases like this. They allege that the company could not demonstrate reasonable process, and they price that failure per record, per day, or per violated provision depending on the regime.
How Penalties Get Sized#
Fines are not pulled from the air. Most regimes weigh a handful of factors, and companies can influence nearly all of them before a breach happens. , Volume and sensitivity of data. Health and financial records cost more than email addresses., Duration of exposure. Every day of undetected access adds weight., Detection capability. Did you have logging that could have caught this?, Cooperation. Did you answer requests completely and on time?, Remediation. Did you fix the root cause, or just the symptom?, Prior incidents. A second breach carries a premium.
The mitigation lever most companies ignore is cooperation quality. Complete, early, well-organized responses consistently correlate with lighter outcomes than minimal compliance. Investigators are people working through a queue. The company that hands them a clean binder moves faster through it.
What to Build Before the Letter Arrives#
A single incident record#
One document, one owner, timestamps for every decision. Detection time, escalation time, containment action, notice decision, notice sent. If three teams keep three versions, you have three liabilities.
A data map that survives contact with reality#
Know where personal data lives, including backups, analytics exports, and vendor copies. Scope disputes almost always trace to a stale map.
A notice template with placeholders, not prose#
The facts should be filled in from the incident record, not rewritten from scratch. Free-form drafting is where timelines drift.
A legal and technical review that happens together#
The reviewer who signs off on the notice should sit with the engineer who read the logs. This single practice prevents most of the mismatches described above.
The Part Companies Underestimate#
Regulators increasingly ask for evidence of the security program, not just the incident. They want to see risk assessments, patch cadence, access reviews, and vendor oversight. A company with a documented program and an honest breach report fares better than a company with a perfect story and no records.
The lesson from the recent failure is not that disclosure is dangerous. It is that inconsistency is. The breach cost the company a remediation budget. The mismatched timeline cost it the argument.
If a notice request arrived tomorrow, the useful question is simple: could three people in your organization produce the same timeline, the same scope figure, and the same containment date without calling each other first? If not, that is the work to do this quarter, before anyone asks.
More articles