On this page
A SOC 2 audit report (also called a SOC 2 report) is a licensed CPA firm’s report on a service organization’s controls, measured against the AICPA’s Trust Services Criteria. It holds the auditor’s opinion, management’s assertion, a description of the system, and the controls in scope. A Type 2 report also tests whether those controls operated effectively over a stated period and lists the results. A Type 1 covers the design of controls on a single date and has no operating-effectiveness testing; SOC 2 Type 1 vs Type 2 covers which to commission, and what a Type 2 report is covers what it contains.
The auditor is independent of the company, so the report is third-party evidence rather than the vendor’s own claim. It is an attestation report, not a certificate (why). A SOC 1 report covers controls relevant to a customer’s financial reporting, and SOC 3 is a short public summary. SOC 1 vs SOC 2 explains which one a customer is asking for, and our guide to SOC service providers explains who does the work.
The opinion, who signed it, the period and the date.
Management's claim on the same matters as the opinion.
What is in scope: services, commitments, customer-side controls, subservice organizations, incidents and changes.
What was tested, how, and each deviation found.
Plans and responses to deviations. Not covered by the auditor's report.
How to Read a SOC 2 Report: Three Questions in Order
A SOC 2 report reads in four steps that answer three questions. Can I rely on this report? Start with the opinion and report period. Does it cover what I am buying? Check the system description, then the exceptions in the control tests. What does it leave to me? Finish with customer-side controls, carved-out subservice providers, and any gap since the period ended.
An unmodified opinion (also called unqualified or clean) is the auditor’s conclusion on the audited system with no modification. A qualified opinion means the auditor found a matter that is material but not pervasive (AT-C 205 .72). The other two of the four opinions are an adverse opinion, which means the matters are material and pervasive (.74), and a disclaimer, which means the auditor could not get enough evidence and the possible effects are material and pervasive (.77). An unmodified opinion does not tell you the report covers your use, or that every control passed. The SOC 2 Guide has the auditor include all identified deviations in the test results and says materiality is generally not applied when deciding which to report (4.19), while AT-C 205.70 calls for a modified opinion only when the matter is or may be material. A clean opinion can therefore sit beside a list of deviations.
The table below follows the report from front to back and turns each part into what the standard requires, a check, and a request to send the vendor. The Section I and II rows answer the first question. The Section III rows that name the service, and the Section IV tests, answer the second. The customer-side control, subservice organization and Section V rows answer the third.
How to Review a Vendor’s SOC 2 Report
The AICPA does not fix a layout. The rows follow the five-part layout many reports use, and our annotated Type 2 report excerpts show each part in the language of a published report. AT-C section 205 sets what the auditor’s report must contain, the SOC 2 Guide is the AICPA’s guidance on applying it to SOC 2, and DC section 200 sets the criteria the system description is measured against.
| Part of the report | What the standard requires | What to check | If not, ask the vendor |
|---|---|---|---|
| Section I, auditor's report: signer, period and date | A title containing "independent", an addressee, and the subject matter with its period. Both sets of criteria: DC section 200 for the description and the Trust Services Criteria for the controls. The firm's signature, city and state, and a date no earlier than the evidence behind the opinion (AT-C 205 .63a to .63d, .63l to .63n; Guide Table 4-3). The report also states management's and the auditor's responsibilities, that the examination followed AICPA attestation standards, and the independence and inherent-limitation statements (.63e to .63j). | The period matches the one in the assertion and the description, and it ended recently. The categories in the scope paragraph are the ones the vendor claims. The report is a Type 2 if the vendor handles your sensitive data, because a Type 1 has no test results. The signing name is a firm you can look up (who signed it). The date falls after the period ends. | The firm's legal name and the date of its latest peer review. The dates of the next period, and a bridge letter for the gap (bridge letters). |
| Section I, auditor's report: opinion | An opinion, in all material respects, that the description presents the system as designed and implemented throughout the period and that the controls were suitably designed, plus for a Type 2 that they operated effectively throughout it (.63k; Guide Table 4-3). A Type 1 gives the first two as of one date. Where the design assumes controls at a subservice organization or at customers, the opinion is conditional on those controls operating (Guide, Appendix C illustrative reports). A modified opinion needs a separate paragraph describing the matter (.71), which the Guide places before the opinion paragraph (4.56, 4.62). | Count the parts: a Type 2 opinion with only two has no finding on operating effectiveness. Read any paragraph above the opinion that describes a matter. Look for "except for the effects of" (qualified, .73), "because of the significance" (adverse, .75) and "do not express an opinion" (disclaimer, .78). The wording each outcome requires is set out in the table by outcome. | The basis for any modified opinion, and what has changed since. |
| Section I, auditor's report: restricted use | An alert that the report is intended solely for named specified parties and should not be used by anyone else (.64, .65). The Guide says SOC 2 reports carry it because they include test results (4.36), and Table 4-3 names the usual parties: the service organization, its current and prospective user entities and business partners, practitioners serving them, and regulators, provided they understand the report's subject. | You are within the named parties before you forward or quote the report. | Only if you fall outside the named parties: the terms on which the vendor will share the report. |
| Section II, management's assertion | A written assertion on the same matters as the opinion: that the description is presented in accordance with the description criteria, that the controls were suitably designed, and for a Type 2 that they operated effectively (Guide 1.19, 2.72). Management writes it. It is generally expected to carry the same modifications as the opinion (3.256). | The assertion's period and parts mirror the opinion. A modified opinion beside an unmodified assertion, or the reverse, needs an explanation. | Why the assertion and the opinion differ, if they do. |
| Section III, system description: what it covers | DC1 the types of services. DC2 the principal service commitments and system requirements. DC3 the infrastructure, software, people, procedures and data. DC5 the applicable criteria and the controls designed for them. | The service you buy is named, with the environments and data flow you will use, and its commitments (uptime, breach notice) match your contract. A report scoped to one product line or environment does not cover a service outside it. Most SOC 2 reports include the Security category, so ask about one that does not. Availability, processing integrity, confidentiality and privacy are optional, so check which the vendor chose against your risk (Trust Services Criteria). | Which systems, environments and criteria are excluded. |
| Section III, system description: what it must disclose | DC4: for incidents in the period that came from controls not suitably designed or operating, or that significantly failed a service commitment, the nature, timing, extent and disposition of each. DC8: any applicable criterion that is not relevant to the system, with the reason. DC9 (Type 2): significant changes to the system during the period, which the Guide expects to give each change's date and how the system differed before and after (3.75). | Find the incident disclosure. Read each reason a criterion was called not relevant against how you use the service. Look for a migration, a new cloud provider or a new subservice organization in the change list, and check the tests cover both sides of it. | If there is no incident disclosure, whether no qualifying incident occurred or none was disclosed. |
| Section III, customer-side controls (CUECs) | DC6: the customer-side controls the design assumes. The Guide's illustrative report states that the examination did not include them (Appendix C). | Each one is something you can run, such as removing leavers' access or enforcing single sign-on on your own tenant. Give each a named owner at your company and confirm it is in place, because the auditor tested the vendor's controls and not yours. A report with no CUECs for a service you configure heavily is worth a second look. The CUEC guide walks through acting on the list. | Which CUECs apply to your use of the service. |
| Section III, subservice organizations | DC7: for each subservice organization the controls depend on, the nature of its service and the criteria its controls are meant to meet. Under the inclusive method the provider's relevant systems and controls are part of the description. Under carve-out the description gives the types of controls assumed of the provider. DC7's guidance says naming a carved-out provider may be useful; it does not require it. | The method is stated, and each provider is named so you know whose report to request. The Guide does not require the name, so ask when it is missing. Under carve-out the auditor does not test the provider's controls, so you need the provider's own SOC report for that assurance. A vendor on a public cloud may rely on the provider's report for the infrastructure layer; our guides to AWS SOC 2 compliance and GCP SOC 2 compliance show how auditors treat those inherited controls. | The names of any providers the report leaves out, and the providers' own current SOC reports (carve-out vs inclusive). |
| Section IV, tests of controls and results (Type 2) | For each control tested: the nature of the tests, and whether the auditor tested a sample or the whole population. When a deviation is found: the number of items tested, and the number and nature of the deviations (Guide 4.18, 4.20, Table 4-1). Materiality is generally not applied when deciding which deviations to report (4.19). Inquiry alone is not enough evidence of operating effectiveness (3.129). | The controls you care about have specific test procedures, populations and results, and the tests use inspection or reperformance, not inquiry alone. For any deviation, compare the sample with the population. The Guide's own example is one deviation in a sample of 25 from a population of 451, then 15 more items tested with none found (4.23). Isolated deviations are normal in a long Type 2 (our reading). Several in access, change management or incident response can point to a weakness the opinion does not surface. | The evidence and period behind those controls (SOC 2 sample size). For any deviation, whether it recurred across periods. How auditors judge exceptions covers when one changes the opinion. |
| Section V, other information (optional) | Not covered by the auditor's report. The auditor reads it for material inconsistencies with the description, the assertion or the report, and for material misstatements of fact (AT-C 205 .58, Guide 4.102, 4.104). The Guide lists future plans, marketing claims and management's responses to deviations as typical content (4.101). A response printed beside the control in the description is part of the description, and the auditor generally evaluates it (4.22, 4.103). | Where a response sits matters: beside the control, it was reviewed as part of the description. In Section V it is the vendor's statement. The Guide ordinarily places forward-looking fixes in this section (4.22), so read them as plans, not evidence. A usable response names the root cause, the fix and a date. | Evidence the fix is in place. Reading one deviation and its response is covered in SOC 2 exceptions and qualified opinions. |
Acceptance is a judgment call. If the signer, period, opinion and scope rows hold and the follow-ups are answered, accept the report and record who owns each CUEC. If the answers are partial, such as a gap since the period ended or an unclear scope, accept with conditions and put a date on each follow-up. If the opinion is modified, the scope leaves out the service you buy, or exceptions repeat in access, change management, or incident response, escalate to whoever owns the vendor risk. Read the opinion, period, and scope for every vendor. Read the controls and exceptions for vendors that hold your sensitive data. Anything missing is a question to send back to the vendor, not a reason to abandon the review. For the wider set of signals reviewers check, see SOC 2 report red flags.
The SOC 2 Quality Guild reliability rubric covers evidence-quality checks like these.
Who Signed It
The opinion letter names the CPA firm that signed the report. Two checks sit outside the report. First, confirm the firm and the signing CPA are licensed: our CPA licensing guide covers the state-board and CPAverify lookups. Second, look the firm up in the AICPA Peer Review public file and read the result and its date; our peer review guide explains each outcome. A firm that does not appear in the public file is a question for the vendor, not a finding on its own. The report authenticity checks cover the rest, and the SOC 2 auditor directory lets you compare firms.
How Long a SOC 2 Report Is Valid (and Bridge Letters)
A SOC 2 report has no expiry date set by the AICPA. Schellman describes 12 months as the general rule of thumb and says it is entirely up to the customer what they will accept. In practice, a report whose period ended more than a year ago usually prompts a request for a current one.
A Type 2 report covers a period that ended in the past. If the period ended on December 31 and you are reviewing it in May, the report says nothing about the months since. Vendors cover that gap with a bridge letter (also called a gap letter), a statement from the vendor’s management on whether material changes to controls have occurred since the report’s end date. Management signs it, not the auditor, so it carries less weight than the report, and Linford notes bridge letters typically cover no more than three months. Our bridge letter guide covers what one should include.
A run of consecutive Type 2 reports with no gaps between periods tells you more than a single one. Our SOC 2 audit renewal playbook covers how vendors keep that coverage unbroken.
If You Are the Vendor: What a Buyer’s Reviewer Will Ask
A buyer’s reviewer will run the table above against your report, and its last column is the list of requests to expect. Our guide to SOC 2 report red flags covers what else lowers a reviewer’s trust: how you describe the report, the pattern of your report periods, and signs of a thin audit. Have these five answers ready:
- Does the system description name the product and environments the buyer will use? A report scoped to one product line or environment does not cover a service outside it.
- When did the period end, and what covers the gap since? Keep a bridge letter ready and know the dates of your next period.
- What were the exceptions, and what did you do about them? Have the root cause, the fix, and the date for each. A response in Section V is unaudited, so a reviewer reads it as your claim.
- Can a customer perform your CUECs? Write them as actions a customer can complete and evidence. See the CUEC guide.
- Which providers are carved out, and where are their reports? Name each subservice organization and the method used. See the carve-out vs inclusive guide.
Customers and prospects can see your SOC 2 report, but not publicly. Its restricted-use paragraph limits the report to your company, your customers, and prospective customers who understand the system, so vendors share the full report under an NDA. A public trust center page can show the report type, the audit period, the CPA firm, the criteria in scope, and your subprocessors, while the full report, with its system description, test results, and any bridge letter, goes out on request. Trust center software compares the tools that run that request and NDA flow.
To plan the audit itself, see SOC 2 audit cost, how long a SOC 2 audit takes, and how to choose a SOC 2 auditor.
To compare SOC 2 audit firms by pricing, timeline, and industry fit, start with the SOC 2 auditor directory.
More in Audit Preparation