What is a SOC 2 exception?
A SOC 2 exception is an instance where a control did not operate as described during the audit — a test that failed. Exceptions appear in Type 2 reports and do not automatically mean you failed the audit.
The full answer
A SOC 2 exception is a specific finding where one of your controls did not work as described during the audit. Because a Type 2 examination tests how controls operated across an observation window — usually three to twelve months — the auditor samples evidence, and any sample that does not meet the control is recorded as an exception.
A common example is an access review that was supposed to happen quarterly but was missed one quarter, or a terminated employee whose access was not removed within your stated timeframe. The auditor documents what was tested, how many items failed, and the nature of the deviation. Exceptions live in the testing results section of a Type 2 report, not in a Type 1.
Importantly, an exception is not the same as failing your SOC 2. A report can contain a handful of exceptions and still carry a clean, unqualified opinion if the auditor concludes the controls were effective overall. Exceptions become more serious when they are numerous or severe enough that the auditor issues a qualified opinion, meaning specific controls did not operate effectively.
When you see exceptions, add a management response explaining the root cause and the fix, then let the corrected control run cleanly into your next audit window — the shortest Type 2 window most auditors accept is three months. Booking your next report through the AuditNex network keeps timing predictable, with SOC 2 audits starting at $2,500 promotionally and averaging about $5,000.
Go deeper
Short answer not enough? These pages cover the full picture:
Get matched with the right auditor
Answer a few questions about your scope and see transparent, comparable pricing from vetted audit firms — no sales calls.
Get instant pricing →Talk to auditors who handle this every week
Every firm on AuditNex is listed on identical terms — placement cannot be bought, and credentials are independently checked.
Related questions
Are SOC 2 reports public?
No. A SOC 2 report is confidential and shared only under NDA with customers, prospects, and auditors. If you want a freely shareable version, the public summary is a SOC 3 report.
Can I share my SOC 2 report with prospects?
Yes, but almost always under an NDA. SOC 2 reports are confidential, so companies share them with prospects and customers after a signed non-disclosure agreement. For a freely shareable version, use a SOC 3.
Can buyers verify my SOC 2 report is real?
Yes. Buyers verify a SOC 2 by confirming the signing CPA firm is licensed, checking the report period and opinion, and often contacting the firm directly. A real report names a licensed firm and follows AICPA formatting.
Can one SOC 2 report cover multiple products?
Yes. One SOC 2 report can cover multiple products or systems as long as they share the same control environment and you define that scope clearly in the system description. Many companies audit their whole platform in a single report.
How long is a SOC 2 report valid?
There is no formal expiry — the AICPA sets none. In practice, buyers treat a SOC 2 report as current for about twelve months from its period end date, then expect a fresh Type 2.
What are complementary user entity controls (CUECs)?
Complementary user entity controls, or CUECs, are controls the service organization assumes its customers will operate for the overall controls to work. They are listed in the SOC 2 report, and the auditor does not test them.
Sources: AICPA SSAE No. 18 attestation standards; AICPA SOC 2 Type 2 testing guidance, 2022. Answer written and maintained by the AuditNex research team; last reviewed July 26, 2026. AuditNex is a marketplace — accredited firms price and scope engagements independently.