DataBreaches.Net

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

If you needed yet one more example of the risks of PHI in employee email accounts

Posted on June 24, 2020 by Dissent

I’m not sure what it might take to get a real shift in how entities approach security of employee email accounts.  Despite known risks of phishing and hacks, a tremendous amount of personally identifiable information (PII) and protected health information (PHI) resides in emails or email attachments in employee accounts.

Read the following chronology provided by Choice Health Management Services in North Carolina. They are a business associate that provides IT, payroll, billing, and compliance functions for numerous independent living, assisted living, and skilled nursing facilities. In “late 2019,” they reportedly discovered suspicious activity in certain employee email accounts. From discovery to notification should take no longer than 60 days under HIPAA and HITECH, right?  But it doesn’t always go so quickly:

With the assistance of third-party forensic investigators, Choice Health Management Services launched an investigation into the nature and scope of this incident. On January 17, 2020, Choice Health Management Services confirmed that certain employee email accounts were subject to unauthorized access, but was unable to determine what, if any, individual emails or attachments within the accounts were subject to unauthorized access. With the assistance of a third-party firm, Choice Health Management Services then began a comprehensive and time-intensive review process of the email accounts subject to unauthorized access to determine what, if any, sensitive information they contained. On March 27, 2020, the review concluded, and Choice Health Management Services learned that personal health information was contained in certain email accounts. However, since the vendor was unable to link a large number of the individuals to the facility where the individuals sought treatment, Choice Health Management Services began a review of its internal records to determine this information so notice could be provided to the appropriate facility. On May 12, 2020, Choice Health Management Services completed its internal review and determined which individuals received care from a facility associated with Choice Health Management Services.  On April 16, 2020 and again on May 22, 2020, Choice Health Management Services notified facilities about the event and requested permission to provide patients and residents with notice, which was subsequently granted.

On June 23, Choice Health Management Services began mailing notices to an unspecified number of individuals. They did not offer them any complimentary monitoring or restoration services, claiming that they had no evidence of any actual misuse of the data and were providing the notice “in an abundance of caution.”

So what did this incident cost them, all told?  They said they have implemented additional safeguards to prevent a future incident, although they are (understandably) not specific about the nature of the additional safeguards. Did they implement 2FA? Do they require password resets every few months with no re-use of passwords permitted? Are they reducing the storage of emails in employee accounts to move it to more secure storage more quickly?

It took them more than 6 months to make notifications on this one incident.  Could they go through this all again tomorrow? What prevents that? And will HHS ever do anything about all the entities that take more than 60 days from when they first detect a problem to actually notifying patients? Or should we all just redefine or clarify the point from which the 60-day clock starts ticking?

Category: Health DataU.S.

Post navigation

← Evil Corp deploys new WastedLocker ransomware
Data stolen from Silicon Valley consulting firm offered for sale on hacker forum →

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

  • Rewards for Justice offers $10M reward for info on RedLine developer or RedLine’s use by foreign governments
  • New evidence links long-running hacking group to Indian government
  • Zaporizhzhia Cyber ​​Police Exposes Hacker Who Caused Millions in Losses to Victims by Mining Cryptocurrency
  • Germany fines Vodafone $51 million for privacy, security breaches
  • Google: Hackers target Salesforce accounts in data extortion attacks
  • The US Grid Attack Looming on the Horizon
  • US govt login portal could be one cyberattack away from collapse, say auditors
  • Two Men Sentenced to Prison for Aggravated Identity Theft and Computer Hacking Crimes
  • 100,000 UK taxpayer accounts hit in £47m phishing attack on HMRC
  • CISA Alert: Updated Guidance on Play Ransomware

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

  • How the FBI Sought a Warrant to Search Instagram of Columbia Student Protesters
  • Germany fines Vodafone $51 million for privacy, security breaches
  • Malaysia enacts data sharing rules for public sector
  • U.S. Enacts Take It Down Act
  • 23andMe Bankruptcy Judge Ponders Trump Bill’s Injunction Impact
  • Hell No: The ODNI Wants to Make it Easier for the Government to Buy Your Data Without Warrant
  • US State Dept. says silence or anonymity on social media is suspicious

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.