In October 2025, the International Organization for Standardization (ISO) has officially released the ISO/IEC 27701:2025, the updated international standard for Privacy Information Management Systems (PIMS). This new edition marks a significant evolution in the way organizations manage personal data protection and privacy governance.
In this article, we provide a clear breakdown of the key changes, outline what the updates mean for both organizations and individual professionals, and offer practical guidance to help you prepare for a smooth and effective transition.
Unlike the 2019 version, which functioned as an extension of ISO/IEC 27001 and ISO/IEC 27002, the 2025 edition stands on its own. Organizations can now implement and certify a PIMS independently, without requiring an established Information Security Management System (ISMS).
This update opens the door for a wider range of organizations — including those without an ISMS — to adopt a globally recognized privacy framework that focuses directly on personal data protection, privacy risks, and compliance requirements.
ISO/IEC 27701:2025 structure is aligned with standard management system frameworks such as ISO/IEC 27001, ISO/IEC 42001, ISO 9001, and ISO 22301. This alignment simplifies integration in multi-standard environments and enhances coherence for organizations managing multiple certifications.
| ISO/IEC 27701:2019 | ISO/IEC 27701: 2025 |
| Positioned as an extension to ISO/IEC 27001 and 27002. | Reframed as a stand-alone standard |
| Emphasized integration into the ISMS structure. | Emphasizes compatibility and alignment with other management system standards. |
| Relied on ISO/IEC 27000, 27001:2013, 27002:2013 as normative references. | Retains only ISO/IEC 29100 as the normative reference. |
| Used term “legislation and/or regulation.” | Modernized to “legal requirements.” |
| Included development note: “Initially developed as ISO/IEC 27552.” | Historical note removed — now a mature, independent standard. |
| Language more technical and ISMS-centric. | Language is more privacy oriented |
| Defined “joint PII controller” and relied on 27000 definitions. | Removes “joint PII controller”; adds definitions for “organization” and “interested party.” |
| Required implementation within an ISMS context. | Applicable independently to any organization processing PII. |
| Used term “stakeholders.” | Updated to ISO’s preferred “interested parties.” |
| Mapping references (29100, 27018, 29151, GDPR) with note on national laws. | Same mappings retained. |
| ISO/IEC 27701:2019 | ISO/IEC 27701:2025 |
| Note: The following clauses (5.2-5.8) were added as an extension to the ISMS requirements. | Note: The following clauses (4-10) are not extensions of the ISMS. They are specifically intended for the establishment of an independent management system, the PIMS. |
| Clause 5.2 Context of the organization | Clause 4 Context of the organization |
| Clause 5.3 Leadership | Clause 5 Leadership |
| Clause 5.4 Planning | Clause 6 Planning |
| Clause 5.5 Support | Clause 7 Support |
| Clause 5.6 Operation | Clause 8 Operation |
| Clause 5.7 Performance evaluation | Clause 9 Performance evaluation |
| Clause 5.8 Improvement | Clause 10 Improvement |
| Clause 6 PIMS-specific guidance related to ISO/IEC 27002 | This clause has been removed completely. The specific guidance is now part of Annex B.3 |
| Clause 7 Additional ISO/IEC 27002 guidance for PII controllers | This clause has been removed completely. The guidance for PII controllers is now part of Annex B.1 |
| Clause 8 Additional ISO/IEC 27002 guidance for PII processors | This clause has been removed completely. The guidance for PII processors is now part of Annex B.2 |
| Annex A PIMS-specific reference control objectives and controls (PII Controllers) | Annex A PIMS reference control objectives and controls for PII controllers and PII processors (A.1) |
| Annex B PIMS-specific reference control objectives and controls (PII Processors) | Annex A PIMS reference control objectives and controls for PII controllers and PII processors (A.2) |
| Annex C Mapping to ISO/IEC 29100 | Annex C Mapping to ISO/IEC 29100 |
| Annex D Mapping to the General Data Protection Regulation | Annex D Mapping to the General Data Protection Regulation |
| Annex E Mapping to ISO/IEC 27018 and ISO/IEC 29151 | Annex E Mapping to ISO/IEC 27018 and ISO/IEC 29151 |
| Annex F How to apply ISO/IEC 27701 to ISO/IEC 27001 and ISO/IEC 27002 | Annex F Correspondence with ISO/IEC 27701:2019 |
Clauses 4–10 have been refined to ensure better focus and practicality:
The annexes in ISO/IEC 27701:2025 have been reorganized and expanded for clarity. The PIMS reference control objectives and controls for PII controllers and PII processors, along with their specific implementation guidance, are now covered in Annex A and Annex B of the standard.
The mapping to ISO/IEC 29100 continues to serve the same purpose as in the 2019 version, although the ISO/IEC 27701 controls have been updated. The same applies to Annex E, which includes the mappings to ISO/IEC 27018 and ISO/IEC 29151. The GDPR mapping in Annex D, in particular, has been revised to better illustrate how ISO/IEC 27701:2025 can serve as a certification framework for demonstrating compliance with global privacy laws. To help identify the key changes in privacy and information security controls, ISO/IEC 27701:2025 now includes Annex F, which provides a correspondence with ISO/IEC 27701:2019.
The ISO/IEC 27701 annexes have been renamed and renumbered. Annex A is consolidated into one, where it was previously two separate annexes for PII processors and PII controllers. The revised Annex A now includes security controls for both PII controllers and PII processors, many of which align with information security controls found in ISO/IEC 27001 and ISO/IEC 27002.
Annex B contains fully rewritten and expanded implementation guidance replacing the 2019 guidance that was split between clauses 7 and 8. It provides practical detail for applying Annex A controls.
All other annexes remain unchanged, with the exception of Annex F. Annex F no longer offers guidance on implementing ISO/IEC 27701 in relation to ISO/IEC 27001 and ISO/IEC 27002; it now provides a mapping of the standard to its previous version.
The 2025 edition allows organizations to implement a PIMS independently, without requiring an existing ISMS. This shift increases flexibility and accessibility for organizations of all sizes and sectors. Key benefits include:
The release of this standard it resets how organizations approach privacy governance. The deadline for transitioning to the new 2025 version of ISO/IEC 27701 standard is October 2028. Official transition rules from accreditation bodies are expected to be published soon.
The transition to ISO/IEC 27701:2025 brings exciting opportunities for professionals looking to upskill or specialize in privacy management. Individuals can benefit from:
Whether you are a privacy officer, IT professional, auditor, consultant, or aspiring data protection specialist, upgrading your skills through ISO/IEC 27701:2025 training helps you stay ahead in a rapidly evolving field.
The transition from ISO/IEC 27701:2019 to 2025 is more than a compliance update—it reflects a shift toward an independent, privacy-focused management system. By understanding these changes and adopting a structured transition approach, organizations can strengthen their privacy practices, enhance stakeholder trust, and remain compliant in a dynamic regulatory landscape.
Start your transition journey today with the ISO/IEC 27701:2025 Transition training course. The course includes an introduction to ISO/IEC 27701:2025 and its evolution from ISO/IEC 27701:2019, along with a clause-by-clause comparison and guidance on transition implementation.
If you are interested to take the training course please check here the planned training courses here contact us at support@pecb.com
Share
This website utilizes technologies such as cookies to enable essential site functionality, as well as for analytics, personalization, and targeted advertising. To learn more, read our Cookie Policy and Data Privacy statement.