CCPA § 7123(c)(1) 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)(1) Authentication, 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).
Authentication is the first component in § 7123(c). The audit looks at multi-factor authentication, which § 7001 defines as verification of at least two of three factor types (knowledge, possession and inherence), and at password practices wherever passwords or passphrases are still used.
The phishing-resistant language is aimed at the workforce and third parties. It names employees, independent contractors, other personnel, service providers and contractors, so the assessment covers which MFA methods those groups use to reach systems that process personal information and whether those methods resist phishing.
What Does CCPA § 7123(c)(1) Say?
The following is the text of 11 CCR § 7123(c)(1), 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:
- (1) Authentication, including:
- (A) Multi-factor authentication (including multi-factor authentication that is resistant to phishing attacks for employees, independent contractors, and any other personnel, service providers, and contractors); and
- (B) If the business uses passwords or passphrases, strong unique passwords or passphrases (e.g., passwords that are at least eight characters in length, not on the business’s disallowed list of commonly used passwords, and not reused).
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)(1) 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)(1) to 7 SCF controls through 7 relationships (1 "subset of", 6 "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)(1). SCF control: Mechanisms exist to facilitate the implementation of Identification and Access Management (IAM) controls.
- IAC-37 Multi-Factor Authentication (MFA). Intersects with (strength 8): 7123(c)(1)(A). SCF control: Automated mechanisms exist to enforce Multi-Factor Authentication (MFA) for: (1) Remote network access; (2) Third-party Technology Assets, Applications and/or Services (TAAS); and/ or (3) Non-console access to critical TAAS that store, transmit and/or process sensitive and/or regulated data.
- IAC-37.2 Phishing-Resistant Multi-Factor Authentication (MFA). Intersects with (strength 8): 7123(c)(1)(A). SCF control: Automated mechanisms exist to enforce phishing-resistant Multi-Factor Authentication (MFA) through authenticators that are cryptographically bound to the verifier's identity, preventing credential relay by an impersonating party.
- IAC-14 Authenticator Management. Intersects with (strength 8): 7123(c)(1)(B). SCF control: Mechanisms exist to: (1) Securely manage authenticators for users and devices; and (2) Ensure the strength of authentication is appropriate to the classification of the data being accessed.
- IAC-15 Password-Based Authentication. Intersects with (strength 8): 7123(c)(1)(B). SCF control: Mechanisms exist to enforce complexity, length and lifespan considerations to ensure strong criteria for password-based authentication.
- IAC-03 Authenticate, Authorize and Audit (AAA). Intersects with (strength 5): 7123(c)(1)(B). 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-16 Passkeys. Intersects with (strength 3): 7123(c)(1)(B). SCF control: Mechanisms exist to utilize passkeys, or equivalent cryptographic key pairing technologies, to authenticate users to 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)(1)
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- MFA on some systems only. The audit covers the business's information system, which § 7001 defines to include resources organized for processing personal information whether or not the business owns them, such as cloud and SaaS applications.
- Phishable second factors for staff. SMS codes and simple push approvals are widely considered vulnerable to phishing. § 7123(c)(1)(A) calls out phishing-resistant MFA for personnel, service providers and contractors.
- Weak rules where passwords remain. The regulation gives three password examples: at least eight characters, not on a disallowed list of commonly used passwords, and not reused.
What Is Reasonable Evidence for CCPA § 7123(c)(1)?
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)(1) 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-13 Authenticator Types. Documented evidence of system authenticator types.
- E-IAC-16 Multi-Factor Authentication (MFA) Configuration. Documented evidence of Multi-Factor Authentication (MFA) enforcement, including replay-resistant and phishing-resistant authenticators for privileged and non-privileged network access.
- E-IAC-17 Authenticator Configuration Settings. Documented evidence of authenticator management settings (e.g., password complexity, default authenticator changes, account lockout, protection of authenticators).
- E-MON-11 System Authenticator Types. Documented evidence of the list of authorized system authenticator types.
- E-IAC-06 Authenticate, Authorize and Audit (AAA) Solution. Documented evidence of an Authenticate, Authorize and Audit (AAA) solution (on-premises and hosted by External Service Providers (ESP)).
Records specific to CCPA § 7123(c)(1) that typically show the requirement is met:
- MFA coverage report. Identity provider reports showing MFA enrollment and enforcement by user group and application.
- Approved authenticator list. The MFA methods allowed for each user group, including phishing-resistant methods for personnel and third parties.
- Password standard and settings. Minimum length, disallowed-password list and reuse rules, with system settings that enforce them.
- Third-party access records. Evidence that service provider and contractor accounts require MFA.
Which ComplianceForge Documents Support CCPA § 7123(c)(1)?
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)(1):
- SCF Policies & Standards (SCRP): editable SCF-based cybersecurity policies, standards and control objectives covering all 34 SCF domains.
- SCF Procedures (CSOP): editable SCF-aligned cybersecurity procedures covering all 34 SCF domains, mapped 1-to-1 to the SCRP standards.
Frequently Asked Questions (FAQ)
Does the CCPA require phishing-resistant MFA? Article 9 lists MFA, including phishing-resistant MFA for employees, independent contractors, other personnel, service providers and contractors, as something the cybersecurity audit must assess if applicable (§ 7123(c)(1)(A)). Gaps the auditor identifies go into the report with the business’s plan to address them (§ 7123(e)(3) and (4)).
What password rules does the CCPA cybersecurity audit look for? Where passwords or passphrases are used, strong unique ones. The regulation gives examples: at least eight characters, not on the business’s list of disallowed commonly used passwords, and not reused (§ 7123(c)(1)(B)).
How do the CCPA regulations define multi-factor authentication? § 7001 defines it as authentication through verification of at least two types of factors: knowledge factors such as a password, possession factors such as a token, or inherence factors such as a biometric characteristic.
Does MFA apply to service providers and contractors under the CCPA? § 7123(c)(1)(A) names service providers and contractors alongside employees, independent contractors and other personnel, so their MFA falls within the authentication assessment.
Bottom Line on CCPA § 7123(c)(1)
Authentication is the first component on the list for a reason. Measure MFA coverage across every system that touches personal information, move personnel and third parties to phishing-resistant methods, and enforce the password examples wherever passwords remain.
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 Scope of Cybersecurity Audit and Audit Report. Next: § 7123(c)(2) Encryption of Personal Information. The rest of the CCPA and CPRA, including Article 10 risk assessments, is covered in the CCPA and CPRA Compliance Guide.