The text of ISO 27701 runs to 64 pages, and a large part of it consists of tables with controls. Which requirements apply to your company, and which tables can you leave aside? After reading this article you will know how the requirements of ISO 27701:2025 are structured, what each clause asks, which controls belong to your role, what you already have because of the GDPR and which edition applies.
Structure of the ISO 27701 requirements
ISO 27701:2025 has two kinds of requirements. Clauses 4 to 10 describe the management system for privacy. Annex A contains the controls. Both are mandatory. In addition, the standard contains explanations and comparisons. This is the layout:
| Part | What it contains | Type |
|---|---|---|
| Clauses 4 to 10 | the management system: context, leadership, planning, support, operation, evaluation, improvement | requirement |
| Annex A | controls in three tables, per role | requirement |
| Annex B | explanation of each control from Annex A | part of the standard (normative), as explanation |
| Annex C | comparison with ISO/IEC 29100, the principles of privacy | for information |
| Annex D | comparison with the GDPR | for information |
| Annex E | comparison with ISO/IEC 27018 and ISO/IEC 29151 | for information |
| Annex F | comparison with the 2019 version | for information |
Annex B is officially part of the standard. The text itself is explanation: how you can implement a control from Annex A. Which controls you must implement follows from Annex A and your risk treatment.
The clauses follow the fixed structure that all ISO management system standards share. As a result they align with ISO 27001, ISO 9001 and other standards. The standard refers to one other standard as a fixed basis: ISO/IEC 29100. That standard describes the concepts and principles of privacy.
Clause 4 of ISO 27701: context of your organisation
You describe your company and the parties that expect something from you. Think of customers and of the people whose data you hold. You record the scope of your system. The 2025 version also asks whether climate change is a relevant issue. That question about climate was also added to other management system standards in 2024, such as ISO 9001 and ISO 27001.
Clause 5 of ISO 27701: leadership
Top management carries the system. It sets a separate privacy policy. It also assigns the roles and the authorities. In the 2019 version this was attached to the information security policy from ISO 27001. Now privacy has its own policy.
Clause 6 of ISO 27701: planning and privacy risks
You assess the privacy risks with a fixed method. For each risk you choose a treatment. You set privacy objectives and plan how to achieve them. If you plan a change to your system, you do so in a controlled way. Which controls from Annex A you take follows from the treatment of your risks.
Clause 7 of ISO 27701: support
You ensure enough people and resources. Your people have the knowledge they need and know what privacy requires of them. You arrange who communicates what. You manage your documents. Which documents are mandatory is explained in the mandatory documents of ISO 27701.
Clause 8 of ISO 27701: operation
You carry out what you planned in clause 6. You repeat the risk assessment at fixed moments and when major changes occur. You also carry out the treatment. Work that you outsource, you control just as well.
Clause 9 of ISO 27701: performance evaluation
You measure whether your system works. You hold an internal audit with a fixed programme. At a fixed moment, management looks at whether the system works. This is called the management review.
Clause 10 of ISO 27701: improvement
You keep improving your system. If something goes wrong, you fix it at the cause. You record what you did.
Annex A of ISO 27701: controls in three tables
Annex A contains the controls, divided over three tables. You take the tables that belong to your roles:
| Table | For whom | Examples of controls |
|---|---|---|
| A.1 | controllers | recording purpose and legal basis, requesting and recording consent, DPIA, contracts with processors, access, rectification and erasure, automated decisions, collecting no more than necessary, retention periods |
| A.2 | processors | agreements with the customer, not using data for own purposes or marketing, reporting when an instruction infringes the law, returning or deleting data after the assignment, notifying and engaging subprocessors |
| A.3 | both roles | security controls for personal data, such as policy, access rights, incidents, backups, logging, encryption, secure development and test data |
Table A.3 is new in the 2025 version. It contains the security controls that used to be in the standard as additions to ISO 27002. As a result you can now obtain ISO 27701 without ISO 27001. Annex B explains for each control how to implement it. That explanation follows the same numbering as the tables.
If you are unsure about your role, ask one question for each processing activity. Do you decide yourself why you use the data? Then you are the controller. Do you use it on behalf of a customer? Then you are the processor.
Take a web shop with 20 people that only processes its own customer data. It is a controller. The web shop takes tables A.1 and A.3. A hosting company that manages servers for other companies is a processor for the data on those servers. It is the controller for its own staff and its own customer contacts. That company therefore takes all three tables.
Controls you already have because of the GDPR
Many controls link to obligations from the GDPR. Annex D of the standard shows that link for each element. These are the best known:
- Record of processing activities. The GDPR requires it in Article 30. In ISO 27701 it is in table A.1 and table A.2.
- DPIA. The GDPR requires it in Article 35. In ISO 27701 it is in table A.1.
- Data processing agreement. The GDPR requires it in Article 28. In ISO 27701, contracts with processors are in table A.1, and agreements with customers and subprocessors in table A.2.
- Rights of data subjects. The GDPR gives people the right of access, rectification and erasure. In ISO 27701 the controls for this are in table A.1.
On one point the standard asks more than the GDPR. You must show that these documents are part of a system that you maintain, measure and improve. An ISO 27701 certificate is not a GDPR certificate, though. Why not is explained in ISO 27701 and the GDPR.
Not applying a control from Annex A of ISO 27701
You do not take a table that does not belong to your role. A web shop that only processes its own customer data takes tables A.1 and A.3 and leaves table A.2 aside. Within a table, your risk treatment determines which controls you take. For ISO 27001 you record that choice in a Statement of Applicability.
We have not been able to verify whether ISO 27701:2025 requires that statement in the same way. For ISO 27001 that requirement is in clause 6.1.3. ISO 27701:2025 also has a clause 6.1.3, on the treatment of privacy risks, but that text is only available for purchase.
So in any case record for each control whether you apply it, and why not if you do not need it. Ask your certification body before stage 1 in what form it wants to see this.
Applicable edition of ISO 27701
The applicable edition is ISO/IEC 27701:2025, the second edition. It was published in October 2025 and replaces the 2019 version. The foreword names as the most important change that the standard has been rewritten as a standalone standard. The European version is EN ISO/IEC 27701:2025. The European standardisation bodies had to publish it as their own standard by April 2026 at the latest.
Do you have a certificate on the 2019 version? Then it remains valid for a while. In the accreditations, the Dutch accreditation body gives 15 October 2028 as the end date for the 2019 version. How to transition is explained in the transition to ISO 27701:2025.
ISO 27701 requirements and your choice of certification body
Your role and the version together determine which certification body fits. On 24 September 2026, 8 certification bodies in the Netherlands had ISO 27701 in their accreditation. Of these, 2 were allowed to certify the 2025 version. The other 6 were only allowed to certify the 2019 version, and only together with ISO 27001. So if you want to obtain ISO 27701 separately, you end up with a small group. Also ask whether the auditor has experience with your role. A processor in the cloud requires different knowledge than a healthcare institution that is mainly a controller.
At CertificeerWijzer you request quotes with one request from certification bodies that may certify ISO 27701 under accreditation. In that request you state your roles and the desired version. You then see straight away who fits your situation.
Sources
- ISO/IEC 27701:2025, foreword, introduction, scope and table of contents (preview via EN ISO/IEC 27701:2025, STN) normy.normoff.gov.sk
- UKAS, F659 Transition Requirements and Gap Analysis, ISO/IEC 27701:2025 and ISO/IEC 27706:2025 ukas.com
- UKAS, Technical Bulletin Transition Arrangements for PIMS, revision 1 (18 August 2026) ukas.com
- RvA, scope C548 (valid from 29 April 2026) rva.nl
- RvA, all accredited organisations for ISO/IEC 17021-1 rva.nl