DataBreaches.Net

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

Some job applicants are first learning about the May, 2018 JobScience breach. Why?

Posted on March 15, 2019 by Dissent

In November, 2018, this site noted a breach disclosed by Huntsville Hospital involving JobScience, Inc., a vendor providing online job application services.  On November 10, we reported that other entities were also affected, such as Tallahassee Memorial Hospital,  who had been notified in September by JobScience, and NorthBay Healthcare Corp., who were notified in October.  Although not posted on this site, DataBreaches.net subsequently noted that El Centro Regional Medical Center had also been notified by JobScience.

DataBreaches.net reached out to JobScience and Bullhorn everal times but never received any replay at all.  Similarly, Huntsville Hospital Health did not reply to two requests for information on this breach.

And there things remained for a while. Until today, when I see that Advocate Sherman Hospital submitted notification to the California Attorney General’s Office about the same May, 2018 incident.

In their letter, Matt Pattelli, their VP – Human Resources, refers to JobScience as a “former service provdier,” and says that they “recently discovered an incident…..”

Recently?  Define “recently.”

What took so long for discovery and notification? Pattelli’s letter provides some clues, but not a really clear explanation:

After provision of additional information by Jobscience in December 2018 and further investigation, we were able to identify in February 2019 that your data was involved. Jobscience stated that law enforcement is aware of the incident, but this notification was not delayed as a result of a law enforcement investigation.

Given that personal information may have included  names, contact information, dates of birth, resumes and Social Security Numbers, you would hope that notification and protective services would be offered quickly.  If other hospitals notified applicants in November, 2018, why did it take so long in this one hospital’s case?  What information wasn’t provided to the hospital that it seemed to need?

Yes, JobScience arranged for services for those affected — even though there is no longer any relationship with the hospital, but what happened here?  And are there any other hospitals that are still first notifying job applicants because of this incident?

DataBreaches.net sent an inquiry earlier today to Advocate Sherman Hospital asking when they were first notifed by Jobscience and why the notification wasn’t sufficient to enable them to do notifications more promptly.  The inquiry also asked whether the hospital terminated their relationship with Jobscience as a result of the incident or if that was unrelated. DataBreaches.net has received no resply as yet, but will update this post if a response is received.


Related:

  • US company with access to biggest telecom firms uncovers breach by nation-state hackers
  • Canada says hacktivists breached water and energy facilities
  • 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)
  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
  • How a hacking gang held Italy’s political elites to ransom
Category: Commentaries and AnalysesHackOf NoteSubcontractorU.S.

Post navigation

← Bitcoin Ransomware Cripples Boston Legal System for Two Weeks
Database leaks 250K legal documents, some marked ‘not designated for publication’ →

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

  • 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
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

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

  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

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.