DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

The Injuries Reilly Ignored: Consumer Data Breaches and Injury-in-Fact

Posted on April 19, 2016 by Dissent

Law student Shannon Grammel writes:

The U.S. Supreme Court denied review in 2012 to thousands of individuals whose data was breached who were alleging increased harm of identity theft and seeking to reverse the U.S. Court of Appeals for the Third Circuit’s decision to deny them standing in Reilly v. Ceridian Corp.1 In so doing, the Supreme Court declined a valuable opportunity to address the Third Circuit’s flawed renunciation of the parallels between data breach, medical monitoring and toxic tort cases.2 Such renunciation erred in conspicuously excluding from its calculus two critical injuries present in all three types of cases: heightened “at risk” status and fear of future harm. These injuries, this article argues, ought to have sufficed for Article III standing in Reilly.

This article proceeds in four parts. It first summarizes the injury-in-fact standing requirement. Next, it introduces the circuits’ divergent approaches to analogizing data breach, medical monitoring, and toxic tort cases. An illustration of the critical oversight the Third Circuit made in mistakenly rejecting these analogies follows. It concludes by urging that the present injuries of “at risk” status and fear of future harm be given their due consideration in the standing calculus.

Read more on Bloomberg BNA.


Related:

  • The 4TB time bomb: when EY's cloud went public (and what it taught us)
  • Some lower-tier ransomware gangs have formed a new RaaS alliance -- or have they? (1)
  • Uncovering Qilin attack methods exposed through multiple cases
  • Predatory Sparrow Strikes: Coordinated Cyberattacks Seek to Cripple Iran's Critical Infrastructure
  • Ex-CISA head thinks AI might fix code so fast we won't need security teams
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
Category: Commentaries and Analyses

Post navigation

← SS7 hack explained: what can you do about it?
Denver Archdiocese payroll system breached, 18,000 at risk →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Checkout.com Discloses Data Breach After Extortion Attempt
  • Washington Post hack exposes personal data of John Bolton, almost 10,000 others
  • Draft UK Cyber Security and Resilience Bill Enters UK Parliament
  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • OpenAI fights order to turn over millions of ChatGPT conversations
  • Maryland Privacy Crackdown Raises Bar for Disclosure Compliance
  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.