Art. 32 GDPR obliges controllers and processors alike to ensure a level of security appropriate to the risk. The state of the art, the costs of implementation, the nature, scope, context and purposes of processing, as well as the likelihood and severity of the risk to data subjects, must be taken into account.
As examples, the provision mentions pseudonymisation and encryption, the ongoing assurance of confidentiality, integrity, availability and resilience of systems, rapid recovery after a physical or technical incident, and a process for regularly testing effectiveness. A contract that only promises “appropriate measures” cannot be measured against this; it only becomes verifiable with a description of the procedures, such as for encryption, rights management, logging, and tenant isolation.
Evidence supplements this description; it does not replace it. Under Art. 28(5) GDPR, adherence to approved codes of conduct under Art. 40 or an approved certification mechanism under Art. 42 may be used as an element to demonstrate sufficient guarantees. For certificates and attestations under other standards, the scope matters: it specifies the audited services and locations.