





An exception is a case where the auditor found that a control did not operate as described, and it is recorded in the test results of your SOC 2 report. SOC 2 does not produce a pass or fail grade. The auditor forms an opinion, and exceptions are one of the things that opinion is based on. Because every customer who reads your report sees them, avoiding exceptions is worth real effort.
Term | What it means |
Exception | A deviation the auditor noted when testing a control, listed with the test results. One exception does not automatically change the opinion. |
Unqualified (unmodified) opinion | The description is fairly presented and the controls meet the criteria in all material respects. A report with this opinion can still list exceptions, especially isolated or remediated ones. |
Qualified opinion | One or more matters are material but limited in scope, so the auditor gives an "except for" opinion. |
Adverse opinion | Problems are material and pervasive, so users cannot rely on the controls or description. This is rare. |
Disclaimer of opinion | The auditor could not obtain enough evidence to form an opinion. |
Auditors weigh the number of exceptions, how widespread they are and how material they are, along with any compensating controls, before deciding which opinion is justified.
Operating exceptions. A control was designed properly but did not run as described, for example a review that was skipped.
Design deficiencies. A control as designed would not meet the criterion.
Evidence gaps. The control may have run, but you cannot show it.
Description issues. The description of the system does not match how the system really works.
Common exception | Typical cause | How to prevent it | Where Cstream fits |
Training not completed on time | No per-person tracking | Assign training at onboarding and follow up on overdue items | Training tracks completion per employee |
Policies not reviewed or acknowledged | No schedule or owner | Version policies, set review dates, collect acknowledgments | Organization Policies handles versioning and assignment |
Vendor reviews overdue or missing | Vendors added informally | Keep one inventory and a review schedule | Vendor Management tests vendors against vendor control tests |
Plans never tested | Plans treated as documents | Schedule and record annual exercises | Assessments records incident response, disaster recovery and continuity tests |
Access not removed promptly | Offboarding steps not tracked | Tie removal to a checklist and verify | People Management assigns tasks per employee |
Changes without approval | Approvals happen in chat | Require approval in a system that keeps records | Version-control integrations feed control test results |
Missing evidence for part of the period | Evidence gathered at the end | Collect evidence continuously | Evidence Management organizes proof against controls |
Control owner unclear | Responsibility assumed, not assigned | Name an owner and backup per control | Job Functions and Projects make roles and tasks explicit |
Description out of date | Systems changed during the window | Review the description when systems change | Asset Management keeps the inventory current |
With Cstream: Observe Pod tests controls continuously, and Test Insights turns failures into a live remediation worklist, so you fix problems while they are still small. One set of checks serves engineers, leadership and auditors, so what your team sees is what your auditor sees.
Understand the cause, not just the instance. Was it a one-off or a process gap?
Fix the process and record the date of the fix.
Write a clear management response that states what happened, why and what changed.
Add a check so it cannot quietly recur.
Tell your customers plainly if they ask. A well-explained, remediated exception is often less worrying to a reviewer than a suspiciously perfect report.
Buyers look at the opinion first, then read the test results anyway. They look for how many exceptions there are, whether they cluster in one area such as access, whether they were remediated and whether the management response is credible.
Assign owners and backups for every control
Put recurring tasks on a calendar before the window opens
Review control results weekly or monthly, not only before the audit
Keep evidence in one organized place
Tell the auditor about system and vendor changes early
With Cstream: the Audit Dashboard shows framework coverage with evidence attached, so you can spot a thin area before the auditor does.
Cstream is the trusted GRC platform that supports startups through every stage of the SOC 2 journey, from planning and control implementation to audit preparation and ongoing compliance. Cstream keeps one data model for IT operations and compliance, so the assets, people, vendors, policies and control test results you use every day are the same ones that support your audit.
Cstream's SOC 2 capabilities include key features supporting preparation and audit, such as:
Cstream works directly with your audit firm to keep reviews moving. Multi-framework Mapping also lets the same controls support ISO 27001, HIPAA and other frameworks later.
Schedule a demo to see how Cstream supports your SOC 2 journey.

