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 Ports, Services and Protocols (§ 7123(c)(11))?

Short Answer

CCPA regulation § 7123(c)(11) requires the cybersecurity audit to assess, if applicable, limitation and control of ports, services and protocols. In practice, that means allowing only the ports, services and protocols needed for business purposes on systems that process personal information, and disabling or restricting the rest.

CCPA § 7123(c)(11) 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)(11) Limitation and Control of Ports, Services and Protocols, 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).

Every open port, running service and enabled protocol is a possible way in. Component (11) asks whether the business limits them to what is needed and controls changes.

This component overlaps with secure configuration in § 7123(c)(5) and segmentation in § 7123(c)(10), so the same baselines and firewall rules often provide the evidence.

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

The following is the text of 11 CCR § 7123(c)(11), 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:
  • (11) Limitation and control of ports, services, and protocols.

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)(11) 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)(11) to 4 SCF controls through 4 relationships (1 "subset of", 3 "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)(11). SCF control: Mechanisms exist to facilitate the implementation of configuration management controls.
  • CFG-03 Least Functionality. Intersects with (strength 8): 7123(c)(11). SCF control: Mechanisms exist to configure Technology Assets, Applications and/or Services (TAAS) to provide only essential capabilities by specifically prohibiting or restricting the use of ports, protocols, and/or services.
  • CFG-04 Secure Baseline Configurations. Intersects with (strength 8): 7123(c)(11). 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.
  • CFG-03.1 Baseline Tailoring. Intersects with (strength 5): 7123(c)(11). 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.

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

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

  • Legacy protocols left enabled. Older protocols without encryption or strong authentication can remain on by default.
  • Default services running. Services installed by default but never used expand the attack surface.
  • No periodic review. Without regular external and internal port scans, new exposures go unnoticed.

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

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

  • E-AST-27 Configuration Management. Documented evidence of standardized configuration management practices.
  • E-AST-33 Tailored Baselines. Documented evidence exists for tailored baseline configurations to address unique business and/or technical requirements (e.g., kiosk, hazardous environments, etc.).
  • 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-19 Secure Baseline Configurations - Network Devices. Documented evidence of secure baseline configurations for all deployed types of network devices.
  • E-AST-20 Secure Baseline Configurations - Server Class Systems. Documented evidence of secure baseline configurations for all deployed types of server-class operating systems.
  • E-AST-21 Secure Baseline Configurations - Workstation Class Systems. Documented evidence of secure baseline configurations for all deployed types of workstation-class operating systems.
  • 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.

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

  • Approved ports and services list. Allowed ports, services and protocols by system type, with business justification.
  • Port scan results. Internal and external scans compared with the approved list.
  • Hardening baselines. Configuration standards that disable unneeded services and protocols.
  • Exception approvals. Documented approvals for any deviations.

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

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

Frequently Asked Questions (FAQ)

What does the CCPA require for ports, services and protocols? The cybersecurity audit must assess, if applicable, limitation and control of ports, services and protocols (§ 7123(c)(11)). The regulation does not list specific ports or protocols.

How is this component usually evidenced? With an approved list of ports, services and protocols, scan results compared with that list, hardening baselines and exception approvals.

How does this relate to secure configuration? It overlaps with secure configuration in § 7123(c)(5), since hardening baselines usually disable unneeded services and protocols.

Does this apply to cloud services? Yes, to the extent cloud resources are part of the information system. Security groups and service settings control exposed ports and protocols there.

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

Component (11) shrinks the attack surface. Keep an approved list, scan against it, disable what is not needed, and document exceptions.

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)(10) Segmentation of an Information System. Next: § 7123(c)(12) Cybersecurity Awareness. The rest of the CCPA and CPRA, including Article 10 risk assessments, is covered in the CCPA and CPRA Compliance Guide.