A.5.34Privacy and protection of personal identifiable information (PII)
Identify and meet your obligations to protect personal data, in line with applicable privacy laws and regulations. Mishandling personal data carries both legal and reputational cost.
Mapping at a glance
A.5.34Privacy and protection of personal identifiable information (PII)ISO/IEC 27001:2022
What an auditor, or Sekit's evidence engine, asks for.
Privacy notice and consent records
The privacy information the company shows people before collecting their data (privacy notice / policy) and how consent is captured and respected.
Data subject rights procedure
The procedure for people to exercise their rights over their data (access, correction, deletion) and how those requests are handled on time.
DPIA and cross-border transfer records
The privacy impact assessments done before new data processing and the records of personal-data transfers to other countries.
From the Sekit evidence catalog
In practice
Privacy compliance usually breaks at the handoff points: consent captured on a signup form that the marketing team never checks before sending an email, or a subject access request that sits in an inbox past the GDPR one-month deadline. A working data subject rights procedure names who verifies identity, who pulls the data, and how the deadline is tracked. Privacy by design means answering data minimisation and retention questions before the first line of code, not bolting on a review afterward. Cross-border transfers need a current safeguard, standard contractual clauses or a Data Privacy Framework certification, verified at onboarding and periodically after.
Common gaps
Consent is captured on the signup form but marketing tools send campaigns without checking whether the person opted in.
Data subject access requests are handled informally by whoever receives the email, with no log of the one-month response deadline.
Vendors receiving personal data outside the EEA were never checked for a valid transfer safeguard at onboarding.
Questions your auditor will ask
How do you verify someone's identity before fulfilling a data subject request?
The data subject rights procedure requires identity verification through a defined method before any access, correction or deletion request is actioned.
What happens if a data subject request is not answered within a month?
Requests are logged with their receive date and tracked against the GDPR deadline, with an escalation if a response is at risk of being late.
Is privacy considered before a new tool or process goes live?
A privacy-by-design check runs as a routine step in project or vendor onboarding, producing a completed record before launch.
What safeguard applies when personal data is sent outside the EEA?
Vendors are checked at onboarding, and periodically after, for a current safeguard such as a signed standard contractual clause or a valid Data Privacy Framework certification.
Where regulation demands it
NIS2 2.1 requires a risk management framework, which privacy impact assessments extend to cover personal data processing specifically.
ENS mp.info.1 addresses personal data directly, requiring the protections this control's privacy program is built to deliver.
Related controls
Via the shared Sekit CSF topic, not the framework's own index.