A subservice organization is a vendor whose controls are necessary, together with yours, to meet your control objectives or the applicable Trust Services Criteria. Under the carve-out method your report excludes that vendor’s controls and names what it is expected to do. Under the inclusive method the vendor’s controls are described and tested inside your report.
Key takeaways
- Not every vendor is a subservice organization. The test is whether you rely on its controls to meet your criteria.
- Carve-out is the norm, and effectively the only option for hyperscale cloud providers.
- Inclusive requires the subservice organization to cooperate, provide a written assertion and be tested by your auditor.
- Either way, you must monitor the subservice organization.
Vendor or subservice organization?
| Vendor | Usually classified as | Why |
|---|---|---|
| Cloud infrastructure host | Subservice organization | Physical and environmental controls are theirs |
| Managed database or identity provider holding in-scope data | Subservice organization | Their controls are part of meeting your criteria |
| Colocation data center | Subservice organization | Physical access |
| HR system, office productivity suite | Vendor | Supports the business but is not needed to meet the criteria for the described system |
| Marketing analytics tool with no customer data | Vendor | Outside the system boundary |
Classification depends on your system description. See how to scope systems for SOC 2.
The two presentation methods
| Carve-out | Inclusive | |
|---|---|---|
| Subservice controls in your description | Excluded | Included |
| Tested by your auditor | No | Yes |
| Subservice management assertion | Not required | Required |
| What your report lists | The services used and the CSOCs assumed | The subservice organization’s relevant controls and results |
| Typical use | Cloud hosts, large SaaS providers | Closely related entities, small specialist providers |
Monitoring is your control
With carve-out, the reader still needs to know you oversee the provider. Typical monitoring: annual review of the subservice organization’s SOC report, follow-up on its exceptions, confirmation that its user controls are in place on your side, and tracking of service performance. See CUECs and CSOCs explained and vendor management for SOC 2.
Frequently asked questions
Can I leave a subservice organization out of the description?
No. If you rely on it, it must be disclosed.
What if my subservice organization has no SOC report?
Use other monitoring: questionnaires, contractual commitments, certifications, your own testing. Expect more auditor attention.
Does carve-out weaken my report?
No. It is the expected presentation for cloud-hosted services, provided the monitoring is real.
Sources & further reading
AICPA SOC 1 and SOC 2 guides; AT-C sections 205 and 320.
Related: SOC 2 on AWS and Azure, How to read a SOC 2 report.
Work with a licensed CPA firm
Auditsuisse Assurance NA PC is a licensed US CPA firm enrolled in the AICPA Peer Review Program. See our published SOC 2 fees or book a scoping call.