CCPA § 7123(c)(14) at a Glance
- Regulation: California Consumer Privacy Act (CCPA) regulations, California Code of Regulations, Title 11, Division 6, Chapter 1, Article 9 (Cybersecurity Audits).
- Section: 11 CCR § 7123(c)(14) Secure Development and Coding Best Practices, one of the 18 components in § 7123(c) Scope of Cybersecurity Audit and Audit Report.
- Status: New. Added by the CCPA Updates, Cybersecurity Audits, Risk Assessments, ADMT and Insurance regulations, effective January 1, 2026.
- Who it applies to: Businesses whose processing of consumers' personal information presents significant risk to consumers' security under § 7120(b).
- When it is assessed: If applicable. The auditor decides which § 7123(c) components apply to the business's information system (§ 7123(b)(2)), and the report must identify them (§ 7123(e)(2)).
- Deadlines: First cybersecurity audit report due April 1, 2028, April 1, 2029 or April 1, 2030 depending on annual gross revenue (§ 7121). Certification of completion due by April 1 after each audit year (§ 7124).
Component (14) applies to businesses that develop or customize software, including websites, mobile apps and internal applications that process personal information. The regulation names code reviews and testing as part of the practices assessed.
The SCF maps more controls to this component than to almost any other in Article 9, which reflects how much secure development spans: requirements, design, coding standards, testing, third-party components and release.
What Does CCPA § 7123(c)(14) Say?
The following is the text of 11 CCR § 7123(c)(14), shown with the § 7123(c) lead-in, from the final regulation text published by CalPrivacy and effective January 1, 2026. Only the formatting has been adjusted for readability.
- (c) The cybersecurity audit must assess the following components, if applicable:
- (14) Secure development and coding best practices, including code-reviews and testing.
Source: CalPrivacy, CCPA Updates, Cybersecurity Audits, Risk Assessments, ADMT and Insurance Regulations (final regulation text). Authority cited: Section 1798.185, Civil Code. Reference: Section 1798.185, Civil Code.
How Does CCPA § 7123(c)(14) Map to the Secure Controls Framework (SCF)?
The SCF publishes a NIST IR 8477 Set Theory Relationship Mapping (STRM) between the CCPA as amended by the CPRA (statute and regulations as of January 2026) and SCF version 2026.3. It maps CCPA § 7123(c)(14) to 34 SCF controls through 34 relationships (1 "subset of", 33 "intersects with").
How to read the mapping: each relationship runs from the CCPA text to the SCF control. "Subset of" means the CCPA requirement is fully contained within the SCF control. "Intersects with" means the CCPA requirement and the SCF control share partial overlap. The strength of relationship runs from 1 (nominal) to 10 (strongest), where 5 is moderately strong and 10 is typically reserved for "equal" and "subset of" relationships.
- TDA-02 Technology Development & Acquisition. Subset of (strength 10): 7123(c)(14). SCF control: Mechanisms exist to facilitate the implementation of tailored development and acquisition strategies, contract tools and procurement methods to meet unique business needs.
- TDA-17 Security, Compliance & Resilience Testing Throughout Development. Intersects with (strength 8): 7123(c)(14). SCF control: Mechanisms exist to require system developers/integrators consult with security, compliance and/or resilience personnel to: (1) Create and implement a Security Testing and Evaluation (ST&E) plan, or similar capability; (2) Implement a verifiable flaw remediation process to correct weaknesses and deficiencies identified during the control testing and evaluation process; and (3) Document the results.
- TDA-03 Development Methods, Techniques & Processes. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to require software developers to ensure that their software development processes employ industry-recognized secure practices for secure programming, engineering methods, quality control processes and validation techniques to minimize flawed and/or malformed software.
- TDA-05 Secure Software Development Practices (SSDP). Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to develop applications based on Secure Software Development Practices (SSDP).
- TDA-05.1 Criticality Analysis During Development. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to require the developer of the Technology Asset, Application and/or Service (TAAS) to perform a criticality analysis at organization-defined decision points in the Secure Development Life Cycle (SDLC).
- TDA-05.2 Threat Modeling. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to perform threat modelling and other secure design techniques, to ensure that threats to software and solutions are identified and accounted for.
- TDA-05.4 Software Design Review. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to have an independent review of the software design to validate: (1) Applicable security, compliance and resilience requirements are met; and (2) Identified risks are remediated.
- TDA-06 Product Management. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to design and implement product management processes to proactively govern the design, development and production of Technology Assets, Applications and/or Services (TAAS) across the System Development Life Cycle (SDLC) to: (1) Improve functionality; (2) Enhance security and resiliency capabilities; (3) Correct security deficiencies; and (4) Conform with applicable statutory, regulatory and/or contractual obligations.
- TDA-06.1 Product Conformity Governance. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to ensure developed Technology Assets, Applications and/or Services (TAAS) conform to applicable statutory and regulatory requirements, based on the product's and/or service's: (1) Use case(s); and (2) Geographic markets.
- TDA-06.3 Ongoing Product Security Support. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to deliver security updates to Technology Assets, Applications and/or Services (TAAS), where applicable, through: (1) Automatic updates; and (2) Notification of available updates to affected users.
- TDA-07 Disclosure of Vulnerabilities. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to disclose information about vulnerabilities to relevant stakeholders, including: (1) A description of the vulnerability(ies); (2) Affected product(s) and/or service(s); (3) Potential impact of the vulnerability(ies); (4) Severity of the vulnerability(ies); and (5) Guidance to remediate the vulnerability(ies).
- TDA-07.1 Reporting Exploitable Vulnerabilities. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to notify applicable stakeholders about potentially exploitable vulnerabilities in organization-developed Technology Assets, Applications and/or Services (TAAS), as required by statutory, regulatory and/or contractual obligations.
- TDA-08 Technical Documentation Artifacts. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to generate appropriate technical documentation artifacts for Technology Assets, Applications and/or Services (TAAS) in sufficient detail to demonstrate conformity with applicable statutory, regulatory and contractual compliance requirements.
- TDA-11 DevSecOps. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to integrate security, compliance and resilience into Development, Security and Operations (DevSecOps) to prioritize secure practices throughout the Software Development Lifecycle (SDLC).
- TDA-11.1 Minimum Viable Product (MVP) Security Requirements. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to design, develop and produce Technology Assets, Applications and/or Services (TAAS) in such a way that risk-based technical and functional specifications ensure Minimum Viable Product (MVP) criteria establish an appropriate level of security and resiliency based on applicable risks and threats.
- TDA-11.2 Insecure Ports, Protocols & Services. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to mitigate the risk associated with the use of insecure ports, protocols and services necessary to operate technology solutions.
- TDA-13 Minimizing Attack Surfaces. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to minimize the attack surface of Technology Assets, Applications and/or Services (TAAS) by reasonably mitigating known exploitable vulnerabilities.
- TDA-13.1 Pre-Established Secure Configurations. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to ensure vendors / manufacturers: (1) Deliver the Technology Asset, Application and/or Service (TAAS) with a pre-established, secure configuration implemented; and (2) Use the pre-established, secure configuration as the default for any subsequent TAAS reinstallation or upgrade.
- TDA-13.2 Malware Testing Prior to Release. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to utilize at least one(1) malware detection tool to identify if any known malware exists in the final binaries of the product or security update.
- TDA-14 Product Testing & Reviews. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to regularly review Technology Assets, Applications and/or Services (TAAS) for an appropriate level of security and resiliency based on applicable risks and threats.
- TDA-14.1 Security, Compliance & Resilience Representatives For Product Changes. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to include appropriate security, compliance and resilience representatives in the product feature and/or functionality change control review process.
- TDA-15 Secure Development Environments. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to maintain a segmented development network to ensure a secure development environment.
- TDA-15.2 Secure Migration Practices. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to ensure secure migration practices purge Technology Assets, Applications and/or Services (TAAS) of test/development/staging data and accounts before it is migrated into a production environment.
- TDA-16.1 Access to Program Source Code. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to limit privileges to change software resident within software libraries.
- TDA-16.2 Approved Code. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to govern the approval of binaries and code for production use.
- TDA-18 Use of Live Data. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to approve, document and control the use of live data in development and test environments.
- TDA-20 Developer Configuration Management. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to require system developers and integrators to perform configuration management during system design, development, implementation and operation.
- TDA-20.1 Developer Threat Analysis & Flaw Remediation. Intersects with (strength 5): 7123(c)(14). SCF control: Mechanisms exist to require system developers and integrators to develop and implement an ongoing Security Testing and Evaluation (ST&E) plan, or similar process, to objectively identify and remediate vulnerabilities prior to release to production.
- TDA-03.1 Software Assurance Maturity Model (SAMM). Intersects with (strength 3): 7123(c)(14). SCF control: Mechanisms exist to utilize a Software Assurance Maturity Model (SAMM) to govern a secure development lifecycle for the development of Technology Assets, Applications and/or Services (TAAS).
- TDA-03.2 Secure Settings By Default. Intersects with (strength 3): 7123(c)(14). SCF control: Mechanisms exist to implement secure configuration settings by default to reduce the likelihood of Technology Assets, Applications and/or Services (TAAS) being deployed with weak security settings that would put the TAAS at a greater risk of compromise.
- TDA-04 Developer Architecture & Design. Intersects with (strength 3): 7123(c)(14). SCF control: Mechanisms exist to require the developers of Technology Assets, Applications and/or Services (TAAS) to produce a design specification and security architecture that: (1) Is consistent with and supportive of the organization's security architecture which is established within and is an integrated part of the organization's enterprise architecture; (2) Accurately and completely describes the required security functionality and the allocation of security, compliance and resilience controls among physical and logical components; and (3) Expresses how individual security functions, mechanisms and services work together to provide required security capabilities and a unified approach to protection.
- TDA-05.3 Supporting Toolchain. Intersects with (strength 3): 7123(c)(14). SCF control: Automated mechanisms exist to improve the accuracy, consistency and comprehensiveness of secure practices throughout the asset's lifecycle.
- TDA-05.5 Software Design Root Cause Analysis (RCA). Intersects with (strength 3): 7123(c)(14). SCF control: Mechanisms exist to assess software design processes that includes: (1) Conducting Root Cause Analysis (RCA) to identify the underlying causes of issues or failures; (2) Developing actions to address the root cause of the issue or failure; and (3) Implementing the actions and monitoring the implementation for effectiveness.
- TDA-15.1 Separation of Development, Testing and Operational Environments. Intersects with (strength 3): 7123(c)(14). SCF control: Mechanisms exist to manage separate development, testing and operational environments to reduce the risks of unauthorized access or changes to the operational environment and to ensure no impact to production Technology Assets, Applications and/or Services (TAAS).
Mapping taken from the STRM published with SCF version 2026.3. Download it at no cost: SCF STRM for the CCPA and CPRA (2026). The SCF explains the method in its Set Theory Relationship Mapping (STRM) guidance.
Common Pitfalls With CCPA § 7123(c)(14)
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- Code reviews without a security focus. Peer reviews that check only functionality can miss security flaws.
- Functional testing only. Security testing such as static and dynamic analysis is part of what testing can cover.
- Third-party components ignored. Open source and vendor libraries can introduce vulnerabilities into applications that process personal information.
- No evidence trail. Reviews and tests that leave no records are hard for an auditor to assess.
What Is Reasonable Evidence for CCPA § 7123(c)(14)?
Article 9 does not publish a fixed evidence list. Under § 7122(d), audit findings must rely primarily on specific evidence such as documents reviewed, sampling and testing, and interviews, and under § 7122(g) the business and the auditor must keep all documents relevant to each audit for at least five years.
The SCF Evidence Request List (ERL) ties evidence artifacts to SCF controls. ERL items linked to the SCF controls mapped to CCPA § 7123(c)(14) include:
- E-TDA-01 Secure Software Development Principles (SSDP). Documented evidence of a Secure Software Development Principles (SSDP). This is program-level documentation in the form of a runbook, playbook or a similar format provides guidance on organizational practices that support existing policies and standards.
- E-TDA-02 Secure Engineering & Data Privacy (SEDP). Documented evidence of a Secure Engineering & Data Privacy (SEDP) program. This is program-level documentation in the form of a runbook, playbook or a similar format provides guidance on organizational practices that support existing policies and standards.
- E-TDA-03 Application Security Testing (AST). Documented evidence of application security testing (e.g., DAST, SAST, fuzzing, etc.).
- E-TDA-04 Design and Development Plan (DDP). Documented evidence of an engineering method to control the design process and govern the lifecycle of the product/service.
- E-TDA-11 Software Assurance Maturity Model (SAMM). Documented evidence of a Software Assurance Maturity Model (SAMM).
- E-TDA-20 Development / Test / Production Environment Separation. Documented evidence of secure development environments and separation of development, test and production environments, including secure migration practices.
- E-TDA-17 System Design Documentation. Documented evidence of system design documentation.
- E-TDA-21 Test Data Management. Documented evidence of restrictions on the use of live / sensitive data in testing and test data integrity controls.
Records specific to CCPA § 7123(c)(14) that typically show the requirement is met:
- Secure development standard. The documented secure coding and development practices.
- Code review records. Pull request reviews showing security checks.
- Security test results. Static and dynamic analysis results with remediation.
- Dependency scanning. Software composition analysis results for third-party components.
- Release approvals. Evidence that security checks are passed before release.
Which ComplianceForge Documents Support CCPA § 7123(c)(14)?
ComplianceForge documentation helps a business build and document the cybersecurity program the audit assesses. Under § 7122(a)(2), the auditor itself must not prepare the business's documents or implement its program. The following documents support CCPA § 7123(c)(14):
Frequently Asked Questions (FAQ)
Does the CCPA require secure coding? The cybersecurity audit must assess, if applicable, secure development and coding best practices, including code reviews and testing (§ 7123(c)(14)).
Does the CCPA name a secure development framework? No. Article 9 does not name a framework. Businesses often align to recognized secure development practices and document how they apply them.
Does this component apply if the business does not write code? The audit assesses components that are applicable to the business’s information system. A business that does not develop or customize software may find this component limited in scope, as determined by the auditor.
What evidence shows secure development for a CCPA audit? A secure development standard, code review records, security test results, dependency scanning and release approvals.
Bottom Line on CCPA § 7123(c)(14)
Secure development is where many applications that handle personal information get their flaws. Document the standard, make reviews and testing security-focused, scan third-party components and keep the records.
Authoritative sources:
This page reproduces California regulatory text from Title 11 of the California Code of Regulations. It is educational, not legal advice. Last reviewed: 2026-11-16.
Other CCPA Article 9 Requirements
Previous: § 7123(c)(13) Cybersecurity Education and Training. Next: § 7123(c)(15) Oversight of Service Providers, Contractors and Third Parties. The rest of the CCPA and CPRA, including Article 10 risk assessments, is covered in the CCPA and CPRA Compliance Guide.