browse Browse

pac.dog pac.dog / Bills

HB 4055Requires 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.

Congress · introduced 2026-01-16

Digest: Tells a local public body to give a report to the state when there is an information security incident. Prescribes what must be in the report. (Flesch Readability Score: 63.4). 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.

Latest action: In House Committee

Sponsors

No sponsorships on file.

Action timeline

  1. · state_lower First reading. Referred to Speaker's desk.
  2. · state_lower Referred to Information Management and Technology with subsequent referral to Ways and Means.
  3. · state_lower Public Hearing held.
  4. · state_lower In committee upon adjournment.

Text versions

No text versions on file yet — same ingest as the action timeline populates these. Each version has direct links to the XML / HTML / PDF at govinfo.gov.

Predicted vote

Aggregated from: actual roll-call votes (when present) → sponsor → cosponsor → party median (predicts YES when ≥25% of the caucus sponsored/cosponsored). Each row labels its confidence tier so you can see why a position was predicted.

0 predicted yes (0%) · 543 predicted no (100%) · 0 unknown (0%)

By party: · R: 0 yes / 277 no · D: 0 yes / 263 no · I: 0 yes / 3 no

pac.dog is a free, independent, non-partisan research tool. Every candidate, committee, bill, vote, member, and nonprofit on this site is mirrored from primary U.S. government sources (FEC, congress.gov, govinfo.gov, IRS) and each state's Secretary of State / election commission — no third-party data vendors, no paywall, no editorial intermediation. Citations to the originating source are on every detail page.