EvidenceSheet

CCR 7123 Scope the audit across the 18 programme components and report fully

The audit assesses how the cybersecurity programme protects personal information from unauthorised access, alteration, destruction, use or release, and from loss of availability, covering the written programme and each applicable component: authentication (including phishing-resistant MFA), encryption, access and privileged account management, data, hardware and software inventories, secure configuration and patching, vulnerability scanning and penetration testing, log management, network monitoring and data loss prevention, anti-malware, segmentation, port and protocol control, awareness, training, secure development, oversight of service providers and third parties, retention and disposal, incident response and business continuity. The report describes the system, criteria and evidence, the effectiveness of controls, gaps with a dated remediation plan, prior-report corrections, responsible individuals, the auditor's signed independence statement, and any breach notifications made. An audit done for another purpose, such as against NIST CSF 2.0, may be used if it meets the article, alone or supplemented.

Source: CCPA/CPRA, CCR 7123. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CCPA/CPRA in the compliance library.

Applies only to a business that meets one of the thresholds in Cal. Civ. Code 1798.140(d).

4
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Cybersecurity audit report containing every element of 7123(e) · Policy repository / GRC workspace
  • Component coverage matrix showing which of the 18 components apply and how each was tested · Policy repository / GRC workspace
  • Remediation plan with owners and target dates for each gap · Policy repository / GRC workspace
  • Copies or descriptions of breach notifications made in the audit period · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

CCR 7122 Use a qualified, objective and independent auditor working from evidence · CCR 7124 Certify completion of the cybersecurity audit to the CPPA