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 Network Monitoring and Defenses (§ 7123(c)(8))?

Short Answer

CCPA regulation § 7123(c)(8) requires the cybersecurity audit to assess, if applicable, network monitoring and defenses. That includes technologies such as bot detection, intrusion detection and intrusion prevention to detect unsuccessful login attempts, monitor authorized users and stop unauthorized access, and data-loss-prevention systems that detect and prevent unauthorized access, use or disclosure of personal information.

CCPA § 7123(c)(8) 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)(8) Network Monitoring and Defenses, 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 (8) is about seeing and stopping attacks. The regulation lists bot detection, intrusion detection and intrusion prevention as technologies a business may use to detect unsuccessful login attempts, monitor the activity of authorized users, and detect and prevent unauthorized access to personal information or loss of its availability.

Data loss prevention is listed separately, with the example of software that detects and prevents unauthorized access, use or disclosure of personal information.

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

The following is the text of 11 CCR § 7123(c)(8), 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:
  • (8) Network monitoring and defenses, including the deployment of:
  • (A) Technologies, such as bot-detection, intrusion-detection, and intrusion-prevention, which a business may use to detect unsuccessful login attempts, monitor the activity of authorized users, and detect and prevent unauthorized access, destruction, use, modification, or disclosure of personal information; or unauthorized activity resulting in the loss of availability of personal information; and
  • (B) Data-loss-prevention systems (e.g., software to detect and prevent unauthorized access, use, or disclosure of personal information).

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)(8) 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)(8) to 9 SCF controls through 10 relationships (1 "equal", 2 "subset of", 7 "intersects with").

How to read the mapping: each relationship runs from the CCPA text to the SCF control. "Equal" means the CCPA requirement and the SCF control are semantically equivalent. "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.

  • DCH-40 Data Loss Prevention (DLP). Equal (strength 10): 7123(c)(8)(B). SCF control: Automated mechanisms exist to implement Data Loss Prevention (DLP) to protect sensitive information as it is stored, transmitted and processed.
  • NET-02 Network Security Controls (NSC). Subset of (strength 10): 7123(c)(8), 7123(c)(8)(A). SCF control: Mechanisms exist to develop, govern & update procedures to facilitate the implementation of Network Security Controls (NSC).
  • MON-05.4 Automated Tools for Real-Time Event Log & Security-Relevant Telemetry Analysis. Intersects with (strength 5): 7123(c)(8)(A). SCF control: Mechanisms exist to utilize a Security Incident Event Manager (SIEM), or similar automated tool, to support near real-time event log and security-relevant telemetry analysis and incident escalation.
  • MON-17 Monitoring for Indicators of Compromise (IOC). Intersects with (strength 5): 7123(c)(8)(A). SCF control: Automated mechanisms exist to identify and alert on Indicators of Compromise (IoC).
  • MON-22 Inbound & Outbound Communications Traffic. Intersects with (strength 5): 7123(c)(8)(A). SCF control: Mechanisms exist to continuously monitor inbound and outbound communications traffic for unusual or unauthorized activities or conditions.
  • MON-23 Network Intrusion Detection & Prevention Systems (NIDS & NIPS) Monitoring. Intersects with (strength 5): 7123(c)(8)(A). SCF control: Mechanisms exist to monitor Network Intrusion Detection / Prevention Systems (NIDS / NIPS) technologies on critical systems, key network segments and network choke points.
  • NET-03 Boundary Protection. Intersects with (strength 5): 7123(c)(8)(A). SCF control: Mechanisms exist to monitor and control communications at the external network boundary and at key internal boundaries within the network.
  • NET-31 Network Intrusion Detection / Prevention Systems (NIDS / NIPS). Intersects with (strength 5): 7123(c)(8)(A). SCF control: Mechanisms exist to employ Network Intrusion Detection / Prevention Systems (NIDS/NIPS) to detect and/or prevent intrusions into the network.
  • SEA-06 Defense-In-Depth (DiD) Architecture. Intersects with (strength 5): 7123(c)(8)(A). SCF control: Mechanisms exist to implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.

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

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

  • Detection without response. The listed technologies are meant to detect and prevent, so alerts need owners and response steps.
  • No monitoring of authorized users. Monitoring the activity of authorized users is one of the purposes named in § 7123(c)(8)(A).
  • DLP limited to email. Personal information can also leave through web uploads, endpoints and cloud sharing.

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

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

  • E-DCH-16 Data Loss Prevention (DLP) Configuration. Documented evidence of Data Loss Prevention (DLP) and exfiltration prevention configurations.
  • E-NET-04 Network Security Controls (NSC). Documented evidence of the organization's network security controls (e.g., boundary protections, content filtering, wireless infrastructure, etc.).
  • E-NET-11 Intrusion Detection / Prevention Deployment. Documented evidence of Network and Host Intrusion Detection / Prevention Systems (NIDS / NIPS, HIDS / HIPS) deployment and monitoring coverage.
  • E-IRO-02 Indicators of Compromise (IOC). Documented evidence of defined Indicators of Compromise (IOC).
  • E-MON-06 Automated Event Escalation & Reporting. Documented evidence of a capability for selected events to alert applicable personnel, or roles, based on the type of event. This can be demonstrated by the configuration of a Security Incident Event Manager (SIEM), or similar technology, that helps automate event log analysis and reporting.
  • E-MON-07 Situational Awareness. Documented evidence of the organization leveraging knowledge of event log generation to gain situational awareness of cross-domain activities (e.g., technology issues, security events, policy violations, service provider activities, remote workforce activities, physical security events, etc.).
  • E-NET-07 External System Accessibility. Documented evidence of a list of Technology Assets, Applications and/or Services (TAAS) accessible from third-party entities.
  • E-NET-08 Internal Boundaries. Documented evidence of key internal boundaries.

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

  • Intrusion detection and prevention records. Coverage, rule sets and alert handling for systems that process personal information.
  • Login attack monitoring. Bot detection and failed-login alerting for consumer and workforce logins.
  • User activity monitoring. Alerts and reviews for unusual activity by authorized users.
  • DLP policies and incidents. DLP rules for personal information and records of how incidents were handled.

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

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

Frequently Asked Questions (FAQ)

Does the CCPA require intrusion detection? The cybersecurity audit must assess, if applicable, network monitoring and defenses, with bot detection, intrusion detection and intrusion prevention as examples of technologies a business may use (§ 7123(c)(8)(A)).

Does the CCPA require data loss prevention? Data-loss-prevention systems are part of the network monitoring and defenses the audit assesses, if applicable (§ 7123(c)(8)(B)).

Why does the CCPA regulation mention bot detection? The regulation lists it among technologies a business may use to detect unsuccessful login attempts, for example automated attacks against consumer or workforce accounts.

Is monitoring of authorized users part of the CCPA cybersecurity audit? Yes. Monitoring the activity of authorized users is one of the purposes named for the technologies in § 7123(c)(8)(A).

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

Component (8) asks whether the business would notice an attack on personal information. Deploy detection where personal information lives, watch failed logins and user activity, and back DLP with people who respond.

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