EvidenceSheet

CCR 7152 Document the risk assessment content and approval

The assessment weighs privacy risks against what the processing gains for consumers, for the business, for other stakeholders and for the public, with the aim of restricting or stopping processing whose risks outweigh its benefits (7154). The report records a specific purpose, the categories of data and the minimum needed, operational details (methods, sources, retention, consumer interaction, approximate numbers, disclosures made, recipients), for ADMT its logic and how outputs drive decisions, specific benefits, negative impacts and their causes (for example security, discrimination, loss of control, coercion, economic, physical, reputational and psychological harm), planned safeguards, whether the processing will go ahead, contributors, and the approval date with the names and roles of reviewers and approvers, including someone with authority to decide on the processing. One assessment may cover comparable activities, and one done under another law may be reused if supplemented (7156).

Source: CCPA/CPRA, CCR 7152. 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
3
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

  • Risk assessment report template containing each 7152(a) element · Policy repository / GRC workspace
  • Completed reports with approval signatures and dates · Policy repository / GRC workspace
  • Safeguard implementation evidence linked to identified negative impacts · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • Mapping showing how assessments done for other state laws were supplemented · 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 7151 Involve the people who run the processing · CCR 7153 Give ADMT customers the facts they need for their own assessment