Law and standard: what changed in 27701:2025 and where it differs from GDPR obligations
ISO/IEC 27701:2025: what changed
No longer an extension of ISO 27001; a PIMS can be built and certified without it. Organisations already integrated with 27001 can keep the integrated architecture; standalone is an option, not a forced split.
Clauses 4–10 share the structure of 27001, 9001 and 42001; controls align with 27001:2022 / 27002:2022 and distinguish PII controller and processor controls.
A three-year transition expected to end in October 2028 (per certification and accreditation body announcements). Combine it with the next surveillance or recertification audit after a gap analysis of scope, SoA and control mapping.
27701 vs GDPR obligations table
Left: the outcome the law requires. Middle: the system 27701 provides. Right: the gap — what a certificate cannot cover is what the consulting work is for.
| GDPR obligation (article) | ISO/IEC 27701:2025 counterpart | Difference and gap |
|---|---|---|
| Territorial scope (Art. 3) | Not addressed; the organisation defines the PIMS scope itself | 27701 does not tell you whether the GDPR reaches you; check applicability first |
| Legal basis and consent (Arts. 6–9) | Controller controls: determine and record purposes and legal basis, consent management | Choosing the legal basis is a legal judgment; special-category exceptions (Art. 9) must be confirmed case by case |
| Data subject rights (Arts. 12–22) | Controller controls: procedures to inform and respond to requests | The one-month deadline, refusal grounds and fee rules come from the GDPR; 27701 only requires a procedure |
| Records of processing (Art. 30) | PIMS documented information, purposes and data flow records | The fields in Art. 30(1)–(2) are the legal minimum; the RoPA must match them |
| Processor contracts (Art. 28) | Processor controls: customer instructions, sub-processing, assistance duties | The eight mandatory terms in Art. 28(3) are legal content; contracts must contain each |
| Breach notification (Arts. 33, 34) | Incident management and notification procedures | 72 hours to the authority, notice to individuals at high risk, and the four content elements come from the GDPR |
| DPIA (Art. 35) | Privacy risk assessment is a core PIMS requirement | When it is mandatory, the nine criteria and prior consultation (Art. 36) are legal rules |
| DPO (Arts. 37–39) | Designation of a privacy role | Mandatory thresholds, independence and reporting to top management are legal rules; a 27701 role is not automatically a statutory DPO |
| EU representative (Art. 27) | No counterpart | A statutory duty for non-EU companies that 27701 does not address at all |
| International transfers (Arts. 44–49) | Controller/processor controls: identify transfers and their basis | SCC modules, TIA, supplementary measures and Art. 49 derogations are legal judgments |
| Accountability (Arts. 5(2), 24) | The whole PIMS, internal audit, management review, certification | 27701's strongest part: turning accountability into auditable records and a third-party certificate |
Conclusion: 27701 proves that a system exists; the GDPR imposes outcome obligations. Winners uses 27701 as the skeleton, hangs every GDPR obligation on its control, closes the gaps in the project, and takes both through certification together.
GDPR, ISO/IEC 27701, CBPR and Taiwan's PDPA: one is a legal duty, the others are ways to prove
The most common misconception in privacy: "27701 or CBPR certification equals GDPR compliance." The four differ in nature, territory and proof; first map where your data flows and who demands proof, then choose.
| Item | Nature | Who and where | Mandatory? | How it is proven |
|---|---|---|---|---|
| GDPR (Regulation (EU) 2016/679) | EU law | Any organisation processing personal data of people in the EU, or offering goods/services to or monitoring them (Article 3), wherever established | Mandatory; fines up to €20M / 4% (Article 83) | A certificate alone does not show compliance; demonstrated through RoPA, DPIA, contracts (Article 28), transfer tools (SCC/BCR), breach records; Article 42 certifications (e.g. Europrivacy) can serve as supporting evidence |
| ISO/IEC 27701:2025 | International privacy information management standard (standalone certification since 2025) | Controllers and processors in any region; governs the management system, not the legal duties themselves | Voluntary; often a due-diligence or contract requirement | Third-party certificate; 2019-edition certificates transition until Oct 2028 |
| APEC CBPR / Global CBPR | Cross-border privacy certification scheme (APEC since 2011; Global CBPR Forum founded 2022, live 9 June 2025) | Transfers among participating economies (US, Japan, Korea, Singapore, Taiwan and others); certified by each economy's Accountability Agent — in Taiwan the Institute for Information Industry (III), approved by APEC in June 2021 | Voluntary; Japan and Singapore recognise Global CBPR as a lawful transfer mechanism | Accountability Agent certification and public directory; annual review |
| Taiwan Personal Data Protection Act | Taiwan law (regulator: Personal Data Protection Commission) | Public and non-public agencies collecting, processing or using personal data in Taiwan | Mandatory | No certificate; demonstrated through security measures, notice, consent and incident reporting; TPIPAS (III) is a voluntary certification |
Key differences
- The EU is not a CBPR participant: CBPR certification is not an Article 46 transfer tool, so EU→Taiwan transfers still need SCC/BCR plus a transfer impact assessment.
- 27701 proves a privacy management system exists; it does not create the statutory GDPR DPO, EU representative, 72-hour notification or DPIA — those are legal procedures a certificate cannot supply.
- CBPR is benchmarked on the APEC Privacy Framework, a lower bar than GDPR; a strong signal to US, Japanese, Korean and Singaporean customers, no effect for EU customers.
- Taiwan's PDPA is the local legal duty; 27701 controls can evidence "appropriate security measures" but are not the law.
How to choose
- EU data subjects or EU customers → implement GDPR duties clause by clause, with 27701 as the backbone and external proof.
- Main markets US, Japan, Korea, Singapore and customers want cross-border proof → CBPR (certified by III) is the most direct; the system can still be built on 27701.
- Customer due diligence only asks for a privacy management certificate → standalone 27701:2025, no 27001 needed first.
- Taiwan-only operations → PDPA compliance first; if you will go abroad later, build once on the 27701 structure.
What to share when implementing together
When combining, share one base: RoPA / data-flow maps (GDPR Article 30 = 27701 processing records = CBPR questionnaire data inventory), privacy risk assessment and DPIA (Article 35 = 27701 risk assessment), processor contracts (Article 28 = 27701 processor controls = CBPR onward-transfer accountability), breach response (Articles 33, 34 = 27701 incident management = PDPA notification). Only each scheme's statutory procedures and certification applications differ.
How Winners works
Winners supports all four: GDPR compliance, ISO 27701 implementation and audit support, CBPR/TPIPAS certification preparation, and PDPA security maintenance plans. The first step is to draw your data flows and customer requirements, then recommend which one, in what order, or how to obtain two proofs from one document set.
Either entry works: start from your industry's pain points or from the standard you plan to adopt — we first clarify the differences, then give you the information and support.
Method: four phases
- 01 Applicability and data inventory
Determine GDPR applicability and required mechanisms; inventory personal data, data flows and transfers; draft the RoPA. Acceptance: determination and RoPA.
- 02 System build
Build the PIMS documents on 27701:2025 and attach the GDPR obligations (rights procedures, processor contracts, breach notification). Acceptance: document set and SoA.
- 03 Legal mechanisms
SCC and TIA, DPIA, DPO and EU representative, as scoped by the chosen entries. Acceptance: the deliverables of each entry.
- 04 Audit, certification and operation
Internal audit, management review, certification support; the external DPO moves into annual operation. Acceptance: certificate and annual compliance report.
The most cost-effective path to full compliance
The law requires an outcome, not the most expensive method. Below is the lightest lawful path from the official text and our practice, the evidence you can reuse, the steps you can merge, and what must never be cut — cutting it voids the whole compliance.
Lightest lawful path
- Organisations that only need privacy proof and have no ISO 27001 should go straight to standalone 27701:2025 certification.[Basis:ISO/IEC 27701:2025 (14 Oct 2025)]
- Organisations with 27001 keep the integrated architecture, treating 27701 as a scope extension audited in the same certification cycle.[Basis:ISO/IEC 27701:2025 harmonised structure]
- Transition 2019 certificates in the next surveillance or recertification audit instead of a separate audit; transition until Oct 2028.[Basis:Certification body transition notices]
- GDPR Article 27 EU representative: occasional, low-risk processing without large-scale special categories is exempt; make and record the assessment before assuming the cost.[Basis:GDPR Article 27(2)(a)]
- No DPO is required below the Article 37 thresholds; above them, an external service contract is the cheapest compliant option.[Basis:GDPR Article 37(1), (6)]
Evidence you can reuse
- The Article 30 RoPA, data flow maps and the 27701 processing-purpose records are one and the same document.[Basis:GDPR Article 30; 27701 controller controls]
- Article 28 processor contracts and 27701 processor controls use one contract template.[Basis:GDPR Article 28(3)]
- The DPIA risk assessment doubles as the 27701 privacy risk assessment record.[Basis:GDPR Article 35; ISO/IEC 42005 as reference]
Steps you can merge
- Merge breach notification with 27001 incident management and CRA Article 14 reporting into one flow; only the 72-hour deadline and the data-subject notice decision are added.[Basis:GDPR Articles 33, 34]
- Complete SCC signing, the TIA and supplier due diligence in one supplier assessment.[Basis:GDPR Article 46; Decision (EU) 2021/914]
Never cut (cutting voids compliance)
- EU→Taiwan transfers always need an Article 46 safeguard (SCC or BCR) plus a TIA; Taiwan has no adequacy decision and "customer consent" cannot carry routine transfers.[Basis:GDPR Articles 44–46, 49]
- A DPIA in Article 35(3) situations is a legal precondition before processing and cannot be done afterwards.[Basis:GDPR Article 35]
- A 27701 certificate is not GDPR compliance; the statutory DPO, EU representative and notification deadlines are not covered by it.[Basis:Difference table on this page]
Sources
- Regulation (EU) 2016/679 (GDPR) — EUR-Lex
- EDPB — Guidelines on Data Protection Impact Assessment (WP248 rev.01)
- EDPB — Opinion 3/2019 on the interplay between the Clinical Trials Regulation and the GDPR
- Commission Implementing Decision (EU) 2021/914 — standard contractual clauses
- ISO — ISO/IEC 27701 (search the ISO catalogue for the 2025 edition)
- EDPB — Guidelines 3/2018 on the territorial scope of the GDPR (Article 3)
Checked against the official documents on 2026-10-24
Next steps
Book a consultant
Confirm GDPR applicability, required mechanisms and the 27701 scope. The first assessment is free.
Book a consultantRequest a service scope
Name entries ①–④ to receive a scope and quote mapped to the deliverables.
Request a service scopeGDPR page
The GDPR within EU compliance integration and its relationship to other EU regulations.
Go to the GDPR pageRelated Deep Insights
In-depth analysis by Winners consultants, 6,000+ words per article
Vendor security configuration vulnerabilities trigger abnormal transfers; financial institutions should strengthen outso
This document analyzes the abnormal fund transfer event involving E.Sun Bank triggered by security vulnerabilities in vendor settings. It highlights that risks have expanded from personal data protection to financial security, emphasizing that financial institutions bear ultimate responsibility for outsourced risks. The author recommends strengthening vendor management from three perspectives—Institutional, Process, and Technical—by incorporating technical details into audits to prevent technical risks from transferring to the bank's systems.
pimsAutomated cyberattacks driven by AI pose risks of personal data leaks, and e-commerce businesses should implement the pr
Facing the risks of personal data leaks caused by AI automation and cyberattacks, the Cybersecurity Agency, Digital Development Department indicated that over ten Taiwanese companies have been affected, with 8 million records of personal data compromised. Companies should implement the principle of data minimization, collecting only necessary fields, and complete reporting and notification within 72 hours in the event of an incident. This article recommends establishing defense mechanisms from institutional, procedural, and technical perspectives to reduce risks and maintain corporate reputation. - Institutional - Procedural - Technical
