Quality, Expert-Derived Cybersecurity Documentation To Keep Organizations Secure, Compliant & Resilient  |  Got Questions? +1-307-241-8740
ComplianceForge

What Does the CCPA Cybersecurity Audit Assess for Secure Configuration (§ 7123(c)(5))?

Short Answer

CCPA regulation § 7123(c)(5) requires the cybersecurity audit to assess, if applicable, secure configuration of hardware and software: software updates and upgrades, securing on-premises and cloud-based environments, masking sensitive personal information by default in applications, security patch management, and change management that keeps changes from undermining existing safeguards.

CCPA § 7123(c)(5) 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)(5) Secure Configuration of Hardware and Software, 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 (5) groups five practices that keep systems hardened over time: keeping software current, securing on-premises and cloud environments, masking, patch management and change management.

The masking item stands out. Applications should mask, by default, the sensitive personal information the regulation cites from the Civil Code, and other personal information as appropriate, by systematically removing or replacing characters with symbols such as asterisks or bullets.

What Does CCPA § 7123(c)(5) Say?

The following is the text of 11 CCR § 7123(c)(5), 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:
  • (5) Secure configuration of hardware and software, including:
  • (A) Software updates and upgrades;
  • (B) Securing on-premises and cloud-based environments;
  • (C) Masking (i.e., systematically removing or replacing with symbols such as asterisks or bullets) the sensitive personal information set forth in Civil Code section 1798.145, subdivisions (ae)(1)(A) and (B) and other personal information as appropriate by default in applications;
  • (D) Security patch management (e.g., receiving systematic notifications of security-related software updates and upgrades; and identifying, deploying, and verifying their implementation); and
  • (E) Change management (i.e., processes and procedures to ensure that changes to information system(s) do not undermine existing safeguards).

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)(5) 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)(5) to 39 SCF controls through 49 relationships (4 "subset of", 45 "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.

  • CFG-02 Configuration Management Program. Subset of (strength 10): 7123(c)(5). SCF control: Mechanisms exist to facilitate the implementation of configuration management controls.
  • DCH-36 De-Identification (Anonymization). Subset of (strength 10): 7123(c)(5)(C). SCF control: Mechanisms exist to de-identify sensitive and/or regulated data through (1) Anonymization; (2) De-identification; (3) Pseudonymization; and/or (4) Redaction.
  • CHG-02 Change Management Program. Subset of (strength 10): 7123(c)(5)(E). Intersects with (strength 3): 7123(c)(5)(D). SCF control: Mechanisms exist to facilitate the implementation of a change management program.
  • VPM-02 Vulnerability & Patch Management Program (VPMP). Subset of (strength 10): 7123(c)(5)(D). SCF control: Mechanisms exist to facilitate the implementation and monitoring of risk-based vulnerability management capabilities.
  • CFG-04 Secure Baseline Configurations. Intersects with (strength 8): 7123(c)(5), 7123(c)(5)(B). Intersects with (strength 5): 7123(c)(5)(A). SCF control: Mechanisms exist to develop, document and maintain secure baseline configurations for Technology Assets, Applications and/or Services (TAAS) that are consistent with industry-accepted hardening standards.
  • VPM-08 Software & Firmware Patching. Intersects with (strength 8): 7123(c)(5)(A), 7123(c)(5)(D). SCF control: Mechanisms exist to conduct software patching for all deployed Technology Assets, Applications and/or Services (TAAS), including firmware.
  • CLD-02 Cloud Services. Intersects with (strength 8): 7123(c)(5)(B). SCF control: Mechanisms exist to facilitate the implementation of cloud management controls to ensure cloud instances are secure and in-line with industry practices.
  • CLD-05 Cloud Security Architecture. Intersects with (strength 8): 7123(c)(5)(B). SCF control: Mechanisms exist to ensure that the cloud security architecture supports the organization's technology strategy to securely design, configure and maintain cloud deployments.
  • CHG-03 Configuration Change Control. Intersects with (strength 8): 7123(c)(5)(E). Intersects with (strength 3): 7123(c)(5)(D). SCF control: Mechanisms exist to govern the technical configuration change control processes.
  • CHG-04 Prohibition Of Changes. Intersects with (strength 8): 7123(c)(5)(E). Intersects with (strength 3): 7123(c)(5)(D). SCF control: Mechanisms exist to prohibit unauthorized changes, unless approved through the organization's defined change management processes.
  • CHG-05 Security, Compliance & Resilience Representative for Asset Lifecycle Changes. Intersects with (strength 8): 7123(c)(5)(E). Intersects with (strength 3): 7123(c)(5)(D). SCF control: Mechanisms exist to include a cybersecurity and/or data protection representative in the configuration change control review process.
  • CHG-06 Security Impact Analysis for Changes. Intersects with (strength 8): 7123(c)(5)(E). Intersects with (strength 3): 7123(c)(5)(D). SCF control: Mechanisms exist to analyze proposed changes for potential security impacts, prior to the implementation of the change.
  • CHG-07 Test, Validate & Document Changes. Intersects with (strength 8): 7123(c)(5)(E). Intersects with (strength 3): 7123(c)(5)(D). SCF control: Mechanisms exist to appropriately test and document proposed changes in a non-production environment before changes are implemented into production.
  • CHG-09 Control Functionality Verification. Intersects with (strength 8): 7123(c)(5)(E). Intersects with (strength 3): 7123(c)(5)(D). SCF control: Mechanisms exist to verify the functionality of security, compliance and resilience controls following implemented changes to ensure applicable controls operate as designed.
  • VPM-03 Attack Surface Scope. Intersects with (strength 8): 7123(c)(5)(D). SCF control: Mechanisms exist to define and manage the scope for its attack surface management activities.
  • VPM-06 Vulnerability Remediation Process. Intersects with (strength 8): 7123(c)(5)(D). SCF control: Mechanisms exist to ensure that vulnerabilities are properly identified, tracked and remediated.
  • VPM-06.1 Centralized Management of Flaw Remediation Processes. Intersects with (strength 8): 7123(c)(5)(D). SCF control: Mechanisms exist to centrally-manage the flaw remediation process.
  • VPM-06.2 Continuous Vulnerability Remediation Activities. Intersects with (strength 8): 7123(c)(5)(D). SCF control: Mechanisms exist to address new threats and vulnerabilities on an ongoing basis and ensure assets are protected against known attacks.
  • VPM-12 Vulnerability Scanning. Intersects with (strength 8): 7123(c)(5)(D). SCF control: Mechanisms exist to detect vulnerabilities and configuration errors by routine vulnerability scanning of systems and applications.
  • AST-37.1 Stable Versions. Intersects with (strength 5): 7123(c)(5)(A). SCF control: Mechanisms exist to install the latest stable version of any software and/or security-related updates on all applicable systems.
  • CFG-07 Baseline Configuration Reviews & Updates. Intersects with (strength 5): 7123(c)(5)(A). SCF control: Mechanisms exist to review and update secure baseline configurations: (1) At least annually; (2) When required due to so; or (3) As part of system component installations and upgrades.
  • CFG-03.2 Development & Test Environment Configurations. Intersects with (strength 5): 7123(c)(5)(B). SCF control: Mechanisms exist to manage secure baseline configurations for development and test environments separately from operational baseline configurations to minimize the risk of unintentional changes.
  • CLD-06 Cloud Infrastructure Security Subnet. Intersects with (strength 5): 7123(c)(5)(B). SCF control: Mechanisms exist to host security-specific technologies in a dedicated subnet.
  • GOV-03 Centralized Management of Security, Compliance & Resilience Controls. Intersects with (strength 5): 7123(c)(5)(B). SCF control: Mechanisms exist to centrally-manage security, compliance and resilience: (1) Controls; and (2) Related processes.
  • NET-02 Network Security Controls (NSC). Intersects with (strength 5): 7123(c)(5)(B). SCF control: Mechanisms exist to develop, govern & update procedures to facilitate the implementation of Network Security Controls (NSC).
  • NET-03 Boundary Protection. Intersects with (strength 5): 7123(c)(5)(B). SCF control: Mechanisms exist to monitor and control communications at the external network boundary and at key internal boundaries within the network.
  • NET-04 Data Flow Enforcement - Access Control Lists (ACLs). Intersects with (strength 5): 7123(c)(5)(B). SCF control: Mechanisms exist to implement and govern Access Control Lists (ACLs) to provide data flow enforcement that explicitly restrict network traffic to only what is authorized.
  • NET-04.1 Deny Traffic by Default & Allow Traffic by Exception. Intersects with (strength 5): 7123(c)(5)(B). SCF control: Mechanisms exist to configure firewall and router configurations to deny network traffic by default and allow network traffic by exception (e.g., deny all, permit by exception).
  • NET-06 Network Segmentation (macrosegmentation). Intersects with (strength 5): 7123(c)(5)(B). SCF control: Mechanisms exist to implement network segmentation within network architectures to isolate Technology Assets, Applications and/or Services (TAAS) from other network resources.
  • NET-06.1 Security Management Subnets. Intersects with (strength 5): 7123(c)(5)(B). SCF control: Mechanisms exist to implement security management subnets to isolate security tools and support components from other internal system components by implementing separate subnetworks with managed interfaces to other components of the system.
  • SEA-05 Secure Engineering Principles. Intersects with (strength 5): 7123(c)(5)(B). SCF control: Mechanisms exist to facilitate the implementation of industry-recognized security, compliance and resilience practices in the specification, design, development, implementation and modification of Technology Assets, Applications and/or Services (TAAS).
  • SEA-06 Defense-In-Depth (DiD) Architecture. Intersects with (strength 5): 7123(c)(5)(B). SCF control: Mechanisms exist to implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.
  • DCH-36.3 Removal, Masking, Encryption, Hashing or Replacement of Direct Identifiers. Intersects with (strength 5): 7123(c)(5)(C). SCF control: Mechanisms exist to remove, mask, encrypt, hash or replace direct identifiers in a dataset.
  • CFG-03.1 Baseline Tailoring. Intersects with (strength 3): 7123(c)(5)(B). SCF control: Mechanisms exist to allow secure baseline configurations to be specialized or customized by applying a defined set of tailoring actions that are specific to: (1) Mission / business functions; (2) Operational environment; (3) Specific threats or vulnerabilities; or (4) Other conditions or situations that could affect mission / business success.
  • CFG-05 Configure Technology Assets, Applications and/or Services (TAAS) for High-Risk Areas. Intersects with (strength 3): 7123(c)(5)(B). SCF control: Mechanisms exist to configure Technology Assets, Applications and/or Services (TAAS) utilized in high-risk areas with more restrictive secure baseline configurations.
  • SEA-04 Alignment With Enterprise Architecture. Intersects with (strength 3): 7123(c)(5)(B). SCF control: Mechanisms exist to develop an enterprise architecture, aligned with industry-recognized leading practices, with consideration for security, compliance and resilience principles that addresses risk to organizational operations, assets, individuals and other organizations.
  • DCH-12 Masking Displayed Sensitive / Regulated Data. Intersects with (strength 3): 7123(c)(5)(C). SCF control: Mechanisms exist to apply data masking to sensitive and/or regulated information that is displayed or printed.
  • CHG-04.1 Access Restriction For Change. Intersects with (strength 3): 7123(c)(5)(D). SCF control: Mechanisms exist to define, document, approve and enforce access restrictions associated with changes to Technology Assets, Applications and/or Services (TAAS).
  • VPM-05 Vulnerability Ranking. Intersects with (strength 3): 7123(c)(5)(D). SCF control: Mechanisms exist to identify and assign a risk ranking to newly discovered security vulnerabilities using reputable outside sources for security vulnerability information.

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)(5)

The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:

  • Cloud left out of baselines. § 7123(c)(5)(B) names both on-premises and cloud-based environments.
  • Masking in some screens only. The regulation says masking by default in applications.
  • Patches deployed but not verified. The regulation's patch management example includes identifying, deploying and verifying security updates.
  • Changes that bypass review. Change management must ensure changes to information systems do not undermine existing safeguards.

What Is Reasonable Evidence for CCPA § 7123(c)(5)?

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)(5) include:

  • E-AST-27 Configuration Management. Documented evidence of standardized configuration management practices.
  • E-AST-12 Secure Baseline Configurations Reviews. Documented evidence of a review process to ensure Secure Baseline Configurations (SBC) are current and applicable (e.g., system configuration settings and associated documentation).
  • E-AST-13 Secure Baseline Configurations - Cloud-Based Services. Documented evidence of secure baseline configurations for all deployed types of cloud-based services or applications.
  • E-CLD-01 Cloud Security Architecture. Documented evidence of cloud security architecture, including security management subnets and infrastructure security zones.
  • E-MNT-03 Patch Management. Documented evidence of maintenance activities for Technology Assets, Applications and/or Services (TAAS) (e.g., patch management).
  • E-VPM-01 Vulnerability & Patch Management Program (VPMP). Documented evidence of a Vulnerability & Patch Management Program (VPMP). 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-CHG-05 Change Control Records. Documented evidence of change control records (including test results, when applicable).
  • E-CHG-04 Evidence of Cybersecurity / Data Privacy Reviews. Documented evidence of Change Control Board (CCB) meeting-related security, compliance and/or resilience reviews for proposed change(s).

