DataBreaches.Net

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

Vermont Updates Data Breach Notification Law

Posted on June 1, 2012 by Dissent

Cynthia Larose and Amy Malone describe recent changes to Vermont’s law that strengthens some consumer protections:

Effective as of May 8, 2012, Vermont’s updated data breach law (Act 109) brings along several changes.  The biggest change is in the notification requirements.  Notification to consumers must now occur no later than 45 days after discovery of the incident and must include the approximate date of the security breach (if known).  To further complicate matters, notification to the Vermont Attorney General must occur within 14 business days of either the discovery of the breach or notice to the consumers, whichever is sooner and must include the date of the security breach, date of discovery of the breach and a preliminary description of the breach.

 Read more on JDSupra.  While the changes described above are positive ones, the law has also changed the trigger from acquisition or access to “unauthorized acquisition…or a reasonable belief of an unauthorized acquisition.”  That change will likely reduce the scope of incidents we learn about.

Related:

  • California Sets 30 Day Deadline for Data Breach Notifications
  • California’s New Delete Request Tool Impacts Data Brokers and Residents
  • Shad White’s office finds nearly a third of Mississippi's state agencies fail cybersecurity requirements
  • California hospitals can escape fines if workers expose patient info
  • Two agencies in one state investigated and fined Healthplex. Was that one too many?
  • Ohio law to require local governments to formally approve ransomware payments
Category: State/Local

Post navigation

← States crack down on prescription-drug "doctor shopping"
SC: Stolen laptop contained veterans' information, VA →

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.