
A data-hosting provider serves 40 customer entities. One user asks for assurance over billing controls. Another asks about security and availability.
Those facts create different subject requests. Billing controls relate to user entities' internal control over financial reporting. Security and availability relate to selected Trust Services Criteria.
A SOC report is an independent attestation report about controls at a service organization. Management describes the system and asserts that the description is fairly presented. Management also asserts that the controls meet the applicable design criteria. The service auditor examines those assertions and reports an opinion.
User entities and their auditors use the report to understand provider controls. They do not need to repeat every procedure themselves. A SOC report is not a guarantee that the provider is risk-free. It also does not automatically cover controls owned by a user entity or a subservice organization.
Outsourcing moves important processing outside the user's walls. Without a clear subject, coverage period, control owner, test result, and opinion, a point-in-time design conclusion could be mistaken for evidence of effective controls throughout a period. The decisions turn on subject matter, time coverage, evidence, and control ownership.
Read the diagram from top to bottom. First identify internal control over financial reporting or selected Trust Services Criteria. Then identify one-date or period coverage. Finally separate known issues, missing evidence, and scope disclosures.
A Type 1 report addresses the description and control design as of a date. A Type 2 report covers a period and adds operating-effectiveness testing and results. Material, pervasive known issues can lead to adverse opinions. Material, pervasive evidence limitations can lead to disclaimers. CUECs and subservice methods are scope facts, not automatic opinion modifications.
Loading diagram…
SOC 1 covers controls relevant to user entities' internal control over financial reporting under AT-C 320. SOC 2 covers controls evaluated against one or more Trust Services Criteria under AT-C 205.
The 2017 Trust Services Criteria are security, availability, processing integrity, confidentiality, and privacy. SOC 3 is a general-use, abbreviated report on Trust Services Criteria. AT-C 105 supplies common attestation concepts.
The qualifier as of one date means Type 1. The report addresses whether the description fairly presents the system and whether controls are suitably designed at that date.
The qualifier throughout the specified period means Type 2. The report also addresses whether controls operated effectively throughout that period.
The customary line is point-in-time design versus period operating effectiveness. For the report form and coverage rules, see Report form, content and test results.
The form normally identifies:
A Type 2 report adds tests of controls and their results. Each test result should identify the control or criterion, the procedure, and the population or sample when relevant. It should also identify the result and any exception.
A Type 1 report may support design work at a date. It does not support a conclusion that controls operated effectively throughout a period.
An exception belongs in the test results when testing finds a deviation. It does not automatically require a modified opinion. For the complete form and test-result presentation, see Report form, content and test results.
If evidence shows a description misstatement, a design failure, or an operating failure, classify the effect before choosing the opinion.
Qualified opinions commonly use except for wording. An isolated exception may still permit an unmodified opinion when it is not material and does not prevent the conclusion. Isolated is a customary description, not a safe harbor.
Neither AT-C 205 nor AT-C 320 provides a fixed dollar or percentage threshold. Material means important to intended users in the circumstances. Pervasive means the effect is broad, substantial, or fundamental to users' understanding. Related opinion-modification concepts appear in AU-C 705.
For the opinion and report wording rules, see Opinions and report modifications.
The service auditor must obtain sufficient appropriate evidence. If evidence is missing, judge the possible effects. Do not treat the matter as a proven control failure.
An adverse opinion addresses a known material and pervasive misstatement. It does not address uncertainty caused by missing evidence. The basis paragraph identifies the matter supporting the modification.
For the distinction between known deficiencies and evidence limitations, see Opinions and report modifications.
A complementary user entity control, or CUEC, is a control the user entity is expected to perform. The service organization's controls assume that the user performs it.
The report identifies the CUEC. The service auditor does not test the user's performance of it. The service auditor also does not give an opinion on that performance.
Under the carve-out method, the report describes the nature of services provided by the subservice organization. It excludes the subservice organization's relevant controls, tests, and results from the service auditor's scope.
Under the inclusive method, the subservice organization's relevant controls are included in the system description. They are examined with the service organization's controls. The opinion covers them when sufficient evidence is obtained.
For these ownership and disclosure effects, see User entity and subservice disclosures.
These facts turn the rules into a repeatable reading method. Start with the subject and coverage. Then ask whether the problem is known or only possible because evidence is missing. Finish by checking whether a user or subservice organization owns part of the control environment.
| Fact in the situation | Sends you to | What changes |
|---|---|---|
| Controls relate to user entities' internal control over financial reporting | SOC 1 under AT-C 320 | Use control objectives relevant to financial reporting. |
| Controls use selected Trust Services Criteria | SOC 2 under AT-C 205 or SOC 3 | Use the selected criteria and report purpose. |
| Report is as of December 31, 20X4 | Type 1 | Address description and design at that date. |
| Report covers January 1 through December 31, 20X4 | Type 2 | Add operating-effectiveness testing and results. |
| Known description, design, or operating failure exists | Known-issue opinion path | Assess materiality and pervasiveness. |
| Sufficient appropriate evidence cannot be obtained | Evidence-limitation opinion path | Assess the possible effect, not a proven failure. |
| User entity performs an assumed control | CUEC disclosure | Identify the user responsibility without opining on it. |
| Subservice controls are excluded or included | Carve-out or inclusive method | Change the described and examined scope. |
Notice that opinion changes depend on materiality, pervasiveness, or evidence limits, not on every scope disclosure.
Northstar Cloud supports billing and access processing for 40 customer entities. Its management assertion says the system description is fairly presented. It also says the controls are suitably designed.
Customers must review their monthly user-access reports. That review is a CUEC. CloudAuth handles multifactor authentication and is initially covered by the carve-out method.
All other facts remain fixed as each row changes. The dates establish point-in-time coverage. Period testing then adds operating-effectiveness results. The later rows separate a known exception, missing evidence, and subservice scope.
Each row states the facts first, followed by the verdict and its reason.
| Step and facts to assess | Verdict | Why | Chapter pointer |
|---|---|---|---|
| Baseline: SOC 1 covers financial-reporting controls as of December 31, 20X4. | Type 1 with unmodified conclusions on description and design, assuming sufficient evidence. | One-date coverage supports design conclusions, not period operating effectiveness. | Report form, content and test results |
| Coverage changes: the report covers January 1 through December 31, 20X4. The auditor tests 25 access-review items with no exceptions. | Type 2 with an unmodified opinion, assuming satisfactory description, design, and evidence. | Period coverage and operating tests require Type 2 reporting with tests and results. | Report form, content and test results |
| Test result changes: 1 of 25 sampled access reviews was missed. Evidence is available. The exception is immaterial and isolated. | The Type 2 report can remain unmodified, with the exception reported in the test results. | An isolated exception is not automatically material. The results still disclose the deviation. | Opinions and report modifications |
| Evidence changes: key-control records are unavailable for all 12 months. The possible effect is material but not pervasive. | A qualified opinion because of an evidence limitation. | Missing evidence creates an uncertain possible effect, not a known misstatement. | Opinions and report modifications |
| Scope changes: CloudAuth moves from carve-out to inclusive. Sufficient evidence about its relevant controls is available. | CloudAuth's controls, tests, and results enter the report and opinion scope. The customer review remains a CUEC. | Inclusive reporting examines the subservice controls. The customer still owns the CUEC. | User entity and subservice disclosures |
Use these short questions to apply the report-form, opinion, evidence, CUEC, and subservice rules. Each item changes a fact that switches the applicable rule.
The questions move from coverage to known issues, evidence limitations, and control ownership. The answer depends on the changing fact, not the service organization's label.
Practice
A service organization reports on controls relevant to user entities' internal control over financial reporting for January 1 through December 31, 20X4. The service auditor tests operating effectiveness during the period. Which statement best describes the report?
In a Type 2 engagement, the description is fairly presented and the controls are suitably designed, but a known control deficiency is material and not pervasive. Which opinion is appropriate?
The service auditor cannot obtain sufficient appropriate evidence about a key control for all 12 months. The possible effect is material but not pervasive, and no known misstatement has been identified. Which opinion is appropriate?
A service organization uses CloudAuth for multifactor authentication and chooses the carve-out method. How should CloudAuth be treated in the report?
A service organization's system assumes that each user entity reviews its own monthly access report. What is the proper report treatment?
The lines below preserve the order for report form, test results, opinions, evidence limits, and scope disclosures.
Ask first: What exactly is the subject, period, evidence, and control owner covered by this report?
Signup to continue reading this lesson and unlimited access questions, flashcards, AI notes, and more
1. In a SOC 1 Type 2 engagement for the year ended December 31, 2025, system-generated backup logs for September and October were destroyed before the service auditor could inspect them. No alternative procedures are available. The possible effects are material but confined to one backup control and are not pervasive to the engagement. What opinion consequence is appropriate?
Answer: D. A qualified opinion on operating effectiveness because of the material, nonpervasive scope limitation
A qualified opinion on operating effectiveness because of the material, nonpervasive scope limitation - The destroyed September and October backup logs, with no alternative procedures available, prevent the service auditor from obtaining sufficient appropriate evidence about the backup control’s operating effectiveness. - Because the possible effects are material but not pervasive to the SOC 1 Type 2 engagement, a qualified opinion is appropriate. An unmodified opinion because the limitation concerns only two months - The number of months alone does not determine the opinion consequence; the question states that the possible effects of the missing logs are material. - With no alternative procedures available, the service auditor cannot resolve the evidence limitation simply because it concerns September and October. An adverse opinion on operating effectiveness because the missing evidence is material - Missing logs create an inability to obtain evidence, not an identified failure of the backup control. - Materiality alone does not warrant an adverse opinion when the stated problem is a nonpervasive scope limitation. A disclaimer of opinion because any material scope limitation prevents an opinion - A disclaimer would require the possible effects of the scope limitation to be material and pervasive. - Here, the limitation is confined to one backup control and is expressly not pervasive to the engagement.
2. A CPA firm is completing an examination of ClearClaim Services' controls over claims-payment processing. ClearClaim processes transactions that user entities record in their financial statements. Management requested coverage for January 1 through December 31, 2026, for use by ClearClaim, its user entities, and their financial statement auditors. During testing, the engagement team identified missing system evidence for a privileged-access termination control and must determine the effect on the report.
3. A service auditor is reporting on a restricted-use SOC 2 Type 2 examination addressing security controls for the year ended December 31, 2025. Management refuses access to archived logs for one control, and no alternative procedures are available. The possible effects are material but confined to that control and are not pervasive to the system. What opinion should the service auditor express?
Answer: C. A qualified opinion because of the material but nonpervasive scope limitation
A qualified opinion because of the material but nonpervasive scope limitation - The unavailable archived logs leave the auditor unable to obtain sufficient appropriate evidence about one security control for the year ended December 31, 2025. - Because the possible effects are material but not pervasive, a qualified opinion addresses the scope limitation. An unmodified opinion with an explanatory paragraph describing the unavailable logs - An explanatory paragraph cannot replace evidence needed to support an unmodified SOC 2 Type 2 opinion. - The missing logs create a material scope limitation, not merely a matter to describe. An adverse opinion because evidence supporting the control was unavailable - An adverse opinion addresses a supported conclusion that the subject matter is materially misstated, rather than an inability to obtain evidence. - Here, the auditor cannot determine the control’s status from the unavailable logs; a deficiency has not been established. A disclaimer of opinion because the scope of testing was restricted by management - Management’s refusal restricts testing, but it does not by itself require a disclaimer. - A disclaimer would require possible effects that are material and pervasive; this limitation is expressly confined to one control.
4. A service auditor examined a hosting provider's security controls for the year ended December 31, 2024. For a new SOC 2 Type 2 examination covering 2025, management states that an automated privileged-access control was unchanged. The restricted-use report will serve customers and their auditors. How should the auditor use the 2024 evidence?
Answer: D. Consider it in planning but obtain evidence that the control operated effectively during 2025.
Consider it in planning but obtain evidence that the control operated effectively during 2025. - The 2024 evidence can inform the auditor’s assessment of the privileged-access control and the design of 2025 procedures. - A SOC 2 Type 2 opinion requires evidence that the control operated effectively during the 2025 examination period. Use it as sufficient evidence because the control is automated and management reported no change. - An automated control may operate consistently, but that does not establish that it operated effectively during 2025. - Management’s statement that the control was unchanged does not replace current-period evidence. Use it after testing only the configuration in effect on December 31, 2025. - Testing the year-end configuration addresses the control at one point in time, not its operation throughout 2025. - The auditor also needs evidence about the control’s operation during the period covered by the Type 2 report. Use it instead of current testing if the prior report contained an unmodified opinion. - An unmodified 2024 opinion concerns the earlier examination period, not the control’s operation in 2025. - The restricted-use report for customers and their auditors still needs evidence supporting its 2025 Type 2 conclusion.
5. PayStream Solutions, Inc. processes payroll transactions for retail companies. Retailers and their financial statement auditors use PayStream's controls when evaluating internal control over financial reporting. A CPA firm is completing an examination of PayStream's system for the period January 1 through December 31. Using the exhibits, determine the appropriate engagement classification, evaluate the evidence concerning logical access provisioning controls, and document the reporting consequence.
6. PayAxis LLC processes payroll for user entities whose financial statements are audited. PayAxis engaged a service auditor to examine controls for the period January 1 through December 31, 2026. The engagement team must determine the appropriate engagement, evaluate PayAxis's system description and test results, and determine the effects of unresolved matters on the service auditor's report dated January 31, 2027.
1. What does management’s assertion in a SOC report address?
Service organization management asserts that the system description is fairly presented and that controls are suitably designed. In a Type 2 report, management also asserts that the controls operated effectively throughout the specified period; a Type 1 report addresses design at a specified point in time.
2. What does the processing integrity criterion assess in a SOC 2 report?
Whether system processing is complete, valid, accurate, timely, and authorized.
3. What is the purpose of a bridge letter in a SOC engagement?
A bridge letter is a service organization's management communication describing relevant changes, or the absence of changes, to controls during the gap between the SOC report period and a later date. It does not update the SOC report or provide independent assurance.
4. Who are the primary users of a SOC 1 report?
User entities and their auditors. A SOC 1 report helps them assess the effect of a service organization's controls on the user entity's financial statements.
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.