Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
ISO/IEC 27018 is the code of practice for protecting personally identifiable information in public clouds, setting out what a cloud provider acting as a processor should do.

What Is ISO/IEC 27018?
ISO/IEC 27018 was the first international standard written specifically about privacy in public cloud computing. First published in 2014 and revised in 2019, it is a code of practice setting out the measures a public cloud provider should implement when it processes personally identifiable information on behalf of its customers.
The framing matters. The standard addresses the provider in the role of processor, acting on the customer’s instructions. The customer remains the controller and keeps the accountability that goes with that, which is precisely the division UK GDPR Article 28 depends on.
Most of the document extends ISO/IEC 27002 controls with privacy-specific guidance. The provisions that change supplier behaviour most are these.
ISO/IEC 27018 is not a certification of GDPR compliance, and no provider should claim otherwise. It predates the GDPR and was not designed against it.
What it does is supply evidence. Article 28(1) requires controllers to use only processors providing sufficient guarantees of appropriate technical and organisational measures. A certificate referencing 27018, alongside ISO 27001, is one of the recognised ways a provider demonstrates those guarantees. Article 28(3) obligations still have to appear in the contract itself: documented instructions, confidentiality, security, subprocessor authorisation, assistance with data subject rights, deletion or return, and audit rights.
For privacy management specifically, ISO/IEC 27701 is the more complete answer, because it extends the management system itself to cover privacy rather than addressing one deployment model.
Like ISO/IEC 27017, this standard is not independently certifiable. It is audited as an extension to an ISO/IEC 27001 scope, and the certificate names both. The major hyperscalers and most enterprise SaaS providers hold it, usually combined with 27001, 27017, and a SOC 2 report.
When reviewing a supplier’s certificate, check three things: that 27001 underlies it, that the scope statement covers the service you are buying rather than a different product line, and that the certification body is accredited. A certificate covering “corporate IT services” tells you nothing about the platform holding your customer records.
The practical approach is to treat the standard as a question list rather than a tick box. Ask the provider to show how each of the areas above is implemented for your service: what instructions mechanism exists, what the subprocessor notification period is, how deletion on termination is evidenced, which countries data is processed in, and what the breach notification timeline to you will be. The last point matters more than buyers usually realise, because your own 72-hour ICO clock under UK GDPR starts when you become aware, and a provider contract permitting notification within an unspecified reasonable period leaves you unable to comply.
Record the answers against the contract terms. Where a SOC 2 report is also available, read the complementary user entity controls alongside this, since the obligations the provider assumes you perform are frequently privacy relevant.
The standard governs the provider’s side of the platform. It says nothing about how you configure the service, who in your organisation holds access, whether you collect more personal data than you need, or whether your lawful basis is sound. Those are controller questions, and no supplier certificate answers them.
Where you need to know whether your own cloud deployment protects the personal data in it, that requires examination of the environment rather than the paperwork. Our cloud security services cover that side of the boundary.
No. The standard predates the GDPR and covers the processor’s measures for personal data in public clouds, not the full set of GDPR obligations. It is useful evidence towards Article 28(1) sufficient guarantees, but the Article 28(3) contract terms, international transfer mechanisms, and the controller’s own accountability all remain separate requirements.
No. It is a code of practice audited as an extension to an ISO/IEC 27001 management system, and certificates reference both standards. Check that the 27001 certification underlies the claim, that the scope statement covers the specific service you are buying, and that the certification body is accredited, UKAS in the UK.
ISO/IEC 27018 is narrow: guidance for public cloud providers acting as processors of personal data. ISO/IEC 27701 is a management system extension covering privacy information management for both controllers and processors, across any deployment model, and is certifiable alongside ISO 27001. Organisations building a privacy programme usually want 27701; cloud buyers assessing a provider look for 27018.
Confirm the underlying ISO 27001 certificate, read the scope statement to ensure it names the service you use rather than another product, and verify the certification body’s accreditation. Then ask service-specific questions the standard raises: subprocessor notification, data location, deletion on termination, and how quickly the provider will notify you of an incident.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.