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 Vulnerability Scans and Penetration Testing (§ 7123(c)(6))?

Short Answer

CCPA regulation § 7123(c)(6) requires the cybersecurity audit to assess, if applicable, internal and external vulnerability scans, penetration testing, and vulnerability disclosure and reporting, such as bug bounty and ethical hacking programs. Article 9 does not set a testing frequency, so the auditor evaluates whether the approach fits the business and its information system.

CCPA § 7123(c)(6) 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)(6) Vulnerability Scans, Penetration Testing and Vulnerability Disclosure, 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 (6) covers three ways to find weaknesses: scanning from inside and outside the network, penetration testing, and channels for outsiders to report vulnerabilities. § 7001 defines penetration testing as testing the security of an information system by attempting to circumvent or defeat its security features through authorized penetration attempts.

Article 9 does not set a scan or test frequency. That differs from some other regulations, such as NY DFS 23 NYCRR 500.5, which calls for annual penetration testing. The audit report must still identify gaps and the plan to address them.

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

The following is the text of 11 CCR § 7123(c)(6), 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:
  • (6) Internal and external vulnerability scans, penetration testing, and vulnerability disclosure and reporting (e.g., bug bounty and ethical hacking programs).

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)(6) 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)(6) to 8 SCF controls through 8 relationships (1 "subset of", 7 "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.

  • VPM-02 Vulnerability & Patch Management Program (VPMP). Subset of (strength 10): 7123(c)(6). SCF control: Mechanisms exist to facilitate the implementation and monitoring of risk-based vulnerability management capabilities.
  • THR-12 Vulnerability Disclosure Program (VDP). Intersects with (strength 8): 7123(c)(6). SCF control: Mechanisms exist to establish a Vulnerability Disclosure Program (VDP) to assist with the secure development and maintenance of Technology Assets, Applications and/or Services (TAAS) that receives unsolicited input from the public about vulnerabilities in organizational TAAS.
  • VPM-12 Vulnerability Scanning. Intersects with (strength 8): 7123(c)(6). SCF control: Mechanisms exist to detect vulnerabilities and configuration errors by routine vulnerability scanning of systems and applications.
  • TDA-07 Disclosure of Vulnerabilities. Intersects with (strength 5): 7123(c)(6). SCF control: Mechanisms exist to disclose information about vulnerabilities to relevant stakeholders, including: (1) A description of the vulnerability(ies); (2) Affected product(s) and/or service(s); (3) Potential impact of the vulnerability(ies); (4) Severity of the vulnerability(ies); and (5) Guidance to remediate the vulnerability(ies).
  • TDA-07.1 Reporting Exploitable Vulnerabilities. Intersects with (strength 5): 7123(c)(6). SCF control: Mechanisms exist to notify applicable stakeholders about potentially exploitable vulnerabilities in organization-developed Technology Assets, Applications and/or Services (TAAS), as required by statutory, regulatory and/or contractual obligations.
  • TDA-17.4 Application Penetration Testing. Intersects with (strength 5): 7123(c)(6). SCF control: Mechanisms exist to perform application-level penetration testing of custom-made Technology Assets, Applications and/or Services (TAAS).
  • THR-12.1 Security Disclosure Contact Information. Intersects with (strength 5): 7123(c)(6). SCF control: Mechanisms exist to enable public submissions of discovered or potential security vulnerabilities.
  • VPM-18 Penetration Testing. Intersects with (strength 5): 7123(c)(6). SCF control: Mechanisms exist to conduct penetration testing on 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)(6)

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

  • External scans only. The component names both internal and external vulnerability scans.
  • Test scope that misses personal information. Scope penetration tests to include the systems that process personal information or can provide access to it.
  • No way for outsiders to report issues. Vulnerability disclosure and reporting, such as bug bounty or ethical hacking programs, is part of the component.

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

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

  • 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-TDA-16 Vulnerability Disclosure Program (VDP). Documented evidence of a Vulnerability Disclosure Program (VDP) (e.g., bug bounty).
  • E-VPM-11 Vulnerability Scanning. Documented evidence of internal and external vulnerability scans being performed.
  • E-VPM-02 Penetration Testing - Application. Documented evidence of Application Security Testing (AST) activities: Abuse case, malformed, and unexpected inputs (e.g., Robustness or Fuzz testing); Attack surface analysis; Vulnerability chaining; Closed box testing of known vulnerability scanning; Software composition analysis of binary executable files; and/or Static and dynamic code analysis, including testing for credentials that are “hardcoded,” default, easily guessed, and easily compromised.
  • E-TDA-03 Application Security Testing (AST). Documented evidence of application security testing (e.g., DAST, SAST, fuzzing, etc.).
  • E-VPM-03 Penetration Testing - Network. Documented evidence of internal and external network penetration testing activities that focus on discovering and exploiting security vulnerabilities.

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

  • Vulnerability scan reports. Internal and external scan results with remediation tracking.
  • Penetration test reports. Scope, findings and retest results.
  • Vulnerability disclosure program. A published reporting channel, intake records and handling procedures.
  • Remediation timelines. Defined fix timeframes by severity and evidence they are met.

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

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

Frequently Asked Questions (FAQ)

How often does the CCPA require penetration testing? Article 9 does not set a frequency. The cybersecurity audit assesses penetration testing, if applicable, under § 7123(c)(6).

Does the CCPA require a bug bounty program? Bug bounty and ethical hacking programs are the regulation’s examples of vulnerability disclosure and reporting. § 7123(c)(6) does not require a specific type of program.

How do the CCPA regulations define penetration testing? § 7001 defines it as testing the security of an information system by attempting to circumvent or defeat its security features by authorizing attempted penetration of the information system.

Do internal vulnerability scans count? Yes. The component covers both internal and external vulnerability scans.

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

Finding weaknesses before attackers do is the point of component (6). Scan inside and out, test the systems that hold personal information, give outsiders a way to report issues, and track fixes to closure.

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)(5) Secure Configuration of Hardware and Software. Next: § 7123(c)(7) Audit-Log Management. The rest of the CCPA and CPRA, including Article 10 risk assessments, is covered in the CCPA and CPRA Compliance Guide.