Ratifi English Iniciar sesión
Ratifi

Proyectos federales de Congress.gov. Proyectos estatales de Open States.

SB 692Sesión 2026

Qué cambió entre versiones

327 párrafos cambiaron+473 palabras agregadas−629 eliminadas

El texto resaltado se agregó en la versión más reciente. El texto tachado se eliminó.

Florida Senate

-

2026

CS for SB 692

By

the Committee on Governmental Oversight and Accountability;

and Senator Leek

7-00972-26 2026692__585-02205-26 2026692c1

1 A bill to be entitled

2 An act relating to cybersecurity standards and

3 liability; amending s. 282.3185, F.S.; authorizingprohibiting

4 local governments tofrom onlyimposing adoptcertain specifiedcybersecurity

5 standards or processes on vendors; defining the term

6 “vendor”; prohibiting local governments from adopting

57 or enforcing certain cybersecurity standards; prohibiting the Department ofor

8 processes; creating s. 768.401, F.S.; defining terms;

9 providing that a local government, a covered entity,

10 or a third-party agent that complies with certain

11 requirements is not liable in connection with a

12 cybersecurity incident under certain circumstances;

13 requiring covered entities and third-party agents to

614 Managementimplement Servicesrevised fromframeworks, delegatingstandards, thelaws, authority toor

7 set such standards to local governments; requiring

815 vendorsregulations towithin comply witha specified cybersecuritytimeframe in order to

9 standards unless otherwise required by state or

16 retain protection from liability; providing that a

17 private cause of action is not established; providing

18 that the fact that a specified defendant could have

19 obtained a liability shield or a presumption against

20 liability is not admissible as evidence of negligence,

21 does not constitute negligence per se, and may not be

1022 federalused lawas orevidence regulationof fault; definingspecifying that the term “vendor”;

11 providing for preemption; creating s. 768.401, F.S.;

1223 definingdefendant terms;in providingcertain thatactions has a localcertain government,burden aof

13 covered entity, or a third-party agent that complies

14 with certain requirements is not liable in connection

15 with a cybersecurity incident under certain

16 circumstances; requiring covered entities and third

17 party agents to implement revised frameworks,

18 standards, laws, or regulations within a specified

24 proof; providing applicability; providing a directive

1925 timeframe in order to retainthe protectionDivision fromof Law Revision; providing an

20 liability; providing that a private cause of action is

21 not established; providing that the fact that a

22 specified defendant could have obtained a liability

23 shield or a presumption against liability is not

24 admissible as evidence of negligence, does not

25 constitute negligence per se, and may not be used as

26 evidenceeffective of fault; specifying that the defendant indate.

27 certain actions has a certain burden of proof;

28 providing applicability; providing a directive to the

29 Division of Law Revision; providing an effective date.

30

27

3128 Be It Enacted by the Legislature of the State of Florida:

3229

3330 Section 1. SubsectionParagraph (a) of subsection (4) of section 282.3185, Florida

3431 282.3185, Florida Statutes, is amended to read:

3532 282.3185 Local government cybersecurity.—

3633 (4) CYBERSECURITY STANDARDS.—

3734 (a)

1.

AEach local government may onlyshall adopt cybersecurity

38

standards that are

Each local government shall adopt

39

cybersecurity 35 standards that safeguard its data, information technology, and

40

technology, and 36 information technology resources to ensure availability,

37 confidentiality, and integrity. The cybersecurity standards must

38 be consistent with generally accepted best practices for

39 cybersecurity, including the National Institute of Standards and

40 Technology Cybersecurity Framework.

41

availability, confidentiality, and integrity. The cybersecurity

2. A local government may not impose cybersecurity

42

standards must be

consistent with

the standards and processes

standards or processes on a vendor which exceed the standards or

43

established by the department through the Florida Digital

processes established under this paragraph, except as necessary

44

Service pursuant to s. 282.318

generally accepted best practices

to comply with state or federal laws, or with industry-specific

45

for cybersecurity, including the National Institute of Standards

requirements applicable to regulated sectors. For purposes of

46

and Technology Cybersecurity Framework

.

The department may not

this paragraph, “vendor” means a sole proprietorship,

47

delegate the authority to set cybersecurity standards to a local

partnership, corporation, trust, estate, cooperative,

48

government.

association, or other commercial entity that contracts with a

49

2.

Unless otherwise required by state or federal laws or

local government to provide information technology commodities

50

regulations, a vendor must comply with cybersecurity standards

or services.

51

that are consistent with the standards and processes established

3. A local government may not adopt or enforce any

52

by the National Institute of Standards and Technology (NIST)

cybersecurity standards or processes that are inconsistent with

53

Cybersecurity Framework 2.0. For purposes of this subparagraph,

this paragraph for contracts entered into or amended on or after

54

“vendor” means a sole proprietorship, partnership, corporation,

July 1, 2026.

55 Section 2. Section 768.401, Florida Statutes, is created to

56 read:

5557

trust, estate, cooperative, association, or other commercial

56

entity.

57 (b)

This subsection preempts any prior cybersecurity

58

standards or processes adopted by a local government which are

59

inconsistent with this subsection

Each county with a population

60

of 75,000 or more must adopt the cybersecurity standards

61

required by this subsection by January 1, 2024. Each county with

62

a population of less than 75,000 must adopt the cybersecurity

63

standards required by this subsection by January 1, 2025

.

64

(c)

Each municipality with a population of 25,000 or more

65

must adopt the cybersecurity standards required by this

66

subsection by January 1, 2024. Each municipality with a

67

population of less than 25,000 must adopt the cybersecurity

68

