Start hereMap service models and shared boundaries
~84 days leftOpen step
Guide library
Industry standard Global

ISO 27017 cloud controls

ISO/IEC 27017:2026 information security controls for cloud services

Find where provider controls end and customer controls begin in a real cloud deployment.

Who it applies to

Cloud service providers and customers using ISO/IEC 27017 to select and implement cloud-specific information security controls.

What you’ll produce

A shared-responsibility matrix, tested cloud controls and supporting assessment evidence.

A cloud control statement has to distinguish what the provider does from what the customer must configure and verify.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Who accepts proof, and what do they expect?
Check the customer, contract or industry program for the standard version, scope, evidence or validation format and due date. Reserve testing and remediation time.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Map one in-scope service or transaction, including providers and supporting systems. Check real evidence against the requirements and confirm whose responsibility each check is.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor validation gaps, expired provider evidence and service changes that affect compliance.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

ISO 27017 cloud controls kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Map service models and shared boundaries · Cloud architect + vendor owner [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Map one in-scope service or transaction, including providers and supporting systems. Check real evidence against the requirements and confirm whose responsibility each check is.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Which service model and cloud provider controls apply to this deployment?
  • Which controls fail if the customer leaves the default configuration in place?

Worked scenario

A provider offers encryption and customer-managed keys. The customer documents who creates keys, rotates them and responds if a key is disabled, then tests how those roles work during recovery.

What to read next

  • ISO 27001

    Tie cloud control decisions to overall information security risk treatment.

  • CSA STAR cloud assurance

    Compare a cloud assurance program based on the Cloud Controls Matrix.

The whole journeyabout 84 days across 4 steps
  1. 01Map service models and shared boundariesCloud architect + vendor owner · ~14 days
  2. 02Assign and document every shared dutySecurity lead + customer and provider owners · ~28 days
  3. 03Check live configuration and control operationCloud operations + assurance · ~28 days
  4. 04Retest changes and review assurance scopeService owner + compliance · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 8 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Map service models and shared boundariesCloud architect + vendor ownerBefore selecting controlsSet a start dateSystem boundary; System inventoryOpen
Assign and document every shared dutySecurity lead + customer and provider ownersBefore onboardingSet a start dateShared cloud control matrix; Supplier termsOpen
Check live configuration and control operationCloud operations + assuranceAhead of assessment and on changesSet a start dateControl evidence; Test reportsOpen
Retest changes and review assurance scopeService owner + complianceAt renewal or material changeSet a start dateChange log; Vendor reviewOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Map service models and shared boundaries

    Who Cloud architect + vendor owner When Before selecting controls

    List services, tenants, regions, support paths and inherited services. Confirm where each party can configure or observe controls.

    What to produce

    System boundaryMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    System inventorySpreadsheet

    Gather first

    • Asset exports or system discovery
    • Service owner interviews
    • Approved scope and architecture

    How to prepare it

    1. Export a dated baseline from the source system. Give each asset, service or record class a stable ID and remove duplicates without losing links to the source.
    2. Add ownership, purpose, sensitivity and any vendor or system it depends on. Mark unknowns explicitly and assign them to someone to resolve.
    3. Reconcile the register against an independent source such as cloud billing or the production deployment list. Set a refresh cadence and an owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    ID
    SYS-014
    Item
    Production billing database
    Owner
    Platform operations
    Location and purpose
    Production EU region, stores invoice and account data
    Impact and dependencies
    High. Identity provider and managed backups.
    Verified on
    2026-11-10, cloud inventory export

    Check before handing it over

    Each item has one accountable owner. The source and as-of date let a reviewer trace it back.

    Share the reviewed inventory with the people building the control, privacy or testing scope.

  2. 02

    Assign and document every shared duty

    Who Security lead + customer and provider owners When Before onboarding

    Describe access, isolation, change, incident, data return and deletion responsibilities. Verify duties against the agreement and actual product behavior.

    What to produce

    Shared cloud control matrixSpreadsheet

    Gather first

    • Cloud architecture
    • Provider assurance and service terms
    • Customer tenant configuration and testing results

    How to prepare it

    1. List the service, tenant, account, region and control. Split the provider, customer and shared tasks into explicit actions.
    2. Identify evidence for each part, such as a provider report section or actual tenant test. Record scope limitations and who can retrieve the evidence.
    3. Walk through a failure with both teams. Confirm the escalation and response responsibilities, then reassess when product or deployment changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Service and control
    Object storage, encryption and key rotation
    Provider task
    Support encryption and report service availability.
    Customer task
    Set policy, operate customer-managed keys and check rotation.
    Evidence
    Provider assurance scope, tenant key policy export and restore test.
    Change trigger
    Move to another region or change key ownership.

    Check before handing it over

    Each team can find its expected action and verify the other party’s responsibility without guessing.

    Share with onboarding, audit and vendor oversight teams.

    Supplier termsMemo

    Gather first

    • Current agreement and service description
    • Applicable flow-down terms or engagement requirements
    • Contract owner and legal review

    How to prepare it

    1. Make a clause-by-clause worksheet. Quote only what you need to identify the current clause, and record each required subject and unresolved question.
    2. Mark where scope, instructions, evidence, security, subprocessors, incident notice, audit rights or termination affect the work. Route proposed wording to authorized reviewers.
    3. Record the signed or agreed version, responsible parties and the dates you need to revisit it. Save the source agreement in its restricted store.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Party and service
    Northstar hosting provider, production backup
    Clause or requirement
    Incident notification and contacts
    Current position
    General notice terms. No operational escalation contacts listed.
    Change to review
    Add named response channel and request confirmation of the timing.
    Owner, status and record
    Vendor lead, legal review pending, contract register V-018

    Check before handing it over

    The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.

    Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.

  3. 03

    Check live configuration and control operation

    Who Cloud operations + assurance When Ahead of assessment and on changes

    Test selected tenant settings, logs, escalation and administrative access. Record evidence that inherited controls and customer settings work together.

    What to produce

    Control evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

    Test reportsMemo

    Gather first

    • Approved test scope and criteria
    • Population and sample records
    • Test approach, results and reviewer requirements

    How to prepare it

    1. State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
    2. For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
    3. Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Test objective
    Check that production role removals happen within the internal deadline.
    Method and population
    All September departures. Test each privileged account.
    Expected result
    Remove access within one business day.
    Observed result
    11 on time. One late by two days, ticket IAM-114.
    Finding and follow-up
    F-008. Retest the next departure and verify alerting.

    Check before handing it over

    Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.

    Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.

  4. 04

    Retest changes and review assurance scope

    Who Service owner + compliance When At renewal or material change

    Assess new provider features, service models and locations. Reconfirm coverage and assign gaps where attestations do not cover the intended use.

    What to produce

    Change logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    Every open item has a next action and closed items have a verifiable record of closure or delivery.

    Use the log at case reviews and provide a restricted copy only where the engagement requires it.

    Vendor reviewSpreadsheet

    Gather first

    • Signed contracts and supplier inventory
    • Critical functions, service relationships and subprocessors
    • Reporting instructions and data dictionary when applicable

    How to prepare it

    1. Identify the contracting entity, supplier identifier, service, dates and location. Map dependencies to critical functions and distinguish direct providers from subcontractors.
    2. Gather evidence on security, continuity, location, access and exit. In a required reporting register, use the current authority workbook and allowed identifiers.
    3. Reconcile records against contracts and procurement data, and validate reference keys. Send missing or inconsistent elements to the supplier and record the final approval.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Arrangement ID
    ICT-018, managed database hosting
    Contract and provider
    Enter signed agreement reference and verified legal entity identifier.
    Service and function
    Managed database supporting invoicing. Record entity and function reference.
    Location and subcontractors
    Check documented data locations and supplier chain.
    Evidence and status
    Contract verified, subcontractor fields under review.

    Check before handing it over

    Each provider and contract record links to an actual function and all required identifiers are present.

    Use the verified register in supplier reviews and put required submissions in the authority’s prescribed format.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes