l9n/ Oregon

2025 Regular Session

House Bill 3228

Directs the Oregon Cybersecurity Advisory Council to conduct assessments to address the reasons why public bodies in this state are unable to meet cybersecurity insurance coverage requirements.

Did not become law. It stopped in the House of Representatives's Ways and Means Committee on June 27, 2025. The 2025 session has ended.

What it does

The synopsis the Legislative Assembly published with the bill.

<b>Digest: Makes a council assess why public bodies are not able to get cybersecurity insurance. Tells the council to submit a report on its findings. Creates a fund. (Flesch Readability Score: 62.9).</b> [<i>Digest: Makes a council study the use of cybersecurity insurance for public bodies. Tells the council to submit a report on its findings. Creates a fund. (Flesch Readability Score: 63.0).</i>] [<i>Requires the Oregon Cybersecurity Advisory Council to study the use of cybersecurity insurance for public bodies.</i>] <b>Directs the Oregon Cybersecurity Advisory Council to conduct assessments to address the reasons why public bodies in this state are unable to meet cybersecurity insurance coverage requirements.</b> Directs the advisory council to submit findings to the interim committees of the Legislative Assembly related to information management and technology not later than [<i>December 31, 2025</i>] <b>September 30, 2026</b>. Establishes the Oregon Cybersecurity Resilience Fund. Appropriates moneys in the fund to the Higher Education Coordinating Commission for distribution to the Oregon Cybersecurity Center of Excellence to assist public bodies with cybersecurity insurance requirements and cybersecurity <b> vulnerabilities, training and</b> incidents. Declares an emergency, effective on passage.

Sponsors

Who carried the bill in each chamber, and who signed on. Each name leads to the member's page.

In the House of Representatives

In the Senate

Its course

January 13 to June 27, 2025, on one scale. In the top row each mark is a day something happened; taller marks are busier days.

Each committee stop sits inside its chamber.

Every action7 actions on 6 days

In the House of RepresentativesJan 13 to Jun 27 · stopped165 days

Waiting for a committeeJan 13 to Jan 174 days

Information Management and TechnologyJan 17 to Apr 2194 days

Ways and MeansApr 21 to Jun 27 · stopped67 days

Amendments

Each amendment offered, and what became of it.

  • House of Representatives committee amendmentAdopted

    Adopted Apr 21

Text

Each version as the Legislative Assembly printed it.

l9n doesn't hold this bill's text yet.

What happened

In l9n's words, one line for each step. Every action as the Legislative Assembly published it is below.

In the House of Representatives Jan 13 – Jun 27

  1. Jan 13Introduced
  2. Jan 17Sent to Information Management and Technology
  3. Mar 21Heard in Information Management and Technology
  4. Apr 18Heard in Information Management and Technology
  5. Apr 21Information Management and Technology recommended it as amended, and that it go to Ways and Means
  6. Sent to Ways and Means
  7. Jun 27Died when the session ended
All 7 actions, as published
  1. Jan 13First reading. Referred to Speaker's desk.House of Representatives
  2. Jan 17Referred to Information Management and Technology with subsequent referral to Ways and Means.House of Representatives
  3. Mar 21Public Hearing held.House of Representatives
  4. Apr 18Work Session held.House of Representatives
  5. Apr 21Recommendation: Do pass with amendments, be printed A-Engrossed, and be referred to Ways and Means by prior reference.House of Representatives
  6. Apr 21Referred to Ways and Means by prior reference.House of Representatives
  7. Jun 27In committee upon adjournment.House of Representatives