CSA STAR cloud assurance
Choose a STAR self-assessment or independent assurance pathway for your cloud service.
ISO/IEC 27001:2022 · Information security management systems
Build an information security management system and prepare for a third-party certification audit.
Organizations of any size seeking a certifiable information security management system (ISMS) within a defined boundary.
ISMS certificate for the audited scope if the external certification body approves.
Confirm the applicable edition, amendments and surveillance cycle with an accredited certification body. Use the licensed standard for normative requirements.
Use the register to report overdue high-risk treatments, audit findings past due, and objectives with deteriorating results. Include the next management or certification review date.
Fill this in with your sponsor and send it to the people who own the work.
ISO 27001 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 Define the ISMS boundary · ISMS lead + leadership [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. Request the licensed standard, product and site inventory, customer commitments, regulatory obligations and system architecture. 2. Walk through one service with Operations and Engineering. Draw the scope and the interfaces with outsourced or excluded services. Bring disputed boundaries to management. 3. Book a working session with risk owners. Agree how risks will be rated, who can accept them and where approvals and evidence will live.
A software company scopes its hosted application and keeps its head office outside the proposed certification boundary. It still documents corporate identity as a dependency because a head-office identity change can affect production access.
Assign shared controls for cloud services inside the scope.
Structure the business continuity work if service disruption is a significant risk.
Checklist, instructions and 15 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Define the ISMS boundary | ISMS lead + leadership | Before risk assessment | Set a start date | Scope statement; Security policy; Obligations register | Open |
| Assess risks and select controls | Risk owners | Before implementation | Set a start date | Risk register; Treatment plan; Statement of Applicability | Open |
| Operate, audit and review the ISMS | Internal auditor + leadership | Before external assessment | Set a start date | Internal audit report; Management review minutes; CAPA log | Open |
| Complete Stage 1 and Stage 2 | Certification body + ISMS lead | Dates agreed with the certification body | Set a start date | Readiness findings; Stage 2 report; Certification decision | Open |
| Maintain certification | ISMS lead | Surveillance and recertification cycle | Set a start date | Audit calendar; Updated SoA; Performance measures | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Identify interested parties, legal and contractual obligations, interfaces, suppliers and activities covered by the ISMS. Approve scope and policy.
Entities, facilities, service flows, relevant interested parties, customer contracts and security obligations.
A versioned scope statement matches the service map and says who owns outsourced interfaces. The obligations register names an owner and pointer to each obligation.
Reopen scope review if Sales requires a service on the certificate that the draft excludes, or if a critical location or outsourced dependency has no owner.
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.
A person who receives the plan can tell when to act, what to check and where to save the result.
Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.
Fictional details. Use the same fields with evidence from your work.
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
Apply approved risk criteria, select treatments and compare selected controls against Annex A. Document applicability, exclusions and implementation status.
Approved scope, risk methodology, obligations register, service architecture and incident history.
The account takeover risk links to its treatment, the SoA entry, the identity configuration and the evidence that privileged access works as designed. Remaining risk has named approval.
Bring unfunded treatments, unresolved exclusions and residual risks outside authorized thresholds to management before assessment.
Fictional details. Use the same fields with evidence from your work.
The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.
Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.
Fictional details. Use the same fields with evidence from your work.
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
Fictional details. Use the same fields with evidence from your work.
A reviewer can trace selected controls to the reasons they are needed and supporting evidence, and can locate a justified decision for every excluded Annex A control.
The ISMS lead holds the controlled SoA and makes the current version available for audit. Control owners update implementation evidence and notify the lead when treatment or scope changes.
Collect operating records, audit the ISMS objectively, review results with leadership and close significant corrective actions.
Operational records, performance objectives, SoA, previous issues and the scope and criteria for internal audit.
The audit file ties a finding to evidence, root cause and corrective action. Management review minutes show a resource decision, owner and checkpoint.
Escalate if the internal auditor is reviewing their own work or if management review minutes record discussion without decisions required to resolve the issues.
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.
Fictional details. Use the same fields with evidence from your work.
The minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.
Fictional details. Use the same fields with evidence from your work.
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
Use Stage 1 to address readiness findings and Stage 2 to demonstrate implementation and effectiveness. Resolve nonconformities within the body’s deadlines.
Current ISMS documents, internal audit and management review records, operating evidence and the certification body’s assessment plan.
The assessment file includes the scope and final SoA version, accepted finding responses and the certification body’s decision when issued.
Escalate any finding that puts Stage 2 or the decision at risk and any mismatch between requested and proposed certificate scope.
Fictional details. Use the same fields with evidence from your work.
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
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.
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.
Monitor objectives and risks, update the SoA for changes, repeat internal audits and management review, and schedule surveillance visits.
Certificate, surveillance schedule, current SoA, incident history and new processes or locations.
A new production region has a change decision, updated artifacts and any required communication to the certification body.
Raise missed surveillance windows, recurring nonconformities and marketing claims that exceed certificate scope.
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.
Fictional details. Use the same fields with evidence from your work.
Every Annex A control has an explicit decision, with supporting justification and implementation status where selected.
Give the approved SoA to the certification body and use it as the baseline for controls and change review.
Fictional details. Use the same fields with evidence from your work.
The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.
Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.
Record the controls needed to treat risks, explain why they are included, state whether they are implemented and justify exclusions of Annex A controls. Link these decisions to the risk treatment plan and keep them current as the scope or risks change.
ISO · ISO/IEC 27001:2022 (opens in a new tab)Use Stage 1 to check scope, documented information and readiness. Stage 2 looks at how the management system is implemented and operates. Confirm the assessor’s evidence requests and deadlines before the visits.
ISO · Certification and conformity assessment (opens in a new tab)