# CUECs and CSOCs Explained: The Controls a SOC Report Assumes Others Perform

> A CUEC is a control a SOC report assumes customers perform; a CSOC is one it assumes subservice organizations perform. Definitions and examples.

- Canonical: https://auditsuisse.com/cuec-and-csoc-explained
- Language: en
- Author: Sébastien Ruosch, CPA — Director of Audits
- Published: 2026-11-14
- Updated: 2026-11-14
- Alternates: fr → https://auditsuisse.com/fr/cuec-et-csoc-expliques, es → https://auditsuisse.com/es/cuec-y-csoc-explicados

SOC reports

 The short answer

Complementary user entity controls (CUECs) are controls that a service organization assumes its customers will implement for the service organization’s controls to be effective. Complementary subservice organization controls (CSOCs) are controls it assumes its own providers, such as a cloud host, will implement. Both are listed in the system description of a [SOC 1](https://auditsuisse.com/soc-1) or [SOC 2 report](https://auditsuisse.com/soc-2).

## Key takeaways

- CUECs point downstream to the customer. CSOCs point upstream to a subservice organization.
- They mark the edges of what the auditor’s opinion covers.
- If you receive a report, the CUECs are a to-do list for your own team.
- If you issue a report, write CUECs that are specific and necessary, not a list of disclaimers.

## Examples

| Type | Example |
| --- | --- |
| CUEC | The customer is responsible for removing its own users’ access when they leave |
| CUEC | The customer is responsible for configuring single sign-on and multi-factor authentication for its tenant |
| CUEC | The customer is responsible for reviewing the reports the service produces |
| CSOC | The cloud provider is responsible for physical access to data centers |
| CSOC | The cloud provider is responsible for environmental protections and hardware disposal |

## If you are the service organization

Identify the points where your control depends on someone else. Write each CUEC as a single action a customer can verify. Tie each to the criterion it supports. For CSOCs, obtain and review the subservice organization’s own SOC report at least annually and check that its CUECs, which now apply to you, are in place. That review is itself a control auditors test under vendor management. See [vendor management for SOC 2](https://auditsuisse.com/vendor-management-for-soc-2-compliance).

## If you are the customer

1. Extract the CUECs from section III of the vendor’s report.
2. Assign an owner for each.
3. Confirm each is performed, and keep evidence.
4. Note any you cannot perform and discuss them with the vendor.

Your own auditors may ask to see this mapping. See [how to read a SOC 2 report](https://auditsuisse.com/how-to-read-a-soc-2-report).

## How they relate to carve-out reporting

CSOCs appear when a subservice organization is presented using the carve-out method, which is the usual treatment for large cloud providers. See [subservice organizations: carve-out vs inclusive](https://auditsuisse.com/subservice-organizations-carve-out-vs-inclusive).

## Frequently asked questions

### Are CUECs tested by the service auditor?

No. They are outside the service organization’s system. The auditor considers whether they are appropriately described.

### How many CUECs is normal?

There is no norm. A very long list can signal that the vendor has pushed core responsibilities onto customers.

### Do CUECs appear in SOC 3 reports?

SOC 3 reports are summaries; the full list is in the SOC 2 report.

## Sources & further reading

AICPA SOC 2 Guide; DC section 200, Description Criteria.

**Related:** [SOC 2 on AWS and Azure](https://auditsuisse.com/soc-2-on-aws-and-azure), [Glossary](https://auditsuisse.com/glossary).

---
Source: https://auditsuisse.com/cuec-and-csoc-explained · This Markdown edition is generated from the same content as the HTML page.
