WISP requirements in Arizona
Arizona starts with a prompt investigation and then runs a 45-day clock from the breach determination, not merely from suspicion of an incident. An Arizona incident file should preserve the security-incident investigation, breach determination date, substantial-economic-loss analysis, resident count, Attorney General and Department of Homeland Security submissions for 1,000+ notices, and any law-enforcement delay record.
Key facts
- Arizona firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Affected-individual notice within 45 days after determining a security-system breach occurred; if law enforcement delay applies, provide required notices within 45 days after law enforcement says notice no longer compromises the investigation.
- Notify the Arizona Attorney General and the Director of the Arizona Department of Homeland Security in writing when notification is required for more than 1,000 individuals; the same notification provided to affected individuals may be submitted if no common form exists.
Key takeaways
- Arizona firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Affected-individual notice within 45 days after determining a security-system breach occurred; if law enforcement delay applies, provide required notices within 45 days after law enforcement says notice no longer compromises the investigation.
- Notify the Arizona Attorney General and the Director of the Arizona Department of Homeland Security in writing when notification is required for more than 1,000 individuals; the same notification provided to affected individuals may be submitted if no common form exists.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Arizona 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. Arizona 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.
Arizona requires additional notice to the three largest nationwide consumer reporting agencies, the Attorney General, and the Director of the Arizona Department of Homeland Security when a breach requires notification of more than 1,000 individuals.
What is specific to Arizona?
Affected-individual notice within 45 days after determining a security-system breach occurred; if law enforcement delay applies, provide required notices within 45 days after law enforcement says notice no longer compromises the investigation. 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 Arizona residents.
Individuals affected by a determined security-system breach involving unencrypted and unredacted computerized personal information, unless the person, law enforcement, or an independent forensic auditor determines that the breach is not reasonably likely to result in substantial economic loss.
Notify the Arizona Attorney General and the Director of the Arizona Department of Homeland Security in writing when notification is required for more than 1,000 individuals; the same notification provided to affected individuals may be submitted if no common form exists.
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 | Arizona 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 | Affected-individual notice within 45 days after determining a security-system breach occurred; if law enforcement delay applies, provide required notices within 45 days after law enforcement says notice no longer compromises the investigation. | Incident clock and counsel review record |
| Regulator path | Notify the Arizona Attorney General and the Director of the Arizona Department of Homeland Security in writing when notification is required for more than 1,000 individuals; the same notification provided to affected individuals may be submitted if no common form exists. | Notification decision log |
| State statute | Ariz. Rev. Stat. § 18-552 | 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 Arizona have its own WISP law?
This page does not claim a standalone Arizona WISP statute for every firm. It explains how federal WISP duties should be paired with Arizona breach-notification planning.
Who reviews Arizona breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Arizona Attorney General and Arizona Department of Homeland Security 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
- Arizona Revised Statutes § 18-552
- Arizona Attorney General data privacy and data breach reporting
- Arizona Attorney General data breach notification FAQ
Build a Arizona-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire