Meet SB-327 connected device security duties with confidence
SB-327 is California's Internet of Things security law, which requires manufacturers of connected devices to build in reasonable security features suited to the device and the information it handles. Signed in September 2018 alongside the identical AB 1906, it became operative on 1 January 2020 and sits in the California Civil Code at sections 1798.91.04 to 1798.91.06.
Is SB-327 right for your organisation?
SB-327 applies to manufacturers of connected devices sold or offered for sale in California, meaning any device that can connect to the internet and has an IP or Bluetooth address. It covers consumer, commercial and industrial products alike, but excludes devices already subject to federal security requirements. Any hardware or IoT company selling into California should be able to show how its devices meet the law.
It is a legal or regulatory requirement for organisations in scope.
- Issued by
- California State Legislature (SB 327, Statutes of 2018, Chapter 886)
- Operative since
- 1 January 2020
- Codified at
- California Civil Code sections 1798.91.04 to 1798.91.06
- Applies to
- Manufacturers of connected devices sold or offered for sale in California
- Enforced by
- California Attorney General, city attorneys, county counsel and district attorneys
- Private right of action
- None
- Assessment route
- No certification scheme; manufacturers self-assess and document reasonable security
- Type
- Law (mandatory)
- Region
- California, US
- In OneClickComply
- Supported today
OneClickComply makes it simple
SB-327 is mapped in OneClickComply's control library and available on request. We map its reasonable security and default authenticator duties to controls you may already run for ISO 27001 or SOC 2, so product security evidence collected once counts towards each. Our in-house audit team and Ask an Auditor can help you interpret what reasonable security means for your devices.
Requirements covered
Three Civil Code sections in Title 1.81.26: the security feature duty in section 1798.91.04, definitions in section 1798.91.05, and exclusions and enforcement in section 1798.91.06.
Manual SB-327 vs. OneClickComply
- Interpreting a vague reasonable security standard with no official checklist
- Proving every device line ships with unique passwords or forced credential setup
- Tracking product security evidence across engineering, manufacturing and suppliers
- Duplicating work already done for ISO 27001, SOC 2 or other IoT rules
- Answering customer and retailer security questionnaires about device security by hand
- Expert guidance and mapped controls turn reasonable security into concrete, documented actions
- Default authenticator controls tracked with evidence you can show on request
- Evidence collected automatically from connected tools and stored in one place
- One control set mapped across frameworks, so evidence counts towards every standard it applies to
- Security questionnaire automation and a trust centre to share your device security posture
Everything you need for SB-327
SB-327 duties mapped to your existing product and information security controls
Evidence of secure default configurations and authentication settings collected automatically
AutoComplete policies covering secure development and default credential management
Continuous monitoring with alerts when connected tool configurations drift
Vendor risk management for contract manufacturers and component suppliers
Ask an Auditor guidance on what reasonable security means for your devices
Three steps to SB-327 compliance
Connect & scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against SB-327 and shows you exactly where you stand.
Fix & generate
OneClickFix remediates technical gaps in one click, and AutoComplete generates SB-327-aligned policies from your real environment.
Monitor & evidence
Continuous monitoring keeps you compliant, and our in-house audit team is on hand when you need expert guidance.
California SB-327 IoT Security Law requirements
The security duties in Civil Code section 1798.91.04 with their subsections, plus the supporting definitions and exclusions sections.
| Reference | Requirement |
|---|---|
| 1798.91.04(a) | Equip connected devices with reasonable security features |
| 1798.91.04(a)(1) | Security appropriate to the nature and function of the device |
| 1798.91.04(a)(2) | Security appropriate to the information collected, contained or transmitted |
| 1798.91.04(a)(3) | Protection from unauthorised access, destruction, use, modification or disclosure |
| 1798.91.04(b) | Reasonable security for devices with authentication outside a local area network |
| 1798.91.04(b)(1) | Unique preprogrammed password for each device |
| 1798.91.04(b)(2) | User must generate new authentication before first access |
| 1798.91.05 | Definitions |
| 1798.91.06 | Exclusions, limitations and enforcement |
Always check the official SB-327 text for the exact wording.
SB-327 FAQs
What is California SB-327?
SB-327 is California's connected device security law, signed in September 2018 and operative since 1 January 2020. It requires manufacturers to equip internet-connected devices with reasonable security features appropriate to the device's nature and function and the information it handles. It is codified in the California Civil Code at sections 1798.91.04 to 1798.91.06 and was the first US state law aimed specifically at Internet of Things security.
Who must comply with SB-327?
Manufacturers of connected devices sold or offered for sale in California must comply. A connected device is any device or physical object capable of connecting to the internet, directly or indirectly, that has an IP address or Bluetooth address. Manufacturer includes companies that contract others to make devices on their behalf. Devices already subject to federal security requirements are excluded, as are certain activities regulated by health privacy laws.
What does SB-327 require?
SB-327 requires a reasonable security feature or features that are appropriate to the device's nature and function, appropriate to the information it collects, contains or transmits, and designed to protect the device and its information from unauthorised access, destruction, use, modification or disclosure. If a device can be authenticated from outside a local area network, the security is deemed reasonable if it has a unique preprogrammed password or makes the user set new credentials before first access.
Does SB-327 ban default passwords?
In effect, yes, for devices that can be authenticated from outside a local area network. Such devices are deemed to have reasonable security if each one ships with a unique preprogrammed password, or if the user must generate a new means of authentication before access is granted for the first time. Shared factory default credentials such as admin and password across every unit do not meet either option.
What are the penalties for breaching SB-327?
SB-327 does not set its own penalty amounts and creates no private right of action. Enforcement rests exclusively with the California Attorney General, city attorneys, county counsel and district attorneys. Manufacturers with weak device security may also face action under other consumer protection laws, so documented, reasonable security is the safest position.
How does SB-327 relate to ISO 27001 and SOC 2?
SB-327 is a product security law, while ISO 27001 and SOC 2 cover an organisation's information security management and controls. They overlap where secure development, configuration management and authentication controls apply to the devices you build. Mapping SB-327 to your existing ISO 27001 or SOC 2 controls lets you reuse evidence, but neither certification on its own proves your devices meet the law.
Does SB-327 apply to third-party software or app stores?
No. The law does not impose duties on manufacturers for unaffiliated third-party software or applications that a user chooses to add to a device. It also places no duty on app store or software marketplace providers to review or enforce compliance, and does not require manufacturers to stop users from having full control over their own devices, including modifying software or firmware.
Does OneClickComply support SB-327?
SB-327 is mapped in OneClickComply's control library and available on request. We map its security feature and default authenticator duties to controls you may already operate for ISO 27001 or SOC 2, collect supporting evidence from connected tools and provide expert guidance from our in-house audit team. OneClickComply does not certify devices or guarantee compliance, but helps you document reasonable security.
Related standards
All standards- California Consumer Privacy Act (CCPA)Law · US
- California Data Breach Notification Law (SB 1386)Law · US
- Nevada Consumer Health Data and Data Security Law (NRS 603A)Law · US
- Oregon Consumer Information Protection Act (ORS 646A.600 to 646A.628)Law · US
- Texas Data Privacy and Security ActLaw · US
- NAIC Insurance Data Security Model Law (MDL-668)Law · US
- Tennessee Information Protection ActLaw · US
- Oregon Consumer Privacy ActLaw · US
Get SB-327 ready, not stressed
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.