Restrict processing on request where the data subject contests the accuracy of the data, for a period enabling the controller to verify it; where the processing is unlawful and the data subject opposes erasure and asks for restriction instead; where the controller no longer needs the data but the data subject requires it for the establishment, exercise or defence of legal claims; and where the data subject has objected under Article 21(1), pending verification of whether the controller's legitimate grounds override theirs. Restricted data may be stored but otherwise processed only with the data subject's consent, for legal claims, for the protection of another person's rights, or for reasons of important public interest. Inform the data subject before a restriction is lifted.
This control maps to 12 controls across 9 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.
GDPR GDPR-Art.18 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of GDPR your existing evidence covers. Hold ISO 27701:2019 and 21 of 41 GDPR 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 ISO 27701:2019 pair alone.
The graph holds this control, the 12 it maps to, and the evidence behind each claim, over MCP and REST.