From the Article 11 date, on a verified request the business must explain in plain language the specific purpose for which ADMT was used about the consumer, the logic and parameters behind the output for that consumer, the output itself, how it was used to reach the decision (and any planned future use), the bar on retaliation, and how to exercise other rights. Existing request channels may be used, the response follows the section 7021 timelines and verification rules, denials must be explained, delivery must be secure, and frequent use (more than four times in 12 months) may be answered at aggregate level. Service providers and contractors must help.
This control maps to 1 controls across 1 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 7222 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 1 it maps to, and the evidence behind each claim, over MCP and REST.