Compliance Guide

Complementary User Entity Controls in AI Vendor SOC 2 Reports

Complementary user entity controls (CUECs) are controls an AI vendor's SOC 2 report assumes the customer operates. To implement them, extract each CUEC from the report, separate it from subservice organization controls, assign a named internal owner, and define the evidence that shows it operates over time.

How to extract and map CUECs

From CUEC to testable internal control

Five stages for turning each CUEC into an owned, evidenced control
StageLabelDescription
1ExtractLocate every CUEC in the report and its system description.
2ClassifySeparate CUECs from subservice organization controls.
3AssignGive each CUEC a named internal owner.
4EvidenceDefine the artifact and the frequency of collection.
5ReviewRecord gaps and exceptions in the vendor risk file.

CUECs that depend on runtime-level controls

Some AI-related CUECs cannot be satisfied with a policy document alone. If a vendor expects you to restrict which tools or data an AI integration can reach, or to monitor how the service is used, you need technical controls that operate while the system is running.

For agent-based deployments, this usually means three capabilities:

  1. Agent identity. Each agent has its own identity rather than sharing a human user's or a common service credential, so access can be attributed and revoked.
  2. Least privilege. Permissions are scoped to the tools and data the agent needs.
  3. Tool call logging. Tool calls are logged with enough context to reconstruct what an agent did and under whose authority.

These are the artifacts that turn a statement like 'customer monitors usage' into evidence.

Turn CUECs into evidence you can show

Talk to our team about runtime governance for AI agents, including agent identity, permissions, and audit logging that support customer-side controls.

Talk to an Expert