DataBreaches.Net

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

If you need to notify abuse survivors of a data breach, is it acceptable to take more than one year to notify them?

Posted on November 1, 2021 by Dissent

Urban Resource Institute in New York City provides shelter and services to victims of domestic abuse, homeless people, and individuals with developmental disabilities.

On May 20, 2020, they were the victim of an attack on employees’ email accounts. Unusual network activity was first noticed on July 23, 2020, but it wasn’t until October, 2020 that their consultants recognized that some email accounts had been accessed. And it wasn’t until June, 2021, that they learned what personal information was in those email accounts.

So it took 11 months from detection of unusual activity to figure out what email accounts had what personal information in them?  Why did it take  so long to figure all this out? How many hours per day and per week were consultants or employees working on this?  It is possible that I am just being unrealistic or unreasonable, but these are abuse victims whose information has possibly been accessed or acquired. The fact that URI and its experts didn’t find evidence of access or acquisition is not really proof that it didn’t happen. And if you can’t be sure what was accessed or acquired, it is possible that someone may have dumped these already on the dark web or might be selling the information, isn’t it? So was this an expedited investigation with “all hands on deck?” Some regulator should look into that.

And why did it take another four months to notify people?

External council from LewisBrisbois for URI writes:

Due to the nature of the services URI provides, traditional notification may present a serious safety risk to the notified population, which includes individuals to whom URI has provided or is providing domestic and family violence services. In particular, notified individuals who reside with a current or former abuser may be at risk should the abuser discover the notified individual sought domestic violence services from URI. In order to provide notice of the incident and access to credit and identity monitoring and protection services, while also mitigating the serious safety risk such notice may present, URI provided anonymized notification letters that do not therein identify URI as the organization that experienced the incident. Should notified individuals request information about the identity of the organization, such information will be disclosed upon confirmation of the safety of the inquiring notified individual. After careful consideration, URI believes this approach balances
the important interests of providing notice of the incident while also prioritizing the safety and security of notification population.

Their consideration of the risks and plan seems reasonable. It is not clear from their notification, however, what they are doing to prevent a recurrence other than their statement that they have put other (unspecified) safeguards in place.  Or why it took four months to send the notification letters to those who needed to be notified.

URI is notifying 16,003 employees and clients of the incident.

No related posts.

Category: Breach IncidentsHack

Post navigation

← Community Medical Centers notifying 656,047 patients of ransomware incident
Las Vegas Cancer Center hit by ransomware over Labor Day weekend; 3,000 patients notified →

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

  • Hunters International to provide free decryptors for all victims as they shut down (1)
  • SEC and SolarWinds Seek Settlement in Securities Fraud Case
  • Cyberattacks Disrupt Iran’s Bread Distribution, Payments Remain Frozen
  • Hacker with ‘political agenda’ stole data from Columbia, university says
  • Keymous+ Hacker Group Claims Responsibility for Over 700 Global DDoS Attacks
  • Data breach reveals Catwatchful ‘stalkerware’ is spying on thousands of phones
  • DOJ investigates ex-ransomware negotiator over extortion kickbacks
  • Hackers Using PDFs to Impersonate Microsoft, DocuSign, and More in Callback Phishing Campaigns
  • One in Five Law Firms Hit by Cyberattacks Over Past 12 Months
  • U.S. Sanctions Russian Bulletproof Hosting Provider for Supporting Cybercriminals Behind 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

  • Ninth Circuit Reviews Website Tracking Class Actions and the Reach of California’s Privacy Law
  • US healthcare offshoring: Navigating patient data privacy laws and regulations
  • Data breach reveals Catwatchful ‘stalkerware’ is spying on thousands of phones
  • Google Trackers: What You Can Actually Escape And What You Can’t
  • Oregon Amends Its Comprehensive Privacy Statute
  • Wisconsin Supreme Court’s Liberal Majority Strikes Down 176-Year-Old Abortion Ban
  • 20 States Sue HHS to Stop Medicaid Data Sharing with ICE

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.