
An SOC engagement is an independent attestation engagement about controls at a service organization or an entity's cybersecurity risk management program. An attestation engagement gives users evidence from an independent practitioner.
Organizations outsource activities such as payroll, payment processing, hosting, data storage, and transaction processing. Their customers, auditors, boards, and business partners still need evidence about controls protecting those activities.
The report type answers the user's main question. SOC 1 addresses controls relevant to user entities' internal control over financial reporting. SOC 2 and SOC 3 address controls over a service organization's system using selected Trust Services Criteria. SOC for Cybersecurity addresses an entity's cybersecurity risk management program. The Trust Services Criteria provide shared definitions for security, availability, processing integrity, confidentiality, and privacy.
The report must first match its subject matter and intended users. The choices can then be separated from criteria, assertions, and timing.
The four report types differ by subject, users, distribution, criteria, and timing. These dimensions keep report choice separate from criteria choice.
| Decision point | SOC 1 | SOC 2 | SOC 3 | SOC for Cybersecurity |
|---|---|---|---|---|
| Main subject | Service organization controls relevant to financial reporting | Service organization's system relevant to selected Trust Services Criteria | Same Trust Services Criteria subject matter as SOC 2 | Entity's cybersecurity risk management program |
| Intended users | Management, user entities, and user auditors | Management, user entities, business partners, regulators, and informed specified users | Broad users needing general-use assurance | Board members, management, investors, business partners, regulators, and broad users |
| Distribution | Restricted to specified users | Restricted to specified users | General use | General use |
| Criteria | Control objectives relevant to financial reporting | Trust Services Criteria selected from commitments and system requirements | Same Trust Services Criteria as SOC 2 | Cybersecurity description criteria and suitable control criteria |
| Assertion and timing | Management's description and assertion; Type 1 is as of a date; Type 2 is for a period | Management's description and assertion; Type 1 is as of a date; Type 2 is for a period | General-use SOC 2 reporting with a stated date or period and less detail | Management's description and assertion; controls are evaluated as of a date or for a period |
SOC 2 and SOC 3 share subject matter, while distribution and report detail separate them.
SOC 1 reports on controls at a service organization. Those controls must be relevant to user entities' internal control over financial reporting.
Its restricted users normally include service organization management, user entities, and user auditors. SOC 2 reports on controls over a service organization's system using selected Trust Services Criteria. It is restricted to informed specified users.
SOC 3 reports on the same Trust Services Criteria subject matter as SOC 2. It is designed for general use and omits detailed descriptions of tests and results. SOC for Cybersecurity reports on an entity's cybersecurity risk management program and related controls for broad stakeholders. It is not simply another name for SOC 2.
The full report purposes and user groups are in SOC report types, users and assertions.
Management is responsible for describing the system or program and providing a written assertion. Management asserts that the description is fairly presented and that controls are suitably designed.
A Type 1 report is as of a specified date. It addresses the description and whether controls were suitably designed and implemented at that date. It does not conclude that controls operated effectively throughout a period.
A Type 2 report covers a specified period. It addresses design and implementation, plus whether controls operated effectively throughout that period. It includes the practitioner's tests and results. Type 2 therefore provides period evidence that Type 1 does not.
SSAE No. 18 supplies the attestation standards source. AT-C 105 covers common attestation concepts. AT-C 205 covers examination engagements. AT-C 320 covers relevant service organization controls for financial reporting.
The full assertion and timing rules are in SOC report types, users and assertions.
The 2017 Trust Services Criteria provide requirements for evaluating controls. They are organized into common criteria and supplemental criteria.
Common criteria CC1-CC9 form the Security category. They are used with every SOC 2 examination. Supplemental criteria add requirements for other categories: A1 for Availability, PI1 for Processing Integrity, C1 for Confidentiality, and P1-P8 for Privacy.
The five category definitions matter. Security means the system is protected against unauthorized access, use, or modification. Availability means the system is available for operation and use as committed or agreed.
Processing integrity means system processing is complete, valid, accurate, timely, and authorized. Confidentiality means information designated as confidential is protected as committed or agreed. Privacy means personal information is collected, used, retained, disclosed, and disposed to meet the entity's objectives.
Criteria are requirements used to evaluate controls. They are not the controls themselves.
The full purpose and organization of the criteria are in Trust Services Criteria.
The service organization's commitments and system requirements determine which Trust Services Criteria are relevant. Security is the common baseline in every SOC 2 examination.
A provider that promises protection against unauthorized access needs Security. A provider that also promises availability during agreed service windows needs Availability.
Promises about complete, valid, accurate, timely, and authorized processing support Processing Integrity. A promise to protect designated confidential information supports Confidentiality. Commitments about personal information support Privacy.
A platform that changes from access protection alone to access protection plus agreed availability has changed its relevant category set. Availability is added to Security.
The presence of an uptime control alone does not decide the category. The service commitment does.
Details on commitments and category changes are in Trust Services Criteria.
Subject matter and users select the report family. The assertion and time period state what management claims. Criteria then define scope within SOC 2.
Ask one question: What is the subject matter, and who needs the report?
Words such as security, controls, and service organization can appear in more than one report. Identify the subject first. Then use intended users and distribution as confirmation.
| A situation about... | Belongs to | Clue words in a scenario |
|---|---|---|
| Provider controls affecting customers' financial reporting | SOC 1 | Internal control over financial reporting, user auditor, user entity, restricted use |
| Service organization's system evaluated against selected Trust Services Criteria | SOC 2 | Security, availability, processing integrity, confidentiality, privacy, tests and results |
| Same Trust Services Criteria assurance for broad users | SOC 3 | General use, public website, same subject matter as SOC 2, no detailed tests |
| Entity's own cybersecurity risk management program | SOC for Cybersecurity | Board, investors, cyber risk management program, program description, general use |
Financial-reporting controls point to SOC 1. Restricted Trust Services Criteria assurance points to SOC 2. General-use Trust Services Criteria assurance points to SOC 3. An entity-wide cybersecurity program points to SOC for Cybersecurity.
The same dimensions provide a complete comparison. SOC 1 is tied to financial reporting. SOC 2 and SOC 3 use the same Trust Services Criteria subject matter. SOC for Cybersecurity addresses a broader program.
| Dimension | SOC 1 | SOC 2 | SOC 3 | SOC for Cybersecurity |
|---|---|---|---|---|
| Primary subject | Service organization controls relevant to financial reporting | Service organization system and controls relevant to selected Trust Services Criteria | Same service organization system and Trust Services Criteria subject matter as SOC 2 | Entity's cybersecurity risk management program and related controls |
| Main purpose | Help user entities and auditors evaluate relevant outsourced controls | Give specified users assurance over controls tied to selected criteria | Give broad users general-use assurance over the same criteria subject matter | Give broad stakeholders information about an entity's cybersecurity program and controls |
| Intended users | Management, user entities, and user auditors | Management, user entities, business partners, regulators, and informed specified users | Anyone needing the general-use report | Board, management, investors, business partners, regulators, and broad users |
| Distribution | Restricted use | Restricted use | General use | General use |
| Criteria | Control objectives relevant to financial reporting | CC1-CC9 plus relevant A1, PI1, C1, and P1-P8 | Same Trust Services Criteria subject matter as SOC 2 | Cybersecurity description criteria and suitable control criteria |
| Management's assertion | Description fairly presents the system; controls are suitably designed; Type 2 adds operating effectiveness | Description fairly presents the system; controls are suitably designed; Type 2 adds operating effectiveness | Same underlying SOC 2-style assertion in a less detailed general-use report | Description fairly presents the program; controls address suitable design and, when applicable, operating effectiveness |
| Type 1 | As of a specified date; design and implementation; no period operating-effectiveness conclusion | As of a specified date; design and implementation; no period operating-effectiveness conclusion | Stated date rule applies; public distribution adds no period evidence | As of a specified date when a Type 1 controls conclusion is included |
| Type 2 | For a specified period; design, implementation, and operating effectiveness, with tests and results | For a specified period; design, implementation, and operating effectiveness, with tests and results | Same underlying period conclusion as SOC 2; detailed tests and results are omitted | For a specified period when a Type 2 controls conclusion is included |
| Do not confuse it with | General cybersecurity reporting or Trust Services Criteria reporting | Public reporting or an entity-wide cybersecurity program report | Different criteria from SOC 2 | A SOC 2 report about a service organization's system |
SOC 2 and SOC 3 have the same subject matter. SOC 2 is restricted and detailed, while SOC 3 is general use and less detailed.
Each situation turns on a different decisive fact. The reason must match the subject matter and users, not merely a word such as security.
Practice
A payroll processor maintains controls over transaction processing that affect the financial statements of its user entities. A user auditor needs a restricted-use report on those controls. Which SOC engagement type is appropriate, and why?
A cloud hosting provider wants a restricted-use report for customer procurement teams that need detailed tests of controls over unauthorized access and system availability during a stated period. Which SOC engagement type is appropriate, and why?
An online service provider wants to post assurance on its website so anyone can evaluate its controls over security and availability. The provider does not want to publish detailed descriptions of the auditor's tests and results. Which SOC engagement type is appropriate, and why?
A corporation's board and investors want a general-use report about the corporation's own cybersecurity risk management program and related controls. They are not asking for controls relevant to customer financial reporting or a service organization's system. Which SOC engagement type is appropriate, and why?
Subject and users: SOC 1 covers financial-reporting controls, SOC 2 covers restricted-use Trust Services Criteria assurance, SOC 3 covers general-use Trust Services Criteria assurance, and SOC for Cybersecurity covers an entity's cybersecurity program.
Assertion and time: Type 1 is design and implementation as of a specified date. Type 2 adds operating effectiveness throughout a specified period.
Criteria structure: Common criteria CC1-CC9 form the Security baseline. Supplemental criteria add Availability, Processing Integrity, Confidentiality, or Privacy requirements.
Commitments: Service commitments and system requirements, not the mere presence of a control, determine relevant Trust Services Criteria categories.
Separating question: What is the subject matter, and who needs the report?
Signup to continue reading this lesson and unlimited access questions, flashcards, AI notes, and more
1. A software provider wants a concise assurance report covering the security controls of its hosted platform for the year ended December 31, 2025. The provider intends to post the report publicly for prospective customers and does not want detailed control descriptions or tests of controls included. Which engagement would best satisfy these objectives?
Answer: A. A SOC 3 examination covering the security category for the period
A SOC 3 examination covering the security category for the period - A SOC 3 examination can address the hosted platform’s security controls over the year ended December 31, 2025. - Its report is suitable for public distribution and omits the detailed control descriptions and tests the provider does not want to publish. A SOC 2 Type 2 examination covering the security category for the period - A SOC 2 Type 2 examination fits the platform, security category, and stated period, but its report includes detailed controls and tests. - Because that detail is intended for users with sufficient knowledge of the system, it does not meet the provider’s public-report objective. A SOC 1 Type 2 examination covering financial-reporting controls for the period - A SOC 1 Type 2 examination addresses controls relevant to customers’ internal control over financial reporting, not the requested security assurance. - Covering the same year does not change that mismatch with the provider’s objective for its hosted platform. A SOC for Cybersecurity examination covering the entity-wide program for the period - A SOC for Cybersecurity examination addresses an entity-wide cybersecurity risk management program, rather than the specified hosted-platform security controls. - The provider’s request is for assurance about that platform under the security category, making SOC 3 the better fit.
2. For the year ended December 31, 2025, a cloud-storage provider wants an assurance report addressing whether its controls relevant to the security and confidentiality trust services criteria operated effectively. The provider intends to post the report publicly for current customers, prospective customers, and other interested parties and does not want the report to disclose detailed control tests or results. Which report should the provider request?
Answer: D. A SOC 3 report suitable for general distribution to interested users
A SOC 3 report suitable for general distribution to interested users - A SOC 3 report can address whether controls met the security and confidentiality trust services criteria and operated effectively during the year ended December 31, 2025. - It is suitable for public distribution and does not disclose the detailed control tests and results the provider wants to omit. A SOC 1 Type 2 report restricted to user entities and their auditors - A SOC 1 report addresses controls relevant to user entities’ internal control over financial reporting, not the stated security and confidentiality criteria. - Its restricted audience also conflicts with posting the report for prospective customers and other interested parties. A SOC 2 Type 1 report restricted to specified knowledgeable users - A Type 1 report addresses controls as of a specified date, not whether they operated effectively throughout 2025. - A SOC 2 report is restricted to specified knowledgeable users, rather than suitable for the provider’s intended public posting. A SOC 2 Type 2 report restricted to specified knowledgeable users - A SOC 2 Type 2 report addresses operating effectiveness over a period under the relevant trust services criteria. - It does not meet the distribution objective because it is restricted to specified knowledgeable users and includes detailed control tests and results.
3. A user auditor is auditing a calendar-year entity that outsources transaction processing. The SOC 1 Type 2 report covers October 1, 2024, through September 30, 2025, with the service auditor expressing an unmodified opinion on controls relevant to user entities' internal control over financial reporting. A bridge letter dated January 8, 2026, from service-organization management states that it is unaware of material changes to the described system or relevant controls from October 1 through December 31, 2025; the service auditor did not perform procedures for this three-month period. Which conclusion is most appropriate concerning the October 1 through December 31 gap period?
Answer: A. Evaluate the bridge letter and obtain additional evidence about relevant controls during the gap period.
Evaluate the bridge letter and obtain additional evidence about relevant controls during the gap period. - The SOC 1 Type 2 opinion covers controls only through September 30, 2025, leaving October 1 through December 31 outside its scope. - The user auditor should evaluate the January 8 bridge letter and obtain additional evidence about relevant controls for that three-month gap. Treat the bridge letter as service-auditor assurance that the controls operated effectively during the gap period. - The bridge letter is a statement from service-organization management, not an assurance report from the service auditor. - The service auditor performed no procedures for October 1 through December 31, so the letter cannot establish operating effectiveness for that period. Extend the service auditor's September 30 opinion through December 31 because management reported no changes. - An unmodified opinion for the period ending September 30 does not extend to December 31. - Management’s statement that it is unaware of material changes does not extend the service auditor’s testing or opinion. Disregard the SOC 1 report because its period does not coincide with the user entity's fiscal year. - The report remains relevant evidence about controls during its October 1, 2024, through September 30, 2025 coverage period. - Its failure to coincide with the calendar year calls for procedures addressing the remaining three months, not disregard of the report.
4. A software-as-a-service provider engages a practitioner to examine controls relevant to system availability for the year ended December 31, 2025. The detailed report will be restricted to customers, prospective customers with sufficient knowledge of the system, and their practitioners. Which criteria should management use to evaluate the controls addressed by the engagement?
Answer: A. The common criteria and the additional criteria for availability
The common criteria and the additional criteria for availability - This restricted-use examination of controls relevant to system availability is a SOC 2 engagement. - Management evaluates those controls using the trust services common criteria and the additional criteria for availability. The common criteria and the additional criteria for processing integrity - Processing integrity concerns whether processing is complete, valid, accurate, timely, and authorized. - The engagement addresses availability, not processing integrity, so its additional criteria do not apply. The control objectives relevant to user entities' financial reporting - Control objectives relevant to user entities’ internal control over financial reporting belong to a SOC 1 engagement. - This examination addresses the SaaS provider’s system availability rather than customers’ financial reporting controls. The service organization's internally developed availability benchmarks only - Internal benchmarks may help describe the provider’s availability commitments and system requirements. - They cannot replace the applicable trust services criteria as the basis for evaluating the controls in this SOC 2 examination.
5. A payment platform's transaction-processing controls affect merchants' revenue recognition, while its security controls are also of interest to prospective customers. Merchant auditors need detailed restricted-use information for the year ended December 31, 2025, but prospective customers want a concise publicly available report. Which reporting approach best addresses both objectives?
Answer: A. Issue a SOC 1 Type 2 report for financial-reporting users and a SOC 3 report covering security for general users
Issue a SOC 1 Type 2 report for financial-reporting users and a SOC 3 report covering security for general users - A SOC 1 Type 2 report provides merchant auditors restricted-use information about transaction-processing controls relevant to revenue recognition, including their operating effectiveness during the year ended December 31, 2025. - A SOC 3 report provides concise, publicly available assurance about security for prospective customers. Issue one SOC 1 Type 2 report and permit unrestricted public distribution of the complete report - A SOC 1 report is restricted to specified users, so its complete report should not be distributed publicly. - It addresses controls relevant to merchants’ financial reporting but does not provide the general-use security report prospective customers want. Issue one SOC 2 Type 2 report covering security and treat it as evidence over merchants' revenue controls - A SOC 2 Type 2 security report addresses security controls, not necessarily the transaction-processing controls relevant to merchants’ revenue recognition. - It cannot replace the SOC 1 report merchant auditors need for financial-reporting controls. Issue one SOC 3 report covering security and include detailed tests of financial-reporting controls - A SOC 3 report is intended for general use and does not include the detailed control tests merchant auditors need. - Its security focus does not substitute for a SOC 1 Type 2 report on controls relevant to merchants’ financial reporting.
6. A practitioner has substantially completed a restricted-use SOC 2 Type 2 examination covering the security criteria for the year ended December 31. Management refuses to provide required written representations concerning its responsibility for the system description and the completeness of information supplied. Law and regulation prevent the practitioner from withdrawing from the engagement. Which action should the practitioner take?
Answer: A. Disclaim an opinion
Disclaim an opinion - Management’s refusal to provide required written representations about the system description and the completeness of information supplied prevents the practitioner from obtaining required evidence. - Because law and regulation prevent withdrawal, the practitioner should disclaim an opinion on the SOC 2 Type 2 examination. Issue a qualified opinion - A qualified opinion does not adequately address the absence of these required representations concerning management’s responsibilities and the information supplied. - The practitioner cannot treat the refusal as a limited exception while otherwise expressing an opinion on the security criteria. Issue an unmodified opinion - An unmodified opinion requires sufficient appropriate evidence, including the required written representations that management refuses to provide. - Substantial completion of the examination does not replace that missing evidence. Issue an adverse opinion - An adverse opinion addresses a material departure in the subject matter, rather than a refusal to provide required evidence. - The facts identify no finding that the system description or security controls warrant an adverse opinion.
7. A service auditor is examining a SOC 2 Type 1 report restricted to management and knowledgeable customers as of June 30, 2026. Management's description states that multifactor authentication is implemented for every privileged account. Which procedure provides the most persuasive evidence that the control was implemented as of June 30?
Answer: C. Inspect the privileged-account configuration and attempt authentication for selected accounts
Inspect the privileged-account configuration and attempt authentication for selected accounts - Inspecting the privileged-account configuration directly addresses whether multifactor authentication was implemented as management described as of June 30, 2026. - Attempting authentication for selected privileged accounts provides evidence that the configured control operates at the point of login, rather than merely appearing in a policy. Inquire of the security administrator whether privileged users are expected to use multifactor authentication - The administrator’s answer describes an expectation, not whether multifactor authentication was implemented for privileged accounts. - Inquiry alone is less persuasive than inspecting the configuration and attempting authentication. Inspect the approved policy requiring multifactor authentication for privileged accounts - An approved policy establishes a requirement but does not show that multifactor authentication was deployed. - Privileged accounts could remain configured without multifactor authentication despite the policy. Review authentication logs generated during the six months preceding June 30 - The logs provide historical evidence of authentication activity, not the most direct evidence of the configuration as of June 30. - Accounts and settings reflected in earlier logs might differ from those in place on the SOC 2 Type 1 report date.
8. A data analytics provider requests a restricted-use SOC 2 Type 1 examination as of September 30, 2026, addressing security and confidentiality. Management proposes proprietary criteria stating that information is protected when management considers the safeguards reasonable. The criteria contain no measurable benchmarks and will not be provided to intended users. What should the practitioner do?
Answer: C. Require management to adopt suitable, measurable criteria that will be available to intended users before accepting
Require management to adopt suitable, measurable criteria that will be available to intended users before accepting - A SOC 2 Type 1 examination as of September 30, 2026, requires suitable criteria for evaluating security and confidentiality at that date. - Management’s judgment of “reasonable” safeguards provides no measurable benchmarks, and the criteria must be available to intended users before the practitioner accepts the engagement. Accept the engagement because restricted-use reports may use criteria unavailable to intended users - Restricted use limits who may use the report; it does not eliminate the requirement that those users have access to the criteria. - It also does not cure criteria that leave the provider’s security and confidentiality safeguards without measurable benchmarks. Convert the engagement to a SOC 3 examination using the proprietary criteria - A SOC 3 examination also requires suitable criteria, so changing the report type would not make management’s subjective standard measurable. - The proposed proprietary criteria would still be unavailable to intended users. Accept the engagement and describe the proprietary criteria only in the practitioner's internal documentation - Internal documentation does not make the criteria available to the intended users of the restricted-use report. - Recording management’s subjective standard in the workpapers also does not supply measurable benchmarks for evaluating security and confidentiality.
9. In a SOC 2 Type 2 engagement covering January 1 through December 31, 2025, the service organization prevents the practitioner from accessing security logs for eight months. The logs relate to controls central to every trust services category in scope, and no alternative procedures are available. The possible effects are material and pervasive. Which report conclusion is appropriate?
Answer: A. Disclaim an opinion because sufficient appropriate evidence cannot be obtained
Disclaim an opinion because sufficient appropriate evidence cannot be obtained - The organization’s refusal to provide eight months of security logs leaves the practitioner unable to obtain sufficient appropriate evidence about controls central to every trust services category in scope. - With no alternative procedures available and possible effects that are material and pervasive, a disclaimer is appropriate for the SOC 2 Type 2 engagement. Express an adverse opinion because the controls did not operate effectively - An adverse opinion requires evidence supporting a conclusion that the controls did not operate effectively. - Missing logs prevent the practitioner from reaching that conclusion; they do not establish that the controls failed. Express a qualified opinion because the limitation is confined to security logs - A qualified opinion would address a scope limitation whose possible effects are material but not pervasive. - Although the missing evidence consists of security logs, those logs concern controls central to every trust services category in scope. Express an unmodified opinion and describe the limitation in an emphasis paragraph - An unmodified opinion is not supported when the practitioner cannot obtain evidence about central controls for eight months. - An emphasis paragraph cannot remedy the lack of evidence or replace the required disclaimer.
1. What do SOC 1, SOC 2, and SOC 3 reports address?
SOC 1 reports focus on financial reporting. SOC 2 reports address security, availability, processing integrity, confidentiality, and privacy. SOC 3 reports are general-use reports covering the same principles as SOC 2.
2. True or False: SOC 2 and SOC 3 reports use the same Trust Services Criteria.
TRUE. Both SOC 2 and SOC 3 reports evaluate controls based on the Trust Services Criteria, ensuring consistency in their assessment.
3. Fill in the blank: SOC 3 reports are designed for use.
General. SOC 3 reports provide a summary of the information in SOC 2 reports and are intended for a broad audience, including potential customers.
4. What is the difference between a Type 1 and Type 2 SOC report?
Type 1: Reports on the fairness of the presentation of management's description of the service organization's system and the suitability of the design of controls at a specific point in time. Type 2: Includes the Type 1 information plus an assessment of the operating effectiveness of the controls over a period of time. Type 2 reports provide more comprehensive assurance as they include the testing of controls over a specified period.
5. What is the typical minimum period over which controls are tested for a Type 2 report?
At least six months. Testing over a period of at least six months provides a reasonable basis for evaluating the operating effectiveness of controls.
6. What is the primary purpose of a SOC 2 report?
To evaluate controls related to security, availability, processing integrity, confidentiality, and privacy. SOC 2 reports are particularly relevant for technology and cloud computing companies that handle sensitive data.
7. What does the availability criterion in a SOC 2 report assess?
Whether the system is available for operation and use as committed or agreed.
8. True or false: A SOC 1 report can be used to assess a service organization's compliance with privacy regulations.
False. A SOC 1 report addresses controls relevant to user entities' internal control over financial reporting, not privacy-regulatory compliance. A SOC 2 report may address privacy if that criterion is included in the engagement, but it reports on relevant controls and is not by itself a legal determination of compliance with privacy regulations.
Get full Oncourse access with lessons, practice questions, flashcards and AI study tools.
Scan to download app
Enter your email to get your 75% OFF code and unlock the full CPA question bank on the app.