Records specific to CCPA § 7123(c)(5) that typically show the requirement is met:

  • Configuration baselines. Hardening standards for servers, endpoints, network devices and cloud services, with compliance scans.
  • Cloud security posture reports. Findings and remediation for cloud accounts that hold personal information.
  • Masking settings. Application settings or screenshots showing default masking.
  • Patch compliance reports. Patch status, exceptions and verification results.
  • Change records. Change tickets showing security review and approval.

Which ComplianceForge Documents Support CCPA § 7123(c)(5)?

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)(5):

Frequently Asked Questions (FAQ)

Does the CCPA require masking of sensitive personal information? The cybersecurity audit must assess, if applicable, masking of the sensitive personal information the regulation lists, and other personal information as appropriate, by default in applications (§ 7123(c)(5)(C)). Masking means systematically removing or replacing characters with symbols such as asterisks or bullets.

What does patch management mean in § 7123(c)(5)? The regulation’s example is receiving systematic notifications of security-related software updates and upgrades, and identifying, deploying and verifying their implementation (§ 7123(c)(5)(D)).

Is cloud configuration in scope for the CCPA cybersecurity audit? Yes. Securing on-premises and cloud-based environments is listed in § 7123(c)(5)(B).

What is change management in the CCPA regulations? Processes and procedures to ensure that changes to information systems do not undermine existing safeguards (§ 7123(c)(5)(E)).

Bottom Line on CCPA § 7123(c)(5)

Secure configuration is ongoing work. Maintain baselines for on-premises and cloud systems, mask sensitive personal information by default, verify that patches land, and route changes through review.

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)(4) Inventory and Management of Personal Information and the Information System. Next: § 7123(c)(6) Vulnerability Scans, Penetration Testing and Vulnerability Disclosure. The rest of the CCPA and CPRA, including Article 10 risk assessments, is covered in the CCPA and CPRA Compliance Guide.