What each standard is for
ISO/IEC 27001:2022 covers information security for whatever information sits in your scope: customer data, source code, financial records, intellectual property. Its risk question is about confidentiality, integrity and availability, and its risks are mostly risks to your organisation.
ISO/IEC 27701 covers the processing of personally identifiable information (PII), the term ISO uses for what the Australian Privacy Act calls personal information. Its risk question is wider in one direction and narrower in another. Narrower, because it only cares about PII. Wider, because it asks about risks to the individuals the information is about, and about things security doesn’t touch: whether you collect only what you need, use it for the purpose you said, tell people what you do, honour their requests, keep it only as long as necessary and transfer it lawfully.
A system can be secure and still fail on privacy. A perfectly protected database of personal information collected without a proper notice, kept forever and shared with an undisclosed partner breaches privacy obligations without a single security incident.
What changed in ISO/IEC 27701:2025
The first edition, ISO/IEC 27701:2019, was an extension to ISO 27001 and ISO 27002. It added privacy requirements on top of an existing ISMS, so in practice you could only certify it alongside ISO 27001.
ISO and IEC published the second edition, ISO/IEC 27701:2025, on 14 October 2025, and withdrew the 2019 edition. The main changes:
- Standalone management system. It now has its own clauses 4 to 10 in the harmonised structure used by ISO 27001, ISO 9001 and ISO 42001, so it can be implemented and certified without ISO 27001.
- Restructured controls. Annex A now sets out its controls in three tables: controls for PII controllers (A.1), controls for PII processors (A.2), and information security controls that apply to both (A.3). Annex B gives implementation guidance for each one. Because A.3 brings the necessary security controls into the standard itself, it no longer leans on ISO 27001’s Annex A.
- GDPR mapping kept. The informative annex mapping the standard to GDPR has been revised rather than removed.
- New rules for certification bodies. ISO/IEC 27706:2025, published alongside it, sets the requirements for bodies that audit and certify privacy information management systems, much as ISO/IEC 27006-1 does for ISMS certification.
If you hold a 2019 certificate, it stays valid during the transition. UKAS, following a consensus of the IAF working group, has set 31 October 2027 for certification bodies to transition and 31 October 2028 for their certified clients. Accreditation bodies set their own arrangements, so confirm the date and how the transition audit will run with your certification body. If you are certifying for the first time, check that the body is accredited for the 2025 edition before you sign.
Side by side
| ISO/IEC 27001:2022 | ISO/IEC 27701:2025 | |
|---|---|---|
| Management system | Information security management system (ISMS) | Privacy information management system (PIMS) |
| What it protects | All information in scope | Personal information (PII) and the privacy of the people it is about |
| Risk focus | Confidentiality, integrity and availability; risks to the organisation | Privacy risks, including risks to individuals |
| Controls | 93 Annex A controls in four themes | Annex A in three tables: PII controller, PII processor, and shared information security controls |
| Roles that matter | Asset and risk owners | Whether you are a PII controller, a PII processor or both |
| Prerequisite | None | None since 2025 (the 2019 edition required an ISMS) |
| Certification | Accredited certification body, three-year cycle | Accredited certification body, three-year cycle; bodies assessed against ISO/IEC 27706 |
| Legal link | Supports APP 11 security obligations | Maps to the wider APPs and GDPR, including rights, notice, use and transfers |
| Who asks for it | Most enterprise and government buyers | Buyers whose personal data you process, especially EU customers and data-heavy sectors |
Controller or processor: why the role decides the work
ISO 27701 uses the same split as GDPR. A PII controller decides why and how personal information is processed. A PII processor processes it on a controller’s behalf. Most businesses are both: a controller for their own staff, prospects and customers’ contact details, and a processor for the personal information their customers load into their platform or hand them to handle.
The controls differ accordingly. Controller controls cover things like identifying and documenting the lawful basis and purpose, privacy notices, consent, privacy impact assessments, responding to individuals’ requests, minimising collection and retention, and managing transfers and disclosures. Processor controls focus on doing only what the customer instructs, supporting the customer with their own obligations (such as requests and breach notification), handling sub-processors, returning or deleting data at the end of a contract, and being transparent about where data is processed.
Get the roles wrong and the Statement of Applicability is wrong too. The most common mistake is a SaaS company scoping itself only as a processor and forgetting the personal information it controls in its own marketing, support and HR systems. The reverse happens too: claiming controller controls as “not applicable” when the business clearly decides what it collects.
How it maps to the Privacy Act and GDPR
The Australian Privacy Act
The Privacy Act doesn’t use the controller and processor terms. It applies obligations to “APP entities” through the 13 Australian Privacy Principles, and a business that handles personal information on a client’s behalf is still bound by the APPs if it is itself an APP entity. ISO 27701 still lines up with the APPs well:
| APP obligation | Where a PIMS addresses it |
|---|---|
| APP 1: open and transparent management, privacy policy | PIMS policy, roles, records of processing, privacy notices |
| APPs 3 and 5: collection and notification | Purpose identification, collection limitation, notice controls |
| APP 6: use and disclosure | Purpose limitation, disclosure records, processor instructions |
| APP 8: cross-border disclosure | Transfer and sub-processor controls |
| APP 11: security, destruction and de-identification | Information security controls, retention and disposal controls |
| APPs 12 and 13: access and correction | Processes for handling individuals’ requests |
| Notifiable Data Breaches scheme | Privacy incident and breach management |
ISO 27001 alone mainly helps with APP 11, which requires reasonable steps, including technical and organisational measures, to protect personal information. See Australia’s new cyber and privacy laws for the 2024 amendments.
GDPR
If you offer goods or services to people in the EU or monitor their behaviour, GDPR can apply to you directly, and EU customers will put you through a data processing agreement either way. ISO 27701’s controller and processor controls line up with GDPR’s principles, lawful basis, data subject rights, processor obligations under Article 28, records of processing, security, breach notification, impact assessments and transfers. The standard’s GDPR annex shows the correspondence. It is not a certification under Article 42 of GDPR, so it supports compliance rather than proving it. Our GDPR readiness page covers whether GDPR applies and what it adds.
When buyers ask for ISO 27701
Security questionnaires increasingly have a privacy section, and the questions about lawful basis, sub-processors, retention and data subject requests are not answered by an ISO 27001 certificate. ISO 27701 comes up most when:
- you process large volumes of customers’ personal information, such as SaaS platforms for HR, payroll, health, education or customer data (see ISO 27001 for SaaS and ISO 27001 for health tech);
- EU or UK customers want evidence behind your data processing agreement;
- a procurement team asks for privacy certification alongside security, or scores it;
- you want one audited answer to the privacy half of security questionnaires.
Most buyers still gate on security first. If you have neither, ISO 27001 is usually the first certificate a buyer checks for; add ISO 27701 when privacy questions start affecting deals. The exception is a business whose buyers care mainly about privacy, which can now certify ISO 27701 on its own.
Do you need both?
| Your situation | What to do |
|---|---|
| Buyers ask about security only | ISO 27001. Build it so personal information is in the asset inventory and risk register |
| You hold ISO 27001 and privacy questions are slowing deals | Add ISO 27701 as an extension of your existing system |
| You are starting from nothing and process lots of customers’ personal information | Build both together and certify in one combined audit |
| Buyers want privacy assurance but not a security certificate | ISO 27701 on its own is now possible; check they won’t ask for ISO 27001 or SOC 2 next |
| You hold an ISO 27701:2019 certificate | Plan the transition to the 2025 edition with your certification body |
One system, combined audits
If you need both, don’t build two systems. Because clauses 4 to 10 follow the same structure, one scope statement, risk process, document control, internal audit programme, management review and corrective action log can serve both. Your privacy risk criteria and the controller and processor controls sit alongside your security work, and much of Table A.3 overlaps with controls you already operate under ISO 27001’s Annex A. Keep a separate Statement of Applicability for each standard.
A certification body accredited for both can audit them together. IAF MD 11 sets out how certification bodies run audits of integrated management systems, including how audit time can be reduced where the systems are genuinely integrated. You get two certificates, and the scopes don’t have to match. Combined audits reduce duplication on shared clauses, but the privacy controls still take their own audit time, and the effort depends mostly on how much personal information you handle and in which roles; see what drives ISO 27001 effort. Aligning the two certification cycles is covered in the ISO 27001 audit cycle.
Getting the controller and processor scoping right, and mapping one set of evidence to the standard, the APPs and GDPR, is the part we take on for clients.
Next step
Both standards require internal audits that are objective and impartial. Staff can do them if they aren’t auditing their own work, which is difficult when the same small team built the privacy and security programs, so many organisations bring in an independent internal audit before Stage 1. To work out whether your buyers need ISO 27701, ISO 27001 or both, book a free 30-minute consultation, or see how our ISO 27001 and ISO 27701 services work.
