CCPA § 7123(c)(3) 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)(3) Account Management and Access Controls, 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 (3) is the most detailed access requirement in Article 9. It limits personnel access to what each job function needs and requires revoking it when no longer needed, including at termination. It also limits service provider, contractor and third-party access to the purposes in the written contracts required by the CCPA and §§ 7051 and 7053.
It covers privileged accounts too, which § 7001 defines as user or service accounts that can perform functions other accounts cannot, such as adding, changing or removing accounts or changing system configurations. Physical access is included, with badges, secure file locations and clean-desk policies as examples.
What Does CCPA § 7123(c)(3) Say?
The following is the text of 11 CCR § 7123(c)(3), 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:
- (3) Account management and access controls, including:
- (A) Restricting each person’s, account’s, or application’s privileges and access to personal information to what is necessary for that person, account, or application to perform their duties. For example:
- (i) If the person is an employee, independent contractor, or any other personnel, restricting their privileges and access to personal information to what is necessary to perform the respective job functions of each individual, and revoking their privileges and access when their job functions no longer require them, including when their employment or contract is terminated;
- (ii) If the person is a service provider or contractor, restricting their privileges and access to personal information to what is necessary for the specific business purpose(s) set forth in, and in compliance with, the written contract between the business and the service provider or contractor required by the CCPA and section 7051; and
- (iii) Restricting the privileges and access of third parties to whom the business sells or shares personal information to the personal information that is necessary for the limited and specified purpose(s) set forth within the contract between the business and the third party required by the CCPA and section 7053.
- (B) Restricting the number of privileged accounts, restricting those privileged accounts’ access functions to only those necessary to perform the account-holder’s job, restricting the use of privileged accounts to when they are necessary to perform functions, and using a privileged-access management solution (e.g., to ensure just-in-time temporary assignment of privileged access).
- (C) Restricting and monitoring the creation of new accounts for employees, independent contractors, or other personnel; service providers or contractors; and privileged accounts, and ensuring that the accounts’ access and privileges are limited as set forth in subsections (c)(3)(A) and (B).
- (D) Restricting and monitoring physical access to personal information (e.g., through the use of badges, secure physical file locations, and enforcement of clean-desk policies).
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)(3) 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)(3) to 21 SCF controls through 33 relationships (3 "subset of", 30 "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.
- IAC-02 Identity & Access Management (IAM). Subset of (strength 10): 7123(c)(3), 7123(c)(3)(C). SCF control: Mechanisms exist to facilitate the implementation of Identification and Access Management (IAM) controls.
- PES-02 Physical & Environmental Protections. Subset of (strength 10): 7123(c)(3)(D). SCF control: Mechanisms exist to facilitate the operation of physical and environmental protection controls.
- IAC-06 Role-Based Access Control (RBAC). Intersects with (strength 8): 7123(c)(3)(A)(i). Intersects with (strength 5): 7123(c)(3)(A), 7123(c)(3)(A)(ii), 7123(c)(3)(A)(iii), 7123(c)(3)(B). SCF control: Mechanisms exist to enforce Role-Based Access Control (RBAC) for Technology Assets, Applications, Services and/or Data (TAASD) to restrict access to individuals assigned specific roles with legitimate business needs.
- IAC-30 Least Privilege. Intersects with (strength 8): 7123(c)(3)(A). Intersects with (strength 5): 7123(c)(3)(A)(iii), 7123(c)(3)(B). SCF control: Mechanisms exist to utilize the concept of least privilege, allowing only authorized access to processes necessary to accomplish assigned tasks in accordance with organizational business functions.
- HRS-08 Onboarding, Transferring & Offboarding Personnel. Intersects with (strength 8): 7123(c)(3)(A)(i), 7123(c)(3)(C). Intersects with (strength 5): 7123(c)(3)(A)(ii). SCF control: Mechanisms exist to proactively govern the following personnel management actions: (1) Onboarding new personnel (e.g., new hires); (2) Transferring personnel into new roles within the organization; and (3) Offboarding personnel (e.g., termination of employment).
- IAC-32 Identification & Authentication for Organizational Users. Intersects with (strength 8): 7123(c)(3)(A)(i). SCF control: Mechanisms exist to uniquely identify and centrally Authenticate, Authorize and Audit (AAA) organizational users and processes acting on behalf of organizational users.
- IAC-10 Privileged Account Management (PAM). Intersects with (strength 8): 7123(c)(3)(B). SCF control: Mechanisms exist to restrict and control privileged access rights for users and Technology Assets, Applications and/or Services (TAAS).
- PES-07 Role-Based Physical Access. Intersects with (strength 8): 7123(c)(3)(D). SCF control: Physical access control mechanisms exist to authorize physical access to facilities based on the position or role of the individual.
- PES-08 Physical Access Control. Intersects with (strength 8): 7123(c)(3)(D). SCF control: Physical access control mechanisms exist to enforce physical access authorizations for all physical access points (including designated entry/exit points) to facilities (excluding those areas within the facility officially designated as publicly accessible).
- PES-13 Monitoring Physical Access. Intersects with (strength 8): 7123(c)(3)(D). SCF control: Physical access control mechanisms exist to monitor for, detect and respond to physical security incidents.
- IAC-03 Authenticate, Authorize and Audit (AAA). Intersects with (strength 5): 7123(c)(3). SCF control: Mechanisms exist to strictly govern the use of Authenticate, Authorize and Audit (AAA) solutions, both on-premises and those hosted by an External Service Provider (ESP).
- IAC-33 Identification & Authentication for Non-Organizational Users. Intersects with (strength 5): 7123(c)(3)(A)(ii), 7123(c)(3)(A)(iii). SCF control: Mechanisms exist to uniquely identify and centrally Authenticate, Authorize and Audit (AAA) third-party users and processes that provide services to the organization.
- TPM-11 Responsible, Accountable, Supportive, Consulted & Informed (RASCI) Matrix. Intersects with (strength 5): 7123(c)(3)(A)(ii). 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-14 Third-Party Contract Requirements. Intersects with (strength 5): 7123(c)(3)(A)(ii), 7123(c)(3)(A)(iii). 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).
- HRS-03 Position Categorization. Intersects with (strength 5): 7123(c)(3)(B). SCF control: Mechanisms exist to manage personnel security risk by assigning a risk designation to all positions and establishing screening criteria for individuals filling those positions.
- IAC-09.1 Management Approval For Privileged Accounts. Intersects with (strength 5): 7123(c)(3)(B), 7123(c)(3)(C). SCF control: Mechanisms exist to restrict the assignment of privileged accounts to management-approved personnel and/or roles.
- IAC-09 Management Approval For New or Changed Accounts. Intersects with (strength 5): 7123(c)(3)(C). SCF control: Mechanisms exist to ensure management approvals are required for new accounts or changes in permissions to existing accounts.
- PES-06 Physical Access Authorizations. Intersects with (strength 5): 7123(c)(3)(D). SCF control: Physical access control mechanisms exist to maintain a current list of personnel with authorized access to organizational facilities (except for those areas within the facility officially designated as publicly accessible).
- PES-10 Physical Security of Offices, Rooms & Facilities. Intersects with (strength 3): 7123(c)(3)(D). SCF control: Mechanisms exist to identify systems, equipment and respective operating environments that require limited physical access so that appropriate physical access controls are designed and implemented for offices, rooms and facilities.
- PES-11 Working in Secure Areas. Intersects with (strength 3): 7123(c)(3)(D). SCF control: Physical security mechanisms exist to allow only authorized personnel access to secure areas.
- PES-14 Visitor Control. Intersects with (strength 3): 7123(c)(3)(D). SCF control: Physical access control mechanisms exist to identify, authorize and monitor visitors before allowing access to the facility (other than areas designated as publicly accessible).
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)(3)
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- Access reviews that skip third parties. § 7123(c)(3)(A)(ii) and (iii) tie service provider, contractor and third-party access to the purposes in their contracts, so reviews need the contract terms at hand.
- Standing privileged access. The regulation's example of what a privileged-access management solution can do is just-in-time temporary assignment of privileged access.
- Account creation that nobody watches. Creating accounts for personnel, service providers, contractors and privileged users must be restricted and monitored, not only reviewed afterwards.
- Forgetting physical access. § 7123(c)(3)(D) covers physical access to personal information, including file storage and clean desks.
What Is Reasonable Evidence for CCPA § 7123(c)(3)?
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)(3) include:
- E-IAC-05 Identity & Access Management (IAM) Function. Documented evidence of an Identity & Access Management (IAM), or similar function, that facilitates the implementation of identification and access management controls.
- E-IAC-02 Defined Roles & Authorizations (RBAC). Documented evidence of defined access control-specific roles (e.g., Role Based Access Control (RBAC)) that affect both logical and physical access authorizations.
- E-IAC-09 Access Authorization Records. Documented evidence of access authorization records.
- E-IAC-03 Privileged User Inventory. Documented evidence of an inventory of privileged users across Technology Assets, Applications and/or Services (TAAS) (internal and external).
- E-HRS-18 Provisioning Checklist (Onboarding). Documented evidence of personnel management practices to formally onboard personnel into their assigned roles.
- E-HRS-19 Deprovisioning Checklist (Offboarding). Documented evidence of personnel management practices to formally offboard personnel from their assigned roles due to employment termination or role change.
- E-TPM-07 System Connection or Processing Agreements. Documented evidence of system connection or processing agreements.
- E-PES-10 Physical Access Authorizations. Documented evidence of physical access authorization activities (e.g., list reviews, termination changes, etc.).
Records specific to CCPA § 7123(c)(3) that typically show the requirement is met:
- Access review records. Periodic reviews of personnel and third-party access, with the access removed as a result.
- Termination samples. Evidence that access was revoked when employment or contracts ended.
- Privileged account inventory and PAM records. The list of privileged accounts, approvals and elevation or session logs.
- Account creation monitoring. Approvals and alerts for new personnel, third-party and privileged accounts.
- Physical access records. Badge reports, secure storage records and clean-desk checks.
Which ComplianceForge Documents Support CCPA § 7123(c)(3)?
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)(3):
Frequently Asked Questions (FAQ)
Does the CCPA require a privileged access management solution? The cybersecurity audit must assess, if applicable, restricting privileged accounts and using a privileged-access management solution, with just-in-time temporary assignment of privileged access as an example (§ 7123(c)(3)(B)).
How does the CCPA regulation treat service provider access? Service provider and contractor access to personal information should be limited to what is necessary for the business purposes in the written contract required by the CCPA and § 7051 (§ 7123(c)(3)(A)(ii)).
Is physical security part of the CCPA cybersecurity audit? Yes. § 7123(c)(3)(D) covers restricting and monitoring physical access to personal information, with badges, secure physical file locations and clean-desk policies as examples.
What is a privileged account under the CCPA regulations? § 7001 defines it as any user or service account that can perform functions other accounts cannot, such as adding, changing or removing other accounts or making configuration changes to an information system.
Bottom Line on CCPA § 7123(c)(3)
Access control is where personal information is won or lost. Tie every account to a job function or contract purpose, put privileged access behind a PAM solution, watch account creation, and include physical access in the 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)(2) Encryption of Personal Information. Next: § 7123(c)(4) Inventory and Management of Personal Information and the Information System. The rest of the CCPA and CPRA, including Article 10 risk assessments, is covered in the CCPA and CPRA Compliance Guide.