California IoT Security Law
California IoT security law (SB-327)
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (20)
Authentication
| Code | Title |
|---|---|
| CA-IOT-PASS | Unique Preprogrammed Password or First-Use Authentication |
| CA-IOT-WAN | Authentication Outside the Local Area Network |
California IoT Security Law: Access Control
Logical and physical access controls (California IoT Security Law)
| Code | Title |
|---|---|
| CA-IOT-11 | Access control policy and enforcement |
| CA-IOT-12 | User access management and provisioning |
| CA-IOT-13 | Authentication and password management |
| CA-IOT-14 | Privileged access management |
| CA-IOT-15 | Access review and recertification |
California IoT Security Law: Asset Management
Information asset management (California IoT Security Law)
| Code | Title |
|---|---|
| CA-IOT-06 | Asset inventory and ownership |
| CA-IOT-07 | Acceptable use of assets |
| CA-IOT-08 | Information classification and labeling |
| CA-IOT-09 | Asset handling procedures |
| CA-IOT-10 | Media management and disposal |
California IoT Security Law: Communications Security
Network and communications security (California IoT Security Law)
| Code | Title |
|---|---|
| CA-IOT-27 | Network security management |
| CA-IOT-28 | Network service security |
| CA-IOT-29 | Segregation in networks |
| CA-IOT-30 | Information transfer policies |
| CA-IOT-31 | Secure messaging |
California IoT Security Law: Cryptography
Cryptographic controls (California IoT Security Law)
| Code | Title |
|---|---|
| CA-IOT-16 | Cryptographic policy and key management |
| CA-IOT-17 | Encryption of data at rest |
| CA-IOT-18 | Encryption of data in transit |
| CA-IOT-19 | Certificate management |
| CA-IOT-20 | Key lifecycle management |
California IoT Security Law: Information Security Policies
Organizational information security policies (California IoT Security Law)
| Code | Title |
|---|---|
| CA-IOT-01 | Information security policy framework |
| CA-IOT-02 | Management direction and commitment |
| CA-IOT-03 | Policy review and update procedures |
| CA-IOT-04 | Roles and responsibilities definition |
| CA-IOT-05 | Contact with authorities and special interest groups |
California IoT Security Law: Operations Security
Secure operations and monitoring (California IoT Security Law)
| Code | Title |
|---|---|
| CA-IOT-21 | Operational procedures and responsibilities |
| CA-IOT-22 | Protection from malware |
| CA-IOT-23 | Backup and recovery procedures |
| CA-IOT-24 | Logging and monitoring |
| CA-IOT-25 | Technical vulnerability management |
| CA-IOT-26 | Audit considerations |
Data Protection
| Code | Title |
|---|---|
| CA-IOT-DATAPROT | Protection of Collected and Transmitted Data |
Enforcement
| Code | Title |
|---|---|
| CA-IOT-ENFORCE | Enforcement by California Authorities |
Governance
| Code | Title |
|---|---|
| CA-IOT-DOC | Documentation of Reasonable Security |
| CA-IOT-INTERNAL | Internal Manufacturer Governance |
Identity
| Code | Title |
|---|---|
| CA-IOT-IDENT | Unique Device Identification and Provisioning Records |
Lifecycle
| Code | Title |
|---|---|
| CA-IOT-RESALE | Resale and Refurbishment Controls |
Patch Management
| Code | Title |
|---|---|
| CA-IOT-UPDATE | Security Update Capability |
Privacy
| Code | Title |
|---|---|
| CA-IOT-PRIV | Privacy Alignment with CCPA and CPRA |
Scope
| Code | Title |
|---|---|
| CA-IOT-EXCL | Exclusions and Federal Preemption |
| CA-IOT-SCOPE | Connected Device Scope Determination |
Security
| Code | Title |
|---|---|
| CA-IOT-LOGIC | Secure Logical Interfaces |
| CA-IOT-MIN | Minimisation of Attack Surface |
| CA-IOT-PHYS | Physical Tamper and Boot Security |
| CA-IOT-REAS | Reasonable Security Features Requirement |
Supply Chain
| Code | Title |
|---|---|
| CA-IOT-SUPPLY | Component and Supply Chain Security |
Testing
| Code | Title |
|---|---|
| CA-IOT-TESTING | Pre-Release Security Testing |
Transparency
| Code | Title |
|---|---|
| CA-IOT-USERINF | User-Facing Security Information |
Vulnerability Management
| Code | Title |
|---|---|
| CA-IOT-VULN | Vulnerability Disclosure and Response |
Your Compliance Coverage
If you comply with California IoT Security Law, you already cover:
OWASP ASVS
33%
17 controls mapped
Compare →BSIMM
33%
17 controls mapped
Compare →3GPP Security
33%
17 controls mapped
Compare →+ 607 more: NIST SP 800-218 (33%), PTES (33%)
See all 610 mapped frameworks ↓Maps to 610 other frameworks
Frequently Asked Questions
What is California IoT Security Law?
California IoT Security Law is a compliance framework from United States - California with 20 domains and 51 controls. California IoT security law (SB-327) It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does California IoT Security Law have?
California IoT Security Law has 51 controls organised across 20 domains. The largest domains are California IoT Security Law: Operations Security (6 controls), California IoT Security Law: Access Control (5 controls), California IoT Security Law: Asset Management (5 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does California IoT Security Law map to?
California IoT Security Law maps to 610 other compliance frameworks. The top mapping partners are OWASP ASVS (33% coverage), BSIMM (33% coverage), 3GPP Security (33% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with California IoT Security Law compliance?
Start your California IoT Security Law compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about California IoT Security Law requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 51 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 701 frameworks.
Get Started Free →Free forever — no credit card required