A subservice organization is a vendor your service provider relies on to deliver its own service — one whose controls are necessary, in combination with the provider's own, to meet commitments to customers. Think AWS beneath a SaaS. SOC reports handle them one of two ways: carve-out (exclude and disclose) or inclusive (include and test).
Not every vendor qualifies. The office-cleaning company and the sales CRM are vendors, but the cloud host running production is a subservice organization. The test: if their controls fail, do your commitments to customers fail?
Plain-English explainer · Applies to SOC 1 & SOC 2 · Last reviewed July 2026
A subservice organization is a vendor your service provider relies on to deliver its own service — one whose controls are necessary, in combination with the provider’s own, for the provider to meet its commitments to customers. Think AWS beneath a SaaS platform. SOC reports handle them one of two ways: carve-out (exclude and disclose) or inclusive (include and test). The concept works identically in SOC 1 and SOC 2. Where a carved-out report assumes specific controls at the vendor, those assumptions are listed as CSOCs — and their customer-side mirror is the CUEC. Both of those lists get a full treatment in our CUECs & CSOCs explainer. This page goes deeper on the underlying concept — what makes a vendor a subservice organization in the first place, how the two methods actually work, and what report readers and service organizations each need to do about the dependency.
Key Takeaways
- A subservice organization’s controls are necessary — combined with the service organization’s own — to meet the service commitments. The cloud host running production qualifies, but the office cleaner and the sales CRM do not.
- The concept and both methods apply identically in SOC 1 and SOC 2.
- Carve-out method (the overwhelming majority of reports): the vendor’s controls are excluded from the description, the dependency is disclosed, and the assumed controls are listed as CSOCs. Readers close the loop with the vendor’s own SOC report.
- Inclusive method (rare): the vendor’s relevant controls are included and tested, and the vendor’s management must provide its own written assertion and representations.
- Carve-out never means “not my problem”: the service organization’s monitoring controls over each subservice organization remain in scope and are typically tested.
What Counts as a Subservice Organization
In the attestation standards behind SOC 1 and SOC 2, a subservice organization is an organization the service organization uses to perform services that are relevant to the service organization’s own system — meaning its controls are needed, together with the service organization’s, to achieve the principal service commitments and system requirements (in SOC 1 terms, the control objectives). That word necessary is what separates a subservice organization from an ordinary vendor.
Usually a subservice organization
- The cloud or hosting provider running your production environment — compute, storage, physical security, environmental controls.
- A managed SOC / MDR provider monitoring your security alerts, when detection and response are part of what you promise customers.
- A payment processor executing transactions inside your service’s delivery path.
- Sub-processors that store, process, or transmit customer data as part of delivering your service.
Usually just a vendor
- The office-cleaning company — no relationship to your service commitments.
- The CRM your sales team uses to track its own pipeline — it supports your business, not the audited system.
- Internal HR or expense tooling that never touches the in-scope system or customer data.
- A marketing analytics tool measuring your website traffic — outside the boundaries of the system description.
The one-question test
“If their controls fail, do your commitments to customers fail?” If AWS loses physical control of the data centre, the SaaS company’s availability and security commitments fail with it — subservice organization. If the cleaning contractor has a bad week, nothing in the SOC report is affected — vendor.
The classification matters because it changes the report. Vendors are handled by ordinary vendor-management controls. Subservice organizations must be identified in the system description, handled by one of exactly two methods, and — under carve-out — leave visible assumptions (CSOCs) that every reader of the report is expected to chase down.
Carve-Out or Inclusive
Management elects a treatment for each subservice organization, and exactly two are permitted. Under carve-out, the vendor’s controls are excluded from the description and from the examination, and the report instead discloses the service, the criteria intended to be met there, and the CSOCs the system assumes — readers close the gap with the vendor’s own SOC report. Under inclusive, the vendor’s relevant controls sit inside the description and the auditor’s testing, which requires its management to sign its own assertion and give written representations. Carve-out dominates because the typical subservice organization is a hyperscale cloud provider that will not join a customer’s audit. The full treatment of the election — the decision table, what each method changes in the report, a dated worked example and the evidence a CPA firm requests — is in carve-out vs inclusive method. For what the resulting CSOC lists mean — and how they mirror the CUECs your report places on your own customers — see CUECs & CSOCs.
How It Looks Inside the Report
Section 3 — management’s description of the system — names each subservice organization, the services it performs, and the method used. The auditor’s opinion also flags the method. In a carve-out report, the language runs along these lines:
“The description excludes the controls of AWS. The trust services criteria can be achieved only if the controls expected to be implemented at AWS, described herein as complementary subservice organization controls, are suitably designed and operating effectively.”
Read that carefully: the opinion on the service organization is conditional on a set of controls nobody in this report tested. Closing that loop is the reader’s job — and it is the step most vendor reviews skip. When you assess a report, work through the subservice organizations the same way you work through the rest of the report’s structure:
- Find the subservice-organization list in Section 3 and note the method used for each one.
- For every carved-out vendor, obtain its own SOC report — for the hyperscalers, these are published for customers to download and review.
- Check that vendor’s report period overlaps the period you care about, and read its opinion and exceptions against the specific CSOCs your service organization relies on.
- Note what the vendor’s report carves out in turn — for critical chains, this is your fourth-party risk, and it can run several layers deep.
- Confirm the service organization’s monitoring controls over its subservice organizations were tested, and read any exceptions against them closely.
If the subservice organization’s own report carries a qualified opinion or exceptions touching the CSOCs in question, treat it exactly as you would exceptions in the primary report: ask what failed, what compensates for it, and whether it touches the services you consume.
Getting It Right as a Service Organization
If you are the one being audited, the subservice-organization work happens in scoping and in your vendor-monitoring controls — long before the auditor arrives.
- Identify your subservice organizations during scoping: hosting, managed SOC/MDR, payment processors, and sub-processors that handle customer data in your delivery path.
- Choose the method for each — in practice, almost always carve-out.
- Implement and evidence monitoring controls: an annual review of each subservice organization’s SOC report (its opinion, its exceptions, the CUECs it places on you, and its period coverage), SLA reviews, and incident-notification clauses in the contract.
- Map their CUECs into your control set. It is a chain: their CUECs become your controls, and your CUECs become your customers’ controls.
- Disclose accurately in your system description — name each subservice organization, the services it performs, and the method used.
Common pitfalls
- Treating every vendor as a subservice organization — it bloats the report and buries the dependencies that actually matter.
- Missing a real one — the report understates your dependency, and a reader who knows your architecture will notice.
- Ignoring period misalignment — a subservice organization’s report that ends months before yours leaves an unexamined gap in the chain.
- Relying on a subservice organization with a qualified opinion without documenting compensating controls on your side.
- Assuming carve-out means “not my problem” — the monitoring is your problem by design, and that is the trade the method makes.
A note on that period point: your own customers manage the gap between your report period and their fiscal year with a bridge letter — and you should expect to manage your subservice organizations’ gaps the same way. In SOC 2 and SOC 1 readiness engagements, Tranquility Cybersecurity builds the subservice-organization inventory, the method decisions, and the monitoring evidence before the examination begins — the examination itself is performed by independent, US-licensed CPA firms.
Subservice Organizations — Common Questions
Which vendors qualify, how the two methods differ, and how far down the chain to look.
What is a subservice organization?
Is AWS a subservice organization?
Is every vendor a subservice organization?
What are CSOCs?
Do I need to review my vendor’s subservice organizations’ reports too?
Why would anyone use the inclusive method?
Related reading: the Learn hub, CUECs & CSOCs, how to read a SOC 2 report, opinions and exceptions, what SOC 2 is, and our SOC 2 and SOC 1 services. More terms — including Carve-out Method, Inclusive Method, and CSOC — in the compliance glossary.
Related Reading
CUECs & CSOCs Explained
The controls a SOC report assumes of you and of carved-out vendors.
Read moreAnatomy of a SOC 2 Report
An interactive, annotated Type II example — click every element to see what it means.
Read moreHow to Read a SOC 2 Report
All five sections annotated, an 8-step reviewer checklist, and the red flags.
Read moreSOC 2 Opinions & Exceptions
Unmodified, qualified, adverse, disclaimer — and why exceptions are not qualification.
Read moreSOC 2 Knowledge Hub
Type 1 vs Type 2, criteria, timelines and audit prep — all guides.
Read moreSOC 1 Knowledge Hub
Every SOC 1 guide — Type I vs II, ICFR controls, timelines, costs — in one place.
Read more