Indiana breach notification lookup
Use this Indiana breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for Indiana: 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 | Ind. Code art. 24-4.9, including §§ 24-4.9-3-1 and 24-4.9-3-3 | Link the decision record to the official citation |
| Deadline | Disclosures and notifications without unreasonable delay and no more than 45 days after discovery; reasonable delay is allowed for system integrity restoration, breach-scope discovery, or Attorney General/law-enforcement delay requests; notify as soon as possible after the basis for delay ends. | Sort multi-state response work by the shortest stated clock |
| Residents | Indiana residents whose unencrypted personal information, or encrypted personal information with access to the encryption key, was or may have been acquired by an unauthorized person and the acquisition has resulted in or could result in identity deception, identity theft, or fraud. | Identify whether affected residents receive notice |
| Regulator | Notify the Indiana Attorney General whenever a database owner makes a consumer breach disclosure; the Attorney General business FAQ directs organizations to submit the breach notification form by email and optionally by mail or fax with a sample notice. | Record AG or regulator portal review |
| Consumer-reporting agencies | Notify each consumer reporting agency when disclosure is required to more than 1,000 Indiana consumers, with information necessary to assist the agency in preventing fraud. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | Indiana requires notice to affected consumers, the Attorney General, and consumer reporting agencies when more than 1,000 Indiana residents are notified; the Attorney General provides a security breach FAQ and breach notification form for businesses. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
Indiana fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
Ind. Code art. 24-4.9, including §§ 24-4.9-3-1 and 24-4.9-3-3 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
Indiana requires notice to affected consumers, the Attorney General, and consumer reporting agencies when more than 1,000 Indiana residents are notified; the Attorney General provides a security breach FAQ and breach notification form for businesses. 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 Indiana 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 Indiana, 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 Indiana 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 Indiana 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 Indiana?
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.