A business using sensitive data beyond the purposes listed in subsection (m) must offer two or more easy methods to limit, require no account or verification, stop the additional use and disclosure as soon as feasible and within 15 business days, instruct service providers and contractors using the data for those additional purposes to stop within the same period, tell third parties that received it for such purposes between the request and its implementation to comply and to pass the request on to anyone they gave it to in that window, let the consumer confirm the request was processed, and wait 12 months before asking for consent again. The permitted purposes in subsection (m) include providing the expected goods or services, security and integrity, short-term transient use, servicing and quality maintenance, and collection without the purpose of inferring characteristics.
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 7027 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.