ISO 27017 cloud controls
Find where provider controls end and customer controls begin in a real cloud deployment.
Cloud Security Alliance Security, Trust, Assurance and Risk program
Choose a STAR self-assessment or independent assurance pathway for your cloud service.
Cloud service providers planning to appear in the STAR Registry and buyers interpreting its published assurance information.
A STAR Registry entry for the selected level and scope, with independent certification or attestation when the applicable Level 2 route is completed.
Level 1 is a self-assessment. Read the assessor’s scope and independent assurance documents when a buyer asks for Level 2.
Monitor unresolved scope questions, controls without evidence, findings that need a retest and the next assessment or renewal date.
Fill this in with your sponsor and send it to the people who own the work.
CSA STAR cloud assurance 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 Choose a level and scope · Cloud assurance + customer 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. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing. 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 SaaS vendor prepares a Level 1 questionnaire for a prospect. When another customer requests independent assurance, the vendor confirms the Level 2 route and reuses the underlying evidence while adjusting the scope and examination schedule.
Checklist, instructions and 9 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Choose a level and scope | Cloud assurance + customer owner | Before committing to the registry | Set a start date | Scope memo; Agreed engagement | Open |
| Answer and substantiate the controls | Control owners + security assurance | Before submitting or entering assessment | Set a start date | Control matrix; Evidence index | Open |
| Complete the selected route | Assessor or provider signatory | On the chosen schedule | Set a start date | Assessment evidence; Submission package; Decision and listing details | Open |
| Maintain registry accuracy | Cloud governance + product | At renewals and product changes | Set a start date | Change log; Renewal calendar | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Confirm procurement requirements, programme level, service scope and the current Cloud Controls Matrix and questionnaire versions.
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.
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.
Match applicable controls and shared responsibilities to evidence. Use the programme questionnaire or assessment files where required.
Fictional details. Use the same fields with evidence from your work.
A different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
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.
For self-assessment, review the answers and the public listing. For independent routes, engage a qualified assessor and track the assessment and registry publication.
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.
The submitted package can be recreated from the index and the receipt is linked to the exact files.
Send the approved package through the official channel. Treat the download as an index, and use issuer forms where required.
Fictional details. Use the same fields with evidence from your work.
The original can be traced to the issuer and its scope and date match the engagement or application.
Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.
Check changes to scope, regions and inherited controls. Refresh submissions and use the correct listing when responding to customer reviews.
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.
Every external deadline links to a real source. Planning targets are visibly marked.
Add approved dates to the team calendar and share them with the people scheduled to deliver or review.