Third-Party ISO Certification Body in UK, Europe, UAE, MENA & Globally. (MENA HO: UAE)
SCS KNOWLEDGE CENTRE

SOC 2 Scope and System Description | Boundaries | SCS

Define SOC 2 service boundaries, categories and shared responsibilities. Prepare a clear system description and scope discussion with SCS for your business.

  1. Home
  2. Knowledge Centre
  3. SOC 2 Scope and System Description | Boundaries | SCS

SOC 2 Scope and System Description — Services, Trust Services Categories and Shared Responsibilities

SOC 2 Scope and System Description — Services, Trust Services Categories and Shared Responsibilities
Define SOC 2 service boundaries, categories and shared responsibilities. Prepare a clear system description and scope discussion with SCS for your business.

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.

Share this article

Need ISO Certification for Your Business?

Speak with our certification specialists to understand certification requirements, audit process, implementation timelines and accredited certification services.

Frequently Asked Questions

Describe the defined service and its supporting system. The practitioner evaluates whether the proposed description and coverage are appropriate.
It needs enough operational detail to explain the service, responsible entity, supporting activities and relevant boundaries.
It is an important input because it records what is sold and the commitments made to customers.
Management is responsible for its description. The independent practitioner evaluates the relevant subject matter within the engagement.
A diagram can support understanding but rarely explains commitments, processes, people and responsibilities by itself.
Describe its actual access and effect on the service so its relevance can be evaluated.
Assess its role in the service rather than relying only on the list of corporate addresses.
Explain its separation and any shared dependencies. Proposed exclusions need review against the actual system.
Record the shared authority and controls. Product boundaries do not automatically remove the effect of common administration.
Identify commitments relevant to the proposed examination and show where they originate and how they are supported.
Do not assume that. Discuss the service, commitments, risks and intended users' needs with the practitioner.
The proposed coverage needs operational and risk information as well as the customer's stated requirement.
Yes. Describe the service promised and the resources and dependencies supporting it.
Explain expected processing results and customer commitments so the appropriate proposed coverage can be considered.
They address different concerns. Record personal-information roles and separately identify confidential-information commitments.
It is evidence about an upstream arrangement, not a substitute for describing your own service and retained responsibilities.
Identify its service, relationship to delivery, relevant assurance information and responsibilities retained by your organisation.
Discuss the actual reporting approach with the practitioner and keep the description and supporting information consistent.
Management still needs an accurate description and clear responsibilities; the method does not eliminate operational accountability.
They identify relevant controls expected of users within the reporting arrangement. Review their actual applicability and allocation.
Keep the operational and customer-facing arrangements consistent and clarify unresolved responsibilities through the appropriate process.
State what it does, its access, oversight and connection to the service rather than naming only the supplier.
Provide the actual dependencies and responsibilities for each relevant arrangement for scope review.
Record the difference and seek clarification before assuming the buyer will accept the proposed report.
Yes. Explain timing and effects on the proposed system, controls and description.
No. Describe the acquired activities and integration status for evaluation.
Provide enough to understand relevant inputs, processing, storage, transfers and responsibilities; agree deeper evidence needs later.
Agree authorised recipients and a suitable method before providing sensitive diagrams or records.
An initial discussion does not itself create assurance. Confirm the applicable engagement and independent reporting arrangements.
Send the service, entity, locations, dependencies, customer requirement and current description or report, identifying unresolved boundary questions.