DataBreaches.Net

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

Why the NM Senate panel blocked the data breach bill

Posted on March 30, 2015 by Dissent

There’s an interesting piece in the Albuquerque Journal that explains why a New Mexico data breach notification bill failed again. It appears that most of the Democrats on the committee voted against it, but why they voted against it is of note. Thomas J. Cole reports:

“The comments appeared to be it was too industry-friendly for the attorneys on the committee,” Rep. William “Bill” Rehm, R-Albuquerque, sponsor of the bill, said in an interview last week.

At the hearing, Sen. Joseph Cervantes, a trial lawyer, said he was concerned about the strength of the notification requirements for companies in the legislation, as well as a cap of $150,000 on the amount of damages the state attorney general could collect from a company for notification violations.

Cervantes, D-Las Cruces, also noted that the measure didn’t explicitly permit individuals to seek damages caused by identity theft or fraud due to notification violations.

Read more on Albuquerque Journal.

So the Democrats killed it because the bill was too weak? The private cause of action will likely prove to be a sticking point in future proposals.

In the meantime, New Mexico remains one of only a few states that have no breach notification law.

 

No related posts.

Category: Breach LawsCommentaries and AnalysesState/Local

Post navigation

← ZW: Raid on newsroom justified: Nyambirai
Ontario’s sole health privacy prosecution quietly dismissed →

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

  • Air Force Employee Pleads Guilty to Conspiracy to Disclose Unlawfully Classified National Defense Information
  • UK police arrest four in connection with M&S, Co-op and Harrods cyberattacks (1)
  • At U.S. request, France jails Russian basketball player Daniil Kasatkin on suspicion of ransomware conspiracy
  • Avantic Medical Lab hacked; patient data leaked by Everest Group
  • Integrated Oncology Network victim of phishing attack; multiple locations affected (2)
  • HHS’ Office for Civil Rights Settles HIPAA Privacy and Security Rule Investigation with Deer Oaks Behavioral Health for $225k and a Corrective Action Plan
  • HB1127 Explained: North Dakota’s New InfoSec Requirements for Financial Corporations
  • Credit reports among personal data of 190,000 breached, put for sale on Dark Web; IT vendor fined
  • Five youths arrested on suspicion of phishing
  • Russia Jailed Hacker Who Worked for Ukrainian Intelligence to Launch Cyberattacks on Critical Infrastructure

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

  • How to Build on Washington’s “My Health, My Data” Act
  • Department of Justice Subpoenas Doctors and Clinics Involved in Performing Transgender Medical Procedures on Children
  • Google Settles Privacy Class Action Over Period Tracking App
  • ICE Is Searching a Massive Insurance and Medical Bill Database to Find Deportation Targets
  • Franklin, Tennessee Resident Sentenced to 30 Months in Federal Prison on Multiple Cyber Stalking Charges
  • On July 7, Gemini AI will access your WhatsApp and more. Learn how to disable it on Android.
  • German court awards Facebook user €5,000 for data protection violations

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.