WISP requirements in California
California is a content-heavy breach-notice state. A Policywright incident file for California should preserve the discovery date, the scope/restoration rationale for any delay, the formatted consumer notice, and the Attorney General sample-submission record when the incident affects more than 500 residents.
Key facts
- California firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Within 30 calendar days of discovery or notification of the breach, subject to law-enforcement delay or time needed to determine scope and restore integrity; AG sample notice within 15 calendar days after notifying consumers when more than 500 residents are affected.
- Submit a sample breach notice to the California Attorney General when notice is required for more than 500 California residents.
Key takeaways
- California firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Within 30 calendar days of discovery or notification of the breach, subject to law-enforcement delay or time needed to determine scope and restore integrity; AG sample notice within 15 calendar days after notifying consumers when more than 500 residents are affected.
- Submit a sample breach notice to the California Attorney General when notice is required for more than 500 California residents.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do California 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. California 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.
California notices must use plain language and include specific headings and content; businesses notifying more than 500 California residents must submit a sample notice to the Attorney General within 15 calendar days after notifying consumers.
What is specific to California?
Within 30 calendar days of discovery or notification of the breach, subject to law-enforcement delay or time needed to determine scope and restore integrity; AG sample notice within 15 calendar days after notifying consumers when more than 500 residents are affected. 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 California residents.
Affected California residents whose covered personal information was, or is reasonably believed to have been, acquired by an unauthorized person.
Submit a sample breach notice to the California Attorney General when notice is required for more than 500 California residents.
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 | California 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 | Within 30 calendar days of discovery or notification of the breach, subject to law-enforcement delay or time needed to determine scope and restore integrity; AG sample notice within 15 calendar days after notifying consumers when more than 500 residents are affected. | Incident clock and counsel review record |
| Regulator path | Submit a sample breach notice to the California Attorney General when notice is required for more than 500 California residents. | Notification decision log |
| State statute | Cal. Civ. Code § 1798.82 | 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 California have its own WISP law?
This page does not claim a standalone California WISP statute for every firm. It explains how federal WISP duties should be paired with California breach-notification planning.
Who reviews California breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any California 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
- California Civil Code § 1798.82
- California Attorney General data-breach reporting
- California Attorney General breach sample submission portal
Build a California-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire