DataBreaches.Net

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

President’s cybersecurity agenda includes proposed federal data breach notification law

Posted on May 12, 2011 by Dissent

To cut to the chase: you can read the language of the proposed data breach notification law here.

Sadly, the proposed language allows entities NOT to notify affected individuals if they conduct a risk assessment and determine that there is no risk to those whose data were breached.

Other problems I see on a first reading are:

1. The law would only apply to entities dealing with 10,000 or more individuals in a 12-month period. That would still leave us without a national data breach law for smaller entities. Don’t their breaches put us at risk?

2. There does not seem to be a provision that would permit the FTC to reject an entity’s risk assessment exemption and to tell them that no, they must notify individuals.

3. The proposal does not require the entity to provide important details about the breach to affected individuals such as when the breach occurred and when it was first detected, or even how the breach occurred – was it a hack, or web exposure, or…?

4. The proposal would supersede much stronger state breach notification laws.

5. The proposal does not establish or recognize a private cause of action.

6. The proposal would still leave us without any national data breach notification law that would apply to paper records outside of HIPAA-covered entities.

7. The proposal does not require the breached entity to post a prominent notice linked from the home page of any web site they maintain.

I’m sure I’ll have other concerns when I read this again tomorrow, but right now, there’s just so much wrong with this weak bill that I wish someone would just go smack the WH on its head and tell them to read this blog or other privacy advocacy sites that have been pointing out certain problems and needs forever.

Update: The government has posted a section-by-section analysis of the data breach notification provisions.


Related:

  • 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
  • UN Cybercrime Convention to be signed in Hanoi to tackle global offences
Category: Commentaries and AnalysesFederalLegislationOf Note

Post navigation

← OH: Laptop with financial information stolen from the home of state Auditor’s Office employee
Eidos and Deus Ex sites hacked, personal data acquired? →

2 thoughts on “President’s cybersecurity agenda includes proposed federal data breach notification law”

  1. Sam says:
    May 13, 2011 at 3:34 pm

    IN RE #4 above: It was my understanding that state laws were to be adhered to BEFORE considering federal laws addressing the same issues (being that they were always/usually more stringent than federal laws).

    1. admin says:
      May 13, 2011 at 3:53 pm

      I wish you were correct, but Section 109 is quite clear that the proposed law will supersede any state law on notification of a breach involving computerized data for entities dealing with over 10k people in a 12-mo. period with one exception – the states can require the entity to include information on victim protection assistance if it is offered by the state.

      What may not be as clear is what happens in cases of breaches that involve entities dealing with fewer than 10k people per year, etc. In that case, state law may still apply, but that’s a guess on my part as I’m not sure how to interpret the proposal.

Comments are closed.

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

  • 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
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

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

  • 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
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

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.