The business weighs the totality of circumstances about the disputed data, must accept and consider documents the consumer supplies, and may ask for documentation where needed. Once corrected the data must stay corrected, with service providers and contractors told to correct their copies. Deletion may replace correction if it does not harm the consumer or the consumer agrees. Denials must be explained, with the consumer told of any right to a written statement contesting the data where the disputed data concerns the consumer's health (a statement of up to 250 words added to the record), and the business may refuse repeat requests on the same point within six months or fraudulent or abusive ones. Where another party was the source, the business names that source.
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 7023 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.