Inaccurate data are rectified without delay (for statements and assessments accuracy concerns the fact of the statement, not its content); where accuracy cannot be established, processing is restricted, and the data subject is told before restriction is lifted; incomplete data are completed where appropriate. Data are erased without delay where processing is unlawful, no longer needed, or erasure is legally required, though restriction may replace erasure where erasure would harm the data subject's legitimate interests, the data are needed as evidence, or erasure is impossible or disproportionate. Automated systems must make restriction clearly visible and block other use without further checks. Rectifications are passed to the source and recipients, who must act on them. Refusals are given in writing with reasons unless this would endanger s 56(2) interests.
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.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.