OneClickComply
    Oregon Consumer Information Protection Act (ORS 646A.600 to 646A.628)Supported in OneClickComply

    Meet ORS 646A breach notice and safeguard duties with confidence

    ORS 646A, the Oregon Consumer Information Protection Act, is Oregon's law on protecting personal information and reporting data breaches.

    ORS 646A mapped
    Automated evidence
    Continuous monitoring
    Who needs ORS 646A

    Is ORS 646A right for your organisation?

    It requires covered entities and their vendors to keep reasonable administrative, technical and physical safeguards, and to notify affected Oregon residents within 45 days of discovering a breach. It also covers security freezes on credit reports and limits on displaying Social Security numbers.

    Any person or organisation that owns, licenses, stores, processes or otherwise possesses Oregon residents' personal information in the course of its business, vocation or volunteer work is a covered entity, wherever it is based. Vendors that process that data for a covered entity have their own duties, including notifying the covered entity of a breach within 10 days. It matters most when you hold names alongside identifiers such as Social Security, driver licence, financial account or health insurance numbers, or account login credentials.

    How we help

    How OneClickComply helps with ORS 646A

    ORS 646A is supported in OneClickComply today, so you can build the reasonable safeguards programme that ORS 646A.622 describes from the same controls you use for ISO 27001 or SOC 2. Continuous monitoring, automated evidence collection and AutoComplete policies help you show administrative, technical and physical safeguards, while incident response and vendor risk tools help you prepare for the 45-day and 10-day notice duties.

    Requirements covered

    Fifteen sections, ORS 646A.600 to 646A.628, with breach notification in ORS 646A.604, security freezes in ORS 646A.606 to 646A.618, Social Security number limits in ORS 646A.620 and the security safeguards duty in ORS 646A.622.

    Why automate

    Manual ORS 646A compliance vs OneClickComply

    Doing it manually

    • Working out which records count as personal information under ORS 646A.602 by hand
    • Proving reasonable safeguards with scattered screenshots and spreadsheets
    • Scrambling to draft compliant notices against a 45-day deadline after a breach
    • Chasing vendors for contract terms and security evidence one email at a time
    • Duplicating the same security work separately for Oregon, GLBA, HIPAA and ISO 27001

    With OneClickComply

    • A control library that maps ORS 646A requirements to the systems you already run
    • Evidence collected automatically and kept audit-ready in one place
    • Incident response policies and playbooks prepared before a breach, not after
    • Central vendor risk records with contract and security evidence on file
    • Controls mapped once and reused across every framework they apply to
    Capabilities

    Everything you need for ORS 646A

    • ORS 646A.622 administrative, technical and physical safeguards mapped to your existing controls

    • Automated evidence of patching, access reviews and monitoring from connected tools

    • AutoComplete incident response and data disposal policies built from your environment

    • Vendor risk management to confirm processors can meet the 10-day breach notice duty

    • Continuous monitoring with alerts when security controls drift

    • Ask an Auditor guidance on notice timing, content and risk of harm decisions

    How it works

    Three steps to ORS 646A compliance

    1. Connect and scan

      Connect your cloud, identity and SaaS tools. OneClickComply checks them against ORS 646A and shows which controls pass and which fail.

    2. Fix and generate

      OneClickFix fixes supported misconfigurations automatically, and AutoComplete drafts ORS 646A policies from your real environment.

    3. Monitor and evidence

      Continuous monitoring flags drift as it happens, and our in-house audit team is on hand when you need expert guidance.

    See how far your current setup is from ORS 646A.

    Requirements

    Oregon Consumer Information Protection Act (ORS 646A.600 to 646A.628) requirements

    Every section of ORS 646A.600 to 646A.628, with the breach notification (646A.604) and safeguards (646A.622) sections split into their main subsections.

    ReferenceRequirement
    646A.600Short title: Oregon Consumer Information Protection Act
    646A.602Definitions, including covered entity, vendor, personal information and breach of security
    646A.604(1)Notice of breach to consumers and the Attorney General
    646A.604(2)Vendor notice to covered entities and the Attorney General
    646A.604(3)Timing of notice, pre-notice measures and law enforcement delay
    646A.604(4)Methods of notice and substitute notice
    646A.604(5)Minimum content of breach notices
    646A.604(6)Notice to nationwide consumer reporting agencies
    646A.604(7)Conditions on credit monitoring and identity theft services
    646A.604(8)No-harm determination and five-year documentation
    646A.604(9)Exemptions for federally regulated, GLBA and HIPAA entities
    646A.604(10)Copies of notices to the Attorney General
    646A.604(11)Violations as unlawful practices and affirmative defence
    646A.606Security freeze requests and proof of authority
    646A.608Deadline for placing, lifting and removing a security freeze
    646A.610No fees for security freezes
    646A.612Conditions for lifting or removing a security freeze
    646A.614Effect of a security freeze on use of consumer reports
    646A.616Requests for a consumer report subject to a freeze
    646A.618No changes to frozen consumer reports

    Always check the official text of ORS 646A for the exact wording.

    FAQs

    ORS 646A questions, answered

    Can't find what you need? Our in-house auditors can talk you through ORS 646A on a 30-minute call.

    What is ORS 646A?

    ORS 646A.600 to 646A.628 is the Oregon Consumer Information Protection Act, Oregon's data breach notification and data security law. It requires anyone holding Oregon residents' personal information to maintain reasonable safeguards, notify affected people and, in larger breaches, the Attorney General. It also governs security freezes on credit reports and restricts printing or publicly displaying Social Security numbers. It is separate from the Oregon Consumer Privacy Act, which sits elsewhere in the same chapter.

    Who must comply with the Oregon Consumer Information Protection Act?

    Any covered entity must comply: a person, business, non-profit or public body that owns, licenses, maintains, stores, collects, processes or otherwise possesses Oregon residents' personal information in its business, vocation, occupation or volunteer activities. There is no revenue or headcount threshold. Vendors that process personal information for a covered entity also have duties, including keeping reasonable safeguards and reporting breaches to the covered entity within 10 days.

    How long do you have to report a data breach in Oregon?

    Covered entities must notify affected Oregon residents in the most expeditious manner possible, without unreasonable delay, and no later than 45 days after discovering or being told of the breach. Vendors must tell the covered entity within 10 days. If more than 250 consumers are notified, the Attorney General must also be told, and if more than 1,000 are affected, nationwide consumer reporting agencies must be notified. Delay is allowed only on a written law enforcement request.

    What counts as personal information under ORS 646A?

    Personal information means an Oregon resident's name combined with an unencrypted data element such as a Social Security number, driver licence or state ID number, passport number, financial account or card number with access codes, biometric data, health insurance identifiers, or medical information. A username or similar identifier with the password or other means needed to access the account also counts. Some data elements count on their own if they would enable identity theft.

    What are the penalties for violating ORS 646A?

    A violation of ORS 646A.600 to 646A.628 is an unlawful trade practice under ORS 646.607, which the Oregon Attorney General can enforce. Separately, the Director of the Department of Consumer and Business Services can issue cease and desist orders and impose civil penalties of up to $1,000 per violation, with each day of a continuing violation counted separately and a maximum of $500,000 for any one occurrence.

    What does ORS 646A.622 require for data security?

    ORS 646A.622 requires covered entities and vendors to develop, implement and maintain reasonable safeguards for the security, confidentiality and integrity of personal information, including secure disposal. An organisation is treated as compliant if it follows GLBA or HIPAA security rules where they apply, complies with a stronger law, or runs an information security programme with the administrative, technical and physical safeguards the section lists. Small businesses may scale safeguards to their size and risk.

    How does ORS 646A relate to ISO 27001 and SOC 2?

    ORS 646A does not name ISO 27001 or SOC 2, but the safeguards it lists, such as risk assessment, staff training, vendor selection, access reviews, patching, monitoring and secure disposal, closely match controls in both. An ISO 27001 or SOC 2 programme is therefore a strong basis for showing reasonable safeguards. Neither replaces the breach notification duties, which still need Oregon-specific timing, content and recipients.

    Does OneClickComply support ORS 646A?

    Yes. ORS 646A is supported in OneClickComply today. It links Oregon's safeguard and breach readiness requirements to controls you may already meet for ISO 27001, SOC 2 or GDPR, with automated evidence collection, policy generation and continuous monitoring. OneClickComply does not certify compliance, but its in-house audit team can advise.

    Start working towards ORS 646A

    Automate controls, gather evidence continuously and stay audit-ready, all on one platform.