CCPA § 7123 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 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).
- 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).
Section 7123 is the core of Article 9. Subsection (a) sets the goal: assess how the cybersecurity program protects personal information from unauthorized access, destruction, use, modification or disclosure, and protects against unauthorized activity that causes loss of availability. Subsection (b) requires the audit to assess the program as a whole, the applicable components and how the business implements and enforces compliance.
Subsection (c) lists 18 components, from authentication and encryption to incident response and business continuity, each assessed if applicable. Subsection (d) lets the audit cover more, subsection (e) lists ten required report contents, and subsection (f) allows reuse of an audit prepared for another purpose, such as one using NIST CSF 2.0, if it meets every Article 9 requirement on its own or with supplementation.
What Does CCPA § 7123 Require?
The following is the text of 11 CCR § 7123 Scope of Cybersecurity Audit and Audit Report from the final regulation text published by CalPrivacy and effective January 1, 2026. Only the formatting has been adjusted for readability. The subparagraphs under each § 7123(c) component are shown on that component's page.
- (a) The cybersecurity audit must assess how the business’s cybersecurity program: protects personal information from unauthorized access, destruction, use, modification, or disclosure; and protects against unauthorized activity resulting in the loss of availability of personal information.
- (b) The cybersecurity audit must assess:
- (1) The business’s establishment, implementation, and maintenance of its cybersecurity program, including the related written documentation thereof (e.g., policies and procedures), that is appropriate to the business’s size and complexity and the nature and scope of its processing activities, taking into account the state of the art and cost of implementing the components of a cybersecurity program; and
- (2) Each of the components of a cybersecurity program listed in subsection (c) that the auditor deems applicable to the business’s information system.
- (3) How the business implements and enforces compliance with its cybersecurity program as described in subsection (b)(1), the applicable components in subsection (c), and any additional components as set forth in subsection (d).
- (c) The cybersecurity audit must assess the following components, if applicable:
- (1) Authentication, including:
- (2) Encryption of personal information, at rest and in transit.
- (3) Account management and access controls, including:
- (4) Inventory and management of personal information and the business’s information system, including:
- (5) Secure configuration of hardware and software, including:
- (6) Internal and external vulnerability scans, penetration testing, and vulnerability disclosure and reporting (e.g., bug bounty and ethical hacking programs).
- (7) Audit-log management, including the centralized storage, retention, and monitoring of logs.
- (8) Network monitoring and defenses, including the deployment of:
- (9) Antivirus and antimalware protections.
- (10) Segmentation of an information system (e.g., via properly configured firewalls, routers, switches).
- (11) Limitation and control of ports, services, and protocols.
- (12) Cybersecurity awareness, including how the business maintains current knowledge of changing cybersecurity threats and countermeasures.
- (13) Cybersecurity education and training, including training for each employee, independent contractor, and any other personnel to whom the business provides access to its information system (e.g., when their employment or contract begins, annually thereafter, and after a personal information security breach, as described in Civil Code section 1798.150).
- (14) Secure development and coding best practices, including code-reviews and testing.
- (15) Oversight of service providers, contractors, and third parties to ensure compliance with sections 7051 and 7053.
- (16) Retention schedules and proper disposal of personal information no longer required to be retained, by (A) shredding, (B) erasing, or (C) otherwise modifying the personal information in those records to make it unreadable or undecipherable through any means.
- (17) How the business manages its responses to security incidents (i.e., its incident response management).
- (18) Business-continuity and disaster-recovery plans, including data-recovery capabilities and backups.
- (d) Nothing in this section prohibits a cybersecurity audit from assessing components of a cybersecurity program that are not set forth in subsections (b) or (c).
- (e) The cybersecurity audit report must:
- (1) Describe the business’s information system; and identify (A) the policies, procedures, and practices that the cybersecurity audit assessed; (B) the criteria used for the cybersecurity audit; and (C) the specific evidence examined to make decisions and assessments, such as documents reviewed, sampling and testing performed, and interviews conducted. The cybersecurity audit report must also explain why assessing those policies, procedures, and practices; using those criteria; and examining that specific evidence justify the auditor’s findings.
- (2) Identify the applicable components in subsection (c), and any additional component assessed in accordance with subsection (d); describe how the business implements and enforces compliance with the policies and procedures in subsection (b)(1), the applicable components in subsection (c), and any additional component assessed in accordance with subsection (d); and explain their effectiveness in preventing unauthorized access, destruction, use, modification, or disclosure of personal information; and preventing unauthorized activity resulting in the loss of availability of personal information.
- (3) Identify and describe in detail the status of any gaps or weaknesses of the policies and procedures in subsection (b)(1), the applicable components in subsection (c), and any additional component assessed in accordance with subsection (d), that the auditor deemed to increase the risk of unauthorized access, destruction, use, modification, or disclosure of consumers’ personal information; or increase the risk of unauthorized activity resulting in the loss of availability of personal information.
- (4) Document the business’s plan to address the gaps and weaknesses identified and described pursuant to subsection (e)(3), including the timeframe in which it will resolve them.
- (5) Identify any corrections or amendments to any prior cybersecurity audit reports.
- (6) Include the title of up to three qualified individuals responsible for the business’s cybersecurity program.
- (7) Include the auditor’s name, affiliation, and relevant qualifications.
- (8) Include a statement that is signed and dated by the highest-ranking auditor that certifies that they completed an independent review of the business’s cybersecurity program and information system, exercised objective and impartial judgment on all issues within the scope of the cybersecurity audit, and did not rely primarily on assertions or attestations by the business’s management.
- (9) If the business provided notification to affected consumer(s) pursuant to Civil Code section 1798.82, subdivision (a), include a sample copy of the notification(s), excluding any personal information; or a description of the notification(s).
- (10) If the business was required to notify any agency with jurisdiction over privacy laws in California of unauthorized access, destruction, use, modification, or disclosure of personal information; or unauthorized activity resulting in the loss of availability of personal information, include a sample copy of the notification(s), excluding any personal information; or a description of the required notification(s), the date(s) and details of the activity that gave rise to the required notification(s), and any related remediation measures taken by the business.
- (f) A business may utilize a cybersecurity audit, assessment, or evaluation that it has prepared for another purpose, provided that it meets all of the requirements of this Article, either on its own or through supplementation. For example, a business may have engaged in an audit that uses the National Institute of Standards and Technology Cybersecurity Framework 2.0 and meets all of the requirements of this Article.
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.
Each § 7123(c) component has its own page with its full text, SCF mapping and evidence:
How Does CCPA § 7123 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 to 10 SCF controls through 25 relationships (16 "subset of", 9 "intersects with").
This page covers subsections (a), (b), (d), (e) and (f). The mappings for the 18 components in § 7123(c) are on each component page.
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.
- CPL-04.1 Conformity Assessment. Subset of (strength 10): 7123(a), 7123(b), 7123(b)(2), 7123(c). SCF control: Mechanisms exist to conduct assessments to demonstrate security, compliance and/or resilience capability conformity with applicable cybersecurity and data protection laws, regulations and/or contractual obligations.
- CPL-04.4 Declaration of Conformity. Subset of (strength 10): 7123(e), 7123(e)(1), 7123(e)(2), 7123(e)(3), 7123(e)(4), 7123(e)(5), 7123(e)(6), 7123(e)(7), 7123(e)(8), 7123(e)(9), 7123(e)(10), 7123(f). STRM note: With a lack of granular controls, NIST CSF 2.0 does not meet all the requirements of this Article. SCF control: Mechanisms exist to generate a declaration of conformity for each conformity assessment, where the document: (1) Is concise; (2) Unambiguously reflects the current status; (3) Is physically or electronically signed; and (4) Where possible, is machine readable.
- CPL-03 Compliance Scope. Intersects with (strength 8): 7123(b)(2). Intersects with (strength 5): 7123(b)(3). SCF control: Mechanisms exist to document and validate the scope of security, compliance and resilience controls that are determined to meet statutory, regulatory and/or contractual compliance obligations.
- GOV-02 Security, Compliance & Resilience Program (SCRP). Intersects with (strength 5): 7123(b)(1). SCF control: Mechanisms exist to facilitate the design, implementation, and monitoring of security, compliance and resilience governance controls.
- GOV-04 Publishing Security, Compliance & Resilience Documentation. Intersects with (strength 5): 7123(b)(1). SCF control: Mechanisms exist to establish, maintain and disseminate policies, standards and procedures necessary for secure, compliant and resilient capabilities.
- CPL-02 Statutory, Regulatory & Contractual Compliance. Intersects with (strength 5): 7123(b)(3). SCF control: Mechanisms exist to facilitate the identification and implementation of relevant statutory, regulatory and contractual controls.
- CPL-04 Ability To Demonstrate Conformity. Intersects with (strength 5): 7123(b)(3). SCF control: Mechanisms exist to ensure the organization is able to demonstrate security, compliance and/or resilience capability conformity with applicable cybersecurity and data protection laws, regulations and/or contractual obligations.
- CPL-06 Non-Conformity Oversight. Intersects with (strength 5): 7123(b)(3). SCF control: Mechanisms exist to identify and document instances of non-conformity with statutory, regulatory and/or contractual obligations, in order to develop appropriate risk mitigation actions.
- GOV-05 Assigned Security, Compliance & Resilience Responsibilities. Intersects with (strength 5): 7123(b)(3). SCF control: Mechanisms exist to assign one or more qualified individuals with the mission and resources to centrally-manage, coordinate, develop, implement and maintain an enterprise-wide Security, Compliance & Resilience Program (SCRP).
- GOV-11 Operationalizing Security, Compliance & Resilience Capabilities. Intersects with (strength 5): 7123(b)(3). SCF control: Mechanisms exist to compel data and/or process owners to operationalize security, compliance and resilience practices for Technology Assets, Applications, Services and/or Data (TAASD) under their control.
The STRM records "no relationship" for the lead-in text of 7123; the numbered paragraphs under it are mapped individually.
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
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- Treating the 18 components as a checklist. § 7123(b)(3) also requires the audit to assess how the business implements and enforces compliance with its program, so policies without evidence of enforcement leave gaps.
- Assuming another audit is enough. An audit prepared for another purpose, such as one using NIST CSF 2.0, counts only if it meets all Article 9 requirements on its own or through supplementation (§ 7123(f)). Compare it with § 7123(c) and (e) before relying on it.
- Missing report elements. The report must include items that are easy to overlook, such as the titles of up to three people responsible for the program, corrections to prior reports, and copies or descriptions of breach notifications.
- Gaps without a plan. § 7123(e)(4) requires the report to document the business's plan to address each gap or weakness, including the timeframe for resolving it.
What Is Reasonable Evidence for CCPA § 7123?
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 include:
- E-CPL-14 Conformity Attestations & Declarations. Documented evidence of conformity assessment results, attestations and/or declarations of conformity, including the designated certifying official.
- E-CPL-07 Control Assessments. Documented evidence of internal or third-party control assessments to provide governance oversight of cybersecurity & data privacy controls.
- E-AST-02 Asset Scoping Guidance. Documented evidence of an asset scoping guidance. This is program-level documentation in the form of a runbook, playbook or a similar format provides guidance on defining in-scope Technology Assets, Applications, Services and/or Data (TAASD) (including third-parties).
- E-CPL-02 Defined Compliance Scope (DCS). Documented evidence of a formal scoping document that identifies applicable statutory, regulatory and/or contractual obligations for the organization. Defines the affected Lines of Business (LOB), internal / external stakeholders and facilities for the specific scope of compliance obligations.
- E-CPL-01 Statutory, Regulatory & Contractual Obligations. Documented evidence of applicable statutory, regulatory and/or contractual obligations for cybersecurity & data privacy controls.
- E-CPL-05 Internal Audit (IA) Findings. Documented evidence of a centrally-managed and prioritized repository Internal Audit (IA) findings.
- E-CPL-09 Non-Compliance Oversight Reporting. Documented evidence of governance oversight reporting of non-compliance to the organization's executive leadership.
- E-GOV-01 Security, Compliance & Resilience Policies. Documented evidence of an appropriately-scoped security, compliance and resilience-focused policies. Policies are high-level statements of management intent from an organization's executive leadership that are designed to influence decisions and guide the organization to achieve the desired outcomes. Policies are enforced by standards and further implemented by procedures to establish actionable and accountable requirements.
Records specific to CCPA § 7123 that typically show the requirement is met:
- Written cybersecurity program. Policies, standards and procedures appropriate to the business's size, complexity and processing activities (§ 7123(b)(1)).
- Information system description. A description of the information system and of the policies, procedures and practices the audit assessed (§ 7123(e)(1)).
- Component applicability record. Which § 7123(c) components the auditor deemed applicable, and why.
- Gap and remediation register. Gaps and weaknesses with owners and target dates (§ 7123(e)(3) and (4)).
- Breach notification copies. Sample consumer and agency notifications, or descriptions of them, where required (§ 7123(e)(9) and (10)).
Which ComplianceForge Documents Support CCPA § 7123?
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:
Frequently Asked Questions (FAQ)
What are the 18 CCPA cybersecurity audit components? Authentication; encryption; account management and access controls; inventory and management of personal information and the information system; secure configuration; vulnerability scans, penetration testing and vulnerability disclosure; audit-log management; network monitoring and defenses; antivirus and antimalware; segmentation; ports, services and protocols; cybersecurity awareness; education and training; secure development and coding; oversight of service providers, contractors and third parties; retention and disposal; incident response; and business continuity and disaster recovery.
Does the CCPA cybersecurity audit have to cover all 18 components? It must assess each component the auditor deems applicable to the business's information system (§ 7123(b)(2) and (c)), and the report must identify the applicable components (§ 7123(e)(2)). The audit may also assess components that are not listed (§ 7123(d)).
Can a NIST CSF 2.0 or other existing audit satisfy § 7123? § 7123(f) allows a business to use an audit, assessment or evaluation prepared for another purpose, such as one using NIST CSF 2.0, if it meets all Article 9 requirements on its own or through supplementation.
What must the CCPA cybersecurity audit report include? A description of the information system and the evidence examined, the applicable components and their effectiveness, gaps and weaknesses, the plan and timeframe to address them, corrections to prior reports, the titles of up to three responsible individuals, the auditor's name and qualifications, a signed statement of independence and, where applicable, breach notification samples (§ 7123(e)).
Bottom Line on CCPA § 7123
Section 7123 turns reasonable security into a defined audit scope. Document the program, map it to the 18 components, keep evidence that it is enforced, and make sure the report template covers all ten § 7123(e) items.
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: § 7122 Thoroughness and Independence of Cybersecurity Audits. Next: § 7123(c)(1) Authentication. The rest of the CCPA and CPRA, including Article 10 risk assessments, is covered in the CCPA and CPRA Compliance Guide.