Skip to content
SOC 2 Compliance Software

Home / Glossary / User entity

Glossary, read 12 Nov 2026

User entity in a SOC 2 examination, defined with a sourced example

All termsRead the guides

The definition of User entity

Schellman's report walkthrough describes complementary controls at user entities as the activities "your user entity (usually the customer)" is expected to implement. For a SOC 2 you might sit on either side: your customers are your user entities, and your cloud provider treats you as one of its user entities.

The common failure is filing a vendor's report without reading it. A Schellman article by a former internal auditor describes reviewing SOC reports that were years out of date, covered a different system from the one being bought, or reported critical findings that nobody flagged. Customers' security teams who read reports properly check the period, the scope, the opinion and the complementary controls.

In SOC 1 examinations the user entity's auditor is a direct reader. Schellman says the reporting period needs to overlap substantially with the period of the financial statements being audited, otherwise the user auditor may do additional testing. The same overlap question is why customers of a SOC 2 provider look at the report period and ask what happened after it ended.

A sourced example

A Schellman article on using vendors' reports gives a concrete failure from a former internal auditor: SOC reports reviewed that were "years out of date," for a system different from the one the organization was considering buying, or that reported critical security findings, none of it flagged in due diligence. Schellman: Using a vendor's SOC 2 report, read 12 Nov 2026.

Sources

  1. Schellman: Using a vendor's SOC 2 report, read 12 Nov 2026
  2. Schellman: How to read your SOC report, read 12 Nov 2026
  3. Schellman: Choosing a SOC reporting period, read 12 Nov 2026

Last reviewed 12 Nov 2026.