What evidence do auditors commonly ask for on CCR 7060 Verify identity for requests to know, delete, correct and access ADMT?

Documented verification procedure by request type and data sensitivity; Records of verification steps taken per request; Fraud detection controls for request intake; Retention rule deleting information collected solely for verification.

What is the most common gap auditors find on CCR 7060?

Notarised affidavits or fees demanded for verification

CCPA/CPRA · Verification, agents, minors and non-discrimination

`CCR 7060` Verify identity for requests to know, delete, correct and access ADMT

A business must set up, document and follow a reasonable verification method, matching what the consumer provides against data it already holds and scaling rigour to the sensitivity of the data and the harm of a wrongful release or deletion: a reasonable degree of certainty for category requests, a reasonably high degree for specific pieces and ADMT access, and account authentication for account holders (7061, 7062). Opt-out, limit and ADMT opt-out requests need no verification. Verification must be free, avoid collecting new sensitive data where possible, use the data only for verification and delete it promptly (1798.130(a)(7)), and include controls against fraudulent verification attempts.

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

artefacts

held by a system

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

Records of verification steps taken per request · Document repository

governing documentDocuments that govern the control

Documented verification procedure by request type and data sensitivity · Policy repository / GRC workspace
Fraud detection controls for request intake · Document repository
Retention rule deleting information collected solely for verification · 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

Notarised affidavits or fees demanded for verification
Verification required before honouring opt-out requests

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 7053 Third-party contract terms for sale or sharing · CCR 7063 Accept requests from authorised agents