“Do you hold ISO/IEC 27701 certification?” — this question from a large client’s supplier assessment questionnaire lands first with the data protection officer. It appears next to the question about ISO 27001, which the company has held for years. The data protection officer passes it to the information security management system lead, who passes it straight back. The question sits exactly between them.
So what is ISO 27701? It links the information security management system on which many organisations’ cybersecurity rests with the management of personal data privacy. Since October 2025, however, it no longer has to be an add-on to ISO 27001, so anyone who knows it as an extension of that standard should check the new edition before answering the client.
What is ISO/IEC 27701?
ISO/IEC 27701 is an international standard of requirements and guidance for a privacy information management system, or PIMS. The current edition, ISO/IEC 27701:2025, edition 2.0, was published on 14 October 2025 under the title “Information security, cybersecurity and privacy protection — Privacy information management systems — Requirements and guidance”.
According to BSI’s description from October 2025, the standard provides a framework for managing personally identifiable information (PII) in line with regulations worldwide. For an organisation operating in the European Union, the point of reference is personal data within the meaning of the GDPR.
It is a management system standard, not a checklist of safeguards. BSI stresses that in the 2025 edition privacy risk assessment and treatment are built into the core clauses of the standard, together with accountability and continual improvement. Anyone familiar with ISO 27001 will recognise the approach: scope and risk first, then measures, and finally evaluation and improvement.
The difference lies in perspective. Information security asks whether data is confidential, intact and available; privacy also asks whether it should be collected at all and how long it should be kept. The GDPR expresses this in Article 5(1): data is collected for specified purposes, limited to what is necessary (data minimisation) and kept no longer than the purpose requires. A perfectly secured database, half of which nobody needs, meets security requirements but not the data minimisation principle.
Is ISO 27701 still an extension to ISO 27001?
Not any more. The first edition, ISO/IEC 27701:2019, published on 5 August 2019, carried the title “Security techniques — Extension to ISO/IEC 27001 and ISO/IEC 27002 for privacy information management — Requirements and guidelines”. It was therefore by definition an extension of two information security standards.
According to BSI, the 2025 edition is a stand-alone Type A management system standard that no longer depends on ISO/IEC 27001 or ISO/IEC 27002. The 2019 edition was withdrawn on 14 October 2025, the day the new one was published.
BSI also notes that the new edition is intended for organisations whether or not they already run an information security management system. The phrase “ISO 27001 extension” therefore describes a withdrawn edition today, and in a client’s questionnaire it is worth checking which edition is meant.
Being stand-alone does not make the ISMS any less useful. An ISO 27001 implementation already covers a risk analysis methodology, a risk register, internal audit and management review, and the privacy system can build on those processes rather than recreate them.
What changed in ISO/IEC 27701:2025?
Independence from ISO 27001 is not the only change. According to BSI’s summary of the changes, the new edition is aligned with ISO’s Harmonized Structure and can be used by organisations of any size, sector or jurisdiction.
BSI also describes a reorganisation of the requirements. Requirements for controllers, processors and subcontractors have been consolidated into a single, clearer annex structure; their intent remains the same, while the numbering and layout have changed. Definitions and responsibilities for the roles have been refined, which according to BSI matters especially where an organisation acts in several roles at once.
The third change concerns context: BSI adds that the text reflects environments such as cloud computing and cross-border transfers without adding new technical controls.
For an organisation with documentation based on the 2019 edition, a practical consequence is the new numbering. References to clauses of the standard in procedures, statements and audit reports will need rewriting, and a mapping between the old and new numbering is worth preparing before the auditor arrives.
Who is ISO 27701 for?
Any organisation that processes personal data, whether as a controller, a processor or a subcontractor. Among its audiences BSI lists controllers and processors including subcontractors, technology companies working with cloud and SaaS, healthcare providers, financial services, the public sector and e-commerce.
The roles come from the GDPR. Under Article 4(7), a controller alone or jointly with others determines the purposes and means of processing, and under Article 4(8), a processor processes personal data on behalf of the controller. An accounting firm that runs payroll for its clients is a processor for them and a controller for its own employees. These dual roles are exactly what the new edition is meant, according to BSI, to describe more clearly.
A certificate can also be a commercial argument. BSI points out that demonstrating commitment through a certifiable management system can differentiate an organisation in the marketplace. A supplier that processes data on behalf of many clients can use it to answer questionnaire questions with one document rather than many explanations.
How does ISO 27701 relate to the GDPR?
The standard is not law and does not replace the GDPR, but it organises how a company meets its obligations and demonstrates that it does. Under Article 5(2) GDPR, the controller is responsible for compliance with the processing principles and must be able to demonstrate it, which is the accountability principle. Article 24(1) adds that technical and organisational measures are reviewed and updated where necessary, and Article 24(2) that, where proportionate, they include the implementation of appropriate data protection policies. Review, updating and policy are also building blocks of a management system.
Several obligations are processes rather than one-off documents. Article 25 requires data protection by design and by default. Article 30 requires a record of processing activities, which has to be updated as the organisation changes.
A management system gives these obligations a permanent form: assigned roles, a review cycle, internal audit and a document trail that can be shown to a supervisory authority or a client. A broader discussion of the principles and individuals’ rights is found in the guide to the GDPR.
Is an ISO 27701 certificate GDPR Article 42 certification?
Not automatically. Article 42 GDPR provides for certification mechanisms intended to demonstrate that processing operations comply with the regulation. Under Article 42(5), certification is issued by certification bodies referred to in Article 43 or by the supervisory authority, on the basis of criteria approved by that authority or by the European Data Protection Board (EDPB).
Article 43(1)(b) adds a requirement for the certification body to be accredited in accordance with EN-ISO/IEC 17065/2012, the standard for bodies certifying products, processes and services. EDPB Guidelines 1/2018 on certification state that the scope of GDPR certification is directed to processing operations or sets of operations, and that criteria should, where appropriate, be interoperable with standards such as ISO standards.
An ISO/IEC 27701 certificate therefore does not become Article 42 certification simply because it concerns privacy. The EDPB collects approved certification mechanisms in a public register (Article 42(8)), so before presenting any certificate as GDPR certification it is worth checking whether the scheme appears there. Even Article 42 certification is voluntary, is issued for a maximum of three years and, under Article 42(4), does not change the obligation to comply with the regulation.
Under Article 24(3) and Article 32(3), an approved certification mechanism may be used as an element in demonstrating compliance. An ISO 27701 certificate outside an approved mechanism does not benefit from these provisions, but it remains evidence that the privacy management system has been checked by an independent auditor, which has value in demonstrating accountability and in client relationships.
Legal position as of 26 October 2026.
The GDPR applies across the European Union; organisations outside it should check how certification is treated under the data protection law that governs them.
Who issues an ISO 27701 certificate?
A certification body, not the consultancy that helped with implementation. Requirements for bodies certifying management systems are set out in ISO/IEC 17021-1, and under that standard the initial certification audit of a management system is conducted in two stages: stage 1 and stage 2.
When choosing a body, check whether it is accredited for this standard and ask which edition it audits against. A certificate without accreditation formally exists, but a client verifying a supplier may not recognise it. Separating roles is also good practice: whoever implemented the system should not certify it, as they would be assessing their own work.
For an organisation already certified to ISO 27001, the natural first step is a conversation with its current certification body. A joint audit schedule for both systems can reduce the number of visits, but whether and how to combine audits is for the body to decide.
What does the new edition mean for holders of ISO 27701:2019 certificates?
A move to the 2025 edition within the deadline set by the certification body’s accreditation body. For example, Singapore’s accreditation body, SAC, announced in April 2026 that certification bodies must transition all their clients to ISO/IEC 27701:2025 by 31 October 2028. That is one accreditation body’s deadline, not a global rule, so an organisation in Poland or elsewhere should ask its own certification body about the timeline.
Preparation is best started with a gap analysis between the current documentation and the new edition. Three questions structure the work: whether the new numbering and the single annex require procedures to be rewritten, whether the privacy system should remain integrated with the ISMS or become a separate system, and whether the description of the controller and processor roles matches what the organisation actually does.
The 2019 edition has been withdrawn, so planning a new implementation against it makes no sense. An organisation just starting out should work on the 2025 edition from day one. When answering client questionnaires, give the full designation of the standard with the year of the edition and the certificate’s expiry date, because a bare “we have ISO 27701” does not say which version the system was assessed against.
How can an organisation with ISO 27001 build a privacy management system?
On the foundation it already has, in five steps. The first is scope and roles: for which processes the organisation is a controller and for which a processor, and whether the scope of the privacy system matches the scope of the ISMS. A software house that certified its ISMS only for its development department, but also processes client data in its support team, will quickly see that the two scopes need to be set separately.
The second step is the record of processing activities under Article 30 GDPR, which becomes the map of personal data in the organisation. The third is extending the risk analysis. Article 32(2) GDPR requires the assessment of security to take account of the risk of accidental or unlawful destruction, loss, alteration, disclosure of or access to data, and high-risk processing also calls for a data protection impact assessment.
The fourth step is bringing the documentation together: data protection policies, the breach-handling procedure, rules for working with processors and training come under the same document control as security policies. The fifth is internal audit and management review that cover privacy, not just information security.
What the ISMS itself looks like, from the structure of the standard to certification, is covered in the guide to ISO 27001.
How do you plan an ISO 27701 implementation from different starting points?
The plan depends on what the organisation already has.
| Starting point | First step | Evidence worth having | Main risk |
|---|---|---|---|
| ISO 27001 certificate, no privacy system | Privacy gap analysis within the current ISMS scope | Record of processing, risk assessment for individuals | Treating privacy as an add-on to security |
| ISO 27701:2019 certificate | Comparison of documentation with the 2025 edition | Mapping of old and new numbering | Transition deadline agreed with the body too late |
| GDPR documentation without a management system | Assigning owners and a review cycle | Review minutes, breach register | Documents without owners, out of date after a year |
| Neither an ISMS nor organised GDPR compliance | Inventory of data processing | Record of processing activities | Scope too broad for a start |
| Processor serving many clients | Description of roles and commitments to controllers | List of contracts and controllers’ instructions | Mixing up the controller and processor roles |
Key takeaways:
- Since the 2025 edition, ISO 27701 is a stand-alone standard, and “ISO 27001 extension” describes a withdrawn edition.
- An organisation with an ISMS can build its privacy system on existing risk, audit and review processes.
- An ISO 27701 certificate is not, on its own, GDPR Article 42 certification and does not release you from obligations.
- The deadline for moving from the 2019 edition is set by the certification body’s accreditation body.
How can nFlo help you organise GDPR compliance and your ISMS ahead of ISO 27701?
We start with personal data. As part of the Comprehensive GDPR Review and Advisory service, we audit processing, inventory data sets and processes, carry out a gap analysis against the GDPR, and assess data processing agreements and technical and organisational measures, ending with a remediation plan, register templates and a breach-handling procedure. This is the input material for a privacy management system.
On the information security side, the ISO 27001 - Implementation and Certification Preparation service covers a gap analysis against ISO/IEC 27001:2022, ISMS documentation, risk analysis, internal audit, management review and support during the certification audit. Both services belong to the governance, risk and compliance area.
nFlo is not a certification body. Certificates are issued by a certification body after the certification audit. If you want to assess how far your organisation is from a privacy management system, let’s talk.
What else should you know about ISO 27701?
Can you implement ISO 27701 without ISO 27001?
According to BSI, yes: the 2025 edition no longer depends on ISO/IEC 27001 or 27002. The withdrawn 2019 edition was an extension to them, and an organisation with an ISMS can still build its privacy system on the ISMS processes.
Does an ISO 27701 certificate release you from GDPR obligations?
No. An ISO 27701 certificate is not, on its own, Article 42 GDPR certification, and even such certification does not change the obligation to comply with the regulation.
Is ISO 27701 mandatory?
No. The GDPR does not require an ISO/IEC 27701 certificate, and its obligations apply whether or not an organisation holds one.
By when do you have to move from ISO 27701:2019 to the 2025 edition?
The deadline is set by the certification body’s accreditation body and may differ between countries, so ask your own certification body about the timeline.
How does ISO 27701 differ from ISO 27001?
ISO/IEC 27001 covers the security of all of an organisation’s information, whereas ISO/IEC 27701 covers the privacy of personally identifiable information and the roles of controller and processor.
