PracticeISCFree practice exam

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.

The ruleWhen achieving applicable SOC 2 criteria depends on user-entity controls outside the service organization's system boundary, management must identify them as CUECs in the system description. The service auditor considers that dependency but does not test the CUECs.

Try one first

A cloud-based accounts-payable service organization is preparing for a SOC 2 examination and is using the carve-out method for its colocation provider. For each item below, classify it as a service-organization control, a subservice-organization control, or a complementary user entity control. Which of the following is most appropriately classified as a complementary user entity control?
Hint

Ask which party (user entity, service organization, or third-party colocation) must perform the activity for the service organization's controls to function.

Sort it

Complementary user entity control

Does a customer perform the necessary control outside Beacon's system boundary? Disclose it as a CUEC; do not test it.

Service-organization control

Does Beacon perform the control? Describe and test it within the SOC 2 Type 2 scope.

Complementary subservice organization control

Does the carved-out data center perform a necessary control Beacon assumes? Identify it as a CSOC; exclude direct testing.

ItemGoes 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.

6 more, each from a different angle

0 of 6 answered · 0 correct

Question 2

BlueCloud hosts payroll data for customers and engages a CPA to perform a SOC 2 Type 2 examination over the security category for 20X6. During planning, the CPA learns that each customer, not BlueCloud, approves and removes that customer's end-user access within the hosted application. Assume this customer-side activity is necessary for the system to meet the applicable security criteria, and BlueCloud's system description clearly identifies that allocation of responsibility. What is the correct treatment in the SOC 2 engagement?
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.

Question 3

During planning of a SOC 1 Type 2 examination for a payroll processor, the service auditor reviews management's draft system description. The service organization performs file-format and duplicate-file checks, payroll calculations, and exception reporting, but payroll inputs (hours worked and pay-rate changes) are submitted by user entities. Management's draft description omits any identification of complementary user-entity controls, stating that customer controls are outside the SOC engagement. Which conclusion is most appropriate?
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.

Question 4

PaxCo provides a SaaS payroll application and is planning a SOC 2 Type 2 examination on the security category for Year 2. PaxCo uses a third-party data center operator, DataHost, for physical security and environmental safeguards over the servers that host PaxCo's application. User entities, however, must promptly remove terminated employees from their own PaxCo application access lists. Management elects the carve-out method for DataHost. Which approach is most appropriate for the service auditor during planning and performance of the engagement?
Hint

Separate duties performed by a user entity from functions outsourced to another service organization, then ask what the carve-out method actually excludes.

Question 5

A CPA is planning a SOC 2 Type 2 examination on the security category for a SaaS payroll processor. During planning, the CPA determines that one relevant security risk can be mitigated only if each user entity enables multifactor authentication (MFA) for its own customer-administrator accounts. The service organization enforces MFA for its own personnel, but customer administrators can still sign in with only a password unless the user entity enables MFA during setup. Management's draft system description says the platform supports MFA but does not identify any complementary user entity controls. Assume no other service-organization control addresses this risk. Which conclusion is best supported?
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.

Question 6

A payroll processing service organization is preparing for a SOC 1 Type 2 examination for 20X5. The organization uses a third-party data center to host the payroll application and perform nightly backups; the data center is presented under the carve-out method. The service organization validates client input files, processes payroll, sends pre-release exception reports to each client, and reviews the data center's SOC report each quarter. Each client is required to approve employee master file changes and to reconcile and approve pre-release exception reports before payroll is finalized. As the practitioner plans the engagement, which control is most appropriately classified as a complementary user entity control?
Hint

Which action must be carried out by each client before payroll is finalized?

Question 7

During planning of an SOC 2 Type 2 examination, the practitioner determines that one applicable trust services criterion can be achieved only if user entities review daily exception reports generated by the service organization's system. Assume the engagement is limited to controls at the service organization, and the practitioner is not engaged to perform procedures at user entities. What is the correct treatment?
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.

Drill all 207 Planning and performing an SOC engagement questionsMixed across every rule in the topic, so you have to spot which one applies. That is how the exam does it.

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

All Planning and performing an SOC engagement practice →

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.