DataBreaches.Net

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

Class Certification Denied for Data Breach Claim Brought by Bank Against Retailer

Posted on March 23, 2019 by Dissent

Balch & Bingham LLP write:

Last week, the U.S. District Court for the Middle District of Alabama denied Southern Independent Bank’s (“Southern Independent’s”) motion for class certification following a data breach which allegedly affected over 2,000 financial institutions across the country. Southern Independent, a community bank located in south Alabama, brought a class action complaint against Fred’s in response to a data breach in which hackers, using malware installed on servers, harvested payment data from consumer debit cards used at Fred’s stores.

As the district court’s opinion outlines, the data breach not only caused damage to the consumers, but also to the financial institutions that initially issued the debit cards to their customers.

And I was following along with this well-written post, and thinking, “Wow, the court is agreeing with Southern Independent on every point, so why was certification denied?”  And then I got to this paragraph, and my head hurt:

Despite the court’s conclusion that Southern satisfied the elements for class certification under Federal Rule of Civil Procedure 23(a), it could not ultimately support a grant of class certification. Southern Independent sought certification under Federal Rule of Civil Procedure 23(b)(3) which, in addition to the requirements outlined above, also mandates that adjudication as a class must be superior to other available methods and that common questions of law and fact predominate.  Alabama’s choice of law rules would necessitate adjudicating claims of negligence under the laws of each plaintiff’s jurisdiction.  The court concluded that doing so for over 2,000 financial institutions would require trying a negligence case under the laws of all fifty-one United States jurisdictions.  That immense logistical burden, coupled with factual disputes as to whether Southern Independent’s customers may have had their financial data compromised elsewhere and whether Southern Independent incurred unreasonable costs in response to the data breach, led the court to advance the case as an individual negligence action brought by Southern Independent against Fred’s.

Read more on JDSupra, and of course, the opinion itself. I thought it was great that the opinion contained a helpful visual:

From the opinion, an explanation of the graphic above:

“The vertical lines with arrows starting from Visa and MasterCard and moving
downward represent the series of contractual relationships that parallel the two sides of the payment card networks. The horizontal line at the bottom connecting
cardholders and merchants represents the connection between the two sides when
cardholders transact with merchants. Finally, the diagonal line represents the
relationship this lawsuit is about: the one between a merchant (Fred’s) and an
issuing bank (SIB). The Seventh Circuit explained that the theory of recovery
represented by the diagonal line would be a “new form of liability . . . in addition to
the remedies already provided by the contracts governing the card payment systems.” Cmty. Bank of Trenton, 887 F.3d at 808.”

Related posts:

  • Fred Hutch failed to reveal threats of potential swatting attacks until this site revealed the threat. Should they have disclosed it themselves?
  • Fred Hutch notifies more patients of November 2023 attack (1)
  • Kept in the Dark — Meet the Hired Guns Who Make Sure School Cyberattacks Stay Hidden
Category: Business SectorCommentaries and Analyses

Post navigation

← Privacy body probes ‘gaps’ in FOI website interface after data leak
UK: Hampshire’s Police Federation comes under cyber attack from hackers →

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

  • Swiss Health Foundation Radix Hit by Cyberattack Affecting Federal Data
  • Russian hackers get 7 and 5 years in prison for large-scale cyber attacks with ransomware, over 60 million euros in bitcoins seized
  • Bolton Walk-In Clinic patient data leak locked down (finally!)
  • 50 Customers of French Bank Hit by Insider SIM Swap Scam
  • Ontario health agency atHome ordered to inform 200,000 patients of March data breach
  • Fact-Checking Claims By Cybernews: The 16 Billion Record Data Breach That Wasn’t
  • Horizon Healthcare RCM discloses ransomware attack in December
  • Disgruntled IT Worker Jailed for Cyber Attack, Huddersfield
  • Hacker helped kill FBI sources, witnesses in El Chapo case, according to watchdog report
  • Texas Centers for Infectious Disease Associates Notifies Individuals of Data Breach in 2024

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

  • The Trump administration is building a national citizenship data system
  • Supreme Court Decision on Age Verification Tramples Free Speech and Undermines Privacy
  • New Jersey Issues Draft Privacy Regulations: The New
  • Hacker helped kill FBI sources, witnesses in El Chapo case, according to watchdog report
  • Germany Wants Apple, Google to Remove DeepSeek From Their App Stores
  • Supreme Court upholds Texas law requiring age verification on porn sites
  • Justices nix Medicaid ‘right’ to choose doctor, defunding Planned Parenthood in South Carolina

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[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.