Home  /  Insights  /  ISO 27001 vs ISO 27701: do you need both?
Insights

ISO 27001 vs ISO 27701: do you need both?

ISO 27001 proves you protect information. ISO 27701 proves you handle personal information properly. Since the 2025 edition they are separate, certifiable standards, so the questions are which one your buyers want and whether you need both.

Cyber Veda

Quick answer: ISO/IEC 27001 is the certifiable standard for an information security management system; ISO/IEC 27701 is the certifiable standard for a privacy information management system. The 2025 edition of ISO 27701, published in October 2025, is standalone, so you no longer need ISO 27001 to certify it. You need ISO 27001 when buyers ask how you secure their data, and ISO 27701 as well when they ask how you handle personal information as a controller or processor. If you need both, run them as one integrated system with a combined audit.

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:2022ISO/IEC 27701:2025
Management systemInformation security management system (ISMS)Privacy information management system (PIMS)
What it protectsAll information in scopePersonal information (PII) and the privacy of the people it is about
Risk focusConfidentiality, integrity and availability; risks to the organisationPrivacy risks, including risks to individuals
Controls93 Annex A controls in four themesAnnex A in three tables: PII controller, PII processor, and shared information security controls
Roles that matterAsset and risk ownersWhether you are a PII controller, a PII processor or both
PrerequisiteNoneNone since 2025 (the 2019 edition required an ISMS)
CertificationAccredited certification body, three-year cycleAccredited certification body, three-year cycle; bodies assessed against ISO/IEC 27706
Legal linkSupports APP 11 security obligationsMaps to the wider APPs and GDPR, including rights, notice, use and transfers
Who asks for itMost enterprise and government buyersBuyers 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 obligationWhere a PIMS addresses it
APP 1: open and transparent management, privacy policyPIMS policy, roles, records of processing, privacy notices
APPs 3 and 5: collection and notificationPurpose identification, collection limitation, notice controls
APP 6: use and disclosurePurpose limitation, disclosure records, processor instructions
APP 8: cross-border disclosureTransfer and sub-processor controls
APP 11: security, destruction and de-identificationInformation security controls, retention and disposal controls
APPs 12 and 13: access and correctionProcesses for handling individuals’ requests
Notifiable Data Breaches schemePrivacy 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 situationWhat to do
Buyers ask about security onlyISO 27001. Build it so personal information is in the asset inventory and risk register
You hold ISO 27001 and privacy questions are slowing dealsAdd ISO 27701 as an extension of your existing system
You are starting from nothing and process lots of customers’ personal informationBuild both together and certify in one combined audit
Buyers want privacy assurance but not a security certificateISO 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 certificatePlan 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.

FAQ

Common questions

Do I need ISO 27001 to get ISO 27701?

Not under the 2025 edition. ISO/IEC 27701:2019 was an extension to ISO 27001, so you needed an ISMS underneath it. ISO/IEC 27701:2025, published in October 2025, is a standalone management system standard with its own clauses and information security controls, so it can be certified on its own. If you already hold ISO 27001, the two integrate easily.

What is the difference between ISO 27001 and ISO 27701?

ISO 27001 manages risks to all information in scope: its confidentiality, integrity and availability. ISO 27701 manages how you process personal information (PII) and the privacy risks to the people it is about, with controls for PII controllers and PII processors. Security is part of privacy, but privacy also covers purpose, consent, transparency, individuals’ rights, retention and transfers.

What happens to ISO 27701:2019 certificates?

They remain valid during a transition period. UKAS, following a consensus of the IAF working group, has set 31 October 2028 as the date by which certified organisations must have transitioned to the 2025 edition. Other accreditation bodies set their own arrangements, so confirm the date and the transition audit approach with your certification body.

Does ISO 27701 certification mean we comply with the Privacy Act or GDPR?

No. ISO 27701 is a management system standard, not a legal compliance scheme, and it is not a GDPR certification mechanism under Article 42. It gives you an audited way to run the practices those laws expect, and its Annex D maps the standard to GDPR, but legal compliance still has to be assessed against the law itself.

Can ISO 27001 and ISO 27701 be audited together?

Yes. Both follow the harmonised management system structure, so a certification body accredited for both can audit them in a combined audit and issue two certificates. Shared clauses such as internal audit and management review are audited once, but the privacy-specific clauses and controls still need their own audit time.

Talk to someone who has taken companies like yours to audit.

Book a free 30-minute consultation. Tell us what is driving the need, and leave with a realistic timeline and the first three things to do.