Framework · Cloud security · Code of practice

ISO 27017 cloud security controls: shared responsibility and certification

ISO/IEC 27017 is a code of practice for information security controls in cloud services. It adds cloud-specific guidance for both cloud service customers and providers to the ISO/IEC 27002 controls, plus seven extra cloud controls, such as shared responsibility and virtual machine hardening. It is usually certified as an extension of ISO 27001.

Key takeaways

What you need to know about ISO 27017

Both sidesGuidance covers the cloud service customer and the provider.
Shared responsibilityThe core idea: write down who does what for each control.
7 cloud controlsAdds controls such as tenant segregation and VM hardening.
Not standaloneIt is certified alongside ISO 27001, not on its own.
Pairs with 27018ISO 27018 adds PII protection for cloud processors.

Who needs ISO 27017?

It is voluntary, but common in cloud supply chains.

SaaS providersEnterprise buyers want proof of cloud-specific controls.
IaaS and PaaS providersCustomers rely on your controls for their own compliance.
Managed cloud service providersTo show how responsibilities are split with clients.
Cloud customers in regulated sectorsTo set clear responsibilities with providers.
ISO 27001 holders moving to cloudA natural scope extension.

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

Code of practice

What does ISO 27017 require?

ISO 27017 asks you to apply ISO 27002 controls with cloud-specific guidance, and to implement seven additional cloud controls, while documenting which responsibilities sit with the customer and which with the provider.

Customer Role

Cloud service customer

Choose providers, set responsibilities, secure your own use.

In QULDEX: Customer duties listed per service
Provider Role

Cloud service provider

Secure the platform and tell customers what you do.

In QULDEX: Provider duties shared with customers
CLD 7

Cloud controls

Shared roles, asset removal, segregation, VM hardening, admin ops, monitoring, network alignment.

In QULDEX: Each CLD control with owners
27002 Guidance

Extended controls

Cloud guidance on existing ISO 27002 controls.

In QULDEX: Mapped to your ISO 27001 SoA
SoA ISO 27001

Statement of Applicability

27017 controls are added to the ISO 27001 SoA.

In QULDEX: SoA generated with 27017 rows
Agreement Contract

Service agreement

Responsibilities written into the cloud contract.

In QULDEX: Contract terms linked to controls
Audit Cert

Certification

Audited with ISO 27001 by an accredited body.

In QULDEX: Evidence shared with the auditor
Cloud controls and guidance

What are the ISO 27017 controls?

ISO 27017 adds seven cloud-specific controls (CLD) and cloud guidance to many ISO 27002 controls. Select any control to see what it asks for, typical evidence and the matching ISO 27001:2022 control.

7additional cloud controls
2015current edition
2roles: customer and provider
27001certified as an extension

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

Additional cloud controls (CLD) 7

  1. CLD.6.3.1Shared roles and responsibilities within a cloud computing environmentCloud-specific (CLD)

    Agree and document how security roles are split between the cloud service customer and provider.

    In QULDEXShared-responsibility matrices are kept per cloud service.

    Typical evidence
    Shared responsibility matrix
    Maps to
    ISO 27001 A.5.23

  2. CLD.8.1.5Removal of cloud service customer assetsCloud-specific (CLD)

    Return or remove customer assets in a timely way when the agreement ends.

    In QULDEXQULDEX records who owns this control in each cloud service, customer or provider, and links the evidence to your ISO 27001 programme.

    Typical evidence
    Exit and data return procedure
    Maps to
    ISO 27001 A.5.23

  3. CLD.9.5.1Segregation in virtual computing environmentsCloud-specific (CLD)

    Keep each customer's virtual environment separated from other customers.

    In QULDEXQULDEX records who owns this control in each cloud service, customer or provider, and links the evidence to your ISO 27001 programme.

    Typical evidence
    Tenant isolation design
    Maps to
    ISO 27001 A.8.22

  4. CLD.9.5.2Virtual machine hardeningCloud-specific (CLD)

    Harden virtual machines to meet business needs.

    In QULDEXQULDEX records who owns this control in each cloud service, customer or provider, and links the evidence to your ISO 27001 programme.

    Typical evidence
    VM hardening baselines
    Maps to
    ISO 27001 A.8.9

  5. CLD.12.1.5Administrator's operational securityCloud-specific (CLD)

    Define and run procedures for administrative operations in the cloud.

    In QULDEXQULDEX records who owns this control in each cloud service, customer or provider, and links the evidence to your ISO 27001 programme.

    Typical evidence
    Admin procedures
    Maps to
    ISO 27001 A.5.37

  6. CLD.12.4.5Monitoring of cloud servicesCloud-specific (CLD)

    Give the customer the ability to monitor aspects of the cloud service it uses.

    In QULDEXQULDEX records who owns this control in each cloud service, customer or provider, and links the evidence to your ISO 27001 programme.

    Typical evidence
    Customer-facing monitoring
    Maps to
    ISO 27001 A.8.16

  7. CLD.13.1.4Alignment of security management for virtual and physical networksCloud-specific (CLD)

    Keep network security policies consistent between virtual and physical networks.

    In QULDEXQULDEX records who owns this control in each cloud service, customer or provider, and links the evidence to your ISO 27001 programme.

    Typical evidence
    Network configuration records
    Maps to
    ISO 27001 A.8.20

