Art.32(1)(c) Ability to restore availability and access in timely manner
What the standard requires
Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the controller and the processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate: (c) the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident;
Quoted verbatim from Regulation (EU) 2016/679 (GDPR), consolidated text, which is in the public domain.
Maps to 1 control in 1 other framework
Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.
Integrations that carry evidence for this family
These connectors produce data relevant to GDPR’s Technical Measures family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.
In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.