standards required by this subsection by January 1, 2025.

69

(d)

Each local government shall notify the Florida Digital

70

Service of its compliance with this subsection as soon as

71

possible.

72 Section 2. Section 768.401, Florida Statutes, is created to

73 read:

74

768.401

Limitation on liability for cybersecurity

7558

incidents.—

76

59

(1)

As used in this section, the term:

77

60

(a)

“Covered entity” means a sole proprietorship,

78

61

partnership, corporation, trust, estate, cooperative,

79

62

association, or other commercial entity.

80

63

(b)

“Cybersecurity standards or frameworks” means one or

81

64

more of the following:

82

65

1.

The National Institute of Standards and Technology

83

66

(NIST) Cybersecurity Framework 2.0;

84

67

2.

NIST special publication 800-171;

8568

3.

NIST special publications 800-53 and 800-53A;

8669

4.

The Federal Risk and Authorization Management Program

8770

security assessment framework;

88

71

5.

The Center for Internet Security (CIS) Critical Security

89

72

Controls;

90

73

6.

The International Organization for

91

74

Standardization/International Electrotechnical Commission 27000

92

75

series (ISO/IEC 27000) family of standards;

93

76

7.

HITRUST Common Security Framework (CSF);

94

77

8.

Service Organization Control Type 2 Framework (SOC 2);

95

78

9.

Secure Controls Framework; or

9679

10.

Other similar industry frameworks or standards.

97

80

(c)

“Disaster recovery” has the same meaning as in s.

9881

282.0041.

99

82

(d)

“Local government” means a county, a municipality, or

100

83

other political subdivision of this state.

101

84

(e)

“Personal information” has the same meaning as in s.

102

85

501.171.

103

86

(f)

“Third-party agent” means an entity that has been

104

87

contracted to maintain, store, or process personal information

105

88

on behalf of a covered entity.

106

89

(2)

A local government is not liable in connection with a

107

90

cybersecurity incident if the local government has implemented

108

91

one or more policies that substantially comply with

109

92

cybersecurity standards or align with cybersecurity frameworks,

110

93

disaster recovery plans for cybersecurity incidents, and multi

111

94

factor authentication.

112

95

(3)

A covered entity or a third-party agent that acquires,

113

96

maintains, stores, processes, or uses personal information has a

114

97

presumption against liability in a class action resulting from a

115

98

cybersecurity incident if the covered entity or the third-party

116

99

agent has a cybersecurity program that does all of the

117

100

following, as applicable:

118101

(a)

Substantially complies with s. 501.171(3)-(6), as

119

102

applicable.

120103

(b)

Has implemented:

121

104

1.One or more policies that substantially comply with

122

105

cybersecurity standards or align with cybersecurity frameworks,

123

106

a disaster recovery plan for cybersecurity incidents, and multi

124

107

factor authentication; or

125

108

2.

If regulated by the state or Federal Government, or

126

109

both, or if otherwise subject to the requirements of any of the

127

110

following laws and regulations, a cybersecurity program that

128

111

substantially complies with the current version of such laws and

129112

regulations, as applicable:

130113

a.

The Health Insurance Portability and Accountability Act

131114

of 1996 security requirements in 45 C.F.R. part 160 and part 164

132

115

subparts A and C.

133

116

b.

Title V of the Gramm-Leach-Bliley Act of 1999, Pub. L.

134

117

No. 106-102, as amended, and its implementing regulations.

135

118

c.

The Federal Information Security Modernization Act of

136

119

2014, Pub. L. No. 113-283.

137

120

d.

The Health Information Technology for Economic and

138

121

Clinical Health Act requirements in 45 C.F.R. parts 160 and 164.

139

122

e.

The Criminal Justice Information Services (CJIS)

140

123

Security Policy.

141124

f.

Other similar requirements mandated by state or federal

142125

laws or regulations.

143

126

(4)

A covered entity’s or a third-party agent’s

144

127

cybersecurity program’s compliance with paragraph (3)(b) may be

145

128

demonstrated by providing documentation or other evidence of an

146

129

assessment, conducted internally or by a third-party, reflecting

147

130

that the covered entity’s or third-party agent’s cybersecurity

148

131

program has implemented the requirements of that paragraph.

149

132

(5)

A covered entity or a third-party agent must update its

150

133

cybersecurity program to incorporate any revisions of relevant

151

134

frameworks or standards or of applicable state or federal laws

152135

or regulations within 1 year after the latest publication date

153136

stated in any such revisions in order to retain protection from

154

137

liability.

155

138

(6)

This section does not establish a private cause of

156

139

action.

157

140

(7)

If a civil action is filed against a local government,

158

141

a covered entity, or a third-party agent that failed to

159

142

implement a cybersecurity program in compliance with this

160

143

section, the fact that such defendant could have obtained a

161

144

liability shield or presumption against liability upon

162

145

compliance is not admissible as evidence of negligence, does not

163146

constitute negligence per se, and may not be used as evidence of

164147

fault under any other theory of liability.

165

148

(8)

In a civil action relating to a cybersecurity incident,

166

149

if the defendant is a local government covered by subsection (2)

167

150

or a covered entity or third-party agent covered by subsection

168

151

(3), the defendant has the burden of proof to establish

169

152

substantial compliance with this section.

170

153

(9)

This section applies to any putative class action filed

171

154

before, on, or after the effective date of this act.

172155 Section 3.

The Division of Law Revision is directed to

173

156

replace the phrase “the effective date of this act” wherever it

174157

occurs in this act with the date this act becomes a law.

175158 Section 4. This act shall take effect upon becoming a law.

Volver al texto completo