WISP requirements in Kentucky
Kentucky’s trigger requires more than unauthorized access: the incident record should connect unauthorized acquisition of unencrypted and unredacted data to actual or reasonably likely identity theft or fraud against a Kentucky resident. A Kentucky WISP file should preserve the discovery or vendor-notification date, owner/licensee notice, scope/restoration rationale, resident notice evidence, and the 1,000-person consumer-reporting-agency threshold analysis.
Key facts
- Kentucky 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 after discovery or notification, subject to law-enforcement delay and scope/restoration needs; data maintainers notify owners or licensees as soon as reasonably practicable; consumer-reporting-agency notice applies for more than 1,000 persons at one time.
- The reviewed Kentucky general breach-notification statute does not impose a routine Attorney General filing trigger on private information holders; affected consumers may contact the Kentucky Attorney General’s Data Breach Hotline or consumer complaint process.
Key takeaways
- Kentucky 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 after discovery or notification, subject to law-enforcement delay and scope/restoration needs; data maintainers notify owners or licensees as soon as reasonably practicable; consumer-reporting-agency notice applies for more than 1,000 persons at one time.
- The reviewed Kentucky general breach-notification statute does not impose a routine Attorney General filing trigger on private information holders; affected consumers may contact the Kentucky Attorney General’s Data Breach Hotline or consumer complaint process.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Kentucky 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. Kentucky 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.
Kentucky’s general breach-notification statute does not create a routine Attorney General filing trigger for private information holders; the Attorney General publishes identity-theft and data-breach consumer guidance and operates a data-breach hotline for affected consumers.
What is specific to Kentucky?
Resident notice in the most expedient time possible and without unreasonable delay after discovery or notification, subject to law-enforcement delay and scope/restoration needs; data maintainers notify owners or licensees as soon as reasonably practicable; consumer-reporting-agency notice applies for more than 1,000 persons at one time. 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 Kentucky residents.
Kentucky residents whose unencrypted personal information was, or is reasonably believed to have been, acquired by an unauthorized person in a breach that actually causes, or is reasonably believed has caused or will cause, identity theft or fraud against a Kentucky resident.
The reviewed Kentucky general breach-notification statute does not impose a routine Attorney General filing trigger on private information holders; affected consumers may contact the Kentucky Attorney General’s Data Breach Hotline or consumer complaint process.
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 | Kentucky 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 after discovery or notification, subject to law-enforcement delay and scope/restoration needs; data maintainers notify owners or licensees as soon as reasonably practicable; consumer-reporting-agency notice applies for more than 1,000 persons at one time. | Incident clock and counsel review record |
| Regulator path | The reviewed Kentucky general breach-notification statute does not impose a routine Attorney General filing trigger on private information holders; affected consumers may contact the Kentucky Attorney General’s Data Breach Hotline or consumer complaint process. | Notification decision log |
| State statute | Ky. Rev. Stat. § 365.732 | 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 Kentucky have its own WISP law?
This page does not claim a standalone Kentucky WISP statute for every firm. It explains how federal WISP duties should be paired with Kentucky breach-notification planning.
Who reviews Kentucky breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Kentucky 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
- Kentucky Revised Statutes § 365.732
- Kentucky Attorney General identity theft and data breach guidance
- Kentucky Revised Statutes Chapter 365 index
Build a Kentucky-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire