ISC · Considerations for System and Organization Controls (SOC) Engagements · 6 practice questions
SOC 2: Select Controls Based on Scoped Risks.
Select SOC 2 controls for their relevance to in-scope criteria and the risks to meeting service commitments and system requirements. Follow a payroll example to see why customer requests do not determine which controls belong in testing.
Try one first
Hint
Consider which Trust Services Criteria are applicable to confidentiality, how to classify controls performed by user entities, and what a carve-out description must disclose about a subservice organization and the service organization's oversight.
Answer C. For a SOC 2 examination, management must select the Trust Services Criteria appropriate to the reported category; common criteria associated with security are generally relevant to confidentiality and should be included when they affect the controls being evaluated. Controls performed by user entities that are necessary to achieve control objectives should be identified as complementary user-entity controls, not as service organization controls. Under the carve-out method the description still must explain the subservice organization's role and any controls the service organization uses to oversee or rely on that subservice (for example, periodic review of the subservice's SOC report), so the draft should be revised before proceeding.
Why not A: Tempting because SOC 2 can target a single category and carve-out excludes the subservice organization's controls from the service organization's testing. However, it is incorrect: confidentiality controls commonly rely on the common (security) criteria and the carve-out approach does not permit omitting required descriptive information about the subservice organization's role or the service organization's oversight controls.
Why not B: Attractive because additional evidence and outside reports increase assurance, but incorrect: additional testing or receipt of a subservice SOC report cannot cure an inadequate or misleading system description or an incorrect classification of controls; the description itself must accurately reflect responsibilities and applicable criteria.
Why not D: Appealing if one associates SOC 3 with simpler public reporting, but incorrect: SOC 3 engagements are based on the same Trust Services Criteria and examination requirements as SOC 2 and do not remove the need to select appropriate criteria or include required description elements for carved-out subservice arrangements.
Step by step
- Start with the scoped criteria
A payroll provider requests a SOC 2 Type 2 examination covering security and availability, with commitments to protect payroll data and maintain uptime. Use those criteria, commitments, and system requirements to assess control relevance.
- Identify the risk
Understand the system and its related controls before selecting controls to test. Here, unauthorized configuration changes could weaken logical access or disrupt processing capacity.
- Challenge the proposed exclusion
Management wants to exclude change approvals as back-office controls because customers mainly request uptime reports and badge-access information. Neither the label nor the customer requests remove the configuration-change risk.
- Select the relevant controls
Include change-approval controls that address unauthorized configuration changes because that risk affects the scoped security and availability criteria. These controls can warrant inclusion even if no outage or data exposure has occurred.
Key points
- Remember: Select a control because of the scoped risk it addresses, not because customers ask about it.
- One control can address risks relevant to both security and availability.
- A control's internal label does not determine its relevance to the scoped criteria.
How the exam traps you
- Test only the controls customers request. Include controls that address relevant scoped risks, even when customers overlook them.
- Exclude change approvals because management calls them back-office controls. Assess what unauthorized changes could do to security and availability.
- Exclude a control because no outage or data exposure occurred. A relevant risk can exist without an actual incident.
Question 2
Hint
Think about what determines a control's relevance to the already-selected trust services categories and to the entity's service commitments and system requirements.
Answer B. SOC 2 scoping is risk-based: controls that are relevant to the selected trust services categories and that address the entity's service commitments and system requirements should be included. Because unauthorized configuration changes could weaken logical access or disrupt processing capacity, matters that affect security and availability, change-approval controls belong in scope if they mitigate those risks.
Why not A: This distractor tempts because customer requests often drive the demand for reports. It fails because customer preference alone does not determine control relevance; the auditor's scope must be driven by whether the controls address risks to the scoped trust services categories and the entity's service commitments and system requirements.
Why not C: Labeling controls as 'back-office' can make them seem irrelevant, which is why this choice tempts. It is incorrect because the substance of the control and the risk it addresses, not a management label, determine whether it affects security or availability and therefore belongs in scope.
Why not D: A prior incident is evidence of a problem and can highlight control weaknesses, so this option may seem persuasive. It is nevertheless incorrect as the primary scoping factor because controls should be included when they mitigate risks to the scoped criteria even if no failure has yet occurred; scoping is proactive and risk-based, not contingent on past incidents.
Question 3
Hint
Focus on what makes a trust services category applicable to the system, not on what users happen to ask for.
Answer B. Include trust services categories that are applicable to the system being examined. Applicability is determined by the entity's commitments to customers and the system's requirements for handling personal information, not merely by customer interest. Privacy should be included only when the Privacy criteria are relevant to how the system collects, uses, retains, discloses, or disposes of personal information.
Why not A: Customer requests can influence management's desire for reporting but do not by themselves make a trust services category appropriate. The practitioner should include Privacy only if it is applicable based on the entity's commitments and system requirements.
Why not C: Confidentiality relates to information designated as confidential, while Privacy specifically concerns personal information and related commitments or requirements. Storing confidential data does not automatically make the Privacy criteria applicable unless the data involve personal information covered by privacy commitments.
Why not D: A privacy incident may be relevant to risk assessment and reporting, but the existence of an incident does not by itself determine whether the Privacy category belongs in scope. Scope is set by the applicability of the criteria to the system and the entity's commitments.
Question 4
Hint
Focus on what professional standards use to drive procedure design after scope and criteria are already set.
Answer D. The auditor plans and performs SOC procedures based on the engagement objectives and the auditor's risk assessment. For an SOC 2 examination, procedures should focus on controls relevant to the selected trust services criteria and on risks that those controls may not be suitably designed or operating effectively during the period. Management preferences may be considered but do not override the auditor's professional judgment.
Why not A: This is tempting because management and customers may emphasize certain controls, but professional standards require the auditor to design procedures based on the auditor's risk assessment and the engagement objectives, not on management preferences alone.
Why not B: Prior-year results can inform planning, but they do not control current-year procedures. The auditor must assess current-period risks, changes in controls, and current evidence rather than relying solely on last year's clean report.
Why not C: While the intended users affect the report's importance, the expected number of user entities does not determine which controls to test or the extent of testing; those decisions are driven by the auditor's assessment of risk and relevance to the selected criteria.
Question 5
Hint
Distinguish management's ability to define scope from the practitioner's obligation that the system description fairly present all service‑organization processes relevant to the covered trust‑services categories.
Answer C. Management defines the system boundary, but the practitioner must obtain a system description that fairly presents the system using suitable criteria. A service‑organization process that lies within those boundaries and is relevant to security and availability cannot be omitted merely because another internal team operates it. If management refuses to revise the description or narrow the scope, the practitioner cannot support an unmodified SOC 2 report covering the originally described system.
Why not A: Tempting because management sets the system boundary, but incorrect: a fair system description must include service‑organization processes within that boundary that are relevant to the trust‑services categories, even if another internal team performs them.
Why not B: Tempting because representation letters provide evidence about management's assertions, but incorrect: a representation letter does not substitute for required descriptive content; fair presentation must appear in the system description itself.
Why not D: Tempting because some responsibilities can be shared with users, but incorrect: complementary user‑entity controls are expectations for user entities, not controls actually performed by the service organization; you cannot reclassify a central IT process as a user control to avoid including it in the description.
Question 6
Hint
Focus on what defines the service organization's system boundaries for a SOC engagement; evidence about a vendor's controls is not the same as the scoping decision.
Answer B. Scoping depends on whether the vendor's services are part of the service organization's system and relevant to the trust services criteria. If so, the vendor should be addressed as a subservice organization and treated via the inclusive or carve‑out approach in the system description and planning. A vendor's SOC report or an absence of incidents may provide evidence about controls but do not, by themselves, determine scoping.
Why not A: Tempting because candidates may view another party's SOC report as dispositive. However, a vendor's report can be evidence about controls but does not by itself decide whether the vendor's services belong in the service organization's system description.
Why not C: Tempting because lack of operational control feels like exclusion. SOC scoping addresses outsourced functions via the subservice organization concept; outsourcing does not automatically remove the vendor from the service organization's system.
Why not D: Tempting because a clean incident history suggests low risk. Nevertheless, incident history does not determine system boundaries, relevance to the system and to the trust services criteria is the controlling consideration.
Common questions
How do you select controls for a SOC 2 examination?
Identify the criteria in scope and the risks to meeting service commitments and system requirements. Select controls relevant to those criteria that address those risks.
Do customer requests determine which SOC 2 controls are tested?
A customer request is a planning input, not the control-selection rule. Customer requests do not justify excluding controls that address risks relevant to the scoped criteria.
Should SOC 2 change-approval controls be included if no incident occurred?
Yes, if they address risks relevant to the scoped criteria. In the payroll example, unauthorized configuration changes could weaken access or disrupt processing even without a prior incident.
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.