On this page

A SOC 2 exception is a documented finding from an auditor’s control testing. In a Type 2 report, which tests controls across the whole review period, a deviation is a failure of a control to operate in a specific instance, such as a sampled item whose evidence does not meet the control as described. A new hire who completes security training on day 35 deviates from a 30-day policy. An exception records the deviation or deviations found, and the AICPA’s SOC 2 Guide (October 2022) says the description of tests would include all identified deviations, and that materiality is generally not applied to that choice because the auditor cannot tell which deviation will matter to an individual report user (4.19). An exception does not by itself modify the opinion.

An unqualified opinion, also called unmodified, is the clean opinion: the auditor found no material departure from the criteria and no material gap in evidence. The report can still list exceptions, as the outcome table in what the standard requires the report to say, by outcome shows.

A qualified opinion is an “except for” conclusion about a material matter whose effects, or possible effects when evidence is insufficient, are not pervasive. It can concern the system description, control design, operating effectiveness, or a scope limitation. Read the basis for the opinion and the detailed findings together. What you should accept depends on what the exception touches in the service you will use, and the opinion cannot tell you that. If your own audit returned a modified opinion, what happens if you fail a SOC 2 audit covers the path back to a clean report.

What to do with a report that lists exceptions

Find the opinion and its basis in the auditor’s report (commonly Section I) and the exceptions in the test results (commonly Section IV). Section numbering varies by firm; the review matrix in our audit report guide shows where each part sits. Then route each finding by how much of your planned use it touches.

Scale vendor follow-up to the risk the exception creates for your intended use.
What the report shows Decision question Constructive next step
A bounded exception outside your planned use Does it touch your data, integration, or the service commitment you depend on? Document why it is out of scope for your risk assessment and monitor the next report or bridge period.
An exception affecting a control you rely on Is the stated cause understood, and is the residual risk acceptable before remediation? Ask for the remediation owner, target date, and evidence that the corrected control has operated.
A qualified opinion or recurring issue in a core area Can the vendor meet your requirements with safeguards, a changed scope, or a later start date? Escalate the decision, define any compensating safeguards, and set a condition for accepting evidence of remediation.
Text alternative: the table routes a vendor finding to documentation, evidence requests, or an escalated decision based on its relevance and recurrence.

Relevance does most of the work. A physical-security exception at a data center you do not use may not touch you. A pattern of late access removal (CC6.2 and CC6.3) on a platform that will hold your customer data does.

A qualified opinion is not an automatic disqualification, and it is not an approval either. It is a reason for closer due diligence. Read the basis to see whether it concerns the description, control design, operating effectiveness, or a limit on the evidence, and which systems or criteria it affects. Do not assume it stays within one Trust Services Category.

Treat a management response as a commitment, not proof that the issue is fixed. Look for a stated cause, an owner, a target date, and a way to verify that the corrected control has operated. Ask for dated records of what changed and that the control ran afterward. A response or a bridge letter explains the claimed fix but is not independent auditor assurance. If you need that, request an appropriately scoped subsequent examination or other auditor reporting.

A worked example: two late removals in a sample of 25

This illustrative example, not a client record, shows how a Type 2 test of an offboarding control reads in the results section. The control supports CC6.2 and CC6.3; our controls library lists example evidence for this control. The population and sample sizes are made up for the example. The Guide sets no sample size; it follows from the tolerable rate of deviation (3.160).

ComponentExample
ControlLogical access credentials for terminated users are removed or disabled within the deadline in the company’s access policy.
Auditor’s testInspected the list of 450 employees terminated during the review period to verify that system access was revoked within 24 hours of their termination date, per company policy. Selected a sample of 25.
Deviations foundFor 2 of the 25 employees tested, system access remained active for more than 72 hours after their termination date: 4 days for one, 6 days for the other.
How it is reportedAs one results statement for the control, with the number tested and the number and nature of the deviations. The Guide’s own example of a control with a deviation reads the same way (4.23).

The Guide lists what the results of a test should give a reader: the control tested, whether the auditor sampled or tested everything, the nature of the test, and, when there are deviations, the number of items tested and the number and nature of the deviations (Table 4-1). The cause is optional. Any cause in the report usually comes from management (4.21). Where a cause sits in the description, it is part of the description, and the auditor would generally include management’s responses in evaluating the description (4.22). In a section such as Other Information Provided by the Service Organization, the auditor’s report does not cover it. Either way it is the company’s account, not the auditor’s finding.

Two things the entry cannot tell you are whether the auditor widened the sample after the first deviation and how much failure the auditor was prepared to accept. The second is the tolerable rate of deviation, and Table 4-1 does not ask the report to state it. Both are fair questions for the vendor or its auditor. Our SOC 2 sample size guide shows how firms choose a sample and when they extend it.

