Cybernion
← Insights

ISO 27001

ISO 27001 vs ISO 27017 and ISO 27018

4 Sept 2026 · Updated 4 Sept 2026

ISO 27001 certifies the management system. ISO 27017 and ISO 27018 are extensions to that same system, not separate certifications. ISO 27017 adds cloud specific security controls split by provider and customer role. ISO 27018 adds controls for protecting personal data a cloud provider processes on a customer’s behalf. Neither works without ISO 27001 underneath it.

The current edition of ISO 27018 is ISO 27018:2025, which aligns to the ISO 27002:2022 controls and adds a new Annex B. It stayed an extension to ISO 27001. For anyone wanting a standalone privacy certification instead, that is now ISO 27701:2025, which no longer requires ISO 27001.

Cloud buyers increasingly ask for all three certificates in the same sentence, and vendors sometimes list them as if they were three separate achievements. They are one achievement with two cloud specific add ons.

What is the difference between ISO 27001 and ISO 27017?

ISO 27001 is generic. It applies to any organisation, cloud or not, and its Annex A controls do not name cloud specific risks such as shared infrastructure, virtual machine isolation, or the split of responsibility between a cloud provider and its customers. ISO/IEC 27017:2015, Code of practice for information security controls based on ISO/IEC 27002 for cloud services, fills that gap. It maps to the same control structure as ISO 27002, adds cloud specific implementation guidance to existing controls, and introduces additional controls that only apply in a cloud context, such as who is responsible for removing data when a customer leaves a service, and how virtual environments are configured and monitored. Notably, ISO 27017 marks each control as either the cloud service provider’s responsibility, the cloud service customer’s responsibility, or shared, which most general standards do not do.

What is the difference between ISO 27001 and ISO 27018?

ISO/IEC 27018, Code of practice for protection of personally identifiable information (PII) in public clouds acting as PII processors, now at its 2025 edition, targets a narrower problem again: how a cloud provider that processes personal data on behalf of a customer should protect it. ISO 27001’s Annex A does not single out personal data as a category, and privacy is addressed more directly in ISO/IEC 27701, the privacy information management standard, which became standalone in its 2025 edition. ISO 27018 falls between the two, cloud specific and privacy specific at once, and applies specifically to providers acting as a processor, meaning they handle personal data under a customer’s instructions rather than deciding how it is used themselves.

Can we get ISO 27017 or ISO 27018 without ISO 27001?

No. Both are extensions, sometimes called code of practice standards, written to be read alongside ISO 27002 and applied to an existing ISMS built to ISO 27001. A certification body assesses an organisation for these extensions using the ISO 27001 audit as the base, adding the extra cloud or privacy specific controls, and typically issues either an extended scope statement on the same certificate or a companion certificate that references the underlying ISO 27001 certification. There is no independent Stage 1 and Stage 2 audit cycle for ISO 27017 or ISO 27018 in isolation.

How do ISO 27017 and ISO 27018 split provider and customer responsibility?

This split is the practical value of ISO 27017 in particular. Traditional Annex A controls describe a single organisation’s responsibility. Cloud services always involve two parties: the provider running the infrastructure or platform, and the customer configuring and using it. ISO 27017 attaches guidance to each control noting which party typically owns it, for example the provider owns physical data centre security while the customer owns access control configuration within their tenancy. This matters for anyone reading a provider’s ISO 27017 certificate: it tells a customer what the provider has covered, not what the customer still needs to configure and secure on its own side.

Should an Australian SaaS provider pursue ISO 27017 and ISO 27018 alongside ISO 27001?

It depends on the buyer, in the same way ISO 27001 versus SOC 2 depends on which market is asking. A base ISO 27001 certificate is enough for most commercial buyers. Government tenders, health, financial services, and enterprise customers handling sensitive personal data increasingly name ISO 27017 or ISO 27018 specifically, particularly for services marketed as cloud native. Cybernion’s ISO 27001 readiness work scopes these extensions in alongside the base ISMS build when a client’s target market calls for them, rather than treating them as a later bolt on, because the control mapping and Statement of Applicability are easier to extend from day one than to retrofit. See ISO 27001 for SaaS for the broader picture.

Dimension ISO 27001 ISO 27017 ISO 27018
Scope General information security management system Cloud specific security controls Personal data protection in the cloud
Stands alone Yes, base certifiable standard No, extends ISO 27001 No, extends ISO 27001
Key addition Clauses 4 to 10 plus 93 Annex A controls Provider and customer responsibility split for cloud controls Controls for processing personal data as a cloud processor
Typical adopter Any certified organisation Cloud service providers and platforms Cloud providers handling personal data on a customer’s behalf
Relation to privacy law Not privacy specific Not privacy specific Supports privacy obligations, does not replace them

Frequently asked questions

Do we need ISO 27001 before adding ISO 27017 or ISO 27018?

Yes. Both are extensions written against an existing information security management system. A certification body audits them alongside, or after, an ISO 27001 audit, using the same management system as the base. Neither stands alone as a certifiable scheme.

What is the difference between ISO 27017 and ISO 27018?

ISO 27017 covers cloud specific security controls, split between what the cloud provider owns and what the customer owns. ISO 27018 covers the protection of personally identifiable information a cloud provider processes on behalf of its customers, acting as a data processor.

Does a cloud customer need ISO 27017 or only a cloud provider?

Mostly providers pursue certification, because the standard defines both provider and customer responsibilities and providers use certification to demonstrate their side is covered. Customers rely on the provider’s certificate rather than seeking their own.

Is ISO 27018 the same as GDPR or the Australian Privacy Act?

No. ISO 27018 is a code of practice for protecting personal data in the cloud, and it can support privacy compliance, but it does not replace a jurisdiction’s privacy law. It maps well against, but is not a substitute for, obligations under the Privacy Act or GDPR.

Do most Australian SaaS providers need these certifications?

Only if the market demands it. Government and enterprise buyers increasingly ask for ISO 27017 and ISO 27018 alongside ISO 27001, particularly for cloud services touching personal or sensitive data, but a base ISO 27001 certificate covers the general case.

Sources:

  1. ISO/IEC 27001:2022, Information security management systems, requirements, ISO, 2022
  2. ISO/IEC 27017:2015, Code of practice for information security controls based on ISO/IEC 27002 for cloud services, ISO, 2015
  3. ISO/IEC 27018:2019, Code of practice for protection of PII in public clouds acting as PII processors, ISO, 2019

Last updated: 4 September, 2026

Related serviceISO 27001 ReadinessSee the service →

Talk to us about your engagement

A scoped proposal within one business day.