UK

UK GDPR: Security of Processing (Article 32)

Security of Processing [Art 32]

Rule: You must implement appropriate technical and organisational measures to ensure security appropriate to the risk.

Security requirements

RequirementWhat it meansCitation
Risk-appropriate securityMeasures must match the level of riskArt 32(1)
State of the artConsider current technology capabilitiesArt 32(1)
Cost of implementationProportionate to resourcesArt 32(1)
Nature, scope, context, purposesConsider what you’re processing and whyArt 32(1)
Risk to rights and freedomsAssess potential harm to individualsArt 32(1)

Measures to consider [Art 32(1)]

MeasureDescriptionCitation
PseudonymisationReplace identifiers with pseudonymsArt 32(1)(a)
EncryptionEncrypt data in transit and at restArt 32(1)(a)
ConfidentialityEnsure ongoing confidentiality of systemsArt 32(1)(b)
IntegrityEnsure ongoing integrity of systemsArt 32(1)(b)
AvailabilityEnsure ongoing availability of systemsArt 32(1)(b)
ResilienceEnsure ongoing resilience of systemsArt 32(1)(b)
Restore accessAbility to restore access to data after incidentArt 32(1)(c)
TestingRegularly test, assess and evaluate effectivenessArt 32(1)(d)

Staff obligations [Art 32(4)]

Anyone processing data under your authority must only process on your instructions.

Source Text

  1. 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:

(a) the pseudonymisation and encryption of personal data;

(b) the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;

(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;

(d) a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.

  1. In assessing the appropriate level of security account shall be taken in particular of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data transmitted, stored or otherwise processed.

  2. Adherence to an approved code of conduct as referred to in Article 40 or an approved certification mechanism as referred to in Article 42 may be used as an element by which to demonstrate compliance with the requirements set out in paragraph 1 of this Article.

  3. The controller and processor shall take steps to ensure that any natural person acting under the authority of the controller or the processor who has access to personal data shall not process them except on instructions from the controller, unless required to do so by Union or Member State law.

Citation

Article 32, UK GDPR

Contains public sector information licensed under the Open Government Licence v3.0 where applicable. This is not legal advice. Always refer to official sources for authoritative text.

llms.txt