Regulators Will Treat Breach Notices Like Earnings Warnings: Expect Mandatory 72-Hour Disclosures
Archi4 min read
Contents
The Next Regulation Isn't About Security. It's About Speed.#
When a company discovers a breach, the first call is usually to its legal team. The second is to its insurer. The third, increasingly, is to a public relations firm. What's missing from that sequence is a call to the public. Regulators are about to change that.
My prediction: within 18 months, a major jurisdiction will mandate public disclosure of material breaches within 72 hours of discovery, with a standardized filing that looks more like an earnings warning than a legal notice. The companies that treat this as a compliance checkbox will fail. The ones that build real-time disclosure into their incident response will set the standard.
Why 72 Hours Is the Wrong Number to Argue About#
The debate over breach notification timelines misses the point. Whether it's 72 hours, 30 days, or 90 days, the real change is that regulators want a public artifact, not a private letter to affected customers. The EU's GDPR already requires notification to a supervisory authority within 72 hours, but most of those notices never see daylight. That's about to change.
Consider the trajectory. The SEC's 2023 rule requiring material incident disclosure on Form 8-K within four business days was a first step. It applied only to public companies and only to incidents deemed material. Expect the next wave to broaden the scope and shorten the clock. State attorneys general in the US are already coordinating on model breach notification language. The UK's ICO has signaled it will publish more enforcement details after incidents. The direction is clear: regulators want a public record.
The reason is simple. Regulators are tired of learning about breaches from journalists. They want to control the narrative, or at least get ahead of it. A mandatory public filing gives them a timestamp and a baseline. It also gives them a paper trail for enforcement.
What a Real-Time Filing Would Look Like#
If I were drafting the rule, it would require three things within 72 hours of discovery:
- A one-page public notice that states what happened, what data was involved, and what the company is doing about it.
- A named executive signature, not a generic legal boilerplate.
- A commitment to update the notice every 30 days until the incident is closed.
That last point is the one companies will hate. It turns a single disclosure into an ongoing obligation. But it's also the one that will build trust. The companies that update regularly will be seen as competent. The ones that go silent will be seen as hiding something.
The Objection: "We Don't Know Enough in 72 Hours"#
That's true. In most breaches, the full scope isn't known in 72 hours. But regulators don't expect perfection. They expect a good-faith effort to describe what is known and what is not. The alternative, waiting for a complete picture, is what leads to the 6-month delays that erode public trust.
The companies that will struggle most are those without a pre-built disclosure template. They will spend the first 48 hours arguing about wording instead of gathering facts. That's a failure of preparation, not of regulation.
The Penalty Structure Will Be the Real Lever#
Fines for late notification are already on the books in many jurisdictions, but they are rarely enforced at scale. Expect that to change. A tiered penalty structure, with higher fines for late filings and even higher for inaccurate ones, would create a real incentive to comply.
More importantly, regulators will start naming names. A public list of companies that failed to file on time is often more effective than a fine. Reputation matters more than compliance budgets.
What Companies Should Do Now#
Stop treating breach response as a legal process. Start treating it as a communications process with legal guardrails. That means: , Draft a public notice template now, with placeholders for facts you won't have until an incident occurs., Assign a named spokesperson who can speak on the record within hours., Build a 72-hour clock into your incident response plan and rehearse it., Decide in advance what you will say when you don't know the full scope.
The companies that do this will turn a regulatory burden into a competitive advantage. The ones that don't will be the cautionary tales in the next round of enforcement actions.
The Regulators' Endgame#
The endgame isn't perfect security. It's a steady stream of public information that lets markets and customers make decisions. That's a shift from the current model, where breaches are disclosed months later in a PDF buried on a corporate website. It's a shift that will feel uncomfortable for many companies. But it's coming. The only question is whether you'll be ready.
More articles