WISP requirements in Wyoming
Wyoming is a misuse-investigation state rather than a fixed-day reporting state. A Policywright Wyoming incident file should preserve when the firm became aware of the breach, the prompt investigation record, the misuse-likelihood determination, scope/restoration steps, any written law-enforcement delay, whether the firm is Wyoming-based for substitute-notice thresholds, resident notice content, and vendor-versus-direct-business-relationship decisions about who sends the single required notice.
Key facts
- Wyoming firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- After becoming aware of a breach, conduct a reasonable and prompt investigation; if misuse occurred or is reasonably likely, notify affected Wyoming residents as soon as possible, in the most expedient time possible and without unreasonable delay, subject to written law-enforcement delay and scope/restoration needs. Data maintainers notify the business entity as soon as practicable after the determination.
- The reviewed Wyoming breach-notification statute does not verify a routine Attorney General breach-reporting trigger; the Attorney General may bring an action to address violations, seek appropriate compliance relief, recover damages, or both.
Key takeaways
- Wyoming firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- After becoming aware of a breach, conduct a reasonable and prompt investigation; if misuse occurred or is reasonably likely, notify affected Wyoming residents as soon as possible, in the most expedient time possible and without unreasonable delay, subject to written law-enforcement delay and scope/restoration needs. Data maintainers notify the business entity as soon as practicable after the determination.
- The reviewed Wyoming breach-notification statute does not verify a routine Attorney General breach-reporting trigger; the Attorney General may bring an action to address violations, seek appropriate compliance relief, recover damages, or both.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Wyoming 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. Wyoming 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.
Wyoming's reviewed statute does not verify a routine Attorney General filing trigger or a fixed calendar deadline; it requires clear and conspicuous resident notices with specific content, including breach description, affected information types, contact resources, protective steps, and any law-enforcement delay that can reasonably be determined.
What is specific to Wyoming?
After becoming aware of a breach, conduct a reasonable and prompt investigation; if misuse occurred or is reasonably likely, notify affected Wyoming residents as soon as possible, in the most expedient time possible and without unreasonable delay, subject to written law-enforcement delay and scope/restoration needs. Data maintainers notify the business entity as soon as practicable after the determination. 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 Wyoming residents.
Wyoming residents whose personal identifying information has been misused or is reasonably likely to be misused after a good-faith, prompt investigation of a breach of the security system.
The reviewed Wyoming breach-notification statute does not verify a routine Attorney General breach-reporting trigger; the Attorney General may bring an action to address violations, seek appropriate compliance relief, recover damages, or both.
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 | Wyoming 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 | After becoming aware of a breach, conduct a reasonable and prompt investigation; if misuse occurred or is reasonably likely, notify affected Wyoming residents as soon as possible, in the most expedient time possible and without unreasonable delay, subject to written law-enforcement delay and scope/restoration needs. Data maintainers notify the business entity as soon as practicable after the determination. | Incident clock and counsel review record |
| Regulator path | The reviewed Wyoming breach-notification statute does not verify a routine Attorney General breach-reporting trigger; the Attorney General may bring an action to address violations, seek appropriate compliance relief, recover damages, or both. | Notification decision log |
| State statute | Wyo. Stat. Ann. §§ 40-12-501 and 40-12-502 | 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 Wyoming have its own WISP law?
This page does not claim a standalone Wyoming WISP statute for every firm. It explains how federal WISP duties should be paired with Wyoming breach-notification planning.
Who reviews Wyoming breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Wyoming 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
- Wyoming Legislature Article 5, including §§ 40-12-501 and 40-12-502
- 2025 Wyoming Statutes § 40-12-502 reference copy
- Wyoming Attorney General consumer education
- Wyoming Attorney General contact information
Build a Wyoming-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire