U.S. California SB-327 — Security of Connected Devices

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting. Framework text may require a separate license unless explicitly provided.
Overview
CaliforniaSB-327, also known as the Security of Connected Devices law, is astate regulation that establishes baseline cybersecurity requirementsfor manufacturers of internet-connected devices sold in California.The law aims to improve consumer protection and data security bymandating reasonable security features in connected products.
Enacted by theCalifornia State Legislature and effective since January 2020, SB-327applies to any manufacturer of devices capable of connecting to theinternet, including smart home technology, IoT devices, and networkedappliances. Its primary focus areas include device authentication,password management, and safeguards against unauthorized access,supporting broader privacy and cybersecurity compliance obligations.
Organizationsimplement SB-327 by integrating secure-by-default configurations,enforcing unique device credentials, and integrating cybersecuritycontrols into product development lifecycles. The regulationcomplements existing data protection laws and guides manufacturers inenhancing compliance programs, conducting risk assessments, anddemonstrating operational security for connected devices.
Why it Matters
CaliforniaSB-327 establishes crucial baseline security requirements forconnected devices, helping organizations better protect user data andsystem integrity.
Key benefitsinclude:
• Support stronger device security oversight
Mandate uniquepreprogrammed passwords or password change at setup, strengtheningoversight of IoT device security practices.
• Strengthen consumer data protection
Prioritizecontrols to limit unauthorized access and exposure of sensitiveconsumer information collected by connected devices.
• Enhance regulatory alignment
Alignorganizational device security practices with evolving state-mandatedexpectations, improving compliance posture in complex regulatoryenvironments.
• Reduce risk of security incidents
Lower thelikelihood of successful attacks and breaches targeting insecuredefault device settings and weak credential management.
• Increase user and stakeholder trust
Demonstrate aproactive commitment to privacy and security, building confidenceamong customers, partners, and regulatory bodies.
How it Works
U.S. CaliforniaSB-327 — Security of Connected Devices sets regulatory requirementsmandating that manufacturers of connected devices incorporatereasonable security features, such as unique preprogrammed passwordsor mechanisms for users to generate new authentication credentials.The framework is anchored in statutory language, outlining coresafeguards that manufacturers must integrate at the device level,with an emphasis on mitigating common vulnerabilities andunauthorized access risks throughout the product lifecycle.
In practice,organizations apply SB-327 by evaluating device securityarchitectures, updating product development processes, and deployingappropriate security controls prior to market release. Complianceactivities typically involve reviewing authentication mechanisms,documenting changes to default credentials, conducting riskassessments, and monitoring fielded devices for ongoing exposure.Manufacturers may also align internal governance programs andincident response processes to ensure conformity with both state lawand broader industry best practices.
With SmartSuite,organizations can operationalize SB-327 compliance by leveragingcontrol libraries mapped to SB-327 requirements, maintainingdevice-specific risk registers, and managing supporting documentationfor regulatory audits. The platform enables teams to centralizepolicy governance, track compliance status, collect evidence ofsecurity controls, and implement remediation workflows to address anyidentified gaps, supporting comprehensive monitoring and auditreadiness.
Key Elements
• Device Security Requirements
Establishesminimum security features for connected devices, includingauthentication capability requirements.
• Reasonable Security Features
Defines criteriafor determining reasonable security measures, considering thedevice’s function and information collected.
• Authentication Mechanism Standards
Specifiesrequirements for unique preprogrammed passwords or user-generatedauthentication credentials.
• Manufacturer Obligations
Describesresponsibilities for manufacturers to ensure device security measuresare adequately incorporated during design.
• Scope and Applicability
Outlines thetypes of devices and use cases covered under the regulation.
• Harm Prevention Provisions
Providesexpectations for measures to protect users from unauthorized access,destruction, use, modification, or disclosure.
Framework Scope
U.S. CaliforniaSB-327 is adopted by manufacturers of connected devices sold oroffered for sale in California. The framework governs IoT devices andembedded systems, with mandatory security features implemented toprotect against unauthorized access, typically in response toregulatory mandates and to support state-level data protection andcompliance obligations.
Framework Objectives
U.S. CaliforniaSB-327 defines security requirements to protect connected devices andenhance cybersecurity risk management.
• Safeguard connected devices through the implementation of robustsecurity controls
• Strengthen cybersecurity governance by establishing clearaccountability for device security
• Ensure compliance with regulatory mandates for data protectionand privacy
• Reduce cybersecurity risk associated with unauthorized deviceaccess and data breaches
• Enhance operational resilience by addressing vulnerabilities inIoT device ecosystems
• Promote audit readiness by maintaining documented securitymeasures and risk management practices California SB-327 sets minimumsecurity requirements for connected devices and is often referencedalongside frameworks such as NIST Cybersecurity Framework, ISO 27001,and NIST SP 800-53 for IoT security. Organizations implement SB-327to meet regulatory compliance, especially manufacturers anddistributors of consumer IoT products targeting California’smarket.
Common Framework Mappings
CaliforniaSB-327 is often mapped to other privacy, IoT, and cybersecurityframeworks to streamline device security requirements, supportmulti-jurisdictional compliance, and demonstrate a defense-in-depthapproach for connected devices.
Mappedframeworks include:
CIS Controls
COPPA
GDPR
ISO/IEC 27001
ISO/IEC 27002
NISTCybersecurity Framework
NIST SP 800-53
PCI DSS
SOC 2
UL 2900
- ClassicifationCategoryCybersecurityDomainCybersecurityFramework FamilyGlobal Privacy Regulations
- Regulatory ContextTypeRegulationLegal InstrumentLawSectorTechnology SectorIndustryCross-Industry
- Region / PublisherRegionNorth AmericaRegion DetailCaliforniaPublisherCalifornia Senate Bill 327 (“Information Privacy: Connected Devices”) is published by the California Legislature, specifically through the official California Legislative Information portal. Therefore, the Publisher is: California Legislature
- VersioningVersion2018Effective DateJanuary 1, 2020Issue DateSeptember 28, 2018
- AdoptionAdoption ModelRegulatory ComplianceImplementation ComplexityModerate
- Official ReferenceOpen Link in New TabSource
License included / downloadable: Yes
California SB-327 is a California state law published by the California Legislature and is publicly available via official government publications.License included with platform
How SmartSuite Supports CA SB-327
Manage IoT security requirements under California SB-327 by organizing device security controls, tracking implementation of “reasonable security features,” and maintaining evidence supporting compliance for connected devices.
IoT Security Requirements Library
Structure SB-327 requirements for unique credentials, authentication, and secure device configuration.
Device Inventory and Lifecycle Tracking
Track connected devices, firmware versions, and lifecycle states across deployment environments.
Secure Configuration and Credential Management
Manage default credential removal, password policies, and secure configuration baselines.
Vulnerability and Patch Management
Track vulnerabilities, remediation actions, and firmware/software update status for devices.
Supplier and Product Security Oversight
Monitor manufacturers, components, and third-party integrations for compliance with security requirements.
Device Security and Regulatory Readiness Reporting
Provide dashboards showing device security posture, gaps, and readiness for regulatory review.
Related frameworks

CIS Controls v8.1 provides prioritized, practical security actions to help organizations mitigate common cyber threats and strengthen defenses.

ISO/IEC 27001:2022 is an international ISMS standard that helps organizations manage information security risks and protect data.

ISO/IEC 27002:2022 provides best-practice information security controls to help organizations select, implement, and manage protections for information assets.

NIST Cybersecurity Framework (CSF) v2.0 is a risk-based framework that helps organizations manage and reduce cybersecurity risks.
Frequently Asked Questions For U.S. California SB-327 (Security of Connected Devices)
California SB-327 establishes security requirements for manufacturers of connected devices sold or offered for sale in California. Its primary goal is to protect consumers from unauthorized access, use, or disclosure of information collected by these devices by mandating reasonable security features.
Yes, compliance with California SB-327 is mandatory for manufacturers of connected devices that are sold or offered for sale in California, regardless of where the manufacturer is located. The law has been enforceable since January 1, 2020.
California SB-327 applies to any manufacturer of a device that is capable of connecting directly or indirectly to the Internet and assigned an IP or Bluetooth address. Devices sold or offered for sale in California, including those via third parties or online retailers, fall within its scope.
Manufacturers must equip devices with “reasonable security features” designed to protect information both during transmission and at rest from unauthorized access or modification. A key requirement is the implementation of unique preprogrammed passwords or a feature that requires users to generate a new means of authentication upon first use.
Manufacturers can implement compliance by conducting threat modeling for connected device risks, ensuring configurable password policies, and performing security testing of device firmware and communication protocols. Documenting processes and maintaining evidence of compliance procedures are critical for audits.
California SB-327 focuses specifically on IoT device security in the consumer context and may overlap with broader frameworks like NIST IoT Cybersecurity Baseline or privacy laws such as the California Consumer Privacy Act (CCPA). Organizations should coordinate SB-327 compliance with general cybersecurity and privacy programs.
Manufacturers must maintain security controls in the design, development, and maintenance of connected devices. Regular reviews and updates to security features, firmware, and device authentication mechanisms are recommended to address emerging threats and evolving compliance expectations.
SmartSuite can help organizations manage California SB-327 compliance by enabling risk tracking of connected device vulnerabilities, managing implementation of required security controls, collecting evidence of compliance activities, and supporting audit readiness through streamlined documentation and reporting on device security status.
Put CRI Profile into action with SmartSuite
Map controls, collect evidence, run assessments, manage remediation, and report readiness - all from a single connected system.

