OR HB 4055
died on adjournmentRelating to information security; declaring an emergency.
Oregon · 2026 Regular Session · lower
Subscribe in a feed reader. The feed covers recorded actions from the last 30 days; Bill Commons may record an action after it happened at the legislature.
Quick answers
Did OR HB 4055 pass?
No. OR HB 4055 died when the 2026 Regular Session adjourned without final action on it. Bills that die this way are sometimes reintroduced in a later session. Latest recorded action (2026-03-07): In committee upon adjournment.
What is OR HB 4055 about?
Requires a local government, local service district or special government body to notify and submit a report to the State Chief Information Officer within 48 hours of an information security incident or ransomware incident. Prescribes the information that a public body is required to report. Directs the State Chief Information Officer to establish a reporting system that allows a public body to submit a notification or report in a timely, secure and confidential manner. Directs the State Chief Information Officer to create a webpage to provide instructions on how to provide notification and submit a report. Requires the State Chief Information Officer to provide an annual report to the Governor and the Joint Legislative Committee on Information Management and Technology on the information security incidents and ransomware incidents reported for the preceding year. Exempts information security incident or ransomware incident reports from disclosure under public records laws and allows for the sharing of information under certain circumstances. Becomes operative July 1, 2026. Declares an emergency, effective on passage.
Description
Requires a local government, local service district or special government body to notify and submit a report to the State Chief Information Officer within 48 hours of an information security incident or ransomware incident. Prescribes the information that a public body is required to report. Directs the State Chief Information Officer to establish a reporting system that allows a public body to submit a notification or report in a timely, secure and confidential manner. Directs the State Chief Information Officer to create a webpage to provide instructions on how to provide notification and submit a report. Requires the State Chief Information Officer to provide an annual report to the Governor and the Joint Legislative Committee on Information Management and Technology on the information security incidents and ransomware incidents reported for the preceding year. Exempts information security incident or ransomware incident reports from disclosure under public records laws and allows for the sharing of information under certain circumstances. Becomes operative July 1, 2026. Declares an emergency, effective on passage.
- Introduced
- 2026-02-02
- Latest action
- 2026-03-07 — In committee upon adjournment.
- Bill type
- bill
- Last updated
- —
Sponsors
Not provided by source.
Committees
Not provided by source.
Action timeline
Newest first
2026-03-07
In committee upon adjournment.
2026-02-06
Public Hearing held.
2026-02-02
Referred to Information Management and Technology with subsequent referral to Ways and Means.
referral-committee
2026-02-02
First reading. Referred to Speaker's desk.
introduction,reading-1,referral-committee
Versions
Documents
Votes
Not provided by source.
Related bills
No related bills recorded for this bill.
Official source
Attribution
Data from openstates_bulk_csv, retrieved 2026-07-24T05:31:04.409453Z
Inspect retained evidence for changes recorded after evidence tracking began:
Session-wide evidence can include changes to other bills:
Use this data
Every field on this page is available from the free public API — no key or licence required. Fetch this bill as JSON: GET /api/v1/bills?jurisdiction=OR&identifier=HB 4055. See the API docs or the MCP server for AI assistants.
Known limitations
- Sponsor party and chamber affiliation are not yet captured by this API.
- Committee referrals are not yet captured.
See the methodology page for data sources and limitations.