Explains the legal obligations organizations face when a data breach occurs, including federal and state notification timelines, affected party communication standards, and regulatory reporting mandates across different jurisdictions.
posts
23andMe Proved That Getting Breached Is Bad — But Notifying Wrong Is Worse In late 2023, 23andMe disclosed a breach affecting nearly 7 million users. The breach itself was devastating. But the company's notification missteps — delayed disclosures, shifting blame to users, and inconsistent communications across jurisdictions — turned a security
In February 2024, Change Healthcare suffered a ransomware attack that exposed the protected health information of approximately 100 million Americans. The fallout wasn't just technical — it was regulatory. Congressional hearings, state attorney general investigations, and an avalanche of class-action lawsuits followed, largely because stakeholders questioned whether data breach
In May 2023, T-Mobile agreed to a $350 million settlement after a data breach exposed the personal information of roughly 76 million people. A significant chunk of that cost wasn't the breach itself — it was the fallout from notification failures, regulatory scrutiny, and class-action lawsuits that followed. If
In January 2022, Broward Health in Florida disclosed a breach affecting 1.35 million patients — and they didn't discover the intrusion until months after the threat actor first gained access. The clock on notification didn't start ticking until they actually found it. That gap between compromise
The SolarWinds Breach Just Made Notification a National Crisis In December 2020, FireEye disclosed that a sophisticated threat actor had compromised SolarWinds Orion software, giving attackers access to roughly 18,000 organizations — including the U.S. Treasury, the Department of Homeland Security, and Fortune 500 companies. Weeks later, we'
73 Hours: The Window That Cost Uber $148 Million In 2018, Uber paid $148 million to settle with all 50 states and the District of Columbia — not because they got breached, but because they covered it up. The company learned about a massive breach affecting 57 million users and drivers
