Framework · Cloud privacy · Code of practice
ISO 27018 cloud privacy: PII protection controls for public cloud providers
ISO/IEC 27018 is a code of practice for protecting personal data (PII) in public clouds that act as PII processors. The 2019 edition adds cloud privacy guidance to ISO/IEC 27002 controls plus an extended set of controls based on ISO/IEC 29100 privacy principles. It is usually certified as an extension of ISO 27001.
What you need to know about ISO 27018
Who needs ISO 27018?
It is voluntary, but common for cloud providers handling personal data.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does ISO 27018 require?
ISO 27018 asks public cloud PII processors to apply ISO 27002 controls with privacy guidance and implement extended controls on consent, purpose, disclosure, breach notification, sub-processing, data location and return of data.
Purpose limitation
Process PII only for the customer's purposes; no advertising use.
In QULDEX: Instructions linked to processingTransparency
Tell customers about disclosures and sub-processors.
In QULDEX: Disclosure and sub-processor logsAccountability
Notify customers of PII breaches promptly.
In QULDEX: Breach log with notificationsInformation security
Encryption, user IDs, restoration logging, media.
In QULDEX: Controls mapped to ISO 27001Privacy compliance
Disclose where PII is stored.
In QULDEX: Data location registerReturn and disposal
Return or delete PII at contract end.
In QULDEX: Exit procedure trackedCertification
Audited with ISO 27001 by an accredited body.
In QULDEX: Evidence shared with the auditorWhat are the ISO 27018 controls?
ISO 27018 adds 25 extended controls for public cloud PII processors, grouped by ISO/IEC 29100 privacy principle. Select any control to see what it asks for and typical evidence.
Showing up to 6 per group. Search, filter, or open a group to see all 25.
Consent and choice 1
PII 01Obligation to cooperate regarding PII principals' rightsHelp the customer respond to people exercising their rights over their data.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Request support records
- Maps to
- GDPR Art. 28(3)(e)
Purpose legitimacy 2
PII 02Public cloud PII processor's purposeProcess PII only for the customer's instructed purposes.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Processing instructions
PII 03Public cloud PII processor's commercial useDon't use customer PII for marketing or advertising without consent.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Commercial use policy
Data minimisation 1
PII 04Secure erasure of temporary filesErase temporary files and documents within a defined period.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Erasure configuration
Use, retention and disclosure 2
PII 05PII disclosure notificationTell the customer about legally binding requests to disclose PII, unless prohibited.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Disclosure request log
PII 06Recording of PII disclosuresRecord disclosures of PII to third parties.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Disclosure records
Openness and transparency 1
PII 07Disclosure of sub-contracted PII processingTell customers about sub-processors before they are used.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Sub-processor list
- Maps to
- GDPR Art. 28(2)
Accountability 3
PII 08Notification of a data breach involving PIINotify the customer promptly of breaches involving their PII.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Breach notification records
- Maps to
- GDPR Art. 33(2)
PII 09Retention of administrative security policiesKeep copies of security policies and procedures for a defined period.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Retention schedule
PII 10PII return, transfer and disposalHave a policy for returning, transferring or disposing of PII when the contract ends.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Exit procedure, disposal records
Information security 13
PII 11Confidentiality or non-disclosure agreementsBind people with access to PII to confidentiality.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Signed NDAs
- Maps to
- ISO 27001 A.6.6
PII 12Restriction of the creation of hardcopy materialLimit printing or hardcopy of PII.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Print controls
PII 13Control and logging of data restorationLog data restoration activities.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Restore logs
- Maps to
- ISO 27001 A.8.13
PII 14Protecting data on storage media leaving the premisesProtect PII on media that leaves your premises.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Media handling records
- Maps to
- ISO 27001 A.7.10
PII 15Use of unencrypted portable storage mediaAvoid unencrypted portable media and devices for PII.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Device encryption policy
PII 16Encryption of PII over public networksEncrypt PII transmitted over public data networks.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- TLS configuration
- Maps to
- ISO 27001 A.8.24
PII 17Secure disposal of hardcopy materialsDispose of hardcopy PII securely.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Shredding records
PII 18Unique use of user IDsGive each user a unique ID for accessing PII.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- User ID policy
- Maps to
- ISO 27001 A.5.16
PII 19Records of authorized usersKeep an up-to-date record of users with access to PII.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Access register
PII 20User ID managementDon't reassign de-activated or expired user IDs.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- User ID procedures
PII 21Contract measuresEnsure contracts with customers cover the processor's PII protection measures.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Customer contracts
PII 22Sub-contracted PII processingHold sub-processors to the same protection obligations by contract.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Sub-processor contracts
PII 23Access to data on pre-used storage spaceMake sure data on reused storage space isn't visible to the next user.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Storage sanitisation design
Privacy compliance 2
PII 24Geographical location of PIITell customers the countries where PII may be stored.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Data location register
- Maps to
- GDPR Art. 44
PII 25Intended destination of PIIMake sure PII sent over networks reaches its intended destination.
In QULDEXQULDEX holds this control with owners and evidence, and reuses it for ISO 27701, GDPR and DPDP processor duties.
- Typical evidence
- Routing and delivery controls
Nothing matches that search.
Control names follow ISO/IEC 27018:2019 Annex A; the "PII nn" IDs are QULDEX numbering, not the standard's. Summaries are QULDEX paraphrases.
How do you get ISO 27018 certified?
Add ISO 27018 to your ISO 27001 scope: map PII processing, implement the extended controls, update the Statement of Applicability, and the certification body audits them together. With ISO 27001 in place, 2 to 4 months is common.
Map PII processing for customers
List services that process customer PII, data categories, locations and sub-processors.
Gap assessment against the extended controls
Compare current practice with the 25 controls and privacy guidance.
Implement controls and update contracts
Close gaps and make sure customer and sub-processor contracts carry the obligations.
Update the SoA and internal audit
Add 27018 controls to the SoA and audit them internally.
Certification audit with ISO 27001
The certification body audits 27018 controls with the ISMS.
Keep it running
Year 1SurveillanceYear 2SurveillanceYear 3Recertification
Durations are typical planning ranges from QULDEX audit delivery.
What documents does ISO 27018 need?
Customers and auditors ask for these to see how you handle their personal data.
| Document | Control | Where it lives in QULDEX |
|---|---|---|
| Sub-processor list | PII 07 | Vendor register |
| Data location register | PII 24 | Evidence vault |
| Disclosure request and disclosure records | PII 05–06 | Evidence vault |
| Breach notification procedure and records | PII 08 | CAPA automation |
| Return, transfer and disposal procedure | PII 10 | Evidence vault |
| Customer contract privacy terms | PII 21 | Vendor register |
| Records of authorised users | PII 19 | Control library |
| Statement of Applicability with 27018 controls | ISO 27001 6.1.3 | Control library (generated) |
Control references use QULDEX numbering shown in the explorer.
How long does ISO 27018 take?
With an ISO 27001 ISMS in place, adding 27018 usually takes 2 to 4 months. Effort depends on how many services process PII and how many sub-processors you use.
Where the time goes
Bars show the upper end of each range on one scale (4 months = full width).
What changes the effort
- Services with PII: each needs mapping and controls
- Sub-processors: each needs contract terms and disclosure
- Data locations: more regions mean more transparency work
- Existing ISO 27001 and 27701: shared controls cut effort
- Customer contracts: privacy terms may need renegotiation
How ready are you for ISO 27018?
Auditors and customers check these eight things first. Nothing you enter leaves this page.
How ISO 27018 maps to GDPR, ISO 27701 and ISO 27017
ISO 27018 controls support GDPR processor obligations and overlap with ISO 27701 processor controls. QULDEX keeps the mapping so one evidence set supports all of them.
ISO 27018 vs ISO 27701
| ISO 27018 | ISO 27701 | |
|---|---|---|
| Type | Code of practice for cloud PII processors | Privacy management-system standard |
| Scope | Public cloud processing PII for customers | Any controller or processor |
| Certification | Extension of ISO 27001 | Standalone since 2025, or integrated |
| Depth | Controls for processors | Full management system with controller and processor controls |
| Use together | Yes; 27018 adds cloud-specific detail | Yes |
| In QULDEX | QULDEX maps 27018 controls to ISO 27701 processor controls so evidence is shared. | |
Privacy crosswalk
| ISO 27018 | GDPR | ISO 27701 | DPDP Act | Shared evidence |
|---|---|---|---|---|
| PII 01 Rights support | Art. 28(3)(e) | Processor: support customer obligations | Sec. 8(2) | Request support |
| PII 02 Purpose | Art. 28(3)(a) | Processor: instructions | Sec. 8(2) | Instructions |
| PII 07 Sub-processors | Art. 28(2) | Processor: subprocessors | — | Sub-processor list |
| PII 08 Breach | Art. 33(2) | Processor: breach notification | Sec. 8(6) | Breach records |
| PII 10 Return and disposal | Art. 28(3)(g) | Processor: return or delete | Sec. 8(7) | Exit records |
| PII 16 Encryption | Art. 32 | Security for PII | Sec. 8(5) | TLS settings |
| PII 24 Location | Art. 44–49 | Transfers | Sec. 16 | Location register |
Indicative mapping for planning, not legal advice. The full crosswalk is in the QULDEX control library.
How QULDEX runs ISO 27018 for cloud providers
QULDEX is ISO 27018 cloud privacy compliance and audit management software built from EGV Group's audit delivery, used by cloud providers and the auditors who test them. Pick your role to see who does what.
For public cloud providers processing customer PII.
- MappingMap PII processingServices, data and locations linked
- GapsAssess controls25 controls with owners
- ContractsUpdate contractsCustomer and sub-processor terms tracked
- SoAUpdate the SoASoA generated with 27018 rows
- AuditHost the auditorControlled, logged evidence sharing
- CustomersAnswer due diligenceSecure links to certificates and lists
For DPOs and privacy consultants.
- MappingRun the gap assessmentA reusable 27018 template
- GapsReview controlsReview and approval states
- ContractsReview DPAsContract status per customer
- SoACheck the SoAGaps flagged per control
- AuditPrepare the clientAn audit-ready pack
- CustomersAnswer questionnairesAnswers linked to evidence
For accredited bodies auditing ISO 27001 with 27018.
- PlanningExtend the audit plan27018 scope in a standard format
- Stage 1Review documentsPolicies and contracts reviewed
- Stage 2Sample evidenceView-only evidence access with download control and an access log
- FindingsGrade nonconformitiesFindings per control
- DecisionCertifyA traceable audit record
- SurveillanceReturn each yearHistory across the cycle
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →ISO 27018 questions people ask
What is ISO 27018?
ISO/IEC 27018 is a code of practice for protecting personal data in public clouds that act as PII processors for their customers.
Who should use ISO 27018?
Public cloud providers, including SaaS, PaaS and IaaS, that process personal data on behalf of customers.
Can you get ISO 27018 certified on its own?
Not usually. It is certified as an extension of ISO 27001, with 27018 controls added to the ISMS scope and Statement of Applicability.
What is the difference between ISO 27018 and ISO 27701?
ISO 27018 is a code of practice for cloud PII processors. ISO 27701 is a full privacy management-system standard for controllers and processors.
Does ISO 27018 help with GDPR?
Yes. Its controls support GDPR Article 28 processor obligations, such as acting on instructions, sub-processor transparency and breach notification.
What is the difference between ISO 27017 and ISO 27018?
ISO 27017 covers cloud security; ISO 27018 covers protection of personal data by cloud processors. They are often certified together.
Can QULDEX run ISO 27018 with ISO 27001 and 27701?
Yes. 27018 is held as an extension of ISO 27001 and mapped to ISO 27701, so evidence is shared.
Go deeper on ISO 27018
Data privacy topic hub
GDPR, ISO 27701 and privacy-law comparisons.
blog.quldex.comISO 27001 topic hub
Including the ISO 27017 and 27018 cloud extensions.
blog.quldex.comDPDP Rules 2025: the compliance timeline
Processor duties under India's rules.
blog.quldex.comAudit evidence naming convention
A file-naming scheme that lets auditors sample without asking.
References
- ISO/IEC 27018:2019, Code of practice for protection of PII in public clouds acting as PII processors. iso.org
- ISO/IEC 29100:2024, Privacy framework. iso.org
- ISO/IEC 27001:2022. iso.org
- ISO/IEC 27701:2025. iso.org
- Regulation (EU) 2016/679 (GDPR), Article 28. eur-lex.europa.eu
Reviewed by
Page history
- : Rebuilt with the 25 extended controls, certification as an ISO 27001 extension, privacy crosswalk and readiness check
- : Page first published
Find your ISO 27018 gaps in 15 minutes
Answer a short readiness check and get a gap summary by control. No sales call needed to see the result.