DataBreaches.Net

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

Is delaying notification for law enforcement purposes ever unreasonable?

Posted on April 5, 2014 by Dissent

Over on Security Bistro, Linda Musthaler discusses the recently disclosed Spec’s breach and the fact that Spec’s knew about the breach but was asked not to disclose it by law enforcement.

We’ve seen this many times – delays in notification so as not to interfere with a law enforcement investigation. But should there be some limits on how long notification can be delayed or should it be open-ended at law enforcement’s request, keeping in mind that law enforcement can only request, it seems, but not order the entity not to disclose?

In terms of a balancing act, if the data involved are “just” credit or debit cards, it’s relatively easy to restore individual’s accounts and issue new account numbers, and it should be relatively easy (although often isn’t) to get credit reports corrected and restored. So even though it’s inconvenient for customers who may be without their cards for a while and who may have to re-do any accounts on automatic payment and spend time correcting credit reports, consumers can be restored and compensated.

But what about if the data being stolen or compromised include SSN or medical information? Should the criminal activity be allowed to run for another year or so while law enforcement investigates and people’s sensitive information or SSN may wind up in the hands of others?  If people become identity theft victims or medical identity theft victims (and not just card fraud or new account fraud victims), it’s a lot harder to fix things. We’ve seen cases where people are arrested erroneously as a result of ID theft. We know that medical identity theft can lead to treatment errors and potentially serious medical care and/or insurance problems. What about those risks? Does law enforcement’s understandable needs outweigh what happens as more people become victims because no one notified them in a timely fashion?

Do we need to draw a line on nondisclosure for law enforcement purposes or not?

You can read Musthaler’s commentary on SecurityBistro.


Related:

  • Some lower-tier ransomware gangs have formed a new RaaS alliance -- or have they? (1)
  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
  • How a hacking gang held Italy’s political elites to ransom
  • Uncovering Qilin attack methods exposed through multiple cases
  • Predatory Sparrow Strikes: Coordinated Cyberattacks Seek to Cripple Iran's Critical Infrastructure
  • Ex-CISA head thinks AI might fix code so fast we won't need security teams
Category: Business SectorCommentaries and AnalysesHackID TheftMalwareU.S.

Post navigation

← FL: Call center employee and 7 others charged in ID theft fraud scheme involving AT&T customer info
IL: New teacher licensing system full of glitches, hitches →

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.