FAQGlobalISO/IEC 27017

ISO/IEC 27017 FAQ Audit Rights

Does ISO/IEC 27017 give every cloud customer a right to audit its provider?

No. ISO/IEC 27017:2015 describes evidence and assurance routes, but the agreement and applicable law determine the customer's enforceable access and .

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
Overview

This guidance uses ISO/IEC 27017:2015, which ISO now lists as withdrawn with ISO/IEC 27017:2026 available as its replacement. Check which edition your agreement or assessment requires. The 2015 edition does not grant every customer an unrestricted right to inspect a provider. It tells customers to request evidence for provider claims and tells providers to offer sufficiently transparent when individual customer audits are impractical or can increase security risk. The agreement still needs to define the assurance route, scope, access, exceptions, and escalation for the service.

Search this module

Find a question or answer quickly

4 of 4 questions
Question 1

How should teams handle Audit Rights under ISO/IEC 27017?

ISO/IEC 27017:2015 does not create an unrestricted on-site audit right. It says customers should request documented evidence for provider claims. When individual audits are impractical or could increase security risk, the provider should make available; a sufficiently transparent independent audit selected by the provider should normally meet the customer's review interest. If independent audit is impractical, the provider should disclose its process and results.

Put the enforceable assurance route in the agreement before service approval. Define the report or certification, covered entities and services, locations, period, exclusions, customer controls, access to supporting material, treatment of exceptions, bridge evidence, remediation follow-up, confidentiality limits, cost, notice, and escalation when evidence is insufficient. If binding law, regulation, or an existing customer commitment requires access that the provider will not supply, negotiate a compliant route or do not approve that use; risk acceptance cannot remove the underlying duty.

  • Name the accountable owner and reviewer for .
  • Record the scope, assumptions, decision, approval date, evidence location, exception status, and next review trigger.
  • Escalate if the offered assurance cannot support a legal, regulatory, contractual, or risk requirement; ISO guidance does not override those requirements.
Question 2

What evidence shows the agreed assurance route is current?

Keep the signed assurance clause, current report or certificate, scope statement, auditor opinion, exceptions, provider response, bridge evidence, and the customer's assessment together. Record any request for extra material and the provider's response. Here, bridge evidence means information about changes, incidents, and controls after the report period; record who supplied it and which gap it addresses.

A report is usable only for the entities, services, regions, controls, subservice organizations, and period it covers. Check whether the report covers the customer's configuration and retained responsibilities; do not infer coverage from the provider's certification or audit opinion alone.

  • Match the report scope to the contracted service and architecture inventory.
  • Map exceptions and complementary customer controls to owners, actions, evidence, and due dates.
  • Record the report date or covered period, any certificate expiry, bridge coverage, the next expected report, and the escalation path for missing or insufficient evidence.
Question 3

Who should approve Audit Rights decisions under ISO/IEC 27017?

Supplier management and the cloud service owner should agree the assurance route with security input. Legal counsel should approve negotiated access, confidentiality, liability, cost, and notice terms when those terms are material.

The risk owner decides whether restricted or missing assurance is acceptable. A provider-selected auditor's opinion informs that decision but does not replace the customer's approval.

  • Use a named owner, named backup, and named escalation forum.
  • Separate preparation work from risk acceptance and final approval.
  • Keep approval records with the evidence rather than in disconnected email threads.
Question 4

When should Audit Rights be reviewed under ISO/IEC 27017?

Review the assurance route before renewal and when the provider entity, service, region, subservice organization, report scope, legal requirement, or material exception changes.

Reassess after a relevant incident, when a certificate expires, or when the report and any bridge evidence no longer cover the period needed for the decision. Document interim evidence and the risk decision if the next independent report is delayed.

  • Set a planned review date and a change-trigger rule.
  • Use findings to update controls, procedures, contracts, risk registers, or training.
  • Carry unresolved items into management review or risk acceptance.
Primary sources

References and citations

iso.org2 citations
Referenced sections
  • Official ISO listing confirming ISO/IEC 27017 is the cloud-services control guidance standard used to frame customer and supplier audit-right evidence.
  • Primary ISO listing for cloud-service security control guidance.
"Code of practice for information security controls based on ISO/IEC 27002 for cloud services"
iso.org
Referenced sections
  • Primary ISO listing for the current ISO/IEC 27001 ISMS requirements standard.
"Information security, cybersecurity and privacy protection — Information security management systems — Requirements"
iso.org
Referenced sections
  • Primary ISO listing for the ISO/IEC 27002 information security control guidance standard.
"Information security controls"
itu.int
Referenced sections
  • The identical 2015 recommendation describes independent evidence and self-assessment when individual customer audits are impractical; it does not state an unrestricted customer audit right.
"A relevant independent audit as selected by the cloud service provider should normally be an acceptable method for fulfilling the cloud service customer's interest in reviewing the cloud service provider's operations, provided sufficient transparency is provided."
Show all related guides (19)

ISO/IEC 27017 Virtualization Responsibilities FAQ

Allocate tenant isolation, virtual-machine hardening, administrative operations, images, snapshots, and virtual-network policy under ISO/IEC 27017.

ISO/IEC 27017 Certification Reality Guide

ISO/IEC 27017 is cloud control guidance, not a standalone management-system certification standard. Learn how to check the actual ISO/IEC 27001 claim and scope.

ISO/IEC 27017 Cloud Provider Checklist Template and Workflow

ISO/IEC 27017 cloud provider checklist covering service scope, shared responsibilities, agreements, tenant isolation, operations, evidence, and secure exit.

ISO/IEC 27017 Cloud Security FAQ

Answers to ISO/IEC 27017:2015 cloud-security questions on shared roles, agreements, administration, logging, assurance, virtualization, and customer controls.

ISO/IEC 27017 Compliance Guide

How cloud providers and customers apply ISO/IEC 27017:2015 through scoped risks, allocated responsibilities, agreements, controls, evidence, and review.

ISO/IEC 27017 Control Mapping to ISO/IEC 27001 Guide

Map ISO/IEC 27017:2015 cloud guidance and CLD controls into an ISO/IEC 27001:2022 ISMS with edition-aware rationale, owners, evidence, and SoA treatment.

ISO/IEC 27017 CSP vs CSC Role Split Comparison

Compare ISO/IEC 27017 responsibilities for cloud service providers and customers, with service-model examples, evidence, and review triggers.

ISO/IEC 27017 Hyperscaler Evidence Pack

What an ISO/IEC 27017:2015 hyperscaler evidence pack should contain, how to test coverage, and where provider assurance must be joined to customer evidence.

ISO/IEC 27017 Hyperscaler Evidence Pack Workflow

A service-specific workflow for testing hyperscaler claims, collecting provider and customer evidence, resolving gaps, and approving cloud risk under ISO/IEC 27017:2015.

ISO/IEC 27017 Shared Responsibility Model Guide

How to allocate provider, customer, and shared cloud security activities under ISO/IEC 27017:2015, document hand-offs, and test the allocation against evidence.

ISO/IEC 27017 vs CSA CCM Comparison

Compare ISO/IEC 27017:2015 with CSA CCM v4.1 by scope, control structure, responsibility mapping, assurance use, and evidence.

ISO/IEC 27017 vs ISO/IEC 27018 Comparison

Compare ISO/IEC 27017:2015 cloud security guidance with ISO/IEC 27018:2025 public-cloud PII processor guidance by scope, role, controls, and evidence.

ISO/IEC 27017 vs SOC 2 Comparison

Compare ISO/IEC 27017 cloud control guidance with SOC 2 attestation reports by purpose, scope, criteria, period, evidence, and customer responsibilities.