Skip to main content
ISO 27001

ISO 27001 vs ISO 27701: Differences and Which You Need

Published
Last updated
ISO 27001
Two linked shields, one with a padlock and one with a person and a fingerprint, connected to a document and a database, representing ISO 27001 security and ISO 27701 privacy

ISO 27001 and ISO 27701 are often mentioned together, and more buyers now ask for both. They are related, but they solve different problems: one manages information security, the other manages privacy. This guide compares them, explains what changed with the 2025 edition of ISO 27701, how both relate to GDPR and India's DPDP Act, and how to run them together. For hands-on help, see our ISO 27001 consulting and ISO 27701 consulting pages.

What is the difference between ISO 27001 and ISO 27701?

ISO 27001 sets requirements for an information security management system (ISMS) that protects all kinds of information. ISO 27701 sets requirements for a privacy information management system (PIMS) that governs how personal data is processed, including your role as a controller or processor. Security protects the data; privacy governs whether and how you use it.

A simple way to see it: ISO 27001 asks "is this customer database protected?" ISO 27701 also asks "should we hold this data at all, for how long, on what basis, and can we answer the person it belongs to?"

ISO 27001ISO 27701
Management systemInformation security management system (ISMS)Privacy information management system (PIMS)
ProtectsAll information: customer, financial, intellectual property, personalPersonal data and the rights of the people it belongs to
Risk focusRisks to confidentiality, integrity and availability of informationPrivacy risks, including risks to individuals
Controls93 Annex A controls in four themesPrivacy controls for organisations acting as controllers and processors
CertificationBy an accredited certification bodyBy an accredited certification body, on its own or alongside ISO 27001 since 2025
Usual triggerCustomer security questionnaires, tenders, partner requirementsCustomers asking how you govern personal data, processor contracts, privacy laws

Can ISO 27701 be certified without ISO 27001?

Yes, since the 2025 edition. ISO/IEC 27701:2025 is a standalone privacy information management standard, so it can be certified on its own or alongside ISO 27001. Under the 2019 edition, ISO 27701 was an extension to ISO 27001 and could only be certified together with an ISO 27001 information security management system.

If you already hold ISO 27701:2019, read ISO 27701:2025 vs 2019: key changes to plan your transition.

Which one do you need?

Start from what your customers and regulators ask for. Choose ISO 27001 if buyers want evidence of information security. Add ISO 27701, or choose it on its own, if you process significant personal data and customers ask how you govern privacy. Many companies that handle customer personal data end up with both, run as one system.

Some practical pointers:

  • You sell software or IT services and get security questionnaires. Start with ISO 27001; it is the one most often asked for.
  • You process personal data on behalf of many clients. Consider ISO 27701 as a processor alongside ISO 27001, because clients will ask how you handle their data.
  • Your business is built on personal data, such as health, HR or consumer services. Plan for both from the start, so you build one system instead of two.
  • Privacy is the only question customers ask. Since 2025, ISO 27701 on its own is an option, but check that your customers will accept it without ISO 27001.

How do ISO 27001 and ISO 27701 relate to GDPR and the DPDP Act?

Neither standard is a law, and certification does not by itself prove you comply with GDPR or India's Digital Personal Data Protection Act. ISO 27701 gives you a management system for privacy, with roles, records and controls that help you meet and evidence legal duties. ISO 27001 supports the security safeguards both laws expect.

In practice, a PIMS helps you organise the work these laws require: knowing what personal data you hold and why, handling requests from individuals, managing processors and responding to breaches. The legal analysis still has to be done against the law itself. See our pages on GDPR and the DPDP Act for what each requires.

What can you share when you do both?

Most of the management system can be shared. ISO 27001 follows the same high-level structure as other ISO management system standards, and ISO 27701:2025 is designed to sit alongside ISO 27001 in an integrated management system. That means you can usually run one set of these processes:

  • scope and context, extended to cover personal data processing
  • leadership, roles and responsibilities, including a named privacy lead
  • the risk method, extended to privacy risks and risks to individuals
  • document control and records
  • competence and awareness training
  • incident management, extended to personal data breaches
  • supplier management, extended to processors and sub-processors
  • internal audit and management review
  • nonconformity and corrective action

What stays privacy-specific?

The work that concerns personal data itself stays privacy-specific: knowing what personal data you process and why, deciding whether you act as controller or processor, handling requests from individuals, and setting retention and deletion rules. ISO 27001 does not ask for these, so they are new work even if your ISMS is mature.

In more detail, a PIMS adds:

  • an inventory of personal data and processing activities
  • deciding, for each activity, whether you act as a controller or a processor
  • the basis for processing, privacy notices and consent where it applies
  • handling requests from individuals to access, correct or delete their data
  • retention and deletion rules for personal data
  • privacy by design in new products and changes
  • privacy terms in contracts with customers and processors

Common mistakes when combining the two

  • Treating privacy as a security add-on, so the personal data inventory never gets built.
  • Writing a second set of policies that repeats the ISMS instead of extending it.
  • Leaving controller and processor roles undecided for some processing activities.
  • Extending incident management to breaches on paper, without testing it.
  • Assuming certification settles legal questions that need advice on the law itself.

A practical order of work

  1. Confirm what customers and regulators actually require.
  2. Map personal data and processing activities, and your role in each.
  3. Set one scope that covers both standards, or ISO 27701 alone.
  4. Extend the risk method to privacy risks.
  5. Write or extend policies and procedures, avoiding duplicate documents.
  6. Implement the security and privacy controls.
  7. Run one internal audit and one management review covering both.
  8. Book a combined audit with a certification body that is accredited for both standards.

How CyberWave GRC helps

We usually run ISO 27001 and ISO 27701 as one management system, so you write one set of shared documents and go through one internal audit and management review. We map your personal data, set your controller and processor roles, and link the work to GDPR and DPDP where they apply. Our fee is fixed, end to end, including the audit, quoted after a free scoping call. An accredited certification body audits you and issues the certificates; we never issue certificates ourselves.

Frequently asked questions

Not harder, but different. ISO 27701 needs you to understand how personal data flows through your business, your role as controller or processor, and the rights of the people whose data you hold. Companies that already run ISO 27001 usually find the management system parts familiar and spend most effort on privacy-specific work.

Often, yes. Many accredited certification bodies can audit ISO 27001 and ISO 27701 together in a combined audit when the two systems share processes such as internal audit and management review. Check that your certification body is accredited for both standards and ask how it plans the combined audit.

No. ISO 27701 certification shows an accredited certification body has audited your privacy information management system against the standard. It helps you organise and evidence privacy work, but GDPR compliance depends on meeting the regulation itself, including lawful bases, individuals' rights and breach notification. Treat certification as supporting evidence, not proof.

Add it if customers ask how you govern personal data, if you act as a processor for many clients, or if you are preparing for GDPR or DPDP obligations. You can reuse your ISMS scope, risk method, internal audit and management review, so the extra work focuses on privacy-specific processes and controls.
Hi! I'm your AI Assistant 💬