SOC 2 Scope and System Description — Services, Trust Services Categories and Shared Responsibilities
A SOC 2 enquiry can become difficult before evidence collection starts. The sales agreement names a platform, the architecture diagram includes several products, and a cloud provider operates part of the infrastructure. The proposed examination needs a coherent account of that service.
Begin with what the organisation promises to deliver and the system supporting those promises. From an assessment perspective, a useful scope record explains boundaries and interfaces well enough for the proposed work to be evaluated. It also identifies unresolved decisions instead of hiding them behind a broad company description.
For a customer deciding between report types, use the separate SOC 2 Type 1 and Type 2 guide. This article addresses the service being examined.
Start with the service the customer purchases
Describe the actual offering in ordinary language. “Technology services” gives little indication of whether the supplier hosts applications, manages customer networks or processes transactions. Identify the responsible entity and explain how the service reaches its users.
The system description has a formal purpose within a SOC 2 engagement. AICPA publishes Description Criteria for its preparation and evaluation. Management's description needs consideration by the independent practitioner; an enquiry worksheet is only a starting point.
Use the service agreement, operating model and relevant architecture information together. If they describe different versions of the service, record the differences before proposing final wording.
Build a boundary record that can be reviewed
|
Area |
Information to record |
Question for review |
|
Service |
Named product and activities delivered |
Does this match the customer's purchase? |
|
Organisation |
Delivering entity and management authority |
Who is responsible for the described operation? |
|
Infrastructure |
Hosting environments and relevant facilities |
What supports the service and where are dependencies? |
|
People and processes |
Operational teams, administration and support |
Which functions can affect the service commitments? |
|
Information |
Important data flows and handling activities |
What enters, moves through and leaves the system? |
|
External providers |
Outsourced activities and significant dependencies |
How are responsibilities divided and evaluated? |
Keep exclusions explicit and explain the reasoning. Removing an office from a diagram does not remove the effect of its administrators if they still manage the production service. Conversely, a separate product should not be included solely because the same company sells it.
Connect categories to commitments and risks
Selecting Trust Services Categories is a scope decision. Record the customer's assurance needs, relevant service commitments and associated risks before discussing the proposed coverage with the practitioner. Avoid treating a longer category list as proof of stronger assurance for an unrelated service.
The AICPA Trust Services Criteria resource is the authoritative starting point. The following is an illustrative decision record, not a prescribed selection formula.
|
Service question |
Information that helps the decision |
|
What security commitments are made? |
Contractual commitments, information flows and risk decisions |
|
What availability is promised? |
Defined services, capacity assumptions and continuity dependencies |
|
What processing result is expected? |
Validity, accuracy, completeness, timing and authorisation expectations |
|
What information is confidential? |
Classification, restrictions and handling commitments |
|
What personal information is handled? |
Processing roles, notices, responsibilities and customer conditions |
Retain the rationale for the proposed categories. Detailed control design and evidence follow from the engagement and actual operation rather than from a generic checklist alone.
Explain cloud and subservice responsibilities
A provider's report can be relevant to an outsourced activity. It does not, by itself, explain the controls retained by the organisation using that provider. Describe the service obtained, the division of responsibilities and the information available for oversight.
Carve-out and inclusive reporting affect how subservice organisations are addressed. Discuss the applicable approach with the practitioner and keep it consistent with the description. Identify complementary controls and relevant user responsibilities without assuming every tenant or supplier performs them identically.
For a vendor-specific illustration of divided responsibilities, AWS explains its shared responsibility model. Apply the actual service arrangement rather than treating one vendor's model as a universal SOC 2 rule.
Follow one service across locations
Consider a fictional SaaS provider contracting through a UAE entity, using Malaysian operations support and an external cloud platform. One team administers production, another handles customer requests, and a third-party service processes messages.
The scope record follows each activity that affects the offering. It identifies who grants access, who authorises changes, where information is processed and which external service supports delivery. It also records a separate experimental product that is not part of the customer offering being proposed.
This example illustrates boundary reasoning. It does not establish an acceptable scope or multi-location reporting arrangement. Those depend on the actual system and engagement review.
For regional context, use the existing UAE and Saudi Arabia SOC 2 guide and Malaysia SOC 2 guide.
Review changes before relying on an old description
Acquisitions, new services, support transfers and cloud migrations can change the boundary. Maintain a change record identifying what happened, when it occurred and which commitments or responsibilities were affected. Inform the relevant practitioner when planning the engagement or evaluating a change during it.
Check the description against current contracts, diagrams, operational authority and provider arrangements. Resolve contradictory terminology before it reaches customer-facing material.
Prepare the scope discussion with SCS
Send the proposed service description, entity, operating locations, architecture summary and responsibility record. Include the customer's requirement and any current report. Mark matters that remain undecided.
Use the SOC 2 evidence guide for detailed record preparation after the boundary has been clarified. For the commercial discussion, visit SCS SOC 2 services or contact SCS about the proposed scope and independent examination arrangements.
Need ISO Certification for Your Business?
Speak with our certification specialists to understand certification requirements, audit process, implementation timelines and accredited certification services.