CCPA § 7123(c)(7) 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)(7) Audit-Log Management, 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).
Logs are how a business detects and reconstructs unauthorized access to personal information. Component (7) looks at three things: whether logs are stored centrally, how long they are kept and whether anyone monitors them.
Logging supports other components, including network monitoring and defenses in § 7123(c)(8) and incident response in § 7123(c)(17).
What Does CCPA § 7123(c)(7) Say?
The following is the text of 11 CCR § 7123(c)(7), 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:
- (7) Audit-log management, including the centralized storage, retention, and monitoring of logs.
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)(7) 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)(7) to 9 SCF controls through 9 relationships (1 "subset of", 8 "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.
- MON-02 Continuous Monitoring. Subset of (strength 10): 7123(c)(7). SCF control: Mechanisms exist to facilitate the implementation of enterprise-wide monitoring controls.
- MON-03 Event Log & Security-Relevant Telemetry Monitoring. Intersects with (strength 8): 7123(c)(7). SCF control: Mechanisms exist to review event logs and security-relevant telemetry on an ongoing basis and escalate incidents in accordance with established timelines and procedures.
- MON-04 System Generated Event Logs & Security-Relevant Telemetry. Intersects with (strength 8): 7123(c)(7). SCF control: Mechanisms exist to generate, monitor, correlate and respond to event logs and security-relevant telemetry from physical, cybersecurity, data protection and supply chain activities to achieve integrated situational awareness.
- MON-04.1 System-Wide / Time-Correlated Audit Trail. Intersects with (strength 8): 7123(c)(7). SCF control: Automated mechanisms exist to compile audit records into an organization-wide audit trail that is time-correlated.
- MON-05 Centralized Collection of Event Logs & Security-Relevant Telemetry. Intersects with (strength 8): 7123(c)(7). SCF control: Mechanisms exist to utilize a Security Incident Event Manager (SIEM), or similar automated tool, to support the centralized collection of event logs and security-relevant telemetry.
- MON-05.1 Centralized Event Log & Security-Relevant Telemetry Review & Analysis. Intersects with (strength 8): 7123(c)(7). SCF control: Automated mechanisms exist to centrally collect, review and analyze event logs and security-relevant telemetry from multiple sources.
- MON-09 Content of Event Logs. Intersects with (strength 8): 7123(c)(7). SCF control: Mechanisms exist to configure Technology Assets, Applications and/or Services (TAAS) to produce event logs that contain sufficient information to, at a minimum: (1) Establish what type of event occurred; (2) When (date and time) the event occurred; (3) Where the event occurred; (4) The source of the event; (5) The outcome (success or failure) of the event; and (6) The identity of any user/subject associated with the event.
- MON-09.1 Audit Trails. Intersects with (strength 8): 7123(c)(7). SCF control: Mechanisms exist to link system access to individual users or service accounts.
- MON-12 Protection of Event Logs & Security-Relevant Telemetry. Intersects with (strength 8): 7123(c)(7). SCF control: Mechanisms exist to protect event logs, security-relevant telemetry and audit tools from unauthorized access, modification and deletion.
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)(7)
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- Logs stored but not reviewed. Monitoring is named alongside storage and retention.
- Gaps in cloud and SaaS logs. The information system includes resources the business does not own, so cloud and SaaS logs belong in scope.
- Retention set by tool defaults. Set retention based on investigation, legal and business needs rather than default settings, and document the decision.
What Is Reasonable Evidence for CCPA § 7123(c)(7)?
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)(7) include:
- E-MON-01 Event Log Review & Analysis. Documented evidence of a capability to perform security event log review and analysis (e.g., system monitoring records, continuous monitoring strategy, etc.).
- E-MON-05 Centralized Event Log Collection. Documented evidence of security-relevant activities being logged and included as part of the centralized event log collection and review/analysis process.
- E-MON-09 Event Logs. Documented evidence of event logs being generated by Technology Assets, Applications and/or Services (TAAS).
- E-MON-02 Malware Activity. Documented evidence of malware activity being logged and included as part of the centralized event log collection and review/analysis process.
- 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-MON-12 Event Log Protection & Time Synchronization. Documented evidence of event log protection (access restriction, cryptographic protection, separate backup) and synchronization with an authoritative time source.
Records specific to CCPA § 7123(c)(7) that typically show the requirement is met:
- Log source inventory. Systems that process personal information and the logs each sends to central storage.
- Central log platform configuration. Collection, retention and access settings for the SIEM or log platform.
- Monitoring records. Alert rules, triage records and periodic log review sign-offs.
- Log protection settings. Controls that prevent logs from being altered or deleted.
Which ComplianceForge Documents Support CCPA § 7123(c)(7)?
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)(7):
Frequently Asked Questions (FAQ)
How long does the CCPA require logs to be kept? Article 9 does not set a log retention period. § 7123(c)(7) requires the audit to assess log retention as part of audit-log management. Separately, § 7122(g) requires documents relevant to each audit to be kept for at least five years.
Does the CCPA require a SIEM? No product is named. The component covers centralized storage, retention and monitoring of logs, which many businesses meet with a SIEM or a similar log platform.
Which logs belong in the CCPA cybersecurity audit? Logs from the systems that process personal information or can provide access to it, including cloud and SaaS resources that are part of the information system.
How does audit-log management relate to incident response? Logs feed detection and investigation, which the audit assesses under incident response management in § 7123(c)(17).
Bottom Line on CCPA § 7123(c)(7)
Collecting logs is the easy part. Centralize the logs from every system that touches personal information, set and enforce a retention period, and show that someone reviews them.
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)(6) Vulnerability Scans, Penetration Testing and Vulnerability Disclosure. Next: § 7123(c)(8) Network Monitoring and Defenses. The rest of the CCPA and CPRA, including Article 10 risk assessments, is covered in the CCPA and CPRA Compliance Guide.