Idaho breach notification lookup
Use this Idaho breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for Idaho: statute citation, stated notification deadline, residents or regulators who may need notice, consumer-reporting-agency threshold, consumer-notice trigger, official source links, and the last verified date.
Last verified 2026-08-13. Not legal advice.
| Field | Verified value | Use in the incident file |
|---|---|---|
| Statute | Idaho Code §§ 28-51-104 to 28-51-107 | Link the decision record to the official citation |
| Deadline | 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. | Sort multi-state response work by the shortest stated clock |
| 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. | Identify whether affected residents receive notice |
| Regulator | 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. | Record AG or regulator portal review |
| Consumer-reporting agencies | The reviewed Idaho Attorney General and Title 28 Chapter 51 materials did not verify a separate statewide consumer-reporting-agency notice trigger for commercial entities. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | 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. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
Idaho fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
Idaho Code §§ 28-51-104 to 28-51-107 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
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. The consumer trigger matters because the clock usually starts only after a legally meaningful incident analysis, not merely because an IT alert appeared.
The last verified date for this Idaho lookup is 2026-08-13. Use that date as a prompt to refresh counsel review before making a live notification decision.
How to use it during an incident
Start with containment and evidence preservation, then identify affected resident states and compare the shortest stated deadline first.
A practical incident file should record discovery time, encryption status, systems involved, affected consumer count, vendor involvement, and the person responsible for counsel review.
For Idaho, the WISP should say where the notification decision log lives, who contacts counsel, who checks the regulator portal, and who approves any consumer notice before it is sent.
This lookup pairs with the Incident Response Plan because the plan owns the workflow: intake, escalation, containment, preservation, notice analysis, communications, and final review.
How it fits the WISP
A WISP should not guess at state-law outcomes; it should make the breach-review path fast, documented, and source-linked.
Pair this lookup with the Idaho WISP requirements page so the firm's written program names the state-aware incident path before an event happens.
Policywright keeps the breach clock separate from the policy packet: the lookup tells you what to review, while the generated packet assigns owners, evidence records, remediation steps, and review cadence.
Not legal advice. A qualified lawyer should confirm whether the incident facts meet a statutory definition, whether substitute notice or regulator notice applies, and whether another state or federal rule changes the timeline.
FAQ
Is this Idaho lookup legal advice?
No. It is a source-linked lookup for incident planning and should be reviewed with qualified counsel before relying on it in a live notification decision.
What if affected residents live outside Idaho?
Use the multi-state lookup page and include every state where affected residents may live. The comparison table sorts selected states by the shortest stated deadline first.
Does this replace the FTC Safeguards Rule notice analysis?
No. State notice review is separate from the federal Safeguards Rule and 16 CFR 314.4(j) analysis. A serious incident file should preserve both review tracks.