WISP requirements for tax preparers in Utah
If your firm prepares tax returns or handles customer financial information in Utah, the written plan itself is federal. 16 CFR 314.3(a) requires a comprehensive information security program written in one or more readily accessible parts, and it has no small-firm exemption. Utah does not issue its own WISP. What Utah adds is a breach-notification layer that decides who you have to tell, and how fast, if customer information gets out.
Key facts
- The WISP itself is required of Utah firms at any size: 16 CFR 314.3(a) has no consumer-count exemption.
- Under 5,000 consumers, 16 CFR 314.6 does lift four duties, including the written incident response plan at 314.4(h). It does not lift the plan.
- Notice in the most expedient time possible without unreasonable delay after determining scope, restoring reasonable system integrity, and accounting for law-enforcement delay; maintainers notify and cooperate with the owner or licensee immediately after discovery if misuse occurs or is reasonably likely.
Key takeaways
- Notify the Utah Attorney General and Utah Cyber Center if misuse of personal information relating to 500 or more Utah residents has occurred or is reasonably likely to occur; include breach date, discovery date, total affected people, Utah resident count, data type, and short breach description to the extent known or available.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Utah 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. Utah 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.
Utah requires notification to the Office of the Attorney General and the Utah Cyber Center when misuse relating to 500 or more Utah residents has occurred or is reasonably likely to occur; the Utah Cyber Center breach form automatically notifies both entities.
What is specific to Utah?
Notice in the most expedient time possible without unreasonable delay after determining scope, restoring reasonable system integrity, and accounting for law-enforcement delay; maintainers notify and cooperate with the owner or licensee immediately after discovery if misuse occurs or is reasonably likely. The plan should identify who evaluates state notice, who contacts counsel, and where the decision record is kept.
Utah is investigation-driven: the first required step is a prompt good-faith analysis of whether personal information has been or will be misused for identity theft or fraud. A Utah WISP incident file should preserve that misuse analysis, scope and restoration steps, Utah resident count, 500-resident Attorney General and Cyber Center filing, 1,000-resident consumer-reporting-agency analysis, and any law-enforcement delay record.
State breach-notification law does not replace the Safeguards Rule. It adds a state-specific response layer when an incident affects Utah residents.
Affected Utah residents when the investigation reveals that misuse of personal information for identity theft or fraud purposes has occurred or is reasonably likely to occur.
Notify the Utah Attorney General and Utah Cyber Center if misuse of personal information relating to 500 or more Utah residents has occurred or is reasonably likely to occur; include breach date, discovery date, total affected people, Utah resident count, data type, and short breach description to the extent known or available.
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 | Utah 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 | Notice in the most expedient time possible without unreasonable delay after determining scope, restoring reasonable system integrity, and accounting for law-enforcement delay; maintainers notify and cooperate with the owner or licensee immediately after discovery if misuse occurs or is reasonably likely. | Incident clock and counsel review record |
| Regulator path | Notify the Utah Attorney General and Utah Cyber Center if misuse of personal information relating to 500 or more Utah residents has occurred or is reasonably likely to occur; include breach date, discovery date, total affected people, Utah resident count, data type, and short breach description to the extent known or available. | Notification decision log |
| State statute | Utah Code § 13-44-202 | Source URL retained in page sources |
FAQ
Is this legal advice?
No. Policywright is a documentation product, not a law firm, and nothing here is 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 Utah have its own WISP law?
This page does not claim a standalone Utah WISP statute for every firm. It explains how federal WISP duties should be paired with Utah breach-notification planning.
Who reviews Utah breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Utah Attorney General and Utah Cyber Center 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
- Utah Code § 13-44-202
- Utah Cyber Center report a breach
- Utah Code § 13-44-301 enforcement
Build a Utah-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire