WISP requirements in Idaho
Idaho should not be modeled as a universal Attorney General filing state. A Policywright Idaho incident file should preserve the illegal-acquisition and misuse-likelihood analysis, the discovery date, scope and restoration rationale, immediate owner/licensee notification for maintained data, whether the organization is a public agency subject to the 24-hour Attorney General rule, and any voluntary commercial report to the Consumer Protection Division.
Key facts
- Idaho 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 measures needed to determine scope, identify affected residents, and restore system integrity; law-enforcement delay may apply; data maintainers notify owners or licensees immediately when misuse occurred or is reasonably likely; public-agency Attorney General notice is due within 24 hours of discovery.
- Idaho public agencies must notify the Idaho Attorney General within 24 hours after discovering a security breach. Commercial entities are not required to notify the Attorney General, but the Attorney General’s Consumer Protection Division accepts voluntary reports by email or mail.
Key takeaways
- Idaho 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 measures needed to determine scope, identify affected residents, and restore system integrity; law-enforcement delay may apply; data maintainers notify owners or licensees immediately when misuse occurred or is reasonably likely; public-agency Attorney General notice is due within 24 hours of discovery.
- Idaho public agencies must notify the Idaho Attorney General within 24 hours after discovering a security breach. Commercial entities are not required to notify the Attorney General, but the Attorney General’s Consumer Protection Division accepts voluntary reports by email or mail.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Idaho 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. Idaho 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.
Idaho public agencies must notify the Attorney General within 24 hours of discovering a security breach; commercial entities may notify the Attorney General Consumer Protection Division but the Attorney General states they are not required to do so.
What is specific to Idaho?
Resident notice in the most expedient time possible and without unreasonable delay, consistent with measures needed to determine scope, identify affected residents, and restore system integrity; law-enforcement delay may apply; data maintainers notify owners or licensees immediately when misuse occurred or is reasonably likely; public-agency Attorney General notice is due within 24 hours of discovery. 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 Idaho residents.
Idaho residents whose unencrypted computerized personal information was illegally acquired and materially compromised, unless a good-faith, reasonable, and prompt investigation determines misuse has not occurred and is not reasonably likely to occur.
Idaho public agencies must notify the Idaho Attorney General within 24 hours after discovering a security breach. Commercial entities are not required to notify the Attorney General, but the Attorney General’s Consumer Protection Division accepts voluntary reports by email or mail.
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 | Idaho 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 measures needed to determine scope, identify affected residents, and restore system integrity; law-enforcement delay may apply; data maintainers notify owners or licensees immediately when misuse occurred or is reasonably likely; public-agency Attorney General notice is due within 24 hours of discovery. | Incident clock and counsel review record |
| Regulator path | Idaho public agencies must notify the Idaho Attorney General within 24 hours after discovering a security breach. Commercial entities are not required to notify the Attorney General, but the Attorney General’s Consumer Protection Division accepts voluntary reports by email or mail. | Notification decision log |
| State statute | Idaho Code §§ 28-51-104 to 28-51-107 | 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 Idaho have its own WISP law?
This page does not claim a standalone Idaho WISP statute for every firm. It explains how federal WISP duties should be paired with Idaho breach-notification planning.
Who reviews Idaho breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Idaho 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
- Idaho Code Title 28, Chapter 51
- Idaho Attorney General security breaches
- Idaho Attorney General Consumer Protection Division
Build a Idaho-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire