After a Breach, Regulators Ask Three Questions. Most Companies Flunk the First.

Archi4 min read

privacyregulationsecuritycompliance

Contents
  1. The Clock Starts Before You Call a Lawyer
  2. Question One: Did You Know Sooner?
  3. Question Two: Was the Data Protected?
  4. Question Three: What Did You Do After?
  5. The Fines Are Smaller Than the Headlines Suggest
  6. What to Have Ready Before the Letter Arrives
  7. The Pattern to Expect

The Clock Starts Before You Call a Lawyer#

A breach notification lands on a regulator's desk. The company has already sent an email to customers, maybe posted a note on its website. The regulator opens a file. The first move is not a fine. It is a request for documents, usually within days. What happens next follows a pattern that repeat players know well, and first-timers learn the hard way.

Most data protection laws give regulators a narrow window to act. In the EU, the GDPR asks companies to notify within 72 hours of becoming aware of a breach. Regulators in the UK, California, and Australia have similar, if less rigid, timelines. The notification itself is rarely the end of the story. It is the start of an investigation that can run for months.

Question One: Did You Know Sooner?#

The first thing an investigator checks is the gap between when the breach happened and when the company reported it. A late notification is treated as a separate failure, and it is often easier to prove than the breach itself. Regulators have fined companies for waiting weeks while they investigated internally. The lesson: the 72-hour clock is not a suggestion.

Small companies often make this worse by trying to fix the problem before telling anyone. That instinct is understandable and legally risky. A breach that might have been contained in a day can become a multi-month investigation when the notification arrives late. The fine for late notification is usually smaller than the fine for the breach itself, but it adds up.

Question Two: Was the Data Protected?#

Investigators then look at what the company did before the breach. Did it encrypt customer records? Did it require multi-factor authentication for administrative accounts? Was sensitive data stored on a laptop that left the office? These questions are not hypothetical. They appear in enforcement notices again and again.

The standard is not perfection. Regulators weigh the size of the company, the sensitivity of the data, and the cost of the safeguards that were missing. A small clinic that stored patient records on an unencrypted server faces a different calculation than a bank that did the same. The fine scales with revenue in many jurisdictions, which means the same mistake costs a solo practitioner far less than a multinational.

Question Three: What Did You Do After?#

This is where companies can recover ground. Regulators look for evidence that the breach led to real changes: new access controls, mandatory training, a revised incident response plan. A company that treats the breach as a one-time event and returns to business as usual is more likely to face a larger penalty. A company that can show a timeline of fixes, with dates and owners, often sees the fine reduced.

The fix does not have to be expensive. One common finding is that a company had no inventory of where personal data lived. Building that inventory is tedious but cheap. Regulators notice when it exists after a breach and did not before.

The Fines Are Smaller Than the Headlines Suggest#

The largest GDPR fines make headlines, but the median penalty is modest. Most enforcement actions end with a fine in the tens of thousands of euros, plus a compliance order. The compliance order is often the more costly part: it requires the company to report progress to the regulator for a year or more, which means legal fees and staff time that dwarf the fine itself.

In the United States, sector regulators handle most breach cases. The FTC has settled with companies over misleading security claims. State attorneys general pursue cases under consumer protection laws. The SEC requires public companies to disclose material breaches within four business days, a rule that has already produced a few high-profile filings. These regulators rarely coordinate, which means a single breach can trigger parallel inquiries.

What to Have Ready Before the Letter Arrives#

A company that can produce three documents quickly is in a better position than one that cannot. The first is a data map: where personal information is stored, who can access it, and how long it is kept. The second is an incident log that records when the breach was detected, who was notified, and what was done. The third is a list of vendors who touch personal data, with contract terms that spell out breach notification duties.

None of this prevents a breach. It shortens the investigation. Regulators are not looking for a perfect security posture. They are looking for evidence that the company took the risk seriously before the breach and took the response seriously after. The companies that fare worst are the ones that treat the notification as paperwork and the investigation as an inconvenience.

The Pattern to Expect#

A typical investigation runs in three phases. First, a document request within two weeks. Second, interviews with security staff and executives, often within two months. Third, a findings letter and a proposed penalty, which can take six months to a year. Companies can negotiate during the second phase, and many do. The negotiation is not about whether the breach happened. It is about how much the company knew and how quickly it acted.

That is why the first question matters most. A company that detected the breach early and reported it on time starts the process with credibility. A company that sat on the news for a month starts on the defensive, and the rest of the investigation follows that tone. The fine is the last thing regulators decide. The first thing they decide is whether the company told the truth about the timeline.

More articles