Study guides / ISC: Information Systems & Controls / Planning SOC engagements
Planning SOC engagements
ISC: Information Systems & Controls · quick review
SOC engagements report on a service organization's controls. SOC 1 covers controls relevant to user entities' financial reporting. SOC 2 and SOC 3 cover the Trust Services Criteria. Planning covers scope, subservice organizations, criteria and management's assertion.
The rules
- SOC 1 (AT-C 320): control objectives relevant to user entities' ICFR. Type 1 covers design at a date. Type 2 adds operating effectiveness over a period.
- SOC 2 (AT-C 205 with the Trust Services Criteria): security (required common criteria), availability, processing integrity, confidentiality and privacy. SOC 3 is a general-use summary.
- Subservice organizations: the inclusive method describes and tests their controls. The carve-out method excludes them but identifies complementary subservice organization controls (CSOCs).
- CUECs are controls the service organization expects user entities to perform so the control objectives can be achieved.
- Preconditions: management takes responsibility for the description, criteria and controls, and provides a written assertion. The service auditor must be independent.
Common traps
- The service auditor never tests user entities' CUECs. User auditors do.
- A Type 1 report can't support reliance on operating effectiveness.
- Using internal audit's work in a SOC engagement is allowed, but the service auditor keeps responsibility and discloses the use in the Type 2 tests section.
How it's tested
Choose the right SOC report, identify carve-out versus inclusive, and explain CUECs, CSOCs and preconditions. Remembering-level items are common.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson