DataBreaches.Net

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

A business associate’s response to a breach raises questions of timeliness

Posted on April 11, 2020 by Dissent

I know we’re in the middle of a pandemic, but an incident involving Avalon Health Care Management occurred before all that.  And once again, I find myself scratching my head over the timeline in a notification and how Health & Human Services/Office for Civil Rights will view the timeline in terms of compliance with the 60-day window to notify of a breach.

As described by their external counsel in a letter dated March 16 to the Washington state attorney general’s office:

On July 9, 2019, Avalon became aware of suspicious activity within its email system. Upon making this discovery, Avalon immediately took steps to secure its email system and investigate the activity. As part of the investigation, Avalon engaged an independent digital forensics expert to determine what happened and whether any personal information had been accessed without authorization. On August 5, 2019, Avalon learned that the email account of one of its employees may have been accessed without authorization. Upon completion of the forensic investigation, Avalon engaged a  document review vendor to search the contents of the impacted email account to identify the individuals whose personal information may have been contained within the account. On December 16, 2019, Avalon learned that the personal information of some of its patients and employees was contained within the account. Avalon then conducted a thorough review of the information that may have been affected and completed a detailed investigation to identify those individuals whose information was potentially impacted and determine their place of residence. Based upon this analysis, on January 27, 2020, Avalon determined that the names and Social Security numbers of 1,723 Washington residents, and the names and limited medical information of an additional 138 Washington residents were contained within the impacted email account and may have been exposed as a result of this incident.

You can read the full notification here.

Remember that the above numbers were specific to Washington State. Avalon reported this incident to HHS on February 14 as impacting 14,500 patients.

But look at how Avalon Health Care described the timeline on their web site in their March 16 notice:

On December 16, 2019, Avalon learned that the personal information of some of its patients and employees contained in an employee email account was potentially exposed to an unauthorized user.  This discovery was made during the course of an independent digital forensic investigation.  By January 27, 2020, Avalon completed a thorough review of the information that may have been affected and completed its investigation to identity those individuals whose information was potentially impacted.  Avalon is unaware of any evidence indicating that anyone’s information has been misused as a result of this incident.

If that’s all you knew, it would sound like Avalon first discovered a problem on December 16, identified those who needed to be notified by January 27, and notified them all by March 16. That’s more than 60 days (unless you figure completing an investigation is your date of discovery), but it’s nowhere near as concerning as their more detailed report that admits that they first detected unusual activity in an email account back in July 2019.

So how would YOU calculate the gap from discovery to notification?  And what will HHS/OCR do? Anything?

Category: Commentaries and AnalysesHackHealth DataOf NoteU.S.

Post navigation

← San Francisco Intl Airport discloses data breach after hack
Less than two weeks after an Indiana hospital reported a phishing-related HIPAA breach, they had a second one →

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

  • Industry Letter – June 23, 2025: Impact to Financial Sector of Ongoing Global Conflicts
  • MNGI Digestive Health settles class action lawsuit stemming from BlackCat attack
  • Four REvil ransomware members released after time served on carding charges
  • Why Dumping Sensitive Data on Network Shares is a Liability
  • A militarily degraded Iran may turn to asymmetrical warfare – raising risk of proxy and cyber attacks
  • Pro-Russian hackers disrupt Dutch government websites ahead of NATO summit
  • Iran-Linked Threat Actors Leak Visitors and Athletes’ Data from Saudi Games
  • UK: Oxford City Council still investigating cyberattack from earlier this month
  • Steelmaker Nucor Says Hackers Stole Data in Recent Attack
  • People’s Republic of China cyber threat activity: Cyber Threat Bulletin

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

  • Sky Views Personal Data as a Potential Weapon in IPTV Piracy War
  • Florida Used a Nationwide Surveillance Camera Network 250 Times To Aid in Immigration Arrests
  • Federal Court Strikes Down HIPAA Reproductive Health Care Privacy Rule
  • The Markup caught 4 more states sharing personal health data with Big Tech
  • Privacy in the Big Sky State: Montana’s Consumer Privacy Law Gets Amended
  • UK Passes Data Use and Access Regulation Bill
  • Officials defend Liberal bill that would force hospitals, banks, hotels to hand over data

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