The contract must bar selling or sharing, name the specific business purposes (not by reference to the contract as a whole), bar use outside those purposes and outside the direct relationship, require compliance with the Act and the same level of protection (for example help with audits, risk assessments, ADMT duties and security under 1798.81.5), give the business rights to check use, including reviews, scans or assessments at least every 12 months, require notice when the provider can no longer comply, give the business rights to stop and remedy misuse, and require help with consumer requests or require the business to pass on the requests the provider must act on. Subcontracts must carry the same terms, and due diligence by the business affects whether it had reason to suspect misuse.
This control maps to 3 controls across 3 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 7051 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 3 it maps to, and the evidence behind each claim, over MCP and REST.