WISP requirements in Wisconsin
Wisconsin combines a 45-day outer limit with a material-risk trigger, so the incident team has to document more than a date. A Wisconsin incident file should preserve when the firm acquired knowledge of the breach, what evidence showed unauthorized acquisition of personal information, why identity theft or fraud was or was not materially likely, and whether law enforcement delayed notice. It should also keep the resident notice content and the 1,000-individual nationwide-consumer-reporting-agency threshold analysis.
Key facts
- Wisconsin firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Individual notice within a reasonable time, not to exceed 45 days after acquiring knowledge of the breach, subject to law-enforcement delay and measures needed to determine scope and restore system integrity; consumer-reporting-agency notice applies for 1,000+ individuals.
- The reviewed Wisconsin statute does not create a routine Attorney General filing trigger; Wisconsin business guidance is provided through the Department of Agriculture, Trade and Consumer Protection, while consumer-reporting-agency notice is triggered at 1,000 or more individuals.
Key takeaways
- Wisconsin firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Individual notice within a reasonable time, not to exceed 45 days after acquiring knowledge of the breach, subject to law-enforcement delay and measures needed to determine scope and restore system integrity; consumer-reporting-agency notice applies for 1,000+ individuals.
- The reviewed Wisconsin statute does not create a routine Attorney General filing trigger; Wisconsin business guidance is provided through the Department of Agriculture, Trade and Consumer Protection, while consumer-reporting-agency notice is triggered at 1,000 or more individuals.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Wisconsin 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. Wisconsin 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.
Wisconsin requires notification of all nationwide consumer reporting agencies when a single incident requires notice to 1,000 or more individuals, and DATCP publishes guidance for businesses and consumers on data breaches.
What is specific to Wisconsin?
Individual notice within a reasonable time, not to exceed 45 days after acquiring knowledge of the breach, subject to law-enforcement delay and measures needed to determine scope and restore system integrity; consumer-reporting-agency notice applies for 1,000+ individuals. 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 Wisconsin residents.
Wisconsin individuals whose personal information was, or is reasonably believed to have been, acquired by an unauthorized person in a way that materially compromises security, confidentiality, or integrity and creates a material risk of identity theft or fraud.
The reviewed Wisconsin statute does not create a routine Attorney General filing trigger; Wisconsin business guidance is provided through the Department of Agriculture, Trade and Consumer Protection, while consumer-reporting-agency notice is triggered at 1,000 or more individuals.
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 | Wisconsin 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 | Individual notice within a reasonable time, not to exceed 45 days after acquiring knowledge of the breach, subject to law-enforcement delay and measures needed to determine scope and restore system integrity; consumer-reporting-agency notice applies for 1,000+ individuals. | Incident clock and counsel review record |
| Regulator path | The reviewed Wisconsin statute does not create a routine Attorney General filing trigger; Wisconsin business guidance is provided through the Department of Agriculture, Trade and Consumer Protection, while consumer-reporting-agency notice is triggered at 1,000 or more individuals. | Notification decision log |
| State statute | Wis. Stat. § 134.98 | 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 Wisconsin have its own WISP law?
This page does not claim a standalone Wisconsin WISP statute for every firm. It explains how federal WISP duties should be paired with Wisconsin breach-notification planning.
Who reviews Wisconsin breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Wisconsin Department of Agriculture, Trade and Consumer Protection 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
- Wisconsin Statutes § 134.98
- Wisconsin DATCP personal data breach FAQ
- Wisconsin DATCP privacy and identity theft resources
Build a Wisconsin-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire