WISP requirements in Oregon
Oregon turns vendor management into a core part of breach response because a vendor has a 10-day duty to notify the covered entity, and the covered entity has a 45-day outer clock for consumer and DOJ notice. An Oregon incident file should preserve the vendor notice date, scope/restoration steps, consumer count, sample consumer notice, Attorney General submission for more than 250 consumers, and any written law-enforcement delay.
Key facts
- Oregon firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Covered-entity consumer and Attorney General notice no later than 45 days after discovering or receiving notification of the breach; vendors must notify the covered entity as soon as practicable and no later than 10 days after discovery or reason to believe a breach occurred.
- Notify the Oregon Attorney General in writing or electronically if notice must be sent to more than 250 consumers; Oregon DOJ says breach reports and sample consumer notices can be submitted through its data breach notice form or by email to databreach@doj.oregon.gov.
Key takeaways
- Oregon firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Covered-entity consumer and Attorney General notice no later than 45 days after discovering or receiving notification of the breach; vendors must notify the covered entity as soon as practicable and no later than 10 days after discovery or reason to believe a breach occurred.
- Notify the Oregon Attorney General in writing or electronically if notice must be sent to more than 250 consumers; Oregon DOJ says breach reports and sample consumer notices can be submitted through its data breach notice form or by email to databreach@doj.oregon.gov.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do Oregon 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. Oregon 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.
Oregon requires Attorney General notice, in writing or electronically, when the covered entity must notify more than 250 consumers; vendors also have a 10-day covered-entity notice duty and may have their own Attorney General notice duty for 250+ consumers or an unknown consumer count.
What is specific to Oregon?
Covered-entity consumer and Attorney General notice no later than 45 days after discovering or receiving notification of the breach; vendors must notify the covered entity as soon as practicable and no later than 10 days after discovery or reason to believe a breach occurred. 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 Oregon residents.
Oregon consumers whose personal information was subject to a breach of security as defined by the Oregon Consumer Information Protection Act.
Notify the Oregon Attorney General in writing or electronically if notice must be sent to more than 250 consumers; Oregon DOJ says breach reports and sample consumer notices can be submitted through its data breach notice form or by email to databreach@doj.oregon.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 | Oregon 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 | Covered-entity consumer and Attorney General notice no later than 45 days after discovering or receiving notification of the breach; vendors must notify the covered entity as soon as practicable and no later than 10 days after discovery or reason to believe a breach occurred. | Incident clock and counsel review record |
| Regulator path | Notify the Oregon Attorney General in writing or electronically if notice must be sent to more than 250 consumers; Oregon DOJ says breach reports and sample consumer notices can be submitted through its data breach notice form or by email to databreach@doj.oregon.gov. | Notification decision log |
| State statute | Or. Rev. Stat. § 646A.604 | 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 Oregon have its own WISP law?
This page does not claim a standalone Oregon WISP statute for every firm. It explains how federal WISP duties should be paired with Oregon breach-notification planning.
Who reviews Oregon breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any Oregon Department of Justice 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
- Oregon Revised Statutes § 646A.604
- Oregon DOJ data breaches guidance
- Oregon DOJ consumer privacy resources
Build a Oregon-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire