ISC · Considerations for System and Organization Controls (SOC) Engagements · 7 practice questions
SOC 2 Complementary User Entity Controls: Examples and Disclosure
Necessary customer controls are CUECs: disclose them in the system description, but do not test them as service-organization controls. Below, sort access controls for Beacon's payroll platform, assuming all are necessary and its data center uses the carve-out method.
Try one first
Hint
Ask which party (user entity, service organization, or third-party colocation) must perform the activity for the service organization's controls to function.
Answer A. A complementary user entity control is an action the user entity is expected to perform that the service organization's controls assume. Prompt notification by each customer about employee access changes is something the user entity must perform for the service organization's access-management controls to operate as intended. Therefore option C is best classified as a complementary user entity control.
Why not B: This is tempting because it relates to security of the service, but it is performed by the third-party colocation provider, making it a subservice-organization control that is carved out under the carve-out method, not a complementary user entity control.
Why not C: This might tempt candidates because it involves the colocation provider, but the activity is performed by the service organization itself, so it is a service-organization control. Under the carve-out method, controls actually performed by the third-party colocation are treated as subservice-organization controls (carved out), whereas monitoring the subservice is a service-organization responsibility.
Why not D: This can mislead because customers approve the batch totals, but the reconciliation itself is performed by the service organization. Because the service organization performs the control activity, it is a service-organization control rather than a complementary user entity control.
Sort it
Does a customer perform the necessary control outside Beacon's system boundary? Disclose it as a CUEC; do not test it.
Does Beacon perform the control? Describe and test it within the SOC 2 Type 2 scope.
Does the carved-out data center perform a necessary control Beacon assumes? Identify it as a CSOC; exclude direct testing.
| Item | Goes to |
|---|---|
| Each customer approves which employees receive payroll-approval and data-export access. | Complementary user entity controlThe customer makes the authorization decision. Beacon's enforcement of permissions does not transfer that responsibility. |
| Beacon reviews the data center's SOC report and investigates physical-access exceptions. | Service-organization controlBeacon performs the monitoring, even though the evidence concerns the data center. |
| The data center checks badges before allowing entry to the server area. | Complementary subservice organization controlThe data center performs the physical-access check that Beacon depends on. |
| Beacon generates monthly user-access reports and makes them available to customers. | Service-organization controlBeacon produces the reports. Customer review is a separate control. |
| Each customer reviews Beacon's monthly access report and reports inappropriate permissions. | Complementary user entity controlThe customer performs the necessary review, even though Beacon supplies the report. |
| Each customer enables MFA for its customer-administrator accounts during setup. | Complementary user entity controlProviding an MFA feature is not the same as activating it. The required activation is the customer's responsibility. |
| The data center logs visitors entering the server area. | Complementary subservice organization controlVisitor logging is performed by Beacon's subservice organization, not by a customer. |
| Beacon removes application access after receiving a termination notice from an authorized customer contact. | Service-organization controlBeacon executes the removal. The customer's notice is a separate complementary control. |
| Each customer promptly notifies Beacon when an employee's access must be removed. | Complementary user entity controlBeacon's removal process depends on timely information supplied by the customer. |
| Beacon enforces MFA for its own privileged personnel. | Service-organization controlBeacon performs this control over its personnel. Customer-administrator MFA activation remains a separate customer responsibility. |
| The data center monitors video covering access to the server area. | Complementary subservice organization controlThe carved-out provider performs the monitoring. Its separate SOC report does not replace disclosure of the dependency. |
| Each customer maintains its list of contacts authorized to request access changes from Beacon. | Complementary user entity controlThe customer determines who may authorize requests. Beacon's reliance on that list does not make its maintenance a Beacon control. |
Key points
- Remember: classify by who performs the control, not by whose system or report it concerns.
- Providing an access report does not make the customer's review a Beacon control.
- Carve-out excludes direct testing of data center controls, not disclosure of necessary complementary subservice organization controls.
- The auditor evaluates whether necessary CUECs are properly described and assesses Beacon's controls assuming those CUECs operate.
How the exam traps you
- Calling customer access reviews Beacon controls because Beacon generates the reports. Separate report generation from review. Beacon generates; the customer reviews.
- Omitting customer controls because the service auditor does not test them. Testing scope does not remove the requirement to disclose necessary CUECs.
- Putting all controls performed outside Beacon into the CUEC bucket. Customers perform CUECs. The carved-out data center performs complementary subservice organization controls.
Question 2
Hint
Focus on how SOC engagements handle controls that are necessary to meet the criteria but are performed by the user entity instead of the service organization.
Answer B. In a SOC 2 engagement, controls necessary to meet the applicable criteria that are performed by user entities are identified as complementary user entity controls (CUECs). The service auditor evaluates the service organization's controls assuming those user-entity responsibilities are met. The practitioner does not ordinarily test controls at user entities as part of the SOC engagement when responsibilities are clearly described.
Why not A: Tempting if a candidate overfocuses on the fact the engagement is on BlueCloud, but necessary user-entity activities cannot be ignored; they should be identified as complementary user entity controls rather than omitted.
Why not C: This seems plausible because the activity is important, but the service auditor's scope is the service organization; necessary user-entity activities are typically handled as CUECs rather than through testing at user entities.
Why not D: This is overly absolute; SOC 2 reporting allows shared-responsibility models if the system description clearly identifies user-entity responsibilities and the engagement is planned accordingly.
Question 3
Hint
Ask whether the stated control objective can be achieved solely by the service organization's controls or only if user entities also perform specific authorization or exception-resolution procedures.
Answer A. AICPA attestation guidance for SOC 1 (AT-C Section 320) requires management's system description to identify complementary user-entity controls when achieving a stated control objective depends on controls performed by user entities. Here, authorization of hours worked and pay-rate changes is performed by user entities and affects whether transactions are from authorized input; the service organization's edit checks and exception reports do not by themselves establish authorization. Therefore, if the control objective depends on those user-entity activities, their omission from the description is not acceptable.
Why not B: This lures candidates who focus on the effectiveness of the service organization's controls; however, edit checks and exception reporting address processing risks but do not by themselves demonstrate that inputs were authorized by the user entity, so they cannot replace disclosure of complementary user-entity controls when authorization depends on user controls.
Why not C: This is tempting because user-entity controls are outside the service organization's operational boundary, but it is incorrect: when a control objective relies on user-entity activities, management must disclose those activities as complementary user-entity controls so report users understand the assumptions.
Why not D: This is tempting because auditors can obtain evidence about user-entity controls, but it is incorrect to suggest auditor testing can substitute for management's responsibility to identify complementary user-entity controls; treating user-entity procedures as though they are controls of the service organization is inappropriate.
Question 4
Hint
Separate duties performed by a user entity from functions outsourced to another service organization, then ask what the carve-out method actually excludes.
Answer B. DataHost is a subservice organization because PaxCo outsourced physical and environmental safeguards. Under the carve-out method the auditor does not directly opine on DataHost's controls, but must still understand those outsourced services and evaluate PaxCo's related controls (for example, vendor management or monitoring) that address the security criteria. The responsibility for removing terminated users is a complementary user entity control performed by the customer, not by the subservice organization.
Why not A: Tempting because both occur outside PaxCo, but complementary user entity controls are performed by the user entity (customer). An outsourced service provider like DataHost is a subservice organization, which is handled via subservice-organization considerations rather than being labeled a user entity control.
Why not C: Although DataHost's controls are relevant, the inclusive method is not automatically required. The carve-out method is permitted if the service auditor appropriately describes the subservice organization's role and evaluates the service organization's relevant controls and monitoring of the subservice organization.
Why not D: This overstates carve-out. Carve-out means the auditor does not directly test or opine on the subservice organization's controls, but the effect of those outsourced services still must be considered and complementary user entity controls remain relevant when necessary to meet the security criteria.
Question 5
Hint
Ask whether the service organization's controls, as described, alone address the in-scope risk; if not, consider what belongs in the system description when customers' actions are required.
Answer A. When achievement of an in-scope trust services criterion depends in part on actions by user entities, management should disclose those actions as complementary user entity controls in the system description. If management declines to identify a necessary complementary user entity control, the system description would not meet the applicable description criteria for the engagement as requested, and the service auditor must consider the effect on the engagement. The auditor cannot treat the dependency as irrelevant simply because the action is performed by user entities.
Why not B: Tempting because user-entity controls are outside the service organization's operation and the auditor does not test them, but incorrect because necessary user-entity actions that affect whether a trust services criterion is met must be disclosed as complementary user entity controls in the system description.
Why not C: Tempting because testing may show many customers enabled MFA in practice; incorrect because sampling operating effectiveness does not substitute for management's obligation to include required complementary user entity controls in the system description that underpins the auditor's opinion.
Why not D: Tempting because concerns about unauthorized access relate to operating effectiveness and incidents, but incorrect because adequacy of the system description is evaluated during planning and must disclose dependencies regardless of whether an incident has occurred.
Question 6
Hint
Which action must be carried out by each client before payroll is finalized?
Answer A. Complementary user entity controls are those the user entities (clients) are expected to perform so the service organization's control objectives can be achieved. Approving and reconciling employee master file changes and reviewing pre-release exception reports are actions each client must perform before payroll is finalized, so they are complementary user entity controls. The other choices are controls performed by the service organization or by the subservice organization (the data center) under the carve-out method.
Why not B: This choice may look plausible since access controls affect system security; however, the data center is a subservice organization and, under the carve-out method, those are treated as subservice controls, not complementary user entity controls.
Why not C: This is tempting because it involves oversight of the data center, but that review is performed by the service organization as a monitoring activity. It is a service organization control, not a complementary user entity control.
Why not D: Edit checks are attractive as a data-integrity control, but in this scenario the checks run within the service organization's system and are implemented by the service organization. They are therefore service organization controls rather than complementary user entity controls.
Question 7
Hint
Focus on the difference between controls at the service organization and controls that user entities must perform for the overall control environment to work as intended.
Answer A. When achievement of a trust services criterion depends in part on actions by user entities, those actions are described as complementary user entity controls. In an SOC 2 engagement limited to the service organization, the practitioner should identify and consider those complementary user entity controls when evaluating the system and the criteria, but does not test whether user entities actually performed them. This approach preserves the engagement scope focused on the service organization's controls.
Why not B: Tempting because user-entity controls are outside the auditor's testing scope, but incorrect: if a criterion depends on user-entity actions they are still relevant and must be identified as complementary user entity controls and considered in the evaluation.
Why not C: This appeals to candidates who think every necessary control must be tested, but a user entity's review is not a control of the service organization and should not be recharacterized or tested by the practitioner when the engagement is limited to the service organization.
Why not D: Overly cautious: a criterion that depends in part on user-entity actions can still be addressed in an SOC 2 report if those actions are identified as complementary user entity controls; the dependency does not automatically prevent reporting on the criterion.
Common questions
What are examples of complementary user entity controls in SOC 2?
Examples include customers approving access, notifying Beacon of terminated users, reviewing access reports, and enabling MFA for customer administrators. They are CUECs when the applicable criteria depend on customers performing them.
Does the SOC 2 auditor test complementary user entity controls?
Not as part of the service-organization examination shown here. The auditor evaluates their identification in the description and assesses Beacon's controls assuming the CUECs operate.
What must the SOC 2 system description disclose about CUECs?
It must identify the necessary customer responsibilities, such as approving access or reporting terminations. Saying only that customer controls are outside the examination does not replace that disclosure.
Watch it solved
A full CPA ISC task-based simulation on Planning and performing an SOC engagement, worked step by step.
SOC Report Selection & Engagement Planning | CPA ISC TBS on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Planning and performing an SOC engagement
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.