On this page
- Where do CUECs appear in a SOC 2 report?
- What do real CUECs look like, and what does each need from you?
- How do you review a vendor’s CUECs?
- What happens if a customer never implements its CUECs?
- How are CUECs different from CSOCs?
- Were CUECs always called complementary user entity controls?
- How do you write CUECs for your own SOC 2 report?
Complementary user entity controls (CUECs) are the controls a vendor’s SOC 2 report says its customers must run for the vendor’s own controls to meet its commitments. They sit in the system description, the service auditor does not test them, and they are your job as the customer. Each one needs an owner and evidence on your side.
A vendor can build multi-factor authentication into its product but cannot make you turn it on, and it cannot remove your leavers from your own tenant. When a commitment depends on an action like that, the report lists it as a CUEC instead of claiming an outcome the vendor does not control. This page shows real CUEC wording from two published reports, what each one needs from you, and how to review the list. Our SOC 2 compliance guide covers the rest of the report.
Where do CUECs appear in a SOC 2 report?
CUECs are listed in the system description, Section III in most reports, usually under a heading such as “Complementary User Entity Controls”. The auditor’s opinion letter points to them in a paragraph saying certain user entity controls are necessary alongside the vendor’s own. Not every report has them: management and the auditor decide whether a customer-side action is needed.
Two published reports show the opinion wording. The letter in TCWGlobal’s report says the description “indicates that certain complementary user entity controls that are suitably designed and operating effectively are necessary, along with controls at TCWGlobal, to achieve TCWGlobal’s service commitments and system requirements.” It then adds: “Our examination did not include such complementary user entity controls and we have not evaluated the suitability of the design or operating effectiveness of such controls.” Windsor Group AG’s letter says the same. The auditor tested the vendor’s side only, so nobody has tested your side unless you do.
Some reports number their description sections after the AICPA description criteria. Windsor Group AG’s headings run “DC 6” for CUECs and “DC 7” for subservice organization controls. There is no fixed count: TCWGlobal’s report lists nine CUECs and Windsor Group AG’s lists six. Wolf & Company notes CUECs are not mandatory in SOC 1 or SOC 2 reports, while Linford & Company, which performs SOC examinations, says most reports have them and that none “may be an indication of an incomplete report”. If a service your team configures heavily, such as identity or data handling, lists none, ask the vendor why. A vendor that does list CUECs is not raising a red flag. It has separated what it controls from what you control. Our annotated Type 2 report excerpts and guide to reading a vendor’s report show the surrounding sections.
What do real CUECs look like, and what does each need from you?
Real CUECs are short sentences that give the customer a task and cite the criterion it supports. The table takes eight from two published SOC 2 Type 2 reports and adds the control you would map each to, the usual owner and the evidence a vendor-risk team would keep. The last two columns are our recommendations, not report content.
The sources are TCWGlobal’s report on its StaffingNation payroll system (Security, Confidentiality and Processing Integrity, March 1, 2023 to February 29, 2024; report PDF) and Windsor Group AG’s report on windsor.ai (Security only, February 20 to May 20, 2026; report PDF). Both companies post their reports themselves. Wordings are quoted as published; use the current report your own vendor gives you.
| CUEC as written | Criteria the report cites | Your control and owner | Evidence to keep |
|---|---|---|---|
| ”Users are responsible for the safekeeping of their credentials to the StaffingNation system.” (TCWGlobal) | CC6.1, CC6.3 | Single sign-on or MFA, plus a credential rule in your acceptable use policy. Owner: IT. | Sign-in settings showing MFA required; signed policy acknowledgements. |
| ”Supervisors are responsible for contacting TCWGlobal in a timely manner to ensure terminated employee account access is removed.” (TCWGlobal) | CC6.1, CC6.3 | A leaver checklist with a step to remove or request removal in this vendor. Owners: HR and the app owner. | Leaver list compared with the vendor’s user list, with removal dates. |
| ”User entities have policies and procedures that grant Windsor Group AG system access only to authorized and trained personnel.” (Windsor) | CC6.1 | Approved access requests and a periodic review of the vendor’s user list. Owner: app owner. | Request tickets with approver; dated review sign-off. |
| ”User entities have policies and procedures for controlling user IDs and passwords that are used to access the Windsor Group AG system.” (Windsor) | CC6.6 | A sign-in policy that covers the vendor’s login, with MFA where the vendor offers it. Owner: security. | The policy; a capture of the tenant’s authentication settings. |
| ”User entities deploy physical security and environmental controls for all local and remote devices and access points that access the Windsor Group AG system.” (Windsor) | CC6.4 | A managed-device baseline and office access control. Owner: IT. | Device management compliance report. |
| ”User entities have controls that require providing notice to Windsor Group AG of any material changes in security requirements and the authorized users list.” (Windsor) | CC2.1 | A step to tell the vendor when admins, contacts or security requirements change. Owner: app owner. | Notice emails or tickets; vendor contact register. |
| ”Clients are responsible for the reconciliation of payroll reports generated by TCWGlobal to what they entered into the system (output to input) to ensure accuracy and completeness.” (TCWGlobal) | PI1.2 | A payroll reconciliation each pay period. Owner: finance. | Signed reconciliation per period, with differences resolved. |
| ”Clients are responsible for the review and approval of all user payroll information for each period.” (TCWGlobal) | PI1.2, PI1.3 | An approval step before payroll is submitted. Owner: payroll manager. | Approval record per period. |
Criterion IDs follow the AICPA Trust Services Criteria. TCWGlobal prints its common criteria without the CC prefix, so “6.1” is CC6.1. For the access rows, the matching controls in our controls library are AC-03 (approved access), AC-04 (leaver removal) and AC-06 (quarterly access review); EP-01 covers device baselines.
The owners differ: six rows sit with IT, security and HR, while the payroll rows belong to finance and relate to processing integrity (PI1.2 covers policies and procedures over system inputs, including completeness and accuracy). A review run only by the security team misses those. The list is also a floor, not a full inventory. TCWGlobal calls its CUECs “the minimum controls that customers must have in operation” and says they should not be regarded as a comprehensive list, and Windsor Group AG says its items “represent only a part of the control considerations that might be pertinent” at the customer. And some items are not controls at all. Wolf & Company separates CUECs from user responsibilities, the duties in your contract that you need to receive the service. TCWGlobal’s list includes “Users are responsible for reviewing and approving the terms and conditions stated in service agreements”, which reads as a contract duty. Hand that one to procurement and skip the control test.
How do you review a vendor’s CUECs?
For each critical vendor, take the CUEC list from the latest report, drop items that do not apply to how you use the service, give each remaining one an owner and a live check, and log gaps with dates. Repeat when the next report arrives, because vendors add and reword CUECs between periods.
- Read the opinion letter’s CUEC paragraph, then the subsection, and ask the vendor about any heavily configured service that lists none.
- Mark which CUECs apply to you. Wolf & Company’s example is a CUEC about physical security of an appliance in the customer’s server room, which means nothing to a customer who only logs in to a hosted service. Record each applicability decision.
- Map each applicable CUEC to a control you already run, a named owner and the evidence in the table. A CUEC with no matching control is a gap.
- Check the live state, not the policy: pull the tenant setting, or compare the vendor’s user list with your HR leavers. Linford & Company advises performing CUECs consistently over the period a report is relied on, so keep evidence across the period, not for a single day.
- Log each gap in your vendor risk register with an owner and a target date, and compare the new list with the last one when the renewed report arrives.
This is one piece of the vendor-risk work behind CC9.2, which reads “The entity assesses and manages risks associated with vendors and business partners.” Our SOC 2 vendor management guide covers the wider program.
What happens if a customer never implements its CUECs?
The vendor’s report and opinion stand, because the auditor tested only the vendor’s controls. What weakens is your ability to rely on any vendor control objective that depends on the missing CUEC. The gap shows up in neither audit, so it surfaces later, as a security incident or as a finding in your own audit.
Linford & Company makes the same point: control failures can still occur at a customer even when the vendor’s controls are designed and operating effectively. A missed CUEC is not an exception in the vendor’s report, since the vendor was never tested on it; SOC 2 exceptions and qualified opinions covers the vendor-side case. In your own SOC 2 examination, an auditor testing your vendor management can ask for evidence that you reviewed vendor reports and acted on what they assign to you. Nobody misstated anything. The risk sits between two organizations’ audits.
How are CUECs different from CSOCs?
CUECs run toward the customer: controls the vendor assumes its customers perform. Complementary subservice organization controls (CSOCs) run toward the vendor’s own suppliers: controls the vendor assumes its subservice organizations perform, such as a hosting provider’s physical security. Both appear in the same description but point in opposite directions.
Windsor Group AG’s report shows both. Its DC 7 section lists the controls it expects from its hosting provider, Hetzner Online GmbH, including “Physical access to data centers is approved by an authorized individual.” Because the provider is carved out, the auditor did not test those controls. Our carve-out vs inclusive method guide explains how the two methods differ.
Were CUECs always called complementary user entity controls?
No. Before SSAE 16, SAS 70 reports expressed the idea as user control considerations (UCCs), and Linford & Company notes you may still hear “client control considerations”. The current name arrived with SSAE 16, which replaced SAS 70 for reports from mid-2011, and SSAE 18 kept it. SOC 2 examinations are performed under AT-C sections 105 and 205; AT-C 320 is the SOC 1 standard. An older report that says “user control considerations” describes the same thing.
How do you write CUECs for your own SOC 2 report?
If you are the vendor, the question comes up in scoping: which commitments in your system description depend on something customers do? Write each CUEC as an action a customer can complete and evidence, tie it to a criterion, and keep the list to what your service needs. SOC 2 scope determination covers where that line falls, and Strike Graph’s list of prompting questions walks through access, network, change management, operations and monitoring. Once scope is settled, browse the SOC 2 auditor directory to choose the firm that will examine it.
More in SOC 2 Basics