What are complementary user entity controls (CUECs)?
Complementary user entity controls, or CUECs, are controls the service organization assumes its customers will operate for the overall controls to work. They are listed in the SOC 2 report, and the auditor does not test them.
The full answer
Complementary user entity controls are the assumptions a service organization builds into its control design about what customers must do on their end. A SaaS provider might design strong access controls internally, but those only protect you if your team promptly removes departing employees, enforces its own passwords, and reviews the access reports the vendor exposes. Those customer-side duties are the CUECs.
They appear in a dedicated section of the SOC 2 report, usually near the system description or the auditor's test results. The auditor lists them but does not test them, because they sit outside the service organization's boundary. Responsibility for operating them falls entirely on the user entity, meaning your company when you are the customer reading the report.
This matters in two directions. When you read a vendor's SOC 2, the CUEC list is effectively a to-do list: the report's clean opinion only holds if you actually perform those controls. Because a Type 2 report covers an observation window that usually runs three to twelve months, the vendor is assuming you operated those controls across the whole period, not just once. When you publish your own SOC 2, well-written CUECs keep your scope defensible, because you are not claiming to control what your customers configure.
Practically, review the CUEC section as carefully as the opinion letter. Map each item to an owner on your side and confirm it is actually happening. When you scope a SOC 2 through the AuditNex network, the licensed firm helps you word CUECs so they reflect real shared responsibilities rather than quietly shifting your own obligations onto customers.
Go deeper
Short answer not enough? These pages cover the full picture:
Get matched with the right auditor
Answer a few questions about your scope and see transparent, comparable pricing from vetted audit firms — no sales calls.
Get instant pricing →Talk to auditors who handle this every week
Every firm on AuditNex is listed on identical terms — placement cannot be bought, and credentials are independently checked.
Related questions
Are SOC 2 reports public?
No. A SOC 2 report is confidential and shared only under NDA with customers, prospects, and auditors. If you want a freely shareable version, the public summary is a SOC 3 report.
Can I share my SOC 2 report with prospects?
Yes, but almost always under an NDA. SOC 2 reports are confidential, so companies share them with prospects and customers after a signed non-disclosure agreement. For a freely shareable version, use a SOC 3.
Can buyers verify my SOC 2 report is real?
Yes. Buyers verify a SOC 2 by confirming the signing CPA firm is licensed, checking the report period and opinion, and often contacting the firm directly. A real report names a licensed firm and follows AICPA formatting.
Can one SOC 2 report cover multiple products?
Yes. One SOC 2 report can cover multiple products or systems as long as they share the same control environment and you define that scope clearly in the system description. Many companies audit their whole platform in a single report.
How long is a SOC 2 report valid?
There is no formal expiry — the AICPA sets none. In practice, buyers treat a SOC 2 report as current for about twelve months from its period end date, then expect a fresh Type 2.
What is a SOC 2 bridge letter?
A SOC 2 bridge letter is a short statement from your management confirming that nothing material changed between your report's period end and a customer's review date. It is written by you, not your auditor.
Sources: AICPA SOC 2 Trust Services Criteria (2017, rev. 2022); AICPA SSAE No. 18 attestation standards. Answer written and maintained by the AuditNex research team; last reviewed July 26, 2026. AuditNex is a marketplace — accredited firms price and scope engagements independently.