CA SB 327
California Security of Connected Devices Law (SB 327) — California State Legislature
Also known as: SB 327, California IoT security law, California Connected Devices Law
At a glance
- Current version
- Civil Code 1798.91.04–1798.91.06, as amended by AB 2392 (2022)
- Published 1 January 2023. source
- Status
- In force
- Next deadline
- None announced
- Who must comply
- Manufacturers of connected devices sold or offered for sale in California, meaning devices that can connect to the internet and are assigned an IP or Bluetooth address. source
- How it is assessed
- The manufacturer builds in reasonable security features; a unique password per device or a forced credential change counts, and a NIST conforming label is an alternative route. source
- Authority
- A California statute (Civil Code Title 1.81.26); the Attorney General, city attorneys, county counsel and district attorneys have exclusive authority to enforce it. source
- Enforced by
- Only public prosecutors can enforce it; the title creates no private right of action. source
- Last change
- None recorded yet
California's connected-device security law: a manufacturer selling an internet-connected device in California must equip it with security features appropriate to what the device does and what data it holds. For a device with outside authentication, a unique preprogrammed password or a forced password change before first access, or a conforming labelling scheme, counts as compliance. Only public prosecutors enforce it.
Recent changes
No changes recorded yet — we are watching, and nothing has been published.
Key dates
No upcoming datesAmendments
-
Civil Code 1798.91.04–1798.91.06, as amended by AB 2392 (2022) AmendmentCurrent text
AB 2392 (Stats. 2022, ch. 785) let manufacturers meet the security duty through a NIST conforming IoT labelling scheme and repealed the duplicate Title 1.81.26 added by SB 327. source
More
- The text in force is the one added by AB 1906 (Stats. 2018, ch. 860) and amended by AB 2392; the identical copy added by SB 327 (Stats. 2018, ch. 886) was repealed.
- The labelling route requires meeting the baseline criteria of a NIST conforming scheme, a conformity assessment that includes a third-party test, inspection or certification, and bearing the scheme's binary label.
-
SB 327 and AB 1906 (2018) Major version
Two identical bills, SB 327 (Stats. 2018, ch. 886) and AB 1906 (ch. 860), signed on 28 September 2018, each conditional on the other, required reasonable security features on connected devices from 1 January 2020. source
Who it applies to
Manufacturers of internet-connected devices sold in California, with carve-outs for devices under federal security requirements and for HIPAA- and CMIA-regulated activity.
- Manufacturer
- The person who manufactures, or contracts with another person to manufacture on its behalf, connected devices sold or offered for sale in California; a contract only to purchase, or to purchase and brand, a device does not count. source
- Connected device
- Any device or other physical object that can connect to the internet, directly or indirectly, and is assigned an IP address or Bluetooth address. source
- Excluded
- Devices whose functionality is subject to federal security requirements, and activity regulated by HIPAA or California's Confidentiality of Medical Information Act. source
- Not covered
- No duty for unaffiliated third-party software a user adds, for app stores to review compliance, or to stop users having full control of their device. source
How compliance is assessed
The manufacturer builds in reasonable security features; a unique password per device or a forced credential change counts, and a NIST conforming label is an alternative route.
- Security feature
- Reasonable security features appropriate to the device's nature and function and to the information it handles, designed to protect it from unauthorized access, destruction, use, modification or disclosure. source
- Passwords
- A device with authentication outside a local area network is deemed compliant if its preprogrammed password is unique to each device, or if the user must generate a new means of authentication before first access. source
- Labelling option
- Alternatively, the device meets the baseline criteria of a NIST conforming labelling scheme, passes its conformity assessment including a third-party test, inspection or certification, and bears its binary label. source
Enforcement and penalties
Only public prosecutors can enforce it; the title creates no private right of action.
- Enforcers
- The Attorney General, a city attorney, a county counsel or a district attorney has exclusive authority to enforce the title. source
- Private suits
- The title shall not be construed to provide a basis for a private right of action. source
- Other law
- Its duties are cumulative with duties under other law and do not relieve anyone of them. source
Documents
- Law text Civil Code 1798.91.04 – Security features of connected devices
- Law text Civil Code 1798.91.05 – Definitions
- Law text Civil Code 1798.91.06 – Scope, exclusions and enforcement
- Law text SB 327 (2018), chaptered text
- Law text AB 1906 (2018), chaptered text
Show 1 more document
- Law text AB 2392 (2022), chaptered text
Verified against official sources on 18 October 2026. We monitor the official sources for this framework. Watching since 20 September 2026. Subscribe to CA SB 327 (RSS)