CCPA § 7123(c)(15) 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)(15) Oversight of Service Providers, Contractors and Third Parties, 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 (15) links the cybersecurity audit to the CCPA contract rules. Service providers and contractors process personal information on the business’s behalf under contracts governed by § 7051, and third parties that receive personal information when the business sells or shares it are covered by § 7053.
The audit assesses whether the business oversees these parties to ensure compliance, which works alongside the access limits for service providers, contractors and third parties in § 7123(c)(3).
What Does CCPA § 7123(c)(15) Say?
The following is the text of 11 CCR § 7123(c)(15), 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:
- (15) Oversight of service providers, contractors, and third parties to ensure compliance with sections 7051 and 7053.
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)(15) 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)(15) to 20 SCF controls through 20 relationships (1 "subset of", 19 "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.
- TPM-02 Third-Party Management. Subset of (strength 10): 7123(c)(15). SCF control: Mechanisms exist to facilitate the implementation of third-party management controls.
- TPM-04 Supply Chain Risk Management (SCRM). Intersects with (strength 8): 7123(c)(15). SCF control: Mechanisms exist to: (1) Evaluate security risks and threats associated with Technology Assets, Applications and/or Services (TAAS) supply chains; and (2) Take appropriate remediation actions to minimize the organization's exposure to those risks and threats, as necessary.
- TPM-08 Third-Party Inventories. Intersects with (strength 8): 7123(c)(15). SCF control: Mechanisms exist to maintain a current, accurate and complete list of External Service Providers (ESPs) that can potentially impact the Confidentiality, Integrity, Availability and/or Safety (CIAS) of the organization's Technology Assets, Applications, Services and/or Data (TAASD).
- TPM-12 Third-Party Services. Intersects with (strength 8): 7123(c)(15). SCF control: Mechanisms exist to mitigate the risks associated with third-party access to the organization's Technology Assets, Applications, Services and/or Data (TAASD).
- TPM-15 Review of Third-Party Services. Intersects with (strength 8): 7123(c)(15). SCF control: Mechanisms exist to monitor, regularly review and assess External Service Providers (ESPs) for compliance with established contractual requirements for security, compliance and resilience controls.
- TPM-17 Managing Changes To Third-Party Services. Intersects with (strength 8): 7123(c)(15). SCF control: Mechanisms exist to control changes to services by suppliers, taking into account the criticality of business Technology Assets, Applications, Services and/or Data (TAASD) that are in scope by the third-party.
- TPM-18 Third-Party Deficiency Remediation. Intersects with (strength 8): 7123(c)(15). SCF control: Mechanisms exist to address weaknesses or deficiencies in supply chain elements identified during independent or organizational assessments of such elements.
- MON-19.1 Monitoring for Third-Party Information Disclosure. Intersects with (strength 5): 7123(c)(15). SCF control: Mechanisms exist to monitor for evidence of unauthorized exfiltration or disclosure of organizational information.
- TPM-09 Third-Party Criticality Assessments. Intersects with (strength 5): 7123(c)(15). SCF control: Mechanisms exist to identify, prioritize and assess suppliers and partners of critical Technology Assets, Applications and/or Services (TAAS) using a supply chain risk assessment process relative to their importance in supporting the delivery of high-value services.
- TPM-10 Third-Party Risk Assessments & Approvals. Intersects with (strength 5): 7123(c)(15). SCF control: Mechanisms exist to conduct a risk assessment prior to the acquisition or outsourcing of technology-related Technology Assets, Applications and/or Services (TAAS).
- TPM-11 Responsible, Accountable, Supportive, Consulted & Informed (RASCI) Matrix. Intersects with (strength 5): 7123(c)(15). SCF control: Mechanisms exist to document and maintain a Responsible, Accountable, Supportive, Consulted & Informed (RASCI) matrix, or similar documentation, to delineate assignment for security, compliance and resilience controls between internal stakeholders and External Service Providers (ESPs).
- TPM-12.1 Conflict of Interests. Intersects with (strength 5): 7123(c)(15). SCF control: Mechanisms exist to ensure that the interests of external service providers are consistent with and reflect organizational interests.
- TPM-12.2 Third-Party Processing, Storage and Service Locations. Intersects with (strength 5): 7123(c)(15). SCF control: Mechanisms exist to restrict the location of information processing/storage based on business requirements.
- TPM-13 Third-Party Personnel Security. Intersects with (strength 5): 7123(c)(15). SCF control: Mechanisms exist to control personnel security requirements including security roles and responsibilities for third-party providers.
- TPM-14 Third-Party Contract Requirements. Intersects with (strength 5): 7123(c)(15). SCF control: Mechanisms exist to require contractual requirements for applicable security, compliance and resilience requirements with third-parties, reflecting the organization's needs to protect its Technology Assets, Applications, Services and/or Data (TAASD).
- TPM-14.1 Contract Flow-Down Requirements. Intersects with (strength 5): 7123(c)(15). SCF control: Mechanisms exist to ensure applicable security, compliance and resilience requirements are included in contracts that flow-down to applicable sub-contractors and suppliers.
- TPM-21.1 Security Compromise Notification Agreements. Intersects with (strength 5): 7123(c)(15). SCF control: Mechanisms exist to compel External Service Providers (ESPs) to provide notification of actual or potential compromises in the supply chain that can potentially affect or have adversely affected Technology Assets, Applications and/or Services (TAAS) that the organization utilizes.
- TPM-16 Third-Party Scope Review. Intersects with (strength 3): 7123(c)(15). SCF control: Mechanisms exist to perform recurring validation of the Responsible, Accountable, Supportive, Consulted & Informed (RASCI) matrix, or similar documentation, to ensure security, compliance and resilience control assignments accurately reflect current: (1) Contractual obligations for the External Service Provider (ESP); (2) Business practices; (3) Applicable stakeholders; and (4) Deployed Technology Assets, Applications and/or Services (TAAS).
- TPM-19 Break Clauses. Intersects with (strength 3): 7123(c)(15). SCF control: Mechanisms exist to include "break clauses" within contracts for failure to meet contract criteria for security, compliance and/or resilience controls.
- TPM-22 First-Party Declaration (1PD). Intersects with (strength 3): 7123(c)(15). SCF control: Mechanisms exist to obtain a First-Party Declaration(1PD) from applicable External Service Providers (ESPs) that provides assurance of compliance with specified statutory, regulatory and contractual obligations for security, compliance and resilience controls, including any flow-down requirements to subcontractors.
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)(15)
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- Contracts signed, then forgotten. Oversight means checking compliance during the relationship, not only at contract signing.
- Unclear roles. Whether a vendor is a service provider, contractor or third party changes which contract rules apply.
- Access broader than the contract. § 7123(c)(3) limits their access to what the contract purposes require.
What Is Reasonable Evidence for CCPA § 7123(c)(15)?
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)(15) include:
- E-TPM-01 Third-Party Contracts. Documented evidence of third-party contractual obligations for cybersecurity & data privacy protections.
- E-TPM-06 Third-Party Terms & Conditions. Documented evidence of terms and conditions for external systems.
- E-TPM-03 Third-Party Service Reviews. Documented evidence of a formal, annual stakeholder review of third-party services for each External Service Provider (ESP).
- E-TPM-02 Third-Party Criticality Assessment. Documented evidence of third-party criticality assessment that evaluates the critical nature of each third-party the organization works with.
- E-DCH-06 Third-Party Inventories. Documented evidence of an inventory of External Service Providers (ESP), contractors, vendors, etc. that directly or indirectly impact the organization's Technology Assets, Applications, Services and/or Data (TAASD).
- E-CPL-03 Shared Responsibility Matrix (SRM) / Controls Responsibility Matrix (CRM). Documented evidence of a Controls Responsibility Matrix (CRM), or similar documentation, that identifies the stakeholder involved in executing assigned controls (e.g., Responsible, Accountable, Supportive, Consulted & Informed (RASCI) matrix).
- E-TPM-07 System Connection or Processing Agreements. Documented evidence of system connection or processing agreements.
- E-RSK-02 Supply Chain Risk Management (SCRM) Plan. Documented evidence of a Supply Chain Risk Management (SCRM) Plan. This is program-level documentation in the form of a playbook, concept of operations or a similar format provides guidance on organizational practices that support existing policies and standards.
Records specific to CCPA § 7123(c)(15) that typically show the requirement is met:
- Vendor inventory with CCPA roles. Each vendor that receives personal information, labeled service provider, contractor or third party.
- Contracts. Executed contracts with the terms §§ 7051 and 7053 require.
- Due diligence and monitoring records. Security questionnaires, assessments and periodic reviews.
- Access reviews for vendors. Reviews showing vendor access matches contract purposes.
Which ComplianceForge Documents Support CCPA § 7123(c)(15)?
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)(15):
Frequently Asked Questions (FAQ)
Does the CCPA cybersecurity audit cover vendors? Yes. § 7123(c)(15) covers oversight of service providers, contractors and third parties to ensure compliance with §§ 7051 and 7053.
What are §§ 7051 and 7053? They are the CCPA regulations that set contract requirements: § 7051 for service providers and contractors, and § 7053 for third parties that receive personal information.
What does oversight look like in practice? A vendor inventory with CCPA roles, contracts with the required terms, due diligence and periodic monitoring, and access reviews tied to contract purposes.
How does this relate to access controls? § 7123(c)(3) limits service provider, contractor and third-party access to what the contract purposes require, and § 7123(c)(15) covers oversight of their compliance.
Bottom Line on CCPA § 7123(c)(15)
Vendors extend the information system. Classify each one, keep contracts current, monitor compliance during the relationship and keep their access within contract purposes.
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)(14) Secure Development and Coding Best Practices. Next: § 7123(c)(16) Retention Schedules and Proper Disposal of Personal Information. The rest of the CCPA and CPRA, including Article 10 risk assessments, is covered in the CCPA and CPRA Compliance Guide.