Written and maintained by CASRAI Editorial Board
Published
On this page
ISO/IEC 27017 (formally ISO/IEC 27017:2015 — Information technology — Security techniques — Code of practice for information security controls based on ISO/IEC 27002 for cloud services, co-published as ITU-T Recommendation X.1631) is the international standard that extends an ISO/IEC 27001 Information Security Management System (ISMS) with cloud-specific security implementation guidance and seven additional cloud controls.
For healthcare delivery organizations, digital health SaaS vendors, and clinical research platforms hosting electronic protected health information (ePHI) on public or hybrid cloud infrastructure, ISO 27017 cloud security formalizes the technical and contractual boundary between the Cloud Service Provider (CSP) and the Cloud Service Customer (CSC), complementing ISO 27799 and the HIPAA compliance checklist.
Ask CASRAI · free to tryQuestion about this guide? Ask CASRAI answers with linked sources. 2 free questions a day, no account.
What Is ISO/IEC 27017:2015 and What Are Its 7 Additional Cloud-Specific Extended Controls Beyond ISO/IEC 27002?
When information security auditors evaluate what is ISO/IEC 27017:2015 and what are its 7 additional cloud-specific extended controls beyond ISO/IEC 27002, they examine two structural layers within the standard:
- Cloud Implementation Guidance for 37 Existing Controls: Across clauses 5 through 18, ISO/IEC 27017 takes 37 baseline controls from ISO/IEC 27002 and adds explicit, side-by-side cloud implementation guidance split into two columns: what the Cloud Service Customer (CSC) must configure and verify, and what the Cloud Service Provider (CSP) must engineer and disclose.
- The 7 Extended Cloud Controls (Annex A `CLD` Controls): Because multi-tenant virtualization, hypervisor isolation, and cloud lifecycle decommissioning introduce risks not fully addressed in traditional on-premises data centers, ISO/IEC 27017 defines seven brand-new controls prefixed with
CLD:
| Extended Control ID | Control Title | Primary Owner | Healthcare & ePHI Cloud Implementation Requirement |
|---|---|---|---|
CLD.6.3.1 |
Shared roles and responsibilities within a cloud computing environment | CSP & CSC | Document and allocate security responsibilities across IaaS, PaaS, and SaaS layers in the HIPAA Business Associate Agreement (BAA) and security responsibility matrix. |
CLD.8.1.5 |
Removal of cloud service customer assets | CSP & CSC | Provide documented, timely, and verifiable cryptographic erasure and return of customer ePHI, virtual machine images, snapshots, and encryption keys upon contract termination. |
CLD.9.5.1 |
Segregation in virtual computing environments | CSP | Enforce strict logical and hypervisor-level isolation between a healthcare customer’s virtual compute/storage resources and all other multi-tenant cloud customers. |
CLD.9.5.2 |
Virtual machine hardening | CSP & CSC | Harden base virtual machine (VM) and container images—removing unnecessary ports, services, and default accounts, enforcing patch baselines, and logging image provenance. |
CLD.12.1.5 |
Administrator’s operational security | CSP & CSC | Define strict procedures, multi-factor authentication (MFA), just-in-time (JIT) privileged access, and immutable logging for cloud control-plane administrators. |
CLD.12.4.5 |
Monitoring of cloud services | CSP & CSC | The CSP must provide capabilities (e.g., AWS CloudTrail, Azure Monitor, GCP Cloud Audit Logs) enabling the CSC to monitor its cloud environment and detect unauthorized ePHI access. |
CLD.13.1.4 |
Alignment of security management for virtual and physical networks | CSP | Ensure that virtual network security policies (VPC security groups, SDN microsegmentation, virtual firewalls) remain consistent with underlying physical network configurations. |
How Does ISO/IEC 27017 Define the Split Between Cloud Service Provider (CSP) and Cloud Service Customer (CSC) Responsibilities for Healthcare Workloads?
A frequent cause of cloud data breaches in healthcare is ambiguity over who configures encryption, identity, and logging—a gap addressed in HIPAA aware vs HIPAA compliant vendor assessments. ISO/IEC 27017 operationalizes the cloud shared responsibility model ephi across three service delivery models:
- Infrastructure as a Service (IaaS — e.g., AWS EC2, Azure Virtual Machines): The CSP is responsible for physical data center security, hardware disposal, hypervisor isolation (`CLD.9.5.1`), and physical-to-virtual network alignment (`CLD.13.1.4`). The healthcare CSC is responsible for guest OS patching and virtual machine hardening (`CLD.9.5.2`), virtual firewall rules, KMS key management, EHR database encryption, and configuring cloud audit log ingestion (`CLD.12.4.5`).
- Platform as a Service (PaaS — e.g., managed FHIR APIs, cloud relational databases): The CSP assumes responsibility for underlying OS and database engine patching, while the healthcare CSC retains responsibility for IAM role least-privilege, application-level access controls, TLS/KMS configuration, and ePHI data lifecycle management.
- Software as a Service (SaaS — e.g., cloud EHR, ambient AI medical scribe, eTMF/EDC): The SaaS vendor acts as a CSP to the hospital (and simultaneously as a CSC to its underlying IaaS hyperscaler). Under `CLD.6.3.1`, the SaaS vendor must map both its own application controls and its inherited hyperscaler controls in the Statement of Applicability (SoA) and HIPAA BAA.
How Do ISO/IEC 27001, 27017 (Cloud Security), 27018 (Cloud PII), and 27799 (Health Informatics Security) Combine in HITRUST and HIPAA BAA Audits?
When compliance officers evaluate iso 27017 vs 27018 healthcare alongside ISO/IEC 27001 and ISO 27799, they treat the four standards as interlocking layers of a unified healthcare cloud assurance stack (see PII vs PHI):
| ISO Standard | Primary Scope & Role | Unique Contribution to Healthcare Cloud Governance |
|---|---|---|
| ISO/IEC 27001:2022 | Certifiable ISMS Management System Requirement Standard | Establishes the overarching risk management framework, internal audit cycle, Statement of Applicability (SoA), and accredited third-party certification. |
| ISO/IEC 27017:2015 | Cloud Service Security Code of Practice (CSP & CSC) | Adds the 37 CSP/CSC split guidance controls and 7 `CLD` controls governing multi-tenant hypervisor isolation, VM hardening, and cloud admin security. |
| ISO/IEC 27018:2019 | Protection of PII in Public Clouds Acting as PII Processors | Adds privacy-specific obligations for cloud processors: strict purpose limitation (no use of customer PII/PHI for marketing or model training without consent), sub-processor transparency, and breach notification support. |
| ISO 27799:2016 | Health Informatics Information Security Management | Tailors ISO/IEC 27002 specifically to clinical environments, covering EHR availability during emergencies, medical device security, clinical audit trails, and patient safety. |
Note that while an organization is formally certified against ISO/IEC 27001, accredited certification bodies issue an extendedISO/IEC 27001 certificate whose Statement of Applicability (SoA) explicitly attests to the inclusion and audit verification of ISO/IEC 27017 and ISO/IEC 27018 controls. Within the HITRUST CSF framework, these controls map directly into the Cloud Service Provider and HIPAA regulatory factors, allowing hospitals to inherit verified physical and virtualization controls from their hyperscaler while auditing their own CSC configuration layer.
Frequently Asked Questions
What is ISO/IEC 27017:2015 and what are its 7 additional cloud-specific extended controls beyond ISO/IEC 27002?
ISO/IEC 27017:2015 is an international standard providing cloud-specific information security guidance for 37 existing ISO/IEC 27002 controls plus 7 new extended controls in Annex A (`CLD.6.3.1` Shared roles and responsibilities, `CLD.8.1.5` Removal of customer assets, `CLD.9.5.1` Segregation in virtual computing environments, `CLD.9.5.2` Virtual machine hardening, `CLD.12.1.5` Administrator operational security, `CLD.12.4.5` Monitoring of cloud services, and `CLD.13.1.4` Alignment of virtual and physical network security).
How does ISO/IEC 27017 define the split between Cloud Service Provider (CSP) and Cloud Service Customer (CSC) responsibilities for healthcare workloads?
For each of its 37 modified controls and 7 extended `CLD` controls, ISO/IEC 27017 provides separate implementation guidance columns for the Cloud Service Provider (CSP) and the Cloud Service Customer (CSC), requiring both parties under `CLD.6.3.1` to contractually document who manages hypervisor isolation, VM hardening, encryption keys, administrative access, and audit logging across IaaS, PaaS, and SaaS healthcare deployments.
How do ISO/IEC 27001, 27017 (cloud security), 27018 (cloud PII), and 27799 (health informatics security) combine in HITRUST and HIPAA BAA audits?
ISO/IEC 27001 provides the certifiable ISMS foundation; ISO/IEC 27017 secures the multi-tenant cloud infrastructure and CSP/CSC operational boundary; ISO/IEC 27018 enforces public cloud data-processor privacy rules (prohibiting unauthorized secondary use of PII/PHI and requiring sub-processor disclosure); and ISO 27799 addresses clinical EHR availability and patient-safety security controls.
Sources
- International Organization for Standardization (ISO) — ISO/IEC 27017:2015 Code of Practice for Information Security Controls Based on ISO/IEC 27002 for Cloud Services
- International Organization for Standardization (ISO) — ISO/IEC 27018:2019 Code of Practice for Protection of Personally Identifiable Information (PII) in Public Clouds Acting as PII Processors
- Microsoft Compliance Documentation — ISO/IEC 27017 Cloud Security Controls and Shared Responsibility







