The assessment weighs privacy risks against what the processing gains for consumers, for the business, for other stakeholders and for the public, with the aim of restricting or stopping processing whose risks outweigh its benefits (7154). The report records a specific purpose, the categories of data and the minimum needed, operational details (methods, sources, retention, consumer interaction, approximate numbers, disclosures made, recipients), for ADMT its logic and how outputs drive decisions, specific benefits, negative impacts and their causes (for example security, discrimination, loss of control, coercion, economic, physical, reputational and psychological harm), planned safeguards, whether the processing will go ahead, contributors, and the approval date with the names and roles of reviewers and approvers, including someone with authority to decide on the processing. One assessment may cover comparable activities, and one done under another law may be reused if supplemented (7156).
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 7152 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.