Glossary · SOC and attestation

Your vendors can end up inside your SOC report as subservice organizations.

A vendor used by a service organization whose controls, together with the service organization's own, are needed for the report's criteria or objectives to be met.

Back to the glossary

01 · In plain words

In plain words

A vendor used by a service organization whose controls, together with the service organization's own, are needed for the report's criteria or objectives to be met.

Most service providers run on other providers: a cloud host, a payments processor, an outsourced support desk. When one of those vendors performs work that your controls depend on, it is a subservice organization. Your report has to say so, and has to say how it treats that vendor.

02 · Why it matters

Why it matters

Who cares about this, and what depends on it.

A customer reading your report wants to know whether the whole chain behind your service is controlled, not only the part you run. If a vendor holds production data or runs part of the process, its failures become yours. The report must either present the vendor by the carve-out method, leaving its controls out but naming the ones you expect it to run, or by the inclusive method, testing them inside your examination. Either way, the examiner will want to see that you monitor the vendor, usually by reading its own SOC report each year.

03 · Where you meet it

Where you will meet it

The documents, meetings and reports where it appears.

Section 3 of the report
The system description lists each subservice organization, what it does and how it is presented.
The CSOC table
The controls you expect each carved-out vendor to operate, paired with the criteria they support.
Your vendor management file
Annual review of each vendor's SOC report, exceptions noted and follow-up recorded.
The scoping call with the CPA firm
Where you agree which vendors are in the chain and which are only suppliers of tools.

04 · An example

A worked example

An illustration, not a real client.

Illustrative: a freight-tracking platform sorts its vendors

A Bengaluru logistics software company lists twelve vendors. Its cloud host stores all shipment data, and an SMS gateway sends delivery alerts. The team also uses a design tool and a payroll app. During scoping, the examiner and the company agree the cloud host is a subservice organization, presented by carve-out, because customer data lives there. The SMS gateway receives only order numbers and a phone number, so after review it is treated as a supplier that the company monitors under its vendor process. The design and payroll tools are outside the system boundary.

05 · Easy to mix up

Easy to mix up with

Neighbouring terms that mean something different.

User entity
The customer that uses your service. A subservice organization sits behind you, not in front.
Any vendor
Only vendors whose controls the criteria or objectives depend on qualify. A note-taking app usually does not.

06 · What to do

What to do with it

Practical steps, and the guides that go deeper.

  • List every vendor that stores, processes or runs part of the in-scope system, and why.
  • Decide with your examiner whether each is presented by carve-out or inclusive method.
  • Write the CSOCs you expect from each carved-out vendor in plain, checkable terms.
  • Collect each vendor's current SOC report and record your review of it.

Sources: AICPA AT-C section 320; AICPA Guide, SOC 2 Reporting on an Examination of Controls at a Service Organization; AICPA DC 200, 2018 Description Criteria.

Questions about Subservice organization

Does using AWS, Azure or Google Cloud make them a subservice organization?

Usually, if your production system runs there.

When the platform hosts the in-scope system, its physical and infrastructure controls support your criteria, so it is normally named as a subservice organization and carved out. Confirm the treatment with your CPA firm during scoping.

What if a subservice organization has no SOC report?

You need another way to show you monitor it.

Options include a certificate such as ISO 27001 with its scope checked, a questionnaire with evidence, or your own review. The examiner decides whether that monitoring is enough for the criteria involved.

Want this applied to your own systems?

Our team can walk through where this term touches your scope, your contracts and your evidence.