A service provider or contractor may retain, use or disclose data received under its contract only for the specified business purposes and the other limited purposes in subsection (a), such as using subcontractors, building or improving its service without profiling for others, security and fraud prevention, and legal compliance. It may not provide cross-context behavioural advertising as a service provider, must handle consumer requests sent to it directly as the business instructs, and must cooperate with the business on requests, including deletion, correction, access to ADMT and opt-out notices. Without a compliant contract a recipient is not a service provider, so disclosure to it may be a sale or sharing.
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 7050 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.