DataBreaches.Net

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

Missouri data breach notification law goes into effect soon

Posted on July 21, 2009 by Dissent

Perkins Coie has provided a short synopsis of key requirements of Missouri’s new data breach notification law, which goes into effect on August 28, 2009.

….. In addition to the more common elements of first name or initial and last name in combination with unencrypted Social Security Number, driver’s license number, financial account number, or credit or debit card number, the statute also includes in the definition of personal information first name or initial and last name in combination with an unencrypted:

  • Unique electronic identifier or routing code, in combination with any required security code, access code, or password that would permit access to an individual’s financial account;
  • Medical information, which includes any information regarding an individual’s medical history, mental or physical condition, or medical treatment or diagnosis by a health care professional; and
  • Health insurance information, which includes an individual’s health insurance policy number or subscriber identification number, any unique identifier used by a health insurer to identify the individual.

Other provisions of interest:

  • If an entity must notify more than 1000 residents, it must notify the Missouri Attorney General’s office and the nationwide consumer reporting agencies of the breach.
  • Civil penalties for violating the statute may reach up to $150,000 per breach of the security of the system.

The full text of the bill can be found at: http://www.house.mo.gov/billtracking/bills091/biltxt/truly/HB0062T.HTM.

Perkins Coie’s chart summarizing all of the states’ data breach notification laws can be found at: http://www.perkinscoie.com/statebreachchart/.

Source:  Perkins Coie blog, Digestible Law.


Related:

  • Resource: NY DFS Issues New Cybersecurity Guidance to Address Risks Associated with the Use of Third-Party Service Providers
  • 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
  • Harrods warns customers their personal data could have been stolen by hackers in new cyber-attack
Category: Breach LawsLegislationState/Local

Post navigation

← FAQ on Nevada’s Security of Personal Information Law (NRS 603A)
Porn Actress Says State Intruded on Privacy →

1 thought on “Missouri data breach notification law goes into effect soon”

  1. Golde says:
    July 21, 2009 at 7:12 pm

    This law is poorly constructed. I had hoped that Missouri would take the best of all the laws and not the worst. SSN and financial records are enough for a thief to use. By limiting the law to a combination with a name does not adequately cover the topic. That means any breach that had credit card information or SSNs only is not a breach. They did not look at the newer laws that covered paper breaches, according to ITRC about 25% of all breaches. And the requirement to notify the credit bureaus if more than 1000 records are affected is a way for the CRAs to create marketing lists and sell their services to a breached company before any other remediation company or consultant can talk with them. Finally, the “risk of harm” allows a company to say no harm can come from the breach without any accountability to a government agency like the Secret Service that can analyze the breach. There is a definite incentive to say- no risk of harm, thereby no notification is needed. A check and balance system was needed in this law.

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

  • 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.