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 Personal Information and Asset Inventories (§ 7123(c)(4))?

Short Answer

CCPA regulation § 7123(c)(4) requires the cybersecurity audit to assess, if applicable, inventory and management of personal information and the information system: personal information inventories such as data maps and flows, classification and tagging that control use and disclosure, hardware and software inventories with allowlisting, and approval processes that keep unauthorized hardware and devices off the system.

CCPA § 7123(c)(4) 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)(4) Inventory and Management of Personal Information and the Information System, 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).

A business cannot protect personal information it cannot find. Component (4) asks the audit to look at where personal information is stored, how it can be accessed, and how classification tags are used to control its use and disclosure.

It also covers the technology side: hardware and software inventories, allowlists of authorized hardware and software that may connect to and run on the information system, and approval processes that prevent unauthorized devices from connecting.

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

The following is the text of 11 CCR § 7123(c)(4), 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:
  • (4) Inventory and management of personal information and the business’s information system, including:
  • (A) Personal information inventories (e.g., maps and flows identifying where personal information is stored, and how it can be accessed) and the classification and tagging of personal information (e.g., how personal information is tagged and how those tags are used to control the use and disclosure of personal information);
  • (B) Hardware and software inventories, and the use of allowlisting (i.e., discrete lists of authorized hardware and software to control what is permitted to connect to and execute on the business’s information system); and
  • (C) Hardware and software approval processes, and preventing the connection of unauthorized hardware and devices to the business’s information system.

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)(4) 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)(4) to 20 SCF controls through 21 relationships (2 "subset of", 19 "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.

  • AST-04 Asset Inventories. Subset of (strength 10): 7123(c)(4). Intersects with (strength 8): 7123(c)(4)(B). SCF control: Mechanisms exist to perform inventories of Technology Assets, Applications, Services and/or Data (TAASD) that: (1) Accurately reflects the current TAASD in use; (2) Identifies authorized software products, including business justification details; (3) Is at the level of granularity deemed necessary for tracking and reporting; (4) Includes organization-defined information deemed necessary to achieve effective property accountability; and (5) Is available for review and audit by designated organizational personnel.
  • IAO-02 Information Assurance (IA) Operations. Subset of (strength 10): 7123(c)(4)(C). SCF control: Mechanisms exist to facilitate the implementation of security, compliance and resilience assessment and authorization controls.
  • AST-17 Network Diagrams & Data Flow Diagrams (DFDs). Intersects with (strength 8): 7123(c)(4)(A). SCF control: Mechanisms exist to maintain network architecture diagrams that: (1) Contain sufficient detail to assess the security of the network's architecture; (2) Reflect the current architecture of the network environment; and (3) Document all sensitive and/or regulated data flows.
  • DCH-04 Data & Asset Classification. Intersects with (strength 8): 7123(c)(4)(A). SCF control: Mechanisms exist to ensure data and assets are categorized in accordance with applicable statutory, regulatory and contractual requirements.
  • DCH-34.1 Data Tags. Intersects with (strength 8): 7123(c)(4)(A). SCF control: Mechanisms exist to utilize data tags to automate the tracking of sensitive and/or regulated data across the information lifecycle.
  • PRI-07 Inventory of Personal Data (PD). Intersects with (strength 8): 7123(c)(4)(A). SCF control: Mechanisms exist to establish and maintain a current inventory of all Technology Assets, Applications and/or Services (TAAS) that collect, receive, process, store, transmit, share, update and/or dispose Personal Data (PD).
  • CFG-02 Configuration Management Program. Intersects with (strength 8): 7123(c)(4)(B). SCF control: Mechanisms exist to facilitate the implementation of configuration management controls.
  • CFG-04 Secure Baseline Configurations. Intersects with (strength 8): 7123(c)(4)(B). 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-14.1 Explicitly Allow / Deny Applications. Intersects with (strength 8): 7123(c)(4)(B). SCF control: Mechanisms exist to explicitly allow (allowlist / whitelist) and/or block (denylist / blacklist) applications that are authorized to execute on systems.
  • CHG-02 Change Management Program. Intersects with (strength 8): 7123(c)(4)(C). SCF control: Mechanisms exist to facilitate the implementation of a change management program.
  • CHG-03 Configuration Change Control. Intersects with (strength 8): 7123(c)(4)(C). SCF control: Mechanisms exist to govern the technical configuration change control processes.
  • CHG-04 Prohibition Of Changes. Intersects with (strength 8): 7123(c)(4)(C). SCF control: Mechanisms exist to prohibit unauthorized changes, unless approved through the organization's defined change management processes.
  • IAO-14 Security Authorization. Intersects with (strength 8): 7123(c)(4)(C). SCF control: Mechanisms exist to ensure Technology Assets, Applications and/or Services (TAAS) are officially authorized prior to "go live" in a production environment.
  • AST-17.2 Data Action Mapping. Intersects with (strength 5): 7123(c)(4)(A). SCF control: Mechanisms exist to create and maintain a map of Technology Assets, Applications and/or Services (TAAS) where sensitive and/or regulated data is stored, transmitted or processed.
  • DCH-05 Sensitive Data Inventories. Intersects with (strength 5): 7123(c)(4)(A). SCF control: Mechanisms exist to maintain inventory logs of all sensitive media and conduct sensitive media inventories at least annually.
  • DCH-11 Media Marking. Intersects with (strength 5): 7123(c)(4)(A). SCF control: Mechanisms exist to mark media in accordance with data protection requirements so that personnel are alerted to distribution limitations, handling caveats and applicable security requirements.
  • DCH-11.1 Automated Marking. Intersects with (strength 5): 7123(c)(4)(A). SCF control: Automated mechanisms exist to mark physical media and digital files to indicate the distribution limitations, handling requirements and applicable security markings (if any) of the information to aid Data Loss Prevention (DLP) technologies.
  • NET-46 Metadata. Intersects with (strength 5): 7123(c)(4)(A). SCF control: Mechanisms exist to enforce information flow controls based on metadata.
  • IAO-11 Technical Verification. Intersects with (strength 5): 7123(c)(4)(C). SCF control: Mechanisms exist to perform Control Validation Testing (CVT) activities to evaluate the design, implementation and effectiveness of technical security, compliance and resilience controls.
  • AST-16 Asset Scope Classification. Intersects with (strength 3): 7123(c)(4)(A). SCF control: Mechanisms exist to determine security, compliance and resilience control applicability by identifying, assigning and documenting the appropriate asset scope categorization for all Technology Assets, Applications and/or Services (TAAS) and personnel (internal and third-parties).

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

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

  • Data maps that stop at core systems. Personal information also sits in SaaS tools, shared drives, spreadsheets, logs and backups.
  • Tags that change nothing. The regulation's example is how tags are used to control use and disclosure, so classification should drive controls, not only labels.
  • Inventories without allowlisting. § 7123(c)(4)(B) pairs hardware and software inventories with allowlisting of what may connect and execute.

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

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

  • E-AST-04 Asset Inventories - Hardware. Documented evidence of an inventory of the organization's technology hardware assets.
  • E-AST-05 Asset Inventories - Software. Documented evidence of an inventory of the organization's software assets.
  • E-AST-08 Asset Inventories - Sensitive / Regulated Data. Documented evidence of an inventory of the organization's sensitive/regulated data (including systems where sensitive/regulated data is stored, processed and/or transmitted) that contains sufficient information to determine the potential impact in the event of a data loss incident.
  • E-DCH-01 Data Classification Scheme. Documented evidence of an organization-specific data classification scheme.
  • E-DCH-05 Data Flow Diagram (DFD). Documented evidence of a Data Flow Diagram (DFD) that accurately identifies where sensitive/regulated data is stored, transmitted and/or processed.
  • E-DCH-02 Data Handling Practices. Documented evidence of an organization-specific data handling practices (e.g., guidance specific the data classification scheme).
  • E-AST-31 Allowlist / Denylist. Documented evidence of software applications that are explicitly allowed (allowlist / whitelist) and/or blocked (denylist / blacklist).
  • E-CHG-05 Change Control Records. Documented evidence of change control records (including test results, when applicable).

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

  • Personal information inventory. Data maps and flows showing where personal information is stored and how it can be accessed.
  • Classification and tagging standard. Categories, tagging rules and the controls each tag triggers.
  • Hardware and software inventories. Current inventories reconciled against discovery tools.
  • Allowlisting and approval records. Allowlist configuration and approvals for new hardware, software and devices.

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

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

  • 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.
  • Data Privacy Program (DPP): editable data privacy program documentation covering GDPR, CCPA and HIPAA privacy requirements, data subject rights and privacy governance.

Frequently Asked Questions (FAQ)

Does the CCPA require a data map? The cybersecurity audit must assess, if applicable, personal information inventories, with maps and flows showing where personal information is stored and how it can be accessed as examples (§ 7123(c)(4)(A)).

What is allowlisting in the CCPA regulations? § 7123(c)(4)(B) describes it as discrete lists of authorized hardware and software that control what is permitted to connect to and execute on the business's information system.

Is data classification part of the CCPA cybersecurity audit? Yes. The component includes classification and tagging of personal information and how the tags are used to control its use and disclosure.

How does the inventory support other audit components? Encryption, access control, retention and disposal, and incident response all depend on knowing where personal information is, so the inventory supports §§ 7123(c)(2), (3), (16) and (17).

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

The inventory is the foundation for most other components. Map personal information beyond core systems, make tags drive controls, and pair hardware and software inventories with allowlisting and device approval.

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