WISP requirements in Minnesota
Minnesota is notable because the consumer-reporting-agency clock can run very fast: 48 hours for breaches requiring notice to more than 500 people. A Minnesota incident file should preserve discovery date, encrypted-data analysis, resident notice decision, whether more than 500 notices go out at one time, and the consumer-reporting-agency notice evidence.
Key facts
- Minnesota firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Resident notice in the most expedient time possible and without unreasonable delay, consistent with law-enforcement delay and scope/restoration needs; nationwide consumer-reporting-agency notice within 48 hours for more than 500 persons at one time.
- The reviewed Minnesota breach-notification statute does not create a routine Attorney General filing trigger; the Minnesota Attorney General publishes consumer guidance and may enforce Minnesota consumer-protection laws where appropriate.
Key takeaways
- Minnesota firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Resident notice in the most expedient time possible and without unreasonable delay, consistent with law-enforcement delay and scope/restoration needs; nationwide consumer-reporting-agency notice within 48 hours for more than 500 persons at one time.
- The reviewed Minnesota breach-notification statute does not create a routine Attorney General filing trigger; the Minnesota Attorney General publishes consumer guidance and may enforce Minnesota consumer-protection laws where appropriate.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Minnesota 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. Minnesota 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.
Minnesota requires a business that must notify more than 500 persons at one time to notify all consumer reporting agencies that compile and maintain files on consumers on a nationwide basis within 48 hours of the discovery of the breach.
What is specific to Minnesota?
Resident notice in the most expedient time possible and without unreasonable delay, consistent with law-enforcement delay and scope/restoration needs; nationwide consumer-reporting-agency notice within 48 hours for more than 500 persons at one time. 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 Minnesota residents.
Minnesota residents whose unencrypted personal information was, or is reasonably believed to have been, acquired by an unauthorized person after discovery or notification of a security breach.
The reviewed Minnesota breach-notification statute does not create a routine Attorney General filing trigger; the Minnesota Attorney General publishes consumer guidance and may enforce Minnesota consumer-protection laws where appropriate.
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 | Minnesota 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 in the most expedient time possible and without unreasonable delay, consistent with law-enforcement delay and scope/restoration needs; nationwide consumer-reporting-agency notice within 48 hours for more than 500 persons at one time. | Incident clock and counsel review record |
| Regulator path | The reviewed Minnesota breach-notification statute does not create a routine Attorney General filing trigger; the Minnesota Attorney General publishes consumer guidance and may enforce Minnesota consumer-protection laws where appropriate. | Notification decision log |
| State statute | Minn. Stat. § 325E.61 | 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 Minnesota have its own WISP law?
This page does not claim a standalone Minnesota WISP statute for every firm. It explains how federal WISP duties should be paired with Minnesota breach-notification planning.
Who reviews Minnesota breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Minnesota Attorney General 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
- Minnesota Statutes § 325E.61
- Minnesota Attorney General data breach consumer guidance
- Minnesota Attorney General data breach enforcement release
Build a Minnesota-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire