Guide, read 12 Nov 2026

# A SOC 2 exception is not a qualified opinion: 4 opinion types apply to an AT-C 205 examination

**The short answer:** A SOC 2 exception is a deviation an auditor records while testing a control, and it is listed in Section 4 of the report. A SOC 2 examination, performed under AT-C 205, ends in one of four opinions: unqualified, qualified, adverse or disclaimer. Exceptions are common and do not by themselves produce a qualified opinion.

[Open the glossary](https://soc2compliancesoftware.com/glossary/) | [See the ranked index](https://soc2compliancesoftware.com/)

## An exception is a deviation the auditor records while testing a control

During a SOC 2 examination the auditor tests each control the company says it runs. When the evidence shows the control was not designed to do its job, or did not run as described, the auditor records an exception. Schellman gives the two causes: a process that is not suitably designed to achieve its result, which can appear in a Type 1 or a Type 2 report, and a process that exists but did not operate as intended, which can appear only in a Type 2.

BARR, a CPA firm that published its own explanation on July 5, 2022, sorts exceptions into three kinds: a misstatement in the system description, a deficiency in control design, and a deficiency in operating effectiveness. A BARR consultant quoted on that page calls the third kind the most common. The example given is a control that removes access within one business day of termination, where one user in the auditor's sample lost access a week late.

One miss is enough. In the same BARR example, a company of 500 people requires every user to complete security training. The auditor tests a sample of employees, and a single employee without training is called out as an exception. BARR says one person is easy to overlook at a larger company that has no tool to track compliance, which is why the tracking behind a control matters as much as the control wording.

## Section 4 lists the tests and any exceptions, and Section 5 carries the response

BARR describes a SOC 2 report in five sections (July 26, 2022): the auditor's report, management's assertion, the system description, the description of criteria with tests, and optional other information. The opinion sits in Section 1. Exceptions are listed in Section 4, beside every control that was tested, and management responses go in Section 5. Layouts vary a little by firm, so check the table of contents of the report in front of you.

A Type 1 report differs here. BARR says a Type 1 Section 4 lists the controls without the auditor's test results, because that engagement only evaluates whether controls were designed properly on one date. A Type 2 Section 4 carries the test performed and the result for each control across the period, and that is where a reader finds exceptions. If you are short of time, read Section 4 before the opinion, because the opinion summarizes it.

The opinion covers three things. Microsoft's SOC 2 page says the auditor's opinion assesses the fairness of the description of controls, whether the controls are designed appropriately, and whether they operated effectively over a specified time period. Schellman's qualified opinion article uses the same split for the report components. An exception in any one of the three can matter, so a clean description does not offset a failed control, and the reverse holds too.

| Section | What it holds | Where exceptions show up |
|---|---|---|
| 1 Auditor's report | The opinion and the basis for it | A qualified or adverse opinion explains the matter here |
| 2 Management assertion | Management's statement about the system and controls | Not listed here |
| 3 System description | The people, process and technology behind the service | A misstatement exception concerns this text |
| 4 Criteria and tests | Each control tested, the test and the result | Each exception, beside its control |
| 5 Other information | Optional material from management | Management responses to exceptions |

## Four opinion types exist, and each carries its own wording

Schellman lists four possible outcomes in an article updated March 20, 2026: unqualified, qualified, adverse and disclaimer of opinion. An unqualified opinion is the clean report. The system was presented fairly in all material respects and the criteria were met. Schellman adds that an unqualified opinion can still sit beside noted findings, as long as they were not material or pervasive enough to prevent the criteria from being achieved.

Qualified is the middle case. Schellman says the auditor expresses it when issues materially affected a criterion but were not prevalent across the scoped system. It tells readers that the system was not presented fairly, that a control was not suitably designed, or that controls did not operate effectively. Schellman calls it quite common and says customers mostly accept it. Treat that as one firm's view, since each buyer sets its own bar.

Adverse and disclaimer are rare in practice. The BARR consultant on the July 5, 2022 page says they have never seen either one. BARR's example of an adverse case is a set of issues spread across change management, logical access and risk management, where the reader should not rely on the vendor's system. A disclaimer means the auditor could not express an opinion because evidence was insufficient.

| Opinion | When the auditor issues it | What the reader sees |
|---|---|---|
| Unqualified | System fairly presented and criteria achieved | A clean opinion; findings may still be listed |
| Qualified | Issues materially affect a criterion but are not pervasive | Wording such as 'except for' and an explanatory paragraph |
| Adverse | Misstatements that are both material and pervasive, backed by sufficient evidence | Wording such as 'because of the significance of the matter' |
| Disclaimer | Management blocked procedures, or evidence was insufficient | No opinion is expressed |

## A qualified opinion turns on a missed criterion, not on the count of exceptions

For a SOC 2, Schellman says a qualified opinion follows when the company does not meet a service commitment, judged against predefined criteria, or when the description of the system has material omissions that could mislead a reader. Its published position is that auditors could find many exceptions and still issue an unqualified opinion. BARR agrees that the effect on the opinion depends on the number of exceptions, their scope and their severity.

Layered controls decide many of these cases. Schellman's example is a terminated employee whose account kept privileged access. That deviation could support a qualification, unless other controls caught it: activity monitoring showing the account was not used after termination, a second login that had also been removed, or a periodic user access review that spotted the account. BARR separately advises backing each security criteria group with two to three controls.

Before an exception becomes final, both firms describe a conversation. The BARR consultant asks the client about suspect evidence first. In one case a vulnerability tracker was tagging severity wrongly, the client fixed the tagging, and the matter never became an exception. Schellman likewise starts by confirming that the auditor understood the technology and received complete information. Answer these questions fast, because a misunderstanding is cheapest to correct before the draft report.

## Buyers read an exception by control, cause and cure

Read an exception the way a customer's security reviewer should: which control failed, whether the criterion was still met, and whether the failure repeated. Schellman says a qualified opinion also tells the customer's own auditors that they can place some reliance on the system but may need extra testing for the areas the qualification touches. Expect that follow-up when the qualified criterion sits close to the customer's data.

A single access removal that ran late, found once and fixed within the period, reads very differently from a control that failed in most samples. The first is one deviation with a cause. The second can leave a criterion unmet. Neither is a verdict on the whole report, because Schellman notes that a qualification in one area does not discount the areas with none, since qualifications attach to specific objectives or commitments.

Dates matter as well. BARR recommends resolving exceptions within the audit period so the company can describe the remediation in its response. A reader can tell the difference between a fix made in month four and tested clean afterward, and a fix planned for next year. Put the fix date in the response, and make sure it falls inside the period if the facts allow it.

## Management responses should state the cause, the fix and a date

Schellman's advice (July 16, 2024) is that a company should respond to findings in its SOC report in almost every case, and that stakeholders largely expect it. The auditor does not evaluate the response. Schellman says responses commonly cover the circumstances of the exception, the root cause, the remediation plan to prevent recurrence, and the timeline. BARR places these responses in Section 5 of the report.

Because the auditor does not evaluate the response, it carries only the company's credibility. Keep it factual and short: one paragraph per exception, naming the control, what happened, what changed and the date the change took effect. If the company disagrees with the finding, raise that with the auditor before the report is final, which matches the first step Schellman lists: confirm that the auditor understood the process.

Do the work behind the words. Schellman's sequence is to validate the finding with the auditor, identify mitigating practices that ran in the period, correct the issue, find the root cause, write a remediation plan with owners, timelines and milestones, and then respond. It also lists an internal assessment before the next audit. A response naming a root cause such as segregation of duties, a missing policy or a misconfiguration reads as work done.

## More guides

- [AWS, Google Cloud and Azure are usually carved out of a SOC 2, which creates CSOCs and CUECs](https://soc2compliancesoftware.com/guides/complementary-user-entity-controls-and-carve-outs/)
- [A penetration test is not required for a SOC 2, and NIST SP 800-115 gives 4 phases to scope against](https://soc2compliancesoftware.com/guides/penetration-test-scope-for-soc-2/)
- [A SOC 2 readiness assessment is a 4-phase gap review that ends without an auditor opinion](https://soc2compliancesoftware.com/guides/readiness-assessments/)

## Sources

- [Schellman: What Determines a Qualified Opinion in a SOC Report](https://www.schellman.com/blog/soc-examinations/qualified-opinion-in-soc-report), read 12 Nov 2026
- [Schellman: Which SOC Report Opinion Do You Want](https://www.schellman.com/blog/soc-examinations/which-soc-opinion-do-you-want), read 12 Nov 2026
- [Schellman: How to Address a Testing Exception in Your SOC Report](https://www.schellman.com/blog/soc-examinations/how-to-address-testing-exceptions-in-soc), read 12 Nov 2026
- [BARR: Common SOC Report Exceptions and How To Mitigate Them](https://www.barradvisory.com/resource/common-soc-report-exceptions/), read 12 Nov 2026
- [BARR: Breaking Down SOC 2 Reports, Each Section](https://www.barradvisory.com/resource/sections-of-a-soc-2-report/), read 12 Nov 2026
- [BARR: Security Trust Services Criteria](https://www.barradvisory.com/resource/trust-services-criteria-security/), read 12 Nov 2026
- [Microsoft Learn: SOC 2 Type 2 overview](https://learn.microsoft.com/en-us/compliance/regulatory/offering-soc-2), read 12 Nov 2026
Last reviewed 12 Nov 2026.

Canonical: https://soc2compliancesoftware.com/guides/soc-2-exceptions-and-qualified-opinions/
