DataBreaches.Net

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

Cheyenne Regional Medical Center notifying patients; employee email accounts had been hacked in March

Posted on December 11, 2019 by Dissent

Cheyenne Regional Medical Center in Wyoming has posted a data security incident notice on its website.

According to the notice, on or about April 5, 2019, CRMC became aware of suspicious activity related to certain employee payroll accounts and launched an investigation.

They ultimately determined that some CRMC employee accounts were accessed without authorization between March 27, 2019 and April 8, 2019. Unfortunately, the investigation was not able to determine which files, if any, were actually accessed or viewed during the affected time period.

CRMC believes that the goal of the attackers was to gain access to employee payroll information, but cannot rule out the possibility that patient information in the employees’ email accounts was (also) targeted.

It wasn’t until November 1, 2019 that their review of all the suspect email accounts was completed but they still did not have contact addresses for those who would need to be contacted.

Interestingly — and a bit untypically — CRMC explains why there was patient info in the employee email accounts:

CRMC’s policies and standard procedures dictate that patient information in our care be stored securely in our electronic health records system; however, based on necessary consultations and for administrative purposes, certain information is also exchanged among our staff and with other providers via email. All such email exchanges are made securely in accordance with CRMC procedures.

CRMC’s investigation confirmed the information present within the impacted email accounts at the time of the incident may include patient name, date of birth, Social Security number, driver’s license number, dates of service, provider name, medical record number, patient identification number, medical information, diagnosis, treatment information, health insurance information, and for a very small number of individuals, credit card information and/or financial account information.

You can read the entire notice here, and will also find FAQs on the breach on that url.

CRMC arranged with Kroll to provide services to those affected, but what I really noted was their detailed timeline of the steps in their incident response. You can find the details on their website notice, but it’s clear that they had to explain why it has taken 8 months since they first became aware of suspicious activity until now to make notifications.

And if you follow their chronology, then you may be left wondering whether HHS’s 60-day rule is unreasonable. Or if it’s reasonable, then explain what CRMC could have or should have done differently in their pre-incident planning and/or incident response that would have enabled them to make notifications within 60 days of discovery of the breach.

Category: Commentaries and AnalysesHackHealth DataU.S.

Post navigation

← Police Procedural: How South Carolina Arrest Records Were Exposed
Iran claims foiled massive state-sponsored cyber-attack →

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

  • Alabama Man Sentenced to 14 Months in Connection with Securities and Exchange Commission X Hack that Spiked Bitcoin Prices
  • Japan enacts new Active Cyberdefense Law allowing for offensive cyber operations
  • Breachforums Boss “Pompompurin” to Pay $700k in Healthcare Breach
  • HHS Office for Civil Rights Settles HIPAA Cybersecurity Investigation with Vision Upright MRI
  • Additional 12 Defendants Charged in RICO Conspiracy for over $263 Million Cryptocurrency Thefts, Money Laundering, Home Break-Ins
  • RIBridges firewall worked. But forensic report says hundreds of alarms went unnoticed by Deloitte.
  • Chinese Hackers Hit Drone Sector in Supply Chain Attacks
  • Coinbase says hackers bribed staff to steal customer data and are demanding $20 million ransom
  • $28 million in Texas’ cybersecurity funding for schools left unspent
  • Cybersecurity incident at Central Point School District 6

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

  • Privacy enforcement under Andrew Ferguson’s FTC
  • “We would be less confidential than Google” – Proton threatens to quit Switzerland over new surveillance law
  • CFPB Quietly Kills Rule to Shield Americans From Data Brokers
  • South Korea fines Temu for data protection violations
  • The BR Privacy & Security Download: May 2025
  • License Plate Reader Company Flock Is Building a Massive People Lookup Tool, Leak Shows
  • FTC dismisses privacy concerns in Google breakup

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.