Complementary user entity controls (CUECs) are the controls a SOC report assumes YOU, the customer, operate. Complementary subservice organization controls (CSOCs) are the controls assumed of a carved-out vendor. Miss either, and the assurance in the report doesn't fully apply.
Defined in the AICPA attestation standards. Both concepts come from the standards behind SOC 1 (AT-C section 320) and SOC 2, and appear in management’s system description in every report.
Plain-English explainer · Applies to SOC 1 & SOC 2 · Last reviewed July 2026
CUECs (complementary user entity controls) are controls that a service organization’s SOC report assumes its customers operate at their own end. CSOCs (complementary subservice organization controls) are controls assumed to be operated by a vendor the service organization itself relies on. Both appear in management’s description of the system in SOC 1 and SOC 2 reports because some control objectives can only be achieved in combination: the service organization does its part, the customer does theirs, and carved-out vendors do theirs. Since SSAE 18, the standards are strict that these lists contain only controls that are genuinely necessary to achieve the stated control objectives — not generic best-practice recommendations. That makes them short, specific, and worth reading: they are the parts of the assurance story that the service auditor did not test.
Key Takeaways
- CUECs are controls the report assumes the customer (user entity) operates — if you don’t operate them, the report’s assurance doesn’t fully apply to you.
- CSOCs are controls assumed of a carved-out subservice organization (typically a cloud/hosting provider), and readers cover them by obtaining that vendor’s own SOC report.
- Carve-out method: the vendor’s controls are excluded from testing and listed as CSOCs. Inclusive method: they are included and tested — fuller coverage, but rare.
- Under SSAE 18, CUEC lists were tightened to only controls necessary to achieve the control objectives — treat every listed CUEC as mandatory homework, not advice.
- Nobody audits CUECs for you: the service auditor doesn’t test them, so user entities (and their auditors) must map each CUEC to an internal control.
Complementary Controls: Yours and Your Vendor’s
A SOC report never claims the service organization controls everything. Control objectives are achieved by three parties together — and the report names the other two.
CUECs — Complementary User Entity Controls
Controls the service organization assumes its customers (user entities) operate at their own end, because the control objectives cannot be met by the service organization alone. Example: a payroll processor assumes the client reviews and approves payroll input before submitting it.
CSOCs — Complementary Subservice Organization Controls
Controls assumed to be in place at a subservice organization the service organization relies on — most commonly a cloud or data-centre provider under the carve-out method. Example: physical access to servers is controlled by the hosting provider, not the SaaS company.
A concrete SOC 1 example: a payroll processor’s control objective is that payroll is processed completely and accurately. The processor validates and calculates (its controls), but it cannot know whether the hours submitted were right — so “client reviews and approves payroll input before submission” is a CUEC. And if the processor runs on a carved-out cloud provider, “physical and environmental protection of production infrastructure” is a CSOC.
Carve-Out vs Inclusive Method
When a service organization depends on another vendor — a subservice organization — management must choose how that vendor appears in the report. The attestation standards allow exactly two treatments.
Carve-out method
- The subservice organization’s services are identified in the system description, but its controls are excluded from the description and from the auditor’s testing.
- The report lists the CSOCs the service organization relies on the subservice organization to perform.
- Report readers close the gap by obtaining the subservice organization’s own SOC report (e.g. the cloud provider’s SOC 1/SOC 2).
- This is by far the more common method — it does not require the subservice organization’s participation in the audit.
Inclusive method
- The subservice organization’s relevant controls are included in the system description and tested by the service auditor.
- Requires the subservice organization to cooperate: provide a management assertion, written representations, and access for testing.
- Gives report readers fuller, single-document coverage — no separate vendor report to chase.
- Rarer in practice, and generally impractical when the subservice organization is a hyperscale provider like AWS, Azure, or GCP.
What To Actually Do With Them
- Find the CUEC list in the system description (and any CUEC-related wording in the auditor’s opinion), then map every CUEC to a named internal control, owner, and evidence source at your organization.
- Keep the mapping current — your financial-statement auditor can ask for it when they rely on the SOC 1, and enterprise customers increasingly ask for it during vendor reviews.
- List the carved-out subservice organizations, obtain each one’s own SOC report, and check its period, scope, and exceptions cover the CSOCs your vendor relies on.
- Check the report period against your fiscal year — if there’s a gap, ask the service organization for a bridge letter covering the interim months.
- If you cannot operate a listed CUEC, raise it with the service organization: either a compensating control on your side or a scope conversation on theirs.
For service organizations drafting a description, the discipline runs the other way: keep the CUEC list short and genuinely necessary, name your subservice organizations and chosen method explicitly, and revisit both at every audit cycle. Vague or bloated CUEC lists are one of the most common findings we see in SOC 1 readiness work.
CUECs & CSOCs — Common Questions
The questions report readers and service organizations ask most.
What are CUECs in a SOC 1 report?
What is the difference between CUECs and CSOCs?
What is the carve-out method vs the inclusive method?
Do CUECs apply to SOC 2 reports too?
Who tests CUECs?
What happens if we can’t meet a CUEC?
Related reading: the Learn hub, what AT-C section 320 requires, SOC 1 bridge letters, our SOC 1 guide and SOC 1 vs SOC 2. More terms in the compliance glossary.
Related Reading
Subservice Organizations
Carve-out vs inclusive — how your vendors' vendors appear in the report.
Read moreWhat Is AT-C Section 320?
The AICPA attestation section behind SOC 1 and its description elements.
Read moreSOC 1 Knowledge Hub
Every SOC 1 guide — Type I vs II, ICFR controls, timelines, costs — in one place.
Read moreSOC 1 Description Criteria
Why SOC 1 has no DC 200 — its description requirements live in AT-C 320.
Read moreHow to Read a SOC 1 Report
A 20-minute review method — four sections, five checks, follow-ups to send.
Read moreHow to Read a SOC 2 Report
All five sections annotated, an 8-step reviewer checklist, and the red flags.
Read more