WISP requirements for tax preparers in Oklahoma
If your firm prepares tax returns or handles customer financial information in Oklahoma, the written plan itself is federal. 16 CFR 314.3(a) requires a comprehensive information security program written in one or more readily accessible parts, and it has no small-firm exemption. Oklahoma does not issue its own WISP. What Oklahoma adds is a breach-notification layer that decides who you have to tell, and how fast, if customer information gets out.
Key facts
- The WISP itself is required of Oklahoma firms at any size: 16 CFR 314.3(a) has no consumer-count exemption.
- Under 5,000 consumers, 16 CFR 314.6 does lift four duties, including the written incident response plan at 314.4(h). It does not lift the plan.
- Resident notice without unreasonable delay after determination or notification of the breach, subject to law-enforcement or homeland/national-security delay and scope/restoration measures; Attorney General notice without unreasonable delay and no later than 60 days after impacted-resident notice for breaches meeting the statutory resident threshold.
Key takeaways
- Notify the Oklahoma Attorney General without unreasonable delay, and no later than 60 days after providing notice to impacted Oklahoma residents, unless the single breach affects fewer than 500 Oklahoma residents; a credit-bureau breach has a separate fewer-than-1,000-residents exemption.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Oklahoma 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. Oklahoma 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.
Oklahoma SB 626 adds Attorney General notice for reportable resident notices: notice to the Attorney General is due without unreasonable delay and no later than 60 days after notice to impacted Oklahoma residents, with exemptions for breaches below the statutory Oklahoma-resident thresholds.
What is specific to Oklahoma?
Resident notice without unreasonable delay after determination or notification of the breach, subject to law-enforcement or homeland/national-security delay and scope/restoration measures; Attorney General notice without unreasonable delay and no later than 60 days after impacted-resident notice for breaches meeting the statutory resident threshold. The plan should identify who evaluates state notice, who contacts counsel, and where the decision record is kept.
Oklahoma changed materially with SB 626, effective January 1, 2026, so older Oklahoma breach workflows are not enough. A Policywright Oklahoma incident file should preserve the determination date, access-and-acquisition evidence, encryption/redaction and encryption-key analysis, identity-theft/fraud risk finding, resident count for the 500-resident Attorney General trigger, any credit-bureau-specific threshold issue, Attorney General form submission, estimated monetary impact if determinable, and the reasonable safeguards in place at the time of the breach.
State breach-notification law does not replace the Safeguards Rule. It adds a state-specific response layer when an incident affects Oklahoma residents.
Oklahoma residents whose unencrypted and unredacted personal information was, or is reasonably believed to have been, accessed and acquired by an unauthorized person and whose breach causes or is reasonably believed to cause identity theft or other fraud.
Notify the Oklahoma Attorney General without unreasonable delay, and no later than 60 days after providing notice to impacted Oklahoma residents, unless the single breach affects fewer than 500 Oklahoma residents; a credit-bureau breach has a separate fewer-than-1,000-residents exemption.
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 | Oklahoma 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 without unreasonable delay after determination or notification of the breach, subject to law-enforcement or homeland/national-security delay and scope/restoration measures; Attorney General notice without unreasonable delay and no later than 60 days after impacted-resident notice for breaches meeting the statutory resident threshold. | Incident clock and counsel review record |
| Regulator path | Notify the Oklahoma Attorney General without unreasonable delay, and no later than 60 days after providing notice to impacted Oklahoma residents, unless the single breach affects fewer than 500 Oklahoma residents; a credit-bureau breach has a separate fewer-than-1,000-residents exemption. | Notification decision log |
| State statute | 24 Okla. Stat. §§ 162-166, including § 163 as amended by SB 626 | Source URL retained in page sources |
FAQ
Is this legal advice?
No. Policywright is a documentation product, not a law firm, and nothing here is 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 Oklahoma have its own WISP law?
This page does not claim a standalone Oklahoma WISP statute for every firm. It explains how federal WISP duties should be paired with Oklahoma breach-notification planning.
Who reviews Oklahoma breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Oklahoma 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
- Oklahoma Statutes § 24-163
- Oklahoma Statutes § 24-165
- Oklahoma SB 626 official bill information
- Oklahoma Attorney General data security breach reporting form
Build a Oklahoma-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire