- ClassificationCategoryData Protection & PrivacyDomainPrivacyFramework FamilyISO 27000 Series
- Regulatory ContextTypeStandardLegal InstrumentStandardSectorTechnology SectorIndustryCloud & Technology Providers
- Region / PublisherRegionGlobalRegion DetailInternationalPublisherInternational Organization for Standardization (ISO) and International Electrotechnical Commission (IEC)
- VersioningVersionThird edition (ISO/IEC 27018:2025); replaces 2019 editionEffective DateAugust 26, 2025Issue DateAugust 26, 2025 (third edition)
- AdoptionAdoption ModelVoluntaryImplementation ComplexityHigh
- Official ReferenceOpen Link in New TabSource
License included / downloadable: No
ISO/IEC 27018:2025 is a paid standard sold by ISO and national standards bodies, and the text is not included with the platform.
Framework text is licensed by its publisher and is included only where stated above.
- ISO/IEC 27018:2025 gives guidelines for protecting personally identifiable information in public clouds acting as PII processors.
- ISO/IEC JTC 1/SC 27 published the third edition on August 26, 2025, replacing the 2019 edition, which ISO withdrew the same day.
- It states guidelines, not conformity requirements, so organizations apply it rather than certify against it.
- Its clause numbers follow ISO/IEC 27002:2022, with public cloud guidance added and an extended control set in Annex A.
- A provider selects controls inside an ISO/IEC 27001-based ISMS and justifies any control it does not select.
Overview
ISO/IEC 27018:2025 is the international standard of guidelines for protecting personally identifiable information (PII) in public clouds acting as PII processors, written for public cloud service providers and used by the customers that assess them. ISO and IEC published this third edition on August 26, 2025, prepared by ISO/IEC JTC 1/SC 27; it cancels and replaces ISO/IEC 27018:2019, which ISO withdrew the same day. It states guidelines, not conformity requirements, so organizations apply it rather than certify against it.
Clause 1 sets control objectives, controls and guidelines in line with the privacy principles of ISO/IEC 29100, based on ISO/IEC 27002:2022 and the regulatory PII requirements that can apply to a public cloud provider. The document follows the 27002:2022 control layout, so its clause numbers match 27002:2022 Clauses 5 to 8, and it adds public cloud guidance to many of those controls plus an extended control set in Annex A (informative). Annex B (informative) maps the layout to the 2019 edition.
A provider implements it by selecting controls inside an information security management system based on ISO/IEC 27001, adding the public cloud PII guidance and the Annex A controls its risks and contracts call for, and justifying any control it does not select (Introduction 0.2 and 0.4). The guidelines can also be relevant to PII controllers (Clause 1).
Why does it matter?
A public cloud provider that processes PII for its customers faces obligations that vary from one jurisdiction to the next, and the split of duties between provider and customer depends on the law and on the contract (Introduction 0.1). ISO/IEC 27018 gives both sides a common set of PII protection controls to select from, so a multinational provider does not rebuild its answer for every market.
Key benefits include:
- A common control set
ISO/IEC 27018 can serve as a common compliance framework for public cloud providers operating in a multinational market (Introduction 0.1).
- Support for the contract
One stated objective is to assist the cloud service customer and the public cloud PII processor in entering into a contractual agreement (Introduction 0.1).
- Transparency for buyers
Another is to let the processor be transparent so customers can select well-governed cloud-based PII processing services (Introduction 0.1).
- A route to audit and compliance rights
It gives customers a mechanism to exercise audit and compliance rights where auditing one customer's data in a multi-party, virtualized environment is technically impractical (Introduction 0.1).
- Clear roles
The text separates the PII controller, the PII processor and the PII principal, so each control has an owner (Clauses 3.3 to 3.5).
How does it work?
The document is built on ISO/IEC 27002:2022 and follows its structure. Clause numbers are aligned with the corresponding 27002:2022 clauses, so controls 5.1 to 5.37 (organizational), 6.1 to 6.8 (people), 7.1 to 7.14 (physical) and 8.1 to 8.34 (technological) appear in the same order. Where a control needs nothing further, the document refers to 27002:2022; where the public cloud context adds something, it gives "Public cloud PII protection implementation guidance" and "Other information for public cloud PII protection" under the control (Clause 4.1).
Table 1 in Clause 4.1 sorts the controls into four groups: public cloud guidance provided, guidance and other information provided, no additional guidance, and guidance together with a cross-reference to Annex A. Annex A (informative) holds the public cloud PII processor extended control set for PII protection, organized in line with the privacy principles of ISO/IEC 29100 (Introduction 0.2). Annex B (informative) gives the correspondence between this edition and ISO/IEC 27018:2019.
Controls are chosen, not assumed. Requirements come from three sources: legal and contractual requirements, risks assessed with ISO/IEC 27005, and corporate policies (Introduction 0.3). Where a provider does not select a control, a justification should be provided, and contracts are expected to state the PII protection responsibilities of the processor, its sub-contractors and the cloud service customer (Introduction 0.4).
Key Elements
- Public cloud PII processor (Clauses 3.5, 3.7)
A public cloud service provider that processes PII on behalf of and in accordance with the instructions of a PII controller, with no processing objectives other than those the customer sets (Introduction 0.1).
- Cloud service customer and PII controller (Clause 3.3)
The customer holds the contract and the authority over the data. It can be a natural person processing their own PII or an organization acting as a PII controller for many PII principals.
- Public cloud PII protection guidance (Clause 4.1)
Implementation guidance added to existing 27002:2022 controls where the public cloud PII context calls for it.
- Control clauses 5 to 8
Organizational, people, physical and technological controls, numbered as in ISO/IEC 27002:2022, including 5.34 Privacy and protection of PII and 8.10 Information deletion.
- Extended control set (Annex A, informative)
Additional controls for public cloud PII protection not covered by 27002, grouped by the ISO/IEC 29100 privacy principles.
- Correspondence with 2019 (Annex B, informative)
A comparison of the 2025 and 2019 control layouts, for organizations that built on the earlier edition.
- Data breach (Clause 3.1)
A compromise of security that leads to accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, protected data.
- Sub-contractors and shared roles (Introduction 0.4)
Responsibilities are split across everyone providing or using the cloud service, and contracts name them.
What does it cover?
ISO/IEC 27018:2025 applies to all types and sizes of organizations, including public and private companies, government entities and not-for-profit organizations, that provide information processing services as PII processors through cloud computing under contract to other organizations (Clause 1). The guidelines can also be relevant to PII controllers. The document does not cover a provider's own use of customer account data, where the provider can act as a PII controller (Introduction 0.1, Note 1).
What are its objectives?
The Introduction gives three objectives and one design intent:
To let the public cloud PII processor be transparent so that cloud service customers can select well-governed cloud-based PII processing services (Introduction 0.1).
To assist the cloud service customer and the public cloud PII processor in entering into a contractual agreement (Introduction 0.1).
To give customers a mechanism for exercising audit and compliance rights in a multi-party, virtualized server environment where auditing individual customer data is impractical (Introduction 0.1).
To extend ISO/IEC 27002 for the distributed nature of the risk and the contract between customer and processor, through implementation guidance and the Annex A control set (Introduction 0.2).
Framework in Context
ISO/IEC 27018 sits beside the standards it depends on. It is based on ISO/IEC 27002:2022, normatively refers to ISO/IEC 27000 and ISO/IEC 22123-1 for terms, and takes its PII definitions from ISO/IEC 29100:2024 (Clauses 2 and 3). The Introduction points to ISO/IEC 27001 for the management system, ISO/IEC 27005 for risk management and ISO/IEC 29134 for privacy impact assessment. ISO/IEC 27701:2025 maps its own controls to ISO/IEC 27018 in its Annex E.
Common Framework Mappings
ISO/IEC 27018 is commonly mapped to the privacy, cloud and security frameworks that overlap with its control set, so one body of evidence can serve several programs.
Mapped frameworks include:
CSA CCM v4
GDPR
ISO 27001:2022
ISO 27002:2022
ISO 27017
ISO 27701
NIST Privacy Framework v1.0
SOC 2
How SmartSuite Supports ISO/IEC 27018:2025
SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.
Use Compliance Management to hold the controls and evidence you select from ISO/IEC 27018, Privacy Management for data inventories, privacy assessments and requests, and Third Party Risk Management for the sub-contractors a processor relies on.
Selected Controls and Justifications
Record which ISO/IEC 27018 and 27002:2022 controls you select, the reason for any you leave out, and the owner of each (Introduction 0.4).
PII Requirements Register
Use Compliance Management to log the legal, contractual and policy requirements for PII that drive your choices (Introduction 0.3).
Processor and Controller Roles
Use Privacy Management to keep data inventories that show which processing you do as a PII processor and which as a PII controller (Introduction 0.1).
Sub-contractor and Supplier Oversight
Use Third Party Risk Management to assess and monitor the sub-contractors and suppliers named in your contracts (Introduction 0.4; Clauses 5.19 to 5.23).
Privacy Assessments and Risk
Run privacy assessments and track the risks and treatments they raise, with approvals and evidence attached (Introduction 0.3).
Audit Evidence and Reporting
Keep an audit trail of control status and open issues that you can share when a customer exercises audit and compliance rights (Introduction 0.1).
Related frameworks

The GDPR (Regulation (EU) 2016/679) sets principles, lawful bases, individual rights and accountability duties for personal data, with fines up to EUR 20 million or 4 percent of turnover.

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

ISO/IEC 27017:2026 gives cloud security control guidance for customers and providers, built on ISO/IEC 27002:2022, with four cloud-specific controls; it replaced the 2015 edition.

ISO/IEC 27701:2025 specifies requirements for a stand-alone privacy information management system (PIMS) for PII controllers and processors, replacing the 2019 edition.
Frequently Asked Questions For ISO/IEC 27018 (Protection of Personally Identifiable Information in Public Clouds)
ISO/IEC 27018 is a set of guidelines, not conformity requirements (Clause 1). It is meant to be used as a reference for selecting PII protection controls within an information security management system based on ISO/IEC 27001, or as guidance on its own (Introduction 0.2). Certification applies to the ISMS, not to ISO/IEC 27018 itself.
Organizations of any type or size that provide information processing services as PII processors through public cloud computing under contract to other organizations (Clause 1). PII controllers can also find the guidelines relevant, although a controller usually carries additional obligations that the document does not specify (Introduction 0.2).
The third edition cancels and replaces ISO/IEC 27018:2019. The Foreword lists two main changes: the text was aligned with ISO/IEC 27002:2022, and Annex B was added to show the correspondence with the 2019 edition. ISO withdrew the 2019 edition on August 26, 2025.
Annex A (informative) is the public cloud PII processor extended control set for PII protection, organized in line with the privacy principles of ISO/IEC 29100 (Introduction 0.2). Because it is informative and Clause 4.1 cross-refers to it, a provider applies the controls its requirements and risks call for and justifies any it leaves out (Introduction 0.4).
No. When a public cloud PII processor handles its customers' account data, it can be acting as a PII controller for that purpose, and the document does not cover that activity (Introduction 0.1, Note 1). The guidelines concern PII the provider processes for and according to the instructions of a cloud service customer.

Put this framework to work in SmartSuite
Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.


