DataBreaches.Net

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

Update on Cottage Health System breach

Posted on September 11, 2014 by Dissent

In December 2013, I reported on a breach involving Cottage Health System.

In their notification to patients, which I included in that post, Cottage Health indicated that about 32,500 patients had their information exposed when a vendor removed security controls on a server. That vendor was later identified as InSync.

On September 4 of this year, HHS added the incident to their public breach tool with this entry:

Cottage Health System, CA,”InSync Computer Solutions, Inc.”, 50918, 03/11/2012, Other, Network Server, 09/04/2014,

It is not clear to me why the HHS entry shows 50,918 for the number of patients affected. Did Cottage Health subsequently update their report of the number affected?

But the HHS log also reveals another detail not disclosed in Cottage Health’s statement in 2013:  the incident occurred on March 11, 2012. So patient information was exposed for nine months before Cottage Health became aware of the problem?

Of course, it’s reasonable to ask why InSync Computer Solutions never noticed their error, but Cottage Health is the entity that patients trusted with their information.

The incident does not appear as a closed investigation, so it will be interesting to see what HHS does in terms recommendations or requirements for the covered entity and its business associate.

UPDATE: In a 2015 report on a subsequent breach, NoozHawk clarified the discrepant numbers reported in this case:

In the 2013 incident, Cottage notified some 32,500 patients that their information may have been exposed by a data breach that occurred between Oct. 8 and Dec. 2 of that year.

Cottage subsequently notified another 18,000 patients about potential exposure during an expanded period — Feb. 20, 2009, to Dec. 2, 2013.


Related:

  • Maintenance Note
  • CISA Alert: Reported Supply Chain Compromise Affecting XZ Utils Data Compression Library, CVE-2024-3094
  • System Status Note
  • System Status Note
  • System Status Note
  • Fraudster's fake data breach claims should remind media to be careful what we report
Category: Uncategorized

Post navigation

← HHS breach tool: When "theft" doesn't mean what you think it means
Midwest Women's Healthcare Specialists breach may have affected over 1,300 patients →

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.