WISP requirements in Virginia
Virginia’s trigger is narrower than a bare access event: the file should document access plus acquisition and the identity-theft or fraud risk analysis. A Virginia WISP incident workflow should preserve the discovery date, scope/restoration delay rationale, resident notice template, Attorney General notice record, payroll-tax data analysis, and the 1,000-person consumer-reporting-agency threshold.
Key facts
- Virginia firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Resident and Attorney General notice without unreasonable delay after discovery or notification, subject to scope/restoration needs and law-enforcement delay; consumer-reporting-agency notice without unreasonable delay for notices to more than 1,000 persons at one time.
- Notify the Virginia Office of the Attorney General when affected residents must be notified; when more than 1,000 persons are notified at one time, provide timing, distribution, and content information to the Office of the Attorney General as well.
Key takeaways
- Virginia firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Resident and Attorney General notice without unreasonable delay after discovery or notification, subject to scope/restoration needs and law-enforcement delay; consumer-reporting-agency notice without unreasonable delay for notices to more than 1,000 persons at one time.
- Notify the Virginia Office of the Attorney General when affected residents must be notified; when more than 1,000 persons are notified at one time, provide timing, distribution, and content information to the Office of the Attorney General as well.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Virginia 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. Virginia 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.
Virginia notice may be delayed to determine breach scope, restore system integrity, or because law enforcement advises delay; employer or payroll-service incidents involving taxpayer identification numbers and income-tax withholding also have an Attorney General notice path.
What is specific to Virginia?
Resident and Attorney General notice without unreasonable delay after discovery or notification, subject to scope/restoration needs and law-enforcement delay; consumer-reporting-agency notice without unreasonable delay for notices to more than 1,000 persons 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 Virginia residents.
Virginia residents whose unencrypted or unredacted computerized personal information was, or is reasonably believed to have been, accessed and acquired and causes or is reasonably believed to cause identity theft or another fraud.
Notify the Virginia Office of the Attorney General when affected residents must be notified; when more than 1,000 persons are notified at one time, provide timing, distribution, and content information to the Office of the Attorney General as well.
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 | Virginia 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 and Attorney General notice without unreasonable delay after discovery or notification, subject to scope/restoration needs and law-enforcement delay; consumer-reporting-agency notice without unreasonable delay for notices to more than 1,000 persons at one time. | Incident clock and counsel review record |
| Regulator path | Notify the Virginia Office of the Attorney General when affected residents must be notified; when more than 1,000 persons are notified at one time, provide timing, distribution, and content information to the Office of the Attorney General as well. | Notification decision log |
| State statute | Va. Code § 18.2-186.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 Virginia have its own WISP law?
This page does not claim a standalone Virginia WISP statute for every firm. It explains how federal WISP duties should be paired with Virginia breach-notification planning.
Who reviews Virginia breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Virginia Office of the 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 Virginia § 18.2-186.6
- Virginia Office of the Attorney General consumer protection
Build a Virginia-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire