SOC Engagements, Service Auditor Reporting, and Cybersecurity Assurance

ISC SOC coverage for engagement types, SOC 1, SOC 2, planning, reporting, and cybersecurity examinations.

This part is the most assurance-specific segment of ISC. The chapters explain how SOC engagements are scoped, performed, and reported, and how the different report types serve different user needs.

SOC questions should begin with report purpose and user need. SOC 1, SOC 2, SOC for Cybersecurity, and engagement-planning questions differ because they address different subject matter, criteria, controls, and report users.

In This Part

SOC Selection Lens

SOC area First question Common ISC trap
SOC overview What subject matter and user need is driving the report? Choosing a SOC report by name rather than purpose.
SOC 1 Are controls relevant to user-entity financial reporting? Using SOC 1 for broad system-security assurance.
SOC 2 Which trust services criteria and system boundaries are in scope? Assuming every trust services category is automatically included.
Planning and performing What evidence, responsibilities, CUECs, and scope decisions support the engagement? Treating SOC work as report drafting rather than assurance execution.
Reporting and opinions How do deviations, limitations, and criteria affect the report conclusion? Ignoring how exceptions change the opinion or user interpretation.
SOC for Cybersecurity Is the engagement about the entity’s cybersecurity risk management program? Confusing SOC for Cybersecurity with SOC 2 security.

SOC Report Selection Sequence

Step What to do Why it matters on ISC
1. Identify user need Determine whether users need financial-reporting assurance, trust-services assurance, cybersecurity program assurance, or execution guidance. SOC report choice should follow the decision users need to make.
2. Match subject matter to report type Select SOC 1, SOC 2, SOC for Cybersecurity, or planning/reporting guidance based on the facts. Similar control language can belong to different report families.
3. Define scope and criteria Identify systems, control objectives, trust services criteria, description criteria, period, and boundaries. Scope determines what the report can and cannot support.
4. Consider dependencies and CUECs Evaluate subservice organizations, user-entity controls, carve-out methods, and inclusive methods. SOC conclusions often rely on controls outside the service organization.
5. Interpret opinion consequences Link exceptions, limitations, deviations, and report type to user reliance. The final opinion changes how users can rely on the report.

How to Use This Part

  • Read this part after Parts I through IV so the system and control background is already in place.
  • Pay attention to the purpose, users, and reporting consequences of each engagement type.
  • Return here whenever an ISC question turns on which SOC framework or report is appropriate.

In this section

Revised on Monday, June 15, 2026