Oregon breach notification lookup
Use this Oregon breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for Oregon: statute citation, stated notification deadline, residents or regulators who may need notice, consumer-reporting-agency threshold, consumer-notice trigger, official source links, and the last verified date.
Last verified 2026-08-13. Not legal advice.
| Field | Verified value | Use in the incident file |
|---|---|---|
| Statute | Or. Rev. Stat. § 646A.604 | Link the decision record to the official citation |
| Deadline | 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. | Sort multi-state response work by the shortest stated clock |
| Residents | Oregon consumers whose personal information was subject to a breach of security as defined by the Oregon Consumer Information Protection Act. | Identify whether affected residents receive notice |
| Regulator | 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. | Record AG or regulator portal review |
| Consumer-reporting agencies | The reviewed Oregon notice section focuses on consumer and Attorney General notice; Oregon DOJ reporting guidance does not identify a separate nationwide consumer-reporting-agency filing threshold for general breach notices. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | 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. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
Oregon fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
Or. Rev. Stat. § 646A.604 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
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. The consumer trigger matters because the clock usually starts only after a legally meaningful incident analysis, not merely because an IT alert appeared.
The last verified date for this Oregon lookup is 2026-08-13. Use that date as a prompt to refresh counsel review before making a live notification decision.
How to use it during an incident
Start with containment and evidence preservation, then identify affected resident states and compare the shortest stated deadline first.
A practical incident file should record discovery time, encryption status, systems involved, affected consumer count, vendor involvement, and the person responsible for counsel review.
For Oregon, the WISP should say where the notification decision log lives, who contacts counsel, who checks the regulator portal, and who approves any consumer notice before it is sent.
This lookup pairs with the Incident Response Plan because the plan owns the workflow: intake, escalation, containment, preservation, notice analysis, communications, and final review.
How it fits the WISP
A WISP should not guess at state-law outcomes; it should make the breach-review path fast, documented, and source-linked.
Pair this lookup with the Oregon WISP requirements page so the firm's written program names the state-aware incident path before an event happens.
Policywright keeps the breach clock separate from the policy packet: the lookup tells you what to review, while the generated packet assigns owners, evidence records, remediation steps, and review cadence.
Not legal advice. A qualified lawyer should confirm whether the incident facts meet a statutory definition, whether substitute notice or regulator notice applies, and whether another state or federal rule changes the timeline.
FAQ
Is this Oregon lookup legal advice?
No. It is a source-linked lookup for incident planning and should be reviewed with qualified counsel before relying on it in a live notification decision.
What if affected residents live outside Oregon?
Use the multi-state lookup page and include every state where affected residents may live. The comparison table sorts selected states by the shortest stated deadline first.
Does this replace the FTC Safeguards Rule notice analysis?
No. State notice review is separate from the federal Safeguards Rule and 16 CFR 314.4(j) analysis. A serious incident file should preserve both review tracks.