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.
What you need to know about ISO 27017
Who needs ISO 27017?
It is voluntary, but common in cloud supply chains.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
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.
Cloud service customer
Choose providers, set responsibilities, secure your own use.
In QULDEX: Customer duties listed per serviceCloud service provider
Secure the platform and tell customers what you do.
In QULDEX: Provider duties shared with customersCloud controls
Shared roles, asset removal, segregation, VM hardening, admin ops, monitoring, network alignment.
In QULDEX: Each CLD control with ownersExtended controls
Cloud guidance on existing ISO 27002 controls.
In QULDEX: Mapped to your ISO 27001 SoAStatement of Applicability
27017 controls are added to the ISO 27001 SoA.
In QULDEX: SoA generated with 27017 rowsService agreement
Responsibilities written into the cloud contract.
In QULDEX: Contract terms linked to controlsCertification
Audited with ISO 27001 by an accredited body.
In QULDEX: Evidence shared with the auditorWhat 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.
Showing up to 6 per group. Search, filter, or open a group to see all 18.
Additional cloud controls (CLD) 7
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
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
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
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
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
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
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
5.1.1Policies for information securityCover 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
6.1.3Contact with authoritiesKnow 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
8.1.1Inventory of assetsInclude 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
9.2.1User registration and de-registrationManage 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
10.1.1Policy on the use of cryptographic controlsDecide 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
12.1.3Capacity managementMonitor 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
12.3.1Information backupAgree 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
12.4.1Event loggingAgree 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
15.1.2Addressing security within supplier agreementsPut 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
16.1.2Reporting information security eventsAgree 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
18.1.1Identification of applicable legislationConsider 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
Nothing matches that search.
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.
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.
Define your cloud role and services
List cloud services in scope and whether you act as customer, provider or both.
Map shared responsibilities
For each control, write down who does what between customer and provider.
Implement cloud controls
Put the seven CLD controls and cloud guidance in place.
Update the SoA and internal audit
Add 27017 controls to the Statement of Applicability and audit them internally.
Certification audit with ISO 27001
The certification body audits 27017 controls during an ISO 27001 audit or a dedicated visit.
Keep it running
Year 1Surveillance with ISO 27001Year 2SurveillanceYear 3Recertification
Durations are typical planning ranges from QULDEX audit delivery. Certification bodies issue 27017 as part of, or alongside, the ISO 27001 certificate.
What documents does ISO 27017 need?
Auditors look for responsibility splits and cloud-specific procedures on top of your ISO 27001 documents.
| Document | Control | Where it lives in QULDEX |
|---|---|---|
| Shared responsibility matrix per cloud service | CLD.6.3.1 | Control library |
| Customer asset return and removal procedure | CLD.8.1.5 | Evidence vault |
| Tenant segregation design | CLD.9.5.1 | Evidence vault |
| VM hardening baselines | CLD.9.5.2 | Control library |
| Administrator operations procedures | CLD.12.1.5 | Evidence vault |
| Customer monitoring capabilities | CLD.12.4.5 | Evidence vault |
| Cloud service agreements with security terms | 15.1.2 | Vendor register |
| Statement of Applicability with 27017 controls | ISO 27001 6.1.3 | Control library (generated) |
Control references use ISO/IEC 27017:2015 numbering.
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
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
How ready are you for ISO 27017?
Auditors check these eight things first. Nothing you enter leaves this page.
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 27017 | ISO 27018 | |
|---|---|---|
| Focus | Cloud security for customers and providers | PII protection by public cloud processors |
| Adds | 7 cloud security controls | Privacy controls for PII processors |
| Applies to | Any cloud service | Public cloud acting as PII processor |
| Certification | Extension of ISO 27001 | Extension of ISO 27001 |
| Use together | Yes, commonly certified together | Yes |
| In QULDEX | QULDEX holds both as extensions to one ISO 27001 control set. | |
Control crosswalk
| ISO 27017 | ISO 27001:2022 | SOC 2 | NIST CSF 2.0 | Shared evidence |
|---|---|---|---|---|
| CLD.6.3.1 Shared roles | A.5.23 | CC9.2 | GV.SC | Responsibility matrix |
| CLD.8.1.5 Asset removal | A.5.23 · A.8.10 | C1.2 | PR.DS | Exit procedure |
| CLD.9.5.1 Segregation | A.8.22 | CC6.1 | PR.IR | Isolation design |
| CLD.9.5.2 VM hardening | A.8.9 | CC7.1 | PR.PS | Baselines |
| CLD.12.4.5 Monitoring | A.8.16 | CC7.2 | DE.CM | Monitoring |
| 12.3.1 Backup | A.8.13 | A1.2 | PR.DS-11 | Backup tests |
| 15.1.2 Supplier agreements | A.5.20 | CC9.2 | GV.SC | Agreements |
Indicative mapping from 27002:2013-based numbering to ISO 27001:2022. The full crosswalk is in the QULDEX control library.
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.
- ScopeList services and rolesCloud services with customer or provider role
- ResponsibilitiesMap who does whatResponsibility matrix per service
- ControlsRun cloud controlsCLD controls with owners and evidence
- SoAUpdate the SoASoA generated with 27017 rows
- AuditHost the auditorControlled, logged evidence sharing
- CustomersShare assuranceSecure links to certificates and matrices
For consultants and internal audit.
- ScopeRun the gap assessmentA reusable 27017 template
- ResponsibilitiesFacilitate mappingMatrix templates
- ControlsReview evidenceReview and approval states
- SoACheck the SoAGaps flagged per control
- AuditPrepare the clientAn audit-ready pack
- CustomersAnswer questionnairesAnswers linked to evidence
For accredited bodies auditing ISO 27001 with 27017.
- PlanningExtend the audit plan27017 scope in a standard format
- Stage 1Review documentsMatrices and procedures 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 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.
Go deeper on ISO 27017
ISO 27001 topic hub
Including the ISO 27017 and 27018 cloud extensions.
blog.quldex.comISO 27001:2022 transition: what changed
How the 2022 Annex A affects cloud controls.
blog.quldex.comAudit evidence naming convention
A file-naming scheme that lets auditors sample without asking.
blog.quldex.comAudit sampling size for compliance
How many samples auditors pull, and why.
References
- 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
- ISO/IEC 27002:2022. iso.org
- ISO/IEC 27001:2022. iso.org
- ISO/IEC 27018:2019. iso.org
- Cloud Security Alliance, Cloud Controls Matrix. cloudsecurityalliance.org
Reviewed by
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.