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.
This control maps to 2 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
CCPA/CPRA CCR 7060 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CCPA/CPRA your existing evidence covers. Hold GDPR and 17 of 89 CCPA/CPRA controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the GDPR pair alone.
The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.