WISP requirements in Georgia
Georgia’s page should not be treated like a universal AG-notice state. A Georgia WISP incident file should identify whether the entity is acting as an information broker, data collector, or service provider, preserve the 24-hour owner/data-collector notification record for maintained data, document the resident-notice timing rationale, and separately track the unusually high 10,000-resident consumer-reporting-agency threshold.
Key facts
- Georgia 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, subject to law-enforcement delay and scope/restoration needs; service providers maintaining data for an information broker or data collector notify the owner or data collector within 24 hours following discovery; consumer-reporting-agency notice applies for more than 10,000 residents at one time.
- The reviewed Georgia general breach-notification materials do not impose a routine Attorney General filing trigger; Georgia Attorney General ConsumerEd provides consumer-facing breach-notification guidance and the AG cybersecurity page provides reporting resources for cyber fraud.
Key takeaways
- Georgia 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, subject to law-enforcement delay and scope/restoration needs; service providers maintaining data for an information broker or data collector notify the owner or data collector within 24 hours following discovery; consumer-reporting-agency notice applies for more than 10,000 residents at one time.
- The reviewed Georgia general breach-notification materials do not impose a routine Attorney General filing trigger; Georgia Attorney General ConsumerEd provides consumer-facing breach-notification guidance and the AG cybersecurity page provides reporting resources for cyber fraud.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Georgia 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. Georgia 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.
Georgia’s public Attorney General ConsumerEd guidance explains the resident-notice duty under O.C.G.A. § 10-1-912; the reviewed general breach law does not create a routine Attorney General filing trigger for private incidents.
What is specific to Georgia?
Resident notice in the most expedient time possible and without unreasonable delay, subject to law-enforcement delay and scope/restoration needs; service providers maintaining data for an information broker or data collector notify the owner or data collector within 24 hours following discovery; consumer-reporting-agency notice applies for more than 10,000 residents 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 Georgia residents.
Georgia residents whose unencrypted personal information was, or is reasonably believed to have been, acquired by an unauthorized person after a breach of the security of the system maintained by an information broker or data collector.
The reviewed Georgia general breach-notification materials do not impose a routine Attorney General filing trigger; Georgia Attorney General ConsumerEd provides consumer-facing breach-notification guidance and the AG cybersecurity page provides reporting resources for cyber fraud.
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 | Georgia 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, subject to law-enforcement delay and scope/restoration needs; service providers maintaining data for an information broker or data collector notify the owner or data collector within 24 hours following discovery; consumer-reporting-agency notice applies for more than 10,000 residents at one time. | Incident clock and counsel review record |
| Regulator path | The reviewed Georgia general breach-notification materials do not impose a routine Attorney General filing trigger; Georgia Attorney General ConsumerEd provides consumer-facing breach-notification guidance and the AG cybersecurity page provides reporting resources for cyber fraud. | Notification decision log |
| State statute | O.C.G.A. § 10-1-912 | 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 Georgia have its own WISP law?
This page does not claim a standalone Georgia WISP statute for every firm. It explains how federal WISP duties should be paired with Georgia breach-notification planning.
Who reviews Georgia breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Georgia Attorney General Consumer Protection Division 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
- Georgia Attorney General ConsumerEd data breach guidance
- Georgia Attorney General cybersecurity resources
- Georgia Department of Human Services data breach policy citing O.C.G.A. § 10-1-910 et seq.
Build a Georgia-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire