SOC 2
Demonstrate how your service protects customer data with an independent CPA examination.
ISO/IEC 27017:2026 information security controls for cloud services
Find where provider controls end and customer controls begin in a real cloud deployment.
Cloud service providers and customers using ISO/IEC 27017 to select and implement cloud-specific information security controls.
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.
Monitor validation gaps, expired provider evidence and service changes that affect compliance.
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.
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.
Tie cloud control decisions to overall information security risk treatment.
Compare a cloud assurance program based on the Cloud Controls Matrix.
Checklist, instructions and 8 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Map service models and shared boundaries | Cloud architect + vendor owner | Before selecting controls | Set a start date | System boundary; System inventory | Open |
| Assign and document every shared duty | Security lead + customer and provider owners | Before onboarding | Set a start date | Shared cloud control matrix; Supplier terms | Open |
| Check live configuration and control operation | Cloud operations + assurance | Ahead of assessment and on changes | Set a start date | Control evidence; Test reports | Open |
| Retest changes and review assurance scope | Service owner + compliance | At renewal or material change | Set a start date | Change log; Vendor review | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
List services, tenants, regions, support paths and inherited services. Confirm where each party can configure or observe controls.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Describe access, isolation, change, incident, data return and deletion responsibilities. Verify duties against the agreement and actual product behavior.
Fictional details. Use the same fields with evidence from your work.
Each team can find its expected action and verify the other party’s responsibility without guessing.
Share with onboarding, audit and vendor oversight teams.
Fictional details. Use the same fields with evidence from your work.
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.
Test selected tenant settings, logs, escalation and administrative access. Record evidence that inherited controls and customer settings work together.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Assess new provider features, service models and locations. Reconfirm coverage and assign gaps where attestations do not cover the intended use.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.