WISP requirements in Maine
Maine is unusually explicit about the sequence: investigate misuse risk, identify scope, notify residents within the 30-day ceiling when no law-enforcement delay applies, and send regulator notice to either DPFR or the Attorney General. A Policywright Maine file should preserve the broker/non-broker role, misuse analysis, scope-identification date, seven-business-day post-law-enforcement-delay clock, CRA notice for 1,000+ people, and AG or DPFR submission evidence.
Key facts
- Maine firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Resident notice as expediently as possible and without unreasonable delay, and if there is no law-enforcement delay, no more than 30 days after becoming aware of the breach and identifying its scope; third-party maintainers notify the data owner immediately; law-enforcement delay may last no longer than seven business days after law enforcement determines notice will not compromise the investigation.
- Notify the appropriate Maine Department of Professional and Financial Regulation regulator if regulated by that department; otherwise notify the Maine Attorney General through the Report a Data Breach service when notice under 10 M.R.S. § 1348 is required.
Key takeaways
- Maine firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Resident notice as expediently as possible and without unreasonable delay, and if there is no law-enforcement delay, no more than 30 days after becoming aware of the breach and identifying its scope; third-party maintainers notify the data owner immediately; law-enforcement delay may last no longer than seven business days after law enforcement determines notice will not compromise the investigation.
- Notify the appropriate Maine Department of Professional and Financial Regulation regulator if regulated by that department; otherwise notify the Maine Attorney General through the Report a Data Breach service when notice under 10 M.R.S. § 1348 is required.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Maine tax preparers need a WISP?
Yes, if they are covered by the FTC Safeguards Rule or IRS tax-data security expectations, they should maintain a written plan. Maine state breach-notice duties make incident planning especially important.
The WISP should start with federal obligations because the Safeguards Rule supplies the security-program structure.
Maine requires regulator notice when resident notice is required: entities regulated by Maine’s Department of Professional and Financial Regulation notify the appropriate department regulator, and other entities notify the Attorney General through the security breach reporting service.
What is specific to Maine?
Resident notice as expediently as possible and without unreasonable delay, and if there is no law-enforcement delay, no more than 30 days after becoming aware of the breach and identifying its scope; third-party maintainers notify the data owner immediately; law-enforcement delay may last no longer than seven business days after law enforcement determines notice will not compromise the investigation. The plan should identify who evaluates state notice, who contacts counsel, and where the decision record is kept.
State breach-notification law does not replace the Safeguards Rule. It adds a state-specific response layer when an incident affects Maine residents.
Maine residents whose personal information has been, or is reasonably believed to have been, acquired by an unauthorized person after the required investigation, including the separate standard for non-broker persons when misuse has occurred or is reasonably possible.
Notify the appropriate Maine Department of Professional and Financial Regulation regulator if regulated by that department; otherwise notify the Maine Attorney General through the Report a Data Breach service when notice under 10 M.R.S. § 1348 is required.
What should the WISP say?
It should describe real safeguards, assign responsibility, map vendors and systems, and include an incident-response path that reaches state-law review quickly.
For a small firm, the strongest plan is plain and evidence-backed: MFA records, backup tests, access reviews, training, vendor lists, and remediation dates.
The plan should never promise a control that is not actually in place.
| Topic | Maine planning note | Evidence |
|---|---|---|
| Federal WISP | Use 16 CFR Part 314 as the program backbone | WISP and annual review |
| IRS tax data | Account for taxpayer records, PTIN practice, portals, and e-file workflows | System inventory and access list |
| Breach notice | Resident notice as expediently as possible and without unreasonable delay, and if there is no law-enforcement delay, no more than 30 days after becoming aware of the breach and identifying its scope; third-party maintainers notify the data owner immediately; law-enforcement delay may last no longer than seven business days after law enforcement determines notice will not compromise the investigation. | Incident clock and counsel review record |
| Regulator path | Notify the appropriate Maine Department of Professional and Financial Regulation regulator if regulated by that department; otherwise notify the Maine Attorney General through the Report a Data Breach service when notice under 10 M.R.S. § 1348 is required. | Notification decision log |
| State statute | 10 M.R.S. §§ 1348 and 1349 | Source URL retained in page sources |
FAQ
Is this legal advice?
No. Policywright is a configurable template product, not a law firm and not legal advice. A qualified lawyer should review state-law reliance or breach-notification decisions.
Does a small firm still need a written plan?
Yes. The Safeguards Rule requires a written information security program for covered financial institutions, and IRS guidance tells paid tax preparers to maintain a written data security plan.
What if a control is not in place yet?
A serious WISP should not pretend. It should identify the gap, assign an owner, set a target date, and preserve a dated remediation record.
Does Maine have its own WISP law?
This page does not claim a standalone Maine WISP statute for every firm. It explains how federal WISP duties should be paired with Maine breach-notification planning.
Who reviews Maine breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Maine Attorney General / Department of Professional and Financial Regulation regulator-notice analysis.
Sources
- FTC Safeguards Rule, 16 CFR Part 314 (eCFR)
- FTC, Safeguards Rule: What Your Business Needs to Know
- FTC, Safeguards Rule notification requirement now in effect (16 CFR 314.4(j), eff. May 13, 2024)
- IRS Publication 5708, Creating a Written Information Security Plan
- IRS Publication 4557, Safeguarding Taxpayer Data
- IRS Form W-12, PTIN Application and Renewal
- IRS Publication 1345, Handbook for Authorized IRS e-file Providers
- Maine Revised Statutes Title 10, § 1348
- Maine Revised Statutes Title 10, § 1349
- Maine Attorney General data security breaches
Build a Maine-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire