Skip to content
SOC 2 Compliance Software

Home / Glossary / Complementary user entity controls

Glossary, read 12 Nov 2026

Complementary user entity controls in a SOC 2 examination, defined with a sourced example

All termsRead the guides

The definition of Complementary user entity controls

In a Schellman-format report, CUECs appear in the system description section when they are in scope. They state what the service organization assumes you do, so its criteria can be met. If a provider says customers must remove access for departed staff, the provider's controls cannot protect you when you skip that step.

Schellman advises readers to reconfirm that CUECs noted in a provider's report are implemented, designed and operating effectively in their own organization, and to implement or strengthen them if they are lacking. Most people skip this and read only the opinion page. Keep a record of who owns each CUEC from your cloud host and where the evidence that it ran is stored.

The same logic applies to you as a customer of a carved-out subservice organization. Schellman's carve-out guidance asks whether the subservice organization's report noted CUECs, whether they are in place at your organization, and whether you perform them effectively. Cross-check each one against a named owner and the evidence in your own team, since a provider's controls only work if yours do too.

A sourced example

Schellman's report guide gives a concrete CUEC: customers may be expected to implement controls ensuring each user account provisioned to access the provider's system was set up properly and carried the appropriate permissions for each user's role. Schellman: How to read your SOC report, read 12 Nov 2026.

Sources

  1. Schellman: How to read your SOC report, read 12 Nov 2026
  2. Schellman: Using a vendor's SOC 2 report, read 12 Nov 2026
  3. Schellman: Carve-out versus inclusive method, read 12 Nov 2026

Last reviewed 12 Nov 2026.