Study guides / ISC: Information Systems & Controls / SOC reporting
SOC reporting
ISC: Information Systems & Controls · quick review
SOC reports combine management's system description and assertion with the service auditor's opinion and, for Type 2, a description of tests and results. Deviations and subsequent events can modify the report.
The rules
- Report sections (Type 2): the service auditor's opinion, management's assertion, management's system description, and the service auditor's description of tests of controls and results.
- Modified opinions: a description that isn't fairly presented, controls that aren't suitably designed, or controls not operating effectively enough to achieve an objective leads to a qualified or adverse opinion.
- Deviations found in testing are listed in the tests-and-results section, whether or not they change the opinion.
- Subsequent events: ask about events through the report date. Undisclosed significant events that affect the description or conclusions modify the report.
- Use restrictions: SOC 1 and SOC 2 are for specified informed users. SOC 3 is general use. Bridge letters from management cover the gap between the period end and a user's year end.
Common traps
- A bridge letter is management's representation, not an auditor's report, so it gives limited evidence.
- Listing a deviation doesn't automatically qualify the opinion. The test is whether the control objective was achieved.
- User auditors must still evaluate the report's period, scope, deviations and CUECs before relying on it.
How it's tested
Identify report elements, decide when to modify the opinion, and explain how user auditors use SOC reports. Expect document review simulations of draft SOC report sections.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson