DataBreaches.Net

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

JPMorgan Chase & Co. explains delay in notifying Connecticut about online security breach

Posted on December 7, 2013 by Dissent

JPMorgan Chase has attempted to explain the delay in notification to Connecticut, but at least one Connecticut official is not satisfied. Ed Jacovino reports:

JPMorgan Chase & Co. says it waited to determine what information could have been involved in an online security breach before telling officials this week that people with state-issued debit cards could have had their personal information stolen.

“When we detected the issue, our first priority was to protect our systems and the cardholders’ data and accounts,” JPMorgan Chase spokesman Mike Fusco said Friday.

Then the company assessed what information could have been hacked. “When we reviewed those results, we quickly took steps to communicate with everyone impacted,” Fusco said.

That review took at least two months.

[…]

The contracts between the state and JPMorgan Chase require much quicker notification of any data breaches.

The contract with the state Department of Revenue Services, for example, says the bank must “immediately notify” the state and people affected if information is compromised. It also allows the state to cancel the contract if information is leaked, and requires JPMorgan to follow certain security standards and share some of its security policies with the state.

Read more on Journal Inquirer.

No related posts.

Category: Commentaries and AnalysesFinancial SectorHack

Post navigation

← Tracking System Prepares New York to Evacuate Patients in Emergencies
Missouri man pleads guilty to his role in computer hacking, ID theft scheme enabled by consumers’ re-use of login credentials →

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

  • Five youths arrested on suspicion of phishing
  • Russia Jailed Hacker Who Worked for Ukrainian Intelligence to Launch Cyberattacks on Critical Infrastructure
  • Kentfield Hospital victim of cyberattack by World Leaks, patient data involved
  • India’s Max Financial says hacker accessed customer data from its insurance unit
  • Brazil’s central bank service provider hacked, $140M stolen
  • Iranian and Pro-Regime Cyberattacks Against Americans (2011-Present)
  • Nigerian National Pleads Guilty to International Fraud Scheme that Defrauded Elderly U.S. Victims
  • Nova Scotia Power Data Breach Exposed Information of 280,000 Customers
  • No need to hack when it’s leaking: Brandt Kettwick Defense edition
  • SK Telecom to be fined for late data breach report, ordered to waive cancellation fees, criminal investigation into them launched

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

  • On July 7, Gemini AI will access your WhatsApp and more. Learn how to disable it on Android.
  • German court awards Facebook user €5,000 for data protection violations
  • Record-Breaking $1.55M CCPA Settlement Against Health Information Website Publisher
  • Ninth Circuit Reviews Website Tracking Class Actions and the Reach of California’s Privacy Law
  • US healthcare offshoring: Navigating patient data privacy laws and regulations
  • Data breach reveals Catwatchful ‘stalkerware’ is spying on thousands of phones
  • Google Trackers: What You Can Actually Escape And What You Can’t

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.
Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report