Bill Commons

FL HB 635

dead

Cybersecurity Standards and Liability

Florida · 2026 Regular Session · lower

Quick answers

Did FL HB 635 pass?

No. FL HB 635 did not pass — it was defeated or died in the legislative process (2026-03-13). Latest recorded action (2026-03-13): Died in State Affairs Committee

What is FL HB 635 about?

Cybersecurity Standards and Liability; Prohibits local governments from imposing certain cybersecurity standards or processes on vendors; defines "vendor"; prohibits local governments from adopting or enforcing certain cybersecurity standards or processes; provides that local government, covered entity, or third-party agent that complies with certain requirements is not liable in connection with cybersecurity incident; requires covered entities & third-party agents to implement revised frameworks, standards, laws, or regulations.

Who sponsors FL HB 635?

Blanco, Giallombardo, Information Technology Budget & Policy Subcommittee are the primary sponsors of FL HB 635.

Description

Cybersecurity Standards and Liability; Prohibits local governments from imposing certain cybersecurity standards or processes on vendors; defines "vendor"; prohibits local governments from adopting or enforcing certain cybersecurity standards or processes; provides that local government, covered entity, or third-party agent that complies with certain requirements is not liable in connection with cybersecurity incident; requires covered entities & third-party agents to implement revised frameworks, standards, laws, or regulations.

Introduced
Latest action
2026-03-13 — Died in State Affairs Committee
Bill type
bill
Last updated

Subjects

Sponsors

  • Blancoprimary
  • Giallombardoprimary
  • Information Technology Budget & Policy Subcommitteeprimary

Committees

Not provided by source.

Action timeline

  1. 2025-12-03

    Filed

    filing

  2. 2025-12-12

    Referred to Information Technology Budget & Policy Subcommittee

    referral-committee

  3. 2025-12-12

    Referred to Civil Justice & Claims Subcommittee

    referral-committee

  4. 2025-12-12

    Referred to State Affairs Committee

    referral-committee

  5. 2025-12-12

    Now in Information Technology Budget & Policy Subcommittee

  6. 2026-01-13

    1st Reading (Original Filed Version)

    filing,reading-1

  7. 2026-01-15

    Added to Information Technology Budget & Policy Subcommittee agenda

  8. 2026-01-20

    Favorable with CS by Information Technology Budget & Policy Subcommittee

    committee-passage-favorable

  9. 2026-01-21

    Reported out of Information Technology Budget & Policy Subcommittee

  10. 2026-01-21

    Laid on Table under Rule 7.18(a)

    deferral

  11. 2026-01-21

    CS Filed

    filing

  12. 2026-01-22

    Referred to Civil Justice & Claims Subcommittee

    referral-committee

  13. 2026-01-22

    Referred to State Affairs Committee

    referral-committee

  14. 2026-01-22

    Now in Civil Justice & Claims Subcommittee

  15. 2026-01-22

    1st Reading (Committee Substitute 1)

    reading-1

  16. 2026-01-30

    Added to Civil Justice & Claims Subcommittee agenda

  17. 2026-02-03

    Favorable by Civil Justice & Claims Subcommittee

    committee-passage-favorable

  18. 2026-02-03

    Reported out of Civil Justice & Claims Subcommittee

  19. 2026-02-03

    Now in State Affairs Committee

  20. 2026-03-13

    Died in State Affairs Committee

    failure

Versions

Documents

Votes

  • Favorable With Committee Substitute (Information Technology Budget & Policy Subcommittee)

    2026-01-20 · pass · 16-0

  • Favorable (Civil Justice & Claims Subcommittee)

    2026-02-03 · pass · 14-1

Related bills

No related bills recorded for this bill.

Official source

Attribution

Data from openstates_bulk_csv, retrieved 2026-07-24T05:19:20.677932Z

Inspect retained evidence for changes recorded after evidence tracking began:

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=FL&identifier=HB 635. 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.