Guide, read 12 Nov 2026

# AWS, Google Cloud and Azure are usually carved out of a SOC 2, which creates CSOCs and CUECs

**The short answer:** Complementary user entity controls (CUECs) are controls a customer must run for the service's controls to work. Complementary subservice organization controls (CSOCs) are controls a hosting provider such as AWS, Google Cloud or Azure is expected to run. Under the carve-out method, a SOC 2 describes them but the auditor does not test them.

[Open the glossary](https://soc2compliancesoftware.com/glossary/) | [See the ranked index](https://soc2compliancesoftware.com/)

## CUECs are controls the customer must run for the service to be secure

A SOC 2 examines the controls of one service organization, but those controls assume things about the customers who use the service. BARR explains that a company's controls were designed with the assumption that certain controls exist at customer organizations, and the system description lists them as complementary user entity controls. BARR's examples are protecting established user IDs and passwords, removing terminated employee access, and endpoint protection on workstations.

BARR, citing the AICPA's recommendation, names eight items a system description should cover: types of services, principal service commitments and system requirements, components of the system, trust services criteria and corresponding controls, CUECs, complementary subservice organization controls, system incidents, and significant changes during the period. CUECs and CSOCs are two of the eight, so a description that omits both lists is incomplete against that checklist.

Write CUECs as customer actions the service relies on, not as a disclaimer. Each should connect to a criterion the company's own controls cannot complete alone: user provisioning on the customer side, review of access granted to the customer's staff, or protection of API keys the company issues. A long list of generic duties reads as risk transfer, and a customer's reviewer will compare each item with what the contract and product let the customer do.

## A subservice organization is a vendor whose controls the company relies on

Schellman separates a vendor from a subservice organization with one test. If a third party's controls, in combination with the company's own, are necessary to meet service commitments, system requirements or the SOC 2 criteria, it is a subservice organization. If the company's controls are enough and vendor monitoring is sufficient, it is only a vendor. Schellman's examples of subservice organizations are a data center operator and a data destruction company relied on to purge data.

Schellman adds a second question: is the description of the vendor's services needed for customers to understand the system? A yes to either question makes the vendor a subservice organization. Its examples of plain vendors are utility companies, accounts payable and sales and marketing providers. A monitoring service whose alerts the company reviews itself stays a vendor, because the control stays with the company.

Plain vendors still count. Schellman says controls over vendors, such as an annual risk assessment, periodic performance checks and clear escalation paths, are needed to meet CC9.2, which reads 'The entity assesses and manages risks associated with vendors and business partners.' A cloud host usually lands on the subservice side, because the company cannot run the physical and environmental security of the provider's data center.

## Carve-out leaves subservice controls untested, and inclusive puts them in the examination

Under the carve-out method, the description and the tests leave out the subservice organization's controls. Schellman says most of its clients choose it, because the provider has its own SOC report that customers can read. Customers then read two documents: the company's report and the provider's. Because the auditor does not test the provider, the company needs its own way to monitor the provider's control environment.

Under the inclusive method, the description and the tests cover the subservice organization's controls. Schellman calls this uncommon and says it needs the provider's cooperation: a written assertion from its management, a system description of its own, and a management representation letter. It fits a smaller provider with no SOC report of its own. It also makes the company responsible for explaining any exceptions found in that environment to its customers.

One duty applies to both methods. Schellman says the report must state the nature of the services each subservice organization provides, whichever method is used. Under carve-out, the report must still define the controls expected to operate at the subservice organization. Those expectations are the complementary subservice organization controls, and they belong in the system description next to the CUECs.

| Method | Subservice controls in the description and tests | Extra paperwork | What the customer reads |
|---|---|---|---|
| Carve-out | No, described only as expected controls (CSOCs) | The company monitors the provider | The company's report and the provider's report |
| Inclusive | Yes, described and tested | Provider's management assertion, system description and representation letter | One report holding both sets of controls |

## AWS, Google Cloud and Azure each publish SOC reports and a shared responsibility page

AWS publishes SOC 1, SOC 2 and SOC 3 reports and says the SOC 2 is available to customers from AWS Artifact while the SOC 3 is a public whitepaper. Its FAQ says Ernst & Young LLP performs the audits, that SOC 2 and SOC 3 reports are issued twice per year, and that each covers 12 months ending 3/31 or 9/30. A monthly SOC Continued Operations Letter covers the span since the last report.

Google Cloud says its core Google Cloud and Google Workspace SOC 2 Type II reports are issued quarterly and downloaded through the Compliance Reports Manager. Microsoft's Azure page says customers can access Azure SOC audit reports and bridge letters from the Service Trust Portal. A company that carves out its host should save the report period, the opinion and the list of complementary controls from whichever of these it uses.

The shared responsibility pages show which duties stay with the company. AWS says the customer manages the guest operating system, including updates and security patches, associated application software and the security group firewall configuration. Microsoft's table assigns customer data, configurations and identities to the customer in every deployment model, and the physical datacenter to Microsoft for IaaS, PaaS and SaaS. Google says responsibilities differ for each service, and each has a different configuration profile.

| Provider | Where the SOC 2 comes from | Public SOC 3 | Stays with the customer, per its page |
|---|---|---|---|
| AWS | AWS Artifact | Whitepaper on the AWS SOC page | Guest operating system and patches, application software, security group configuration |
| Google Cloud | Compliance Reports Manager | Also requested through Compliance Reports Manager | Varies by service; each has its own configuration profile |
| Microsoft Azure | Service Trust Portal | Publicly available Azure SOC 3 report, per Microsoft | Customer data, configurations and settings, identities and users in every model |

## A CSOC statement names the provider, the service and the criteria it supports

BARR's advice is to list the hosting provider, whether AWS, Azure or GCP, and describe what criteria it helps the company meet. A usable statement reads: the provider is expected to operate physical access controls over its data centers, environmental protections and host infrastructure, supporting the physical access and availability criteria. Then state the other half, which is how the company monitors the provider and how often.

Reading the provider's report is the control that makes a carve-out safe. Schellman's questions are: did the provider receive an unqualified opinion, did the auditor note exceptions that touch your service, which CUECs does its report list, and are those CUECs in place and performed effectively at your company? The last one is easy to miss. The provider's report lists duties for you, and your own examination can produce an exception on them.

Keep a dated record of each review: the report period, the reviewer, exceptions noted, CUECs mapped to your controls, and the gap to the latest bridge letter. For AWS, the monthly letter covers the span from the last report to the letter date. An auditor can ask for that record when testing a vendor monitoring control, and a missing review is the kind of deviation that becomes a Section 4 exception.

## More guides

- [A penetration test is not required for a SOC 2, and NIST SP 800-115 gives 4 phases to scope against](https://soc2compliancesoftware.com/guides/penetration-test-scope-for-soc-2/)
- [A SOC 2 readiness assessment is a 4-phase gap review that ends without an auditor opinion](https://soc2compliancesoftware.com/guides/readiness-assessments/)
- [A SOC 3 is the public summary of a SOC 2 examination, and AWS, Google and Microsoft publish one](https://soc2compliancesoftware.com/guides/soc-3-and-the-public-report/)

## Sources

- [Schellman: The Difference Between Subservice Organizations and Vendors](https://www.schellman.com/blog/soc-examinations/subservice-organizations-vs-vendors-within-soc), read 12 Nov 2026
- [Schellman: Which SOC Method Should You Use, Carve-Out vs Inclusive](https://www.schellman.com/blog/soc-examinations/carveout-vs-inclusive-method), read 12 Nov 2026
- [BARR: How to Write System Descriptions](https://www.barradvisory.com/resource/how-to-write-system-descriptions/), read 12 Nov 2026
- [BARR: Breaking Down SOC 2 Reports, Each Section](https://www.barradvisory.com/resource/sections-of-a-soc-2-report/), read 12 Nov 2026
- [AWS: SOC Compliance and FAQs](https://aws.amazon.com/compliance/soc-faqs/), read 12 Nov 2026
- [AWS: Shared Responsibility Model](https://aws.amazon.com/compliance/shared-responsibility-model/), read 12 Nov 2026
- [Microsoft Learn: Shared responsibility in the cloud](https://learn.microsoft.com/en-us/azure/security/fundamentals/shared-responsibility), read 12 Nov 2026
- [Google Cloud: Shared responsibility and shared fate](https://cloud.google.com/architecture/framework/security/shared-responsibility-shared-fate), read 12 Nov 2026
- [Google Cloud: SOC 2 compliance](https://cloud.google.com/security/compliance/soc-2), read 12 Nov 2026
- [Microsoft Learn: Azure SOC 2 Type 2](https://learn.microsoft.com/en-us/azure/compliance/offerings/offering-soc-2), read 12 Nov 2026
Last reviewed 12 Nov 2026.

Canonical: https://soc2compliancesoftware.com/guides/complementary-user-entity-controls-and-carve-outs/
