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.

Key takeaways

What you need to know about ISO 27018

ProcessorsIt is written for public cloud providers processing PII for customers.
Customer trustShows customers how you protect their personal data.
Privacy principlesControls follow the ISO/IEC 29100 privacy principles.
Not standaloneCertified as an extension of ISO 27001.
GDPR fitSupports GDPR Article 28 processor obligations.

Who needs ISO 27018?

It is voluntary, but common for cloud providers handling personal data.

SaaS providers with personal dataCustomers want proof you protect their users' data.
Public cloud platformsA recognised privacy assurance for processors.
HR, CRM and marketing platformsHeavy personal data processing.
Providers selling into the EUSupports GDPR processor due diligence.
ISO 27001 and 27017 holdersA natural privacy extension.

QULDEX helps here first: the readiness check shows where you stand before you commit budget.

Code of practice

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 Principle

Purpose limitation

Process PII only for the customer's purposes; no advertising use.

In QULDEX: Instructions linked to processing
Disclosure Principle

Transparency

Tell customers about disclosures and sub-processors.

In QULDEX: Disclosure and sub-processor logs
Breach Principle

Accountability

Notify customers of PII breaches promptly.

In QULDEX: Breach log with notifications
Security Principle

Information security

Encryption, user IDs, restoration logging, media.

In QULDEX: Controls mapped to ISO 27001
Location Principle

Privacy compliance

Disclose where PII is stored.

In QULDEX: Data location register
Exit Contract

Return and disposal

Return or delete PII at contract end.

In QULDEX: Exit procedure tracked
Audit Cert

Certification

Audited with ISO 27001 by an accredited body.

In QULDEX: Evidence shared with the auditor
Extended controls

What 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.

25extended controls
16ISO 27002 controls with privacy guidance
11privacy principles (ISO 29100)
2019current edition

Showing up to 6 per group. Search, filter, or open a group to see all 25.

Consent and choice 1

  1. PII 01Obligation to cooperate regarding PII principals' rights

    Help 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

  1. PII 02Public cloud PII processor's purpose

    Process 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

  2. PII 03Public cloud PII processor's commercial use

    Don'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

  1. PII 04Secure erasure of temporary files

    Erase 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

  1. PII 05PII disclosure notification

    Tell 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

  2. PII 06Recording of PII disclosures

    Record 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

  1. PII 07Disclosure of sub-contracted PII processing

    Tell 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

  1. PII 08Notification of a data breach involving PII

    Notify 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)

  2. PII 09Retention of administrative security policies

    Keep 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

  3. PII 10PII return, transfer and disposal

    Have 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

  1. PII 11Confidentiality or non-disclosure agreements

    Bind 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

  2. PII 12Restriction of the creation of hardcopy material

    Limit 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

  3. PII 13Control and logging of data restoration

    Log 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

  4. PII 14Protecting data on storage media leaving the premises

    Protect 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

  5. PII 15Use of unencrypted portable storage media

    Avoid 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

  6. PII 16Encryption of PII over public networks

    Encrypt 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

  7. PII 17Secure disposal of hardcopy materials

    Dispose 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

  8. PII 18Unique use of user IDs

    Give 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

  9. PII 19Records of authorized users

    Keep 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

  10. PII 20User ID management

    Don'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

  11. PII 21Contract measures

    Ensure 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

  12. PII 22Sub-contracted PII processing

    Hold 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

  13. PII 23Access to data on pre-used storage space

    Make 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

  1. PII 24Geographical location of PII

    Tell 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

  2. PII 25Intended destination of PII

    Make 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

Control names follow ISO/IEC 27018:2019 Annex A; the "PII nn" IDs are QULDEX numbering, not the standard's. Summaries are QULDEX paraphrases.

Certification path

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.

  1. Map PII processing for customers

    List services that process customer PII, data categories, locations and sub-processors.

  2. Gap assessment against the extended controls

    Compare current practice with the 25 controls and privacy guidance.

  3. Implement controls and update contracts

    Close gaps and make sure customer and sub-processor contracts carry the obligations.

  4. Update the SoA and internal audit

    Add 27018 controls to the SoA and audit them internally.

  5. Certification audit with ISO 27001

    The certification body audits 27018 controls with the ISMS.

  6. Keep it running

    Year 1Surveillance
    Year 2Surveillance
    Year 3Recertification

Durations are typical planning ranges from QULDEX audit delivery.

Documented information

What documents does ISO 27018 need?

Customers and auditors ask for these to see how you handle their personal data.

DocumentControlWhere it lives in QULDEX
Sub-processor listPII 07Vendor register
Data location registerPII 24Evidence vault
Disclosure request and disclosure recordsPII 05–06Evidence vault
Breach notification procedure and recordsPII 08CAPA automation
Return, transfer and disposal procedurePII 10Evidence vault
Customer contract privacy termsPII 21Vendor register
Records of authorised usersPII 19Control library
Statement of Applicability with 27018 controlsISO 27001 6.1.3Control library (generated)

Control references use QULDEX numbering shown in the explorer.

Time and cost

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

PII mapping2–3 wk
Gap assessment2–3 wk
Implement and contracts1–3 mo
SoA and internal audit2–4 wk
Certification audit1–3 days

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
Readiness check · 2 minutes

How ready are you for ISO 27018?

Auditors and customers check these eight things first. Nothing you enter leaves this page.

PII 02Do you process customer PII only on their instructions?
PII 03Is commercial use of customer PII prohibited without consent?
PII 07Do you publish and notify changes to sub-processors?
PII 08Can you notify customers promptly of a breach?
PII 10Is there a procedure to return or delete PII at contract end?
PII 16Is PII encrypted over public networks?
PII 24Do you tell customers where PII is stored?
SoAAre 27018 controls in your Statement of Applicability?
Crosswalk

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 27018ISO 27701
TypeCode of practice for cloud PII processorsPrivacy management-system standard
ScopePublic cloud processing PII for customersAny controller or processor
CertificationExtension of ISO 27001Standalone since 2025, or integrated
DepthControls for processorsFull management system with controller and processor controls
Use togetherYes; 27018 adds cloud-specific detailYes
In QULDEXQULDEX maps 27018 controls to ISO 27701 processor controls so evidence is shared.

Privacy crosswalk

ISO 27018GDPRISO 27701DPDP ActShared evidence
PII 01 Rights supportArt. 28(3)(e)Processor: support customer obligationsSec. 8(2)Request support
PII 02 PurposeArt. 28(3)(a)Processor: instructionsSec. 8(2)Instructions
PII 07 Sub-processorsArt. 28(2)Processor: subprocessors—Sub-processor list
PII 08 BreachArt. 33(2)Processor: breach notificationSec. 8(6)Breach records
PII 10 Return and disposalArt. 28(3)(g)Processor: return or deleteSec. 8(7)Exit records
PII 16 EncryptionArt. 32Security for PIISec. 8(5)TLS settings
PII 24 LocationArt. 44–49TransfersSec. 16Location register

Indicative mapping for planning, not legal advice. The full crosswalk is in the QULDEX control library.

Where QULDEX fits

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.

  1. MappingMap PII processingServices, data and locations linked
  2. GapsAssess controls25 controls with owners
  3. ContractsUpdate contractsCustomer and sub-processor terms tracked
  4. SoAUpdate the SoASoA generated with 27018 rows
  5. AuditHost the auditorControlled, logged evidence sharing
  6. CustomersAnswer due diligenceSecure links to certificates and lists
Without one systemWith QULDEX
Sub-processor list out of dateSub-processors tracked with contracts
Customer questionnaires answered by handAnswers linked to evidence
Separate privacy evidence for 27018 and 27701One control set mapped to both
Data locations unclearLocation register per service
10+years of audit delivery500+audits deliveredBoth sidesof the audit on one platformRBACand a full audit trail on every action
FAQ

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.

Sources

References

  1. ISO/IEC 27018:2019, Code of practice for protection of PII in public clouds acting as PII processors. iso.org
  2. ISO/IEC 29100:2024, Privacy framework. iso.org
  3. ISO/IEC 27001:2022. iso.org
  4. ISO/IEC 27701:2025. iso.org
  5. Regulation (EU) 2016/679 (GDPR), Article 28. eur-lex.europa.eu

Reviewed by

Manisha Dubey

Framework reviewer · QULDEX

Reviewed this page against ISO/IEC 27018:2019: extended controls, certification approach and the privacy crosswalk.

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.

Schedule
Book a Demo