WISP requirements in Nevada
Nevada’s statute has no fixed day count, so the incident record should show why the notice timing was still the most expedient possible under the facts. A Nevada WISP incident file should preserve discovery or vendor-notification date, owner/licensee immediate notice if applicable, unencrypted-data analysis, resident count, nationwide consumer-reporting-agency notice for 1,000+ persons, and whether the firm elected to notify the Attorney General under the published AG process.
Key facts
- Nevada 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; data maintainers must notify the owner or licensee immediately after discovery if the data was, or is reasonably believed to have been, acquired by an unauthorized person; CRA notice applies for 1,000+ persons.
- Nevada does not create a routine Attorney General filing requirement in NRS 603A.220, but the Attorney General has enforcement authority under NRS 603A.290 and states that operators and data collectors may elect to email breach notices to OperatorAGNotices@ag.nv.gov.
Key takeaways
- Nevada 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; data maintainers must notify the owner or licensee immediately after discovery if the data was, or is reasonably believed to have been, acquired by an unauthorized person; CRA notice applies for 1,000+ persons.
- Nevada does not create a routine Attorney General filing requirement in NRS 603A.220, but the Attorney General has enforcement authority under NRS 603A.290 and states that operators and data collectors may elect to email breach notices to OperatorAGNotices@ag.nv.gov.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Nevada 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. Nevada 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.
Nevada law gives the Attorney General enforcement authority, and the Attorney General states that operators and data collectors may elect to provide breach notice to the Office by email.
What is specific to Nevada?
Resident notice in the most expedient time possible and without unreasonable delay, subject to law-enforcement delay and scope/restoration needs; data maintainers must notify the owner or licensee immediately after discovery if the data was, or is reasonably believed to have been, acquired by an unauthorized person; CRA notice applies for 1,000+ persons. 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 Nevada residents.
Nevada residents whose unencrypted personal information was, or is reasonably believed to have been, acquired by an unauthorized person from computerized data owned or licensed by the data collector.
Nevada does not create a routine Attorney General filing requirement in NRS 603A.220, but the Attorney General has enforcement authority under NRS 603A.290 and states that operators and data collectors may elect to email breach notices to OperatorAGNotices@ag.nv.gov.
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 | Nevada 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; data maintainers must notify the owner or licensee immediately after discovery if the data was, or is reasonably believed to have been, acquired by an unauthorized person; CRA notice applies for 1,000+ persons. | Incident clock and counsel review record |
| Regulator path | Nevada does not create a routine Attorney General filing requirement in NRS 603A.220, but the Attorney General has enforcement authority under NRS 603A.290 and states that operators and data collectors may elect to email breach notices to OperatorAGNotices@ag.nv.gov. | Notification decision log |
| State statute | Nev. Rev. Stat. § 603A.220 | 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 Nevada have its own WISP law?
This page does not claim a standalone Nevada WISP statute for every firm. It explains how federal WISP duties should be paired with Nevada breach-notification planning.
Who reviews Nevada breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Nevada 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
- Nevada Revised Statutes Chapter 603A
- Nevada Attorney General notice regarding data breaches
- Nevada Attorney General contact page
Build a Nevada-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire