ISO Standards

ISO 27701 vs ISO 27001: When You Need Both

ISO 27701 vs ISO 27001: When You Need Both
In short

ISO 27001 covers information security management, while ISO 27701 covers privacy information management, focused on personal data and the roles of controller and processor. Since the 2025 edition, ISO 27701 is a standalone standard and no longer needs ISO 27001 first. Choose by what customers ask, then consider both together because they overlap strongly.

In this article
  1. ISO 27701 vs ISO 27001: what is the difference?
  2. When do you need ISO 27001 only?
  3. When do you need ISO 27701?
  4. When should you have both?
  5. How do you build both without duplicating work?
  6. Frequently asked questions

ISO 27701 vs ISO 27001 is a common question for companies that handle personal data and want a recognised way to show they protect it. The two standards are closely related, but they answer different questions. One is about information security. The other is about privacy. Since late 2025, you can also certify to one without the other.

ISO/IEC 27001 sets requirements for an information security management system (ISMS), which protects the confidentiality, integrity and availability of information of all kinds. ISO/IEC 27701:2025 sets requirements for a privacy information management system (PIMS), which manages the processing of personal data and the rights of the people it concerns. The 2025 edition was published in October 2025 and is a standalone standard. The 2019 edition was an extension of ISO 27001, which is why older articles still describe it that way.

ISO 27701 vs ISO 27001: what is the difference?#

PointISO 27001ISO 27701:2025
FocusInformation security across the organisationPrivacy and personal data processing
ProtectsAll information assetsPersonal data and the people it relates to
RolesNot role-specificGuidance for controllers and processors
Risk viewRisks to the organisation's informationRisks to individuals as well as to the organisation
Key recordsRisk register, Statement of Applicability, security recordsRecords of processing, privacy notices, rights requests, impact assessments
PrerequisiteNoneNone since the 2025 edition

The simplest way to see the difference is to look at who is protected. In ISO 27001, the organisation decides what matters and protects it. In ISO 27701, the focus moves to the individuals whose data you process: their rights, their expectations and the harm they could suffer. This shift changes the risk assessment, the records you keep and the questions an auditor asks.

When do you need ISO 27001 only?#

ISO 27001 is enough when your customers ask for information security assurance and personal data is a small or incidental part of what you handle. A manufacturing company that mainly protects designs and business data, or an IT services company whose clients ask about security controls, may start there. The standard still requires you to consider legal and contractual duties, including those on personal data, but it does not build a full privacy management system.

When do you need ISO 27701?#

ISO 27701 fits when personal data is central to your business, and customers, regulators or partners want evidence of privacy management. Examples include data processors that handle customer records for others, healthcare, education and fintech businesses, marketing and analytics firms and software companies with large user bases. In India, a PIMS can support your response to the Digital Personal Data Protection Act, and for exports it supports duties under laws such as the GDPR. A certificate does not by itself prove legal compliance, but it gives a structured system for managing it.

Under the 2025 edition, a company with a strong privacy focus but no need for a full security certificate can certify to ISO 27701 alone. That helps smaller processors and firms whose customers ask specifically about privacy.

Procurement teams often ask which certificate is better. Neither is better in general. Ask your buyers. Some enterprise customers in regulated sectors request both, and some ask only for security assurance. A short conversation with a few customers will tell you which one earns its cost.

When should you have both?#

  • You handle large volumes of personal data and also need to show strong security.
  • Customers ask for both a security certificate and privacy assurance.
  • You want one integrated management system with shared routines.
  • You operate in several jurisdictions with different privacy laws.

The two standards overlap strongly. Leadership, risk method, document control, training, internal audit, management review and many controls such as access control, logging and incident response serve both. If you build them together, you share work and may share audit time.

Be careful about scope. If the PIMS covers personal data processing in services that sit outside the ISMS scope, you will need to cover the supporting security there too. Plan the scopes together, and keep the boundaries clear in your documents, so the certification body can see which services and data flows each certificate covers.

How do you build both without duplicating work?#

  1. Decide the scope for each, and align them where you can.
  2. Use one management system structure and one set of core processes.
  3. Add privacy-specific content: records of processing, lawful basis and purpose records, privacy notices, rights handling and privacy impact assessments.
  4. Extend the risk assessment to cover risks to individuals.
  5. Define whether you act as controller, processor or both, and apply the matching guidance.
  6. Train staff on security and privacy together.
  7. Ask your certification body about combined audits.

Our ISO 27701 toolkit offers editable documents and a gap assessment checklist for a privacy information management system, with one year of e-mail support and a free upgrade within 6 months. If you want guided help, see our ISO 27701 consulting in India. If you need the security side too, you can read about ISO 27001. No one can promise an audit result, because the certification body decides.

Finally, check the current status of the standard with your certification body. The 2025 edition is recent, and certification rules, transition dates and the way bodies combine audits are still settling. A short email now can save a surprise later.

Frequently asked questions#

Is ISO 27701 an add-on to ISO 27001?#

It was under the 2019 edition. The 2025 edition is a standalone standard, so ISO 27001 is no longer a prerequisite, although many organisations hold both.

Does ISO 27701 make us compliant with privacy laws?#

No. It helps you build a system that supports compliance, but laws have their own legal tests. Take legal advice for your duties.

What happens to certificates to the 2019 edition?#

They remain valid for now. Ask your certification body for its transition plan and dates.

For the full guide to the privacy standard read our complete guide to ISO 27701 or contact AdWiser.

Found this useful?

Share it with your network, and follow AdWiser Enterprise Consulting on LinkedIn for more certification guides and compliance tips.

Share:

Leave a Comment

Comments are reviewed before they appear. Please keep them relevant and leave out web links.

Ready to put this into practice?

Start with the ISO 27701:2025 Toolkit and adapt it to your organisation, or talk to us about implementation support.

Chat on WhatsApp