ISO 27017 cloud controls
Find where provider controls end and customer controls begin in a real cloud deployment.
System and Organization Controls 2
Demonstrate how your service protects customer data with an independent CPA examination.
Service organizations whose customers need assurance about controls relevant to security and any additional Trust Services categories in scope.
Restricted-use CPA report with an opinion, management assertion and system description.
Security is the core category. Add availability, processing integrity, confidentiality or privacy according to service commitments. Agree the observation period with the CPA firm.
Report control runs due versus completed this month, overdue corrective actions, and any planned changes to the system boundary. Flag gaps that may affect the report period before promising a customer an issue date.
Fill this in with your sponsor and send it to the people who own the work.
SOC 2 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 system and report · Security lead + executive sponsor [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. Sales brings the customer requests. Engineering brings the production architecture, identity provider, cloud accounts, deployment flow and service vendors. Security turns these into a draft scope memo. 2. Security and Engineering walk one recent access removal and one production change from request to completion. Capture the original timestamps, approval and system record. Use missing evidence to size the work before setting the Type 2 start date. 3. The executive sponsor approves the scope, named control owners and budget. The lead gets the firm’s evidence request process, availability and expected dates in writing.
A hosted invoicing company receives a Type 2 request. Before agreeing dates, its security lead checks that privileged access reviews and release approvals have been running in production and that their records cover the agreed boundary.
Checklist, instructions and 14 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Define the system and report | Security lead + executive sponsor | Before engaging the auditor | Set a start date | Scope memo; System inventory; Agreed engagement | Open |
| Map and implement controls | Control owners | Before the report date or period | Set a start date | Control matrix; Remediation tracker; System description draft | Open |
| Operate controls and retain evidence | Engineering + operations | Throughout the agreed Type 2 period | Set a start date | Evidence index; Access reviews; Change and incident populations | Open |
| Complete fieldwork and issue the report | Independent CPA + management | After the period or as-of date | Set a start date | Final system description; Management assertion; Issued report | Open |
| Maintain controls between reports | Security lead | Ongoing | Set a start date | Corrective actions; Next-period scope and dates | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. This estimate assumes a Type 2 report. Check official dates and agree real durations with your team.
List services, data, infrastructure and vendors in the boundary. Choose report type and criteria with the CPA firm. Document how subservice organizations will be treated.
Customer commitments, service catalog, production architecture, hosting agreements and the list of delivery teams.
The scope memo identifies the customer-facing service, legal entity, environments, vendors and agreed report period. A cloud account in the diagram can be traced back to the inventory and an owner.
Escalate if the report is expected to cover a product or location that Engineering left out, or if the requested customer date leaves insufficient time for the agreed observation period and fieldwork.
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.
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.
Map criteria to controls and owners. Close gaps in access, change management, logging, incident response and supplier oversight. Draft the system description.
Approved scope, applicable Trust Services Criteria, system description draft and results from the first evidence walkthrough.
An access-review ticket contains the dated list of privileged identities, reviewer decisions and links to removal tickets. Its group counts reconcile to the identity-provider export.
Raise controls that nobody can run during leave, controls built only on paper, or controls that depend on logs configured to expire before fieldwork.
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.
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 draft agrees with the scope, service commitments and control matrix. Someone who uses the service can understand the boundary.
Management owns the description. Send the approved version to the CPA firm for its examination.
Collect contemporaneous records from real control runs and preserve populations for sampling. Escalate missed controls and capture corrective actions.
Control calendar, access to source systems, observation dates and the secure evidence request list.
A sampled production change links from the deployment population to the pull request, reviewer, approval time and deployment log. The approval can be shown to precede release.
Tell the project lead promptly if a population is incomplete or a control failed. Agree next steps with the CPA firm and retain the original records.
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 reviewer can reproduce group counts, trace each decision to an accountable person and confirm effective removal. Unclosed exceptions appear in the same review.
The identity administrator files source exports, signed review and closure evidence as one packet. The control owner submits the packet reference through the CPA firm’s secure channel when requested.
Fictional details. Use the same fields with evidence from your work.
The reviewer can reproduce the count and trace any selected item back to the original system.
Transfer the export, query, reconciliation and any exclusions to the independent tester.
Provide samples, respond to exceptions and confirm the accuracy of the description. Management signs its assertion and representation letter.
CPA request list, complete populations, management’s draft system description, vendor treatment and exception register.
Management can locate the signed assertion, issued report, documented exceptions and distribution decision in one restricted location.
Send unresolved disagreements about dates, scope or exceptions to management and the CPA firm before the assertion is signed.
Fictional details. Use the same fields with evidence from your work.
The written description, diagrams and control records agree. A reviewer can understand end-to-end operation.
Send the approved draft to management and the independent evaluator. Transfer it to the prescribed system plan or report template when needed.
Fictional details. Use the same fields with evidence from your work.
The signer has reviewed the claims, period and supporting evidence. The actual assertion follows the CPA firm’s applicable wording.
The CPA firm receives the signed assertion from management. Use this worksheet for preparation only.
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.
Track exceptions, evaluate scope changes and book the next examination around customer reporting needs.
Issued report, findings and exceptions, contract commitments, system change roadmap and upcoming assurance requests.
The next-period memo records confirmed dates, boundary changes and any corrective action with the retest artifact and reviewer.
Bring forward a likely coverage gap, an exception that recurs or a major service change before the next reporting dates are committed.
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.
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.
Type 1 examines whether the description is fairly presented and controls are suitably designed as of a given date. Type 2 also tests operating effectiveness over a specified period. Ask the report user what they need before agreeing the dates with a CPA firm.
AICPA · SOC suite of services (opens in a new tab)Start with evidence you can only collect while controls are running, such as dated access reviews, periodic restore tests and change approvals. Save the complete source population, the review decisions and proof that exceptions were resolved.
Management owns the description. Service owners supply the architecture and workflows, the compliance lead reconciles the controls, and management approves the version the CPA firm examines.
AICPA · SOC suite of services (opens in a new tab)