ISO 27002 controls with cloud guidance 11

  1. 5.1.1Policies for information security

    Cover cloud-specific risks and responsibilities in your security policy.

    In QULDEXQULDEX holds the cloud-specific guidance alongside your ISO 27001 control, so one evidence set serves both.

    Typical evidence
    Cloud security policy
    Maps to
    ISO 27001 A.5.1

  2. 6.1.3Contact with authorities

    Know which jurisdictions' authorities apply to the cloud service and where data is held.

    In QULDEXQULDEX holds the cloud-specific guidance alongside your ISO 27001 control, so one evidence set serves both.

    Maps to
    ISO 27001 A.5.5

  3. 8.1.1Inventory of assets

    Include cloud-hosted information and assets in the inventory, with ownership split clearly.

    In QULDEXQULDEX holds the cloud-specific guidance alongside your ISO 27001 control, so one evidence set serves both.

    Typical evidence
    Cloud asset inventory
    Maps to
    ISO 27001 A.5.9

  4. 9.2.1User registration and de-registration

    Manage cloud service user accounts, including the provider's administrative access.

    In QULDEXQULDEX holds the cloud-specific guidance alongside your ISO 27001 control, so one evidence set serves both.

    Typical evidence
    User provisioning records
    Maps to
    ISO 27001 A.5.16

  5. 10.1.1Policy on the use of cryptographic controls

    Decide who manages encryption and keys in the cloud service.

    In QULDEXQULDEX holds the cloud-specific guidance alongside your ISO 27001 control, so one evidence set serves both.

    Typical evidence
    Key management responsibilities
    Maps to
    ISO 27001 A.8.24

  6. 12.1.3Capacity management

    Monitor cloud capacity to avoid service loss.

    In QULDEXQULDEX holds the cloud-specific guidance alongside your ISO 27001 control, so one evidence set serves both.

    Typical evidence
    Capacity monitoring
    Maps to
    ISO 27001 A.8.6

  7. 12.3.1Information backup

    Agree who backs up what, and test restores.

    In QULDEXQULDEX holds the cloud-specific guidance alongside your ISO 27001 control, so one evidence set serves both.

    Typical evidence
    Backup responsibilities and tests
    Maps to
    ISO 27001 A.8.13

  8. 12.4.1Event logging

    Agree logging capabilities and access to logs between customer and provider.

    In QULDEXQULDEX holds the cloud-specific guidance alongside your ISO 27001 control, so one evidence set serves both.

    Typical evidence
    Log access arrangements
    Maps to
    ISO 27001 A.8.15

  9. 15.1.2Addressing security within supplier agreements

    Put cloud security responsibilities into the service agreement.

    In QULDEXQULDEX holds the cloud-specific guidance alongside your ISO 27001 control, so one evidence set serves both.

    Typical evidence
    Cloud service agreement
    Maps to
    ISO 27001 A.5.20

  10. 16.1.2Reporting information security events

    Agree how security events are reported between customer and provider.

    In QULDEXQULDEX holds the cloud-specific guidance alongside your ISO 27001 control, so one evidence set serves both.

    Typical evidence
    Incident reporting terms
    Maps to
    ISO 27001 A.6.8

  11. 18.1.1Identification of applicable legislation

    Consider the laws that apply where the provider stores or processes data.

    In QULDEXQULDEX holds the cloud-specific guidance alongside your ISO 27001 control, so one evidence set serves both.

    Typical evidence
    Legal register by location
    Maps to
    ISO 27001 A.5.31

Control numbers follow ISO/IEC 27017:2015, which uses the ISO/IEC 27002:2013 numbering. The second group is a selection of controls with cloud guidance. Summaries are QULDEX paraphrases.

Certification path

How do you get ISO 27017 certified?

Add ISO 27017 to your ISO 27001 scope: map responsibilities, implement the cloud controls, update the Statement of Applicability, and the certification body audits them together. With ISO 27001 in place it often takes 2 to 4 months.

  1. Define your cloud role and services

    List cloud services in scope and whether you act as customer, provider or both.

  2. Map shared responsibilities

    For each control, write down who does what between customer and provider.

  3. Implement cloud controls

    Put the seven CLD controls and cloud guidance in place.

  4. Update the SoA and internal audit

    Add 27017 controls to the Statement of Applicability and audit them internally.

  5. Certification audit with ISO 27001

    The certification body audits 27017 controls during an ISO 27001 audit or a dedicated visit.

  6. Keep it running

    Year 1Surveillance with ISO 27001
    Year 2Surveillance
    Year 3Recertification

Durations are typical planning ranges from QULDEX audit delivery. Certification bodies issue 27017 as part of, or alongside, the ISO 27001 certificate.

Documented information

What documents does ISO 27017 need?

Auditors look for responsibility splits and cloud-specific procedures on top of your ISO 27001 documents.

DocumentControlWhere it lives in QULDEX
Shared responsibility matrix per cloud serviceCLD.6.3.1Control library
Customer asset return and removal procedureCLD.8.1.5Evidence vault
Tenant segregation designCLD.9.5.1Evidence vault
VM hardening baselinesCLD.9.5.2Control library
Administrator operations proceduresCLD.12.1.5Evidence vault
Customer monitoring capabilitiesCLD.12.4.5Evidence vault
Cloud service agreements with security terms15.1.2Vendor register
Statement of Applicability with 27017 controlsISO 27001 6.1.3Control library (generated)

Control references use ISO/IEC 27017:2015 numbering.

Time and cost

How long does ISO 27017 take?

With an ISO 27001 ISMS in place, adding 27017 usually takes 2 to 4 months. Without ISO 27001, plan for both together.

Where the time goes

Role and services1–2 wk
Responsibility mapping2–4 wk
Implement controls1–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

  • Your role: providers carry more controls than customers
  • Number of services: each needs a responsibility matrix
  • Multi-tenancy: segregation evidence grows with architecture complexity
  • Existing ISO 27001: the main prerequisite
  • Sub-providers: your own cloud providers' assurances
Readiness check · 2 minutes

How ready are you for ISO 27017?

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

ScopeHave you listed cloud services in scope and your role in each?
CLD.6.3.1Is there a shared responsibility matrix for each service?
CLD.8.1.5Do you have a procedure to return or remove customer data?
CLD.9.5.1Can you show tenants are segregated?
CLD.9.5.2Are VM hardening baselines applied?
CLD.12.4.5Can customers monitor their use of the service?
15.1.2Do cloud agreements state security responsibilities?
SoAAre 27017 controls in your Statement of Applicability?
Crosswalk

How ISO 27017 maps to ISO 27001:2022, ISO 27018 and SOC 2

ISO 27017 was written against ISO 27002:2013, so its controls need mapping to the 2022 Annex A. QULDEX keeps that mapping, plus links to ISO 27018 and SOC 2.

ISO 27017 vs ISO 27018

ISO 27017ISO 27018
FocusCloud security for customers and providersPII protection by public cloud processors
Adds7 cloud security controlsPrivacy controls for PII processors
Applies toAny cloud servicePublic cloud acting as PII processor
CertificationExtension of ISO 27001Extension of ISO 27001
Use togetherYes, commonly certified togetherYes
In QULDEXQULDEX holds both as extensions to one ISO 27001 control set.

Control crosswalk

ISO 27017ISO 27001:2022SOC 2NIST CSF 2.0Shared evidence
CLD.6.3.1 Shared rolesA.5.23CC9.2GV.SCResponsibility matrix
CLD.8.1.5 Asset removalA.5.23 · A.8.10C1.2PR.DSExit procedure
CLD.9.5.1 SegregationA.8.22CC6.1PR.IRIsolation design
CLD.9.5.2 VM hardeningA.8.9CC7.1PR.PSBaselines
CLD.12.4.5 MonitoringA.8.16CC7.2DE.CMMonitoring
12.3.1 BackupA.8.13A1.2PR.DS-11Backup tests
15.1.2 Supplier agreementsA.5.20CC9.2GV.SCAgreements

Indicative mapping from 27002:2013-based numbering to ISO 27001:2022. The full crosswalk is in the QULDEX control library.

Where QULDEX fits

How QULDEX runs ISO 27017 alongside ISO 27001

QULDEX is ISO 27017 cloud security compliance and audit management software built from EGV Group's audit delivery, used by cloud providers, customers and the auditors who test them. Pick your role to see who does what.

For organisations extending ISO 27001 to cloud.

  1. ScopeList services and rolesCloud services with customer or provider role
  2. ResponsibilitiesMap who does whatResponsibility matrix per service
  3. ControlsRun cloud controlsCLD controls with owners and evidence
  4. SoAUpdate the SoASoA generated with 27017 rows
  5. AuditHost the auditorControlled, logged evidence sharing
  6. CustomersShare assuranceSecure links to certificates and matrices
Without one systemWith QULDEX
Responsibilities assumed, never writtenA responsibility matrix per service
Customer questionnaires answered from scratchAnswers linked to evidence
Separate 27017 and 27001 evidenceOne control set with extensions
Exit procedures untestedAsset return tracked as evidence
10+years of audit delivery500+audits deliveredBoth sidesof the audit on one platformRBACand a full audit trail on every action
FAQ

ISO 27017 questions people ask

What is ISO 27017?

ISO/IEC 27017 is a code of practice for information security controls in cloud services, for both cloud service customers and providers.

Can you get ISO 27017 certified on its own?

Not usually. Certification bodies certify it as an extension of ISO 27001, adding 27017 controls to the ISMS scope and Statement of Applicability.

What are the 7 additional ISO 27017 controls?

Shared roles and responsibilities, removal of customer assets, segregation in virtual environments, VM hardening, administrator operational security, monitoring of cloud services, and alignment of virtual and physical network security.

What is the difference between ISO 27017 and ISO 27018?

ISO 27017 covers cloud security for customers and providers. ISO 27018 covers protection of personal data by public cloud providers acting as PII processors.

Does ISO 27017 apply to cloud customers?

Yes. It gives guidance to customers as well as providers, especially on agreeing and documenting responsibilities.

Is ISO 27017 updated for ISO 27002:2022?

The current edition is from 2015 and uses 27002:2013 numbering, so organisations map it to the 2022 Annex A. Check whether a revision has been published.

Can QULDEX run ISO 27017 with ISO 27001 and 27018?

Yes. 27017 and 27018 are held as extensions of one ISO 27001 control set, with shared evidence.

Sources

References

  1. ISO/IEC 27017:2015 | ITU-T X.1631, Code of practice for information security controls based on ISO/IEC 27002 for cloud services. iso.org
  2. ISO/IEC 27002:2022. iso.org
  3. ISO/IEC 27001:2022. iso.org
  4. ISO/IEC 27018:2019. iso.org
  5. Cloud Security Alliance, Cloud Controls Matrix. cloudsecurityalliance.org

Reviewed by

Swati Chaturvedi

Framework reviewer · QULDEX

Reviewed this page against ISO/IEC 27017:2015: cloud controls, shared responsibility, certification approach and crosswalk.

Page history
  • : Rebuilt with the 7 cloud controls, shared responsibility, certification as an ISO 27001 extension and readiness check
  • : Page first published

Find your ISO 27017 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