Check that the control, the test, the result, and the response describe the same problem at the same level of detail.

How auditors judge exceptions

The auditor first decides whether the deviations found point to a control deficiency, then whether the deficiencies, alone or together, are material to the service commitments and system requirements the company has set (Guide 3.182, 3.187). If they are likely to be, the opinion on controls is modified. Pervasiveness then sets how far: material but not pervasive gives a qualified opinion, material and pervasive an adverse one, and missing evidence whose possible effects are both material and pervasive a disclaimer. The wording each outcome requires is in what the standard requires the report to say, by outcome.

The measure is the vendor’s own commitments, not your use. The Guide says the same deficiency can be material at one company and not at another, and gives an example: two cloud infrastructure providers whose failover design is likely to leave processing capacity at 50% of peak load for the first day of a failover. One serves SaaS storage and retrieval companies and commits to monthly total capacity. The other serves trading platforms and commits to peak transaction-processing volume. The Guide says the auditor is likely to reach different conclusions for the two (3.188, 3.189). Among the qualitative factors the Guide lists (3.190):

  • Relevance to a commitment. A deficiency in a control whose risk other controls already cover (often called compensating controls) may not matter. The Guide’s example is encrypted backup tapes. The description does not list physical controls over the tape store, because the tapes are encrypted and the encryption and key management controls are effective, so a gap in physical access to the tape store is likely immaterial.
  • Whether the description names the control. If the description includes a control, report users are likely to assume it matters, and a deficiency in it would likely be considered material.
  • What the company has told users elsewhere. If the auditor knows of a website claim that all client data is kept encrypted at all times, the auditor is more likely to treat that representation as important, and so material, to report users.
  • Laws and regulations, and other parties. Where the company is subject to laws or regulations related to security or the other categories in scope, deficiencies and deviations related to compliance are likely to be significant. A deficiency that could also cause a deficiency at a user entity or business partner is more likely to be considered material.
  • Earlier periods and intent. A threat found in a prior period can weigh on the current conclusion, and an intentional act, particularly one by management or senior management, is likely to be considered more material than an unintentional one.

The count enters through quantitative factors, which the Guide describes as matters such as the tolerable rate of deviation and the observed rate of deviation. For operating effectiveness, the auditor considers the effect of deviations individually and in combination with others (3.191). It is one input, not the whole judgment. None of the factors turns on how one customer plans to use the service, so the table above puts that question to you.

Check the exception pattern against the opinion

Start with the opinion and any Basis for Qualified Opinion. AT-C 205.71 requires the auditor to describe the matter behind any modification in a separate paragraph, so that is where the explanation should be. Then trace the cited criteria into the detailed testing section. A qualified opinion should identify the matter that drove it, and the testing detail should let you see its scope. If several exceptions concern the same risk and the opinion gives you no way to reconcile them, ask the vendor or auditor for an explanation. That mismatch is a review question, not a conclusion about the audit.

An unqualified opinion does not make every exception irrelevant. The auditor has judged the exceptions against the vendor’s commitments; whether a finding affects the systems, data, or commitments you will rely on is a separate decision. Make it after reviewing scope, exceptions, complementary user entity controls, and remediation.

When your customers review your exceptions

Your customers’ security teams run this review in reverse: they read your opinion, trace each exception into the testing section, and weigh your management response as a commitment. How a management response reads to a reviewer is covered in what happens if you fail a SOC 2 audit.

What helps:

  • Share the full report under NDA, including the testing detail and any management response, rather than a summary of it.
  • Keep your account consistent with the report. If your explanation and the auditor’s wording describe different problems, the reviewer is likely to trust the auditor’s version.

What tends to backfire:

  • Calling a finding typical. “Exceptions are common for this control” or “a qualified opinion is normal” asks the reviewer to judge an average report instead of yours. It can invite closer scrutiny, not less.
  • Arguing with the auditor. The reviewer has the CPA firm’s signed opinion and was not part of the fieldwork, so disputing a finding after issuance can cost credibility. Raise a disagreement with the auditor before the report is issued. Once it is final, accept the finding as written and show what changed.
  • Steering the reading. Telling a reviewer which sections matter, or that a finding “doesn’t apply” to them without showing why, does the opposite of what you intend. Show the scope and let them decide.

The other signals customers check, including how the report is described and the pattern of report periods, are in our guide to SOC 2 report red flags.

The SOC 2 auditor directory compares firms on scope, pricing, and timelines. Ask how each firm evaluates exceptions and communicates the basis for a modified opinion.