-
IntroducedNov 15, 2023
-
Passed HouseMar 01, 2024
-
Passed SenateMar 05, 2024
-
Signed into Law
Cybersecurity Incident Liability; Provides county, municipality, other political subdivision of state, 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 adopt revised frameworks, standards, laws, or regulations within specified time period; provides private cause of action is not established; provides certain failures are not evidence of negligence & do not constitute negligence per se; specifies defendant in certain actions has certain burden of proof.
Last Action See all actions
House • Jul 10, 2024: Veto Message received
Latest Bill Text See all bill texts
Official Summary/Bill Text
Comments on HB 473
Tweets
Whip Lists
Sponsors
Votes
YES: 81
- Abbott
- Overdorf
- Altman
- Payne
- Alvarez
- Esposito
- Perez
- Amesty
- Fabricio
- Persons-Mulicka
- Anderson
- Fine
- Plakon
- Andrade
- Plasencia
- Porras
- Garcia
- Baker
- Garrison
- Redondo
- Bankson
- Giallombardo
- Renner
- Gonzalez Pittman
- Rizo
- Gossett-Seidman
- Roach
- Basabe
- Bell
- Grant
- Robinson, W.
- Beltran
- Gregory
- Rommel
- Griffitts
- Roth
- Berfield
- Rudman
- Black
- Borrero
- Shoaf
- Botana
- Holcomb
- Brackett
- Sirois
- Jacques
- Brannan
- Smith
- Buchanan
- Snyder
- Busatta Cabrera
- Killebrew
- Stark
- Koster
- Steele
- Canady
- LaMarca
- Stevenson
- Caruso
- Leek
- Tant
- Temple
- Lopez, V.
- Tomkow
- Chamberlin
- Trabulsy
- Maney
- Tramont
- Chaney
- Massullo
- Truenow
- Clemons
- McClain
- Tuck
- McClure
- Melo
- Michael
- Duggan
- Mooney
- Yarkosky
- Yeager
NO: 28
Actions
- Jul 10, 2024 | House
- Veto Message received
- Jun 26, 2024 | legislature
- Vetoed by Governor
- Jun 17, 2024 | legislature
- Signed by Officers and presented to Governor
- Mar 05, 2024 | House
- In Messages
- Ordered enrolled
- Mar 05, 2024 | Senate
- Withdrawn from Rules
- Placed on Calendar, on 2nd reading
- Substituted for CS/SB 658
- Read 2nd time
- Read 3rd time
- CS passed; YEAS 32 NAYS 8
- Mar 01, 2024 | Senate
- In Messages
- Referred to Rules
- Received
- Mar 01, 2024 | House
- Read 3rd time
- CS passed; YEAS 81, NAYS 28
- Feb 29, 2024 | House
- Read 2nd time
- Placed on 3rd reading
- Added to Third Reading Calendar
- Feb 26, 2024 | House
- Bill added to Special Order Calendar (2/29/2024)
- Feb 22, 2024 | House
- Bill referred to House Calendar
- Added to Second Reading Calendar
- Feb 21, 2024 | House
- Favorable with CS by Judiciary Committee
- Reported out of Judiciary Committee
- Laid on Table under Rule 7.18(a)
- CS Filed
- 1st Reading (Committee Substitute 2)
- Feb 19, 2024 | House
- PCS added to Judiciary Committee agenda
- Feb 06, 2024 | House
- Favorable by State Administration & Technology Appropriations Subcommittee
- Reported out of State Administration & Technology Appropriations Subcommittee
- Now in Judiciary Committee
- Feb 02, 2024 | House
- Added to State Administration & Technology Appropriations Subcommittee agenda
- Jan 25, 2024 | House
- Referred to State Administration & Technology Appropriations Subcommittee
- Referred to Judiciary Committee
- Now in State Administration & Technology Appropriations Subcommittee
- Jan 24, 2024 | House
- Reported out of Commerce Committee
- Laid on Table under Rule 7.18(a)
- CS Filed
- 1st Reading (Committee Substitute 1)
- Jan 23, 2024 | House
- Favorable with CS by Commerce Committee
- Jan 19, 2024 | House
- Added to Commerce Committee agenda
- Jan 09, 2024 | House
- 1st Reading (Original Filed Version)
- Nov 22, 2023 | House
- Referred to Commerce Committee
- Referred to State Administration & Technology Appropriations Subcommittee
- Referred to Judiciary Committee
- Now in Commerce Committee
- Nov 15, 2023 | House
- Filed