California IoT Security Law: every control, and what you already have

6 controls 3 frameworks share controls with it United States - California verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

If you run	Shared controls
NIST Cybersecurity Framework 2.0	2	measure it →
CCPA/CPRA	1	measure it →
US Consumer Product Safety Commission (CPSC)	1	measure it →

Every control

Code	Control	Also in
`CA-SB327-1798.91.04a`	Reasonable Security Feature Requirement	2
`CA-SB327-1798.91.04b`	Authentication Outside a Local Area Network (Password Safe Harbor)	2
`CA-SB327-1798.91.04c`	NIST Conforming Labeling Scheme (Alternative Compliance)	0
`CA-SB327-1798.91.05`	Scope and Definitions (Connected Device, Manufacturer, Authentication)	0
`CA-SB327-1798.91.06`	Exclusions and Federal Preemption	0
`CA-SB327-1798.91.06e`	Enforcement and No Private Right of Action	0

Tell me when California IoT Security Law files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for California IoT Security Law, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition