Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
A.5.34 Privacy and protection of personal identifiable information (PII)
Not mandatory by default – decided in your SoA
What it means in plain language
Protect personal data (PII) as required by privacy laws such as GDPR and the Swiss nFADP.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
PII protection works only when privacy duties are translated into concrete data flows, lawful bases, and operational checks across collection, use, sharing, and retention. The main failure mechanism is not missing policy text, but incomplete knowledge of where personal data sits, which vendors receive it, and when a DPIA or privacy review is required. Teams should connect the legal register, privacy notices, and review workflow to accountable roles and evidence.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
The organisation keeps personal data, but the record of processing activities is incomplete, outdated, or missing processors, transfers, retention periods, and deletion responsibilities.
High-risk processing proceeds without a documented DPIA or equivalent risk review, leaving privacy threats such as profiling, large-scale monitoring, or cross-border transfer unassessed.
Data subject request handling is ad hoc: requests are received by multiple teams, deadlines are missed, and there is no traceable case file showing verification, response, and closure.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Maintain a live register of processing activities linked to the legal register. For each activity, record purpose, categories of data subjects and data, recipients, transfers, retention, and the owner responsible for privacy decisions. Review it after new systems, suppliers, or use cases go live.
Use the DPIA template for high-risk or materially changed processing. The privacy lead, legal counsel, and system owner should assess necessity, proportionality, transfer risk, security measures, and residual concerns. Where risk remains elevated, record the decision, escalation route, and any restrictions before launch.
Build a request-handling workflow for access, erasure, correction, objection, and portability requests where applicable. Track identity verification, statutory deadline, decision, response content, and exceptions such as legal retention, then retain the case file for evidence of consistent handling.
Align privacy notices, consent or other lawful basis records, and processor contracts to actual practice. Sample a subset of applications and vendors each quarter to confirm disclosures match reality, sharing is limited to stated purposes, and deleted data is also removed from downstream systems or archives where required.
What an auditor will ask to see
Record of processing activities with owners, purposes, data categories, recipients, transfers, and retention entries.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.