DataBreaches.Net

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

Seeking clarification on Maine’s data breach notification statute

Posted on December 5, 2023 by Dissent

If you can’t get an interpretation of a state breach notification statute from the state’s attorney general, where can you get it?

DataBreaches recently wrote to the Maine Attorney General’s Office:

I am not sure I really understand a provision in Chapter 210-B §1348. Security breach notice requirements, and am seeking clarification.

In Paragraph 1, it says: “The notices required under paragraphs A and B must be made as expediently as possible and without unreasonable delay, consistent with the legitimate needs of law enforcement pursuant to subsection 3 or with measures necessary to determine the scope of the security breach and restore the reasonable integrity, security and confidentiality of the data in the system. If there is no delay of notification due to law enforcement investigation pursuant to subsection 3, the notices must be made no more than 30 days after the person identified in paragraph A or B becomes aware of a breach of security and identifies its scope. ‘

I need clarification on what it means to identify or determine the scope of the breach. Can an entity take 8 months to figure out everyone they need to notify and say that the breach was only “discovered” after they completed that full investigation? Or is the breach discovered for purposes of reporting to the regulator when the entity knows personal information has been accessed or acquired, even if they are not yet sure exactly how many people and who had their data acquired?

I read a lot of notification letters appended to submissions to your site from health care entities that report a “breach discovered” date that is not in compliance with how HIPAA and HITECH define “discovered.” Their letters are pretty much deceiving patients about when a breach was “discovered,” and I wonder if they are in compliance with Maine’s statute or if they are also violating Maine’s statute.

Here’s the response from Danna Hayes, J.D., Special Assistant to the AG Office of the Maine Attorney General

Thank you for your inquiry. The Attorney General is unable to provide legal advice to the public and our interpretation of requirements of the breach notification law is very dependent on specific facts and circumstances, which we would have to investigate to ascertain compliance. We don’t and couldn’t investigate every breach notice that is filed with our office. The database is published as a public service to consumers and the public.

If they can’t answer the question about what the statute means in terms of when a breach must be reported by, how can entities be expected to comply with it?

Related posts:

  • Updates to the Gramm-Leach-Bliley Act Cybersecurity Requirements
Category: Breach LawsState/Local

Post navigation

← East River Medical Imaging notifies 605,809 patients of breach
CBIZ KA Notice of Data Privacy Incident (Prime Healthcare) →

2 thoughts on “Seeking clarification on Maine’s data breach notification statute”

  1. Adam says:
    December 5, 2023 at 10:02 am

    Doing a lot of work with lawyers, but not being one I think the issue is the part where you ask “I wonder if they are in compliance with Maine’s statute” and they don’t want to say.

    If you ask “are there circumstances where “awareness” means that a full investigation has been completed” or is the meaning of awareness that a reasonable person has reason to be aware (or something more narrow) then they’re not ruling on “compliance”

    1. Dissent says:
      December 5, 2023 at 12:01 pm

      OK. Your turn. Go ask. 🙂

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

  • Qantas customers involved in mammoth data breach
  • CMS Sending Letters to 103,000 Medicare beneficiaries whose info was involved in a Medicare.gov breach.
  • Esse Health provides update about April cyberattack and notifies 263,601 people
  • Terrible tales of opsec oversights: How cybercrooks get themselves caught
  • International Criminal Court hit with cyber attack during NATO summit
  • Pembroke Regional Hospital reported canceling appointments due to service delays from “an incident”
  • Iran-linked hackers threaten to release emails allegedly stolen from Trump associates
  • National Health Care Fraud Takedown Results in 324 Defendants Charged in Connection with Over $14.6 Billion in Alleged Fraud
  • Swiss Health Foundation Radix Hit by Cyberattack Affecting Federal Data
  • Russian hackers get 7 and 5 years in prison for large-scale cyber attacks with ransomware, over 60 million euros in bitcoins seized

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

  • The Trump administration is building a national citizenship data system
  • Supreme Court Decision on Age Verification Tramples Free Speech and Undermines Privacy
  • New Jersey Issues Draft Privacy Regulations: The New
  • Hacker helped kill FBI sources, witnesses in El Chapo case, according to watchdog report
  • Germany Wants Apple, Google to Remove DeepSeek From Their App Stores
  • Supreme Court upholds Texas law requiring age verification on porn sites
  • Justices nix Medicaid ‘right’ to choose doctor, defunding Planned Parenthood in South Carolina

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.