WISP requirements in Alabama
Alabama requires a documented investigation before the 45-day notice clock is resolved, so a WISP incident file should preserve more than an alert timestamp. Keep the breach determination, substantial-harm analysis, affected-individual count, written law-enforcement delay if any, 10-day third-party-agent notice if applicable, and the Attorney General/consumer-reporting-agency notices when the 1,000-person threshold is crossed.
Key facts
- Alabama firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Individual notice within 45 days after the covered entity determines a breach occurred and is reasonably likely to cause substantial harm; third-party agents must notify the covered entity as expeditiously as possible and no later than 10 days after determining or having reason to believe a breach occurred; AG and CRA notices apply for 1,000+ individuals.
- Notify the Alabama Attorney General as expeditiously as possible and without unreasonable delay, and no later than 45 days, when notice is required for more than 1,000 individuals; the AG online form implements the Data Breach Notification Act reporting path.
Key takeaways
- Alabama firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Individual notice within 45 days after the covered entity determines a breach occurred and is reasonably likely to cause substantial harm; third-party agents must notify the covered entity as expeditiously as possible and no later than 10 days after determining or having reason to believe a breach occurred; AG and CRA notices apply for 1,000+ individuals.
- Notify the Alabama Attorney General as expeditiously as possible and without unreasonable delay, and no later than 45 days, when notice is required for more than 1,000 individuals; the AG online form implements the Data Breach Notification Act reporting path.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Alabama 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. Alabama 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.
Alabama requires Attorney General and nationwide consumer reporting agency notice when a covered entity provides breach notice to more than 1,000 individuals at a single time.
What is specific to Alabama?
Individual notice within 45 days after the covered entity determines a breach occurred and is reasonably likely to cause substantial harm; third-party agents must notify the covered entity as expeditiously as possible and no later than 10 days after determining or having reason to believe a breach occurred; AG and CRA notices apply for 1,000+ individuals. 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 Alabama residents.
Individuals whose sensitive personally identifying information has been acquired or is reasonably believed to have been acquired by an unauthorized person and is reasonably likely to cause substantial harm, after the covered entity completes the statutory investigation.
Notify the Alabama Attorney General as expeditiously as possible and without unreasonable delay, and no later than 45 days, when notice is required for more than 1,000 individuals; the AG online form implements the Data Breach Notification Act reporting path.
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 | Alabama 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 | Individual notice within 45 days after the covered entity determines a breach occurred and is reasonably likely to cause substantial harm; third-party agents must notify the covered entity as expeditiously as possible and no later than 10 days after determining or having reason to believe a breach occurred; AG and CRA notices apply for 1,000+ individuals. | Incident clock and counsel review record |
| Regulator path | Notify the Alabama Attorney General as expeditiously as possible and without unreasonable delay, and no later than 45 days, when notice is required for more than 1,000 individuals; the AG online form implements the Data Breach Notification Act reporting path. | Notification decision log |
| State statute | Ala. Code § 8-38-5 and § 8-38-6 | 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 Alabama have its own WISP law?
This page does not claim a standalone Alabama WISP statute for every firm. It explains how federal WISP duties should be paired with Alabama breach-notification planning.
Who reviews Alabama breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Alabama 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
- Code of Alabama § 8-38-5
- Code of Alabama § 8-38-6
- Code of Alabama § 8-38-8
- Alabama Attorney General data breach notification form
Build a Alabama-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire