Measure 04 · Capacity
The first three measures show the pressure rising. This one asks the other half of the question: when a major failure hits, how fast and how far does the response reach — and does it touch the thing that made the failure systemic?
The pattern across six cases
Every response comes after the failure, never before it. Firms rebuild their own defenses — but only their own. And the size of the regulatory response has no relationship to how far the failure spread. What predicts a new rule isn't damage. It's whether personal data leaked inside a sector a regulator already polices.
Six of the twelve cascade incidents are examined as matched pairs — each linking one serious failure to the regulatory or enforcement action that followed. For each: did the firm respond, did a binding rule follow, and how long did it take? Read them in order and the pattern surfaces on its own.
A battery-room fire caused a nationwide outage over eleven hours. The narrowest cross-sector reach of the six — and the only one that produced genuinely new law.
USIM and identity data for 23M+ subscribers exposed. A record fine under existing data-protection law — no new statute. Now under legal challenge.
A poisoned update reached ~18,000 organizations. The SEC's disclosure rule followed, though it grew out of guidance already in motion — and the enforcement case was largely thrown out in 2025.
The largest US health-sector breach. HHS proposed a HIPAA overhaul and named the breach directly — but the rule is still only a proposal, its deadline already passed.
A zero-day hit 2,500+ organizations across all eight sectors — the widest cascade in the study. No new rule. Nearly three years later, a regulator fined a victim over notification timing and data retention — never touching the shared dependency itself.
A faulty update crashed ~8.5M systems across seven of eight sectors — called the largest IT outage in history. The firm rebuilt its release process. The regulatory response: an alert, a hearing, and a note urging resilience. No binding rule.
Line up the widest cascades against the narrowest. MOVEit and CrowdStrike caused the broadest damage in the entire study — and neither produced a single new binding rule. Kakao, the narrowest in cross-sector terms, produced the only new law. If regulation tracked systemic disruption, this would be upside down.
It isn't tracking disruption. It's tracking data exposure inside a sector a regulator already oversees. SK Telecom exposed subscriber IDs, and a data-protection law was there to use. Change Healthcare exposed health records, and HIPAA was there. CrowdStrike exposed no data and named no attacker — so no tool was reached for at all, even for the largest outage on record.
This is the efficiency–fragility tradeoff showing up in the institutional record instead of in theory. Firms can fix their own flaws, but a firm can't fix its own centrality. Concentration isn't a defect any single company can be cited for — so a regulatory system built to police data breaches simply can't see it. The pressure grows along one axis. The defense is arrayed along another. And that, not slowness, is the gap.