Skip to content
SOC 2 Compliance Software

Home / Glossary / Control exception

Glossary, read 12 Nov 2026

Control exception in a SOC 2 examination, defined with a sourced example

All termsRead the guides

The definition of Control exception

Schellman's example of a design exception is having no vendor management program to assess subservice organizations. Its example of an operating exception is a program that says subservice organizations are assessed at least annually, where the review was not completed. Both are reported in the auditor's testing results with the nature and extent of the deviation.

Breadth drives the outcome. Schellman says the key considerations are how critical the failed control is to the objective and how widely it failed, such as 15 of 25 runs against one of 25. Auditors may extend the sample after one miss. A-LIGN says additional samples are selected on exceptions to decide whether a key control is operating effectively.

After an exception, Schellman's six steps are to check the facts with the auditor, identify mitigating controls, correct the issue, find the root cause, form a remediation plan, and respond in the report. Schellman notes the response is not evaluated by the auditor, and Section 5 of the report is unaudited.

A sourced example

Schellman's SOC 1 article asks readers to judge an exception by breadth, with the example "did it fail for 15 of 25 job processing runs or was it only one of 25." It adds that the criticality of the failed control to the objective matters, and that the auditor decides whether the control alone or with other well-designed controls still met the objective. Schellman: Managing exceptions in SOC 1, read 12 Nov 2026.

Sources

  1. Schellman: Managing exceptions in SOC 1, read 12 Nov 2026
  2. Schellman: Addressing testing exceptions in SOC, read 12 Nov 2026
  3. Schellman: Qualified opinion in a SOC report, read 12 Nov 2026
  4. A-LIGN: Can you fail a SOC 2 examination, read 12 Nov 2026

Last reviewed 12 Nov 2026.