WISP requirements in Indiana
Indiana combines a firm 45-day outer deadline with an Attorney General notice duty whenever consumer disclosure is required, so the AG submission should not be left as a late administrative step. A Policywright Indiana file should preserve the discovery date, identity-theft/fraud risk analysis, delay rationale if any, resident notice copy, Attorney General form/email record, and the 1,000-consumer reporting-agency trigger decision.
Key facts
- Indiana firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- 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.
- 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.
Key takeaways
- Indiana firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- 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.
- 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.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Indiana 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. Indiana 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.
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.
What is specific to Indiana?
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. 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 Indiana 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.
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.
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 | Indiana 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 | 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. | Incident clock and counsel review record |
| Regulator path | 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. | Notification decision log |
| State statute | Ind. Code art. 24-4.9, including §§ 24-4.9-3-1 and 24-4.9-3-3 | 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 Indiana have its own WISP law?
This page does not claim a standalone Indiana WISP statute for every firm. It explains how federal WISP duties should be paired with Indiana breach-notification planning.
Who reviews Indiana breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Indiana 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
- Indiana General Assembly, Indiana Code Title 24 Article 4.9
- Indiana Attorney General security breach FAQ and notification form for businesses
- Indiana Attorney General file a complaint/report notice page
Build a Indiana-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire