SOC 2 FundamentalsExceptionsRisk AcceptanceSOC 2Audit

Exceptions & Waivers in SOC 2: A Practical Guide

Learn how to document, approve, and manage control exceptions and accepted risks without creating audit problems.

SecureSpect Team··8 min read

What Are Control Exceptions?

A control exception occurs when a SOC 2 requirement cannot be met as designed — temporarily or permanently — and the organization makes a documented, approved decision to accept the associated risk rather than immediately remediate it.

Exceptions are normal. Auditors expect them. What auditors do not accept is undocumented exceptions, or exceptions where the risk was never formally evaluated.

The Four Elements of a Valid Exception

Every exception in your risk register should have:

1. Description — What control is not being met and why. Be specific: "Production database backups are retained for 30 days, not the 90 days specified in our backup policy" is better than "backup retention non-compliant."

2. Business justification — Why full remediation is not happening immediately. Storage cost, vendor constraint, migration in progress, and low data sensitivity are all legitimate reasons — as long as they're documented.

3. Compensating controls — What partially mitigates the risk in lieu of the missing control. Auditors want to see that you've thought about risk reduction even while the exception is open.

4. Expiry date and owner — Every exception must have a named owner who is accountable for remediation or re-approval, and a date by which the exception is reviewed.

Common Exception Scenarios

Vendor-Imposed Limitations

A SaaS vendor doesn't support audit logging export. You can't force the vendor to add the feature. Document: the control gap, your compensating control (manual quarterly review of vendor's admin console), and a mitigation plan (evaluate alternatives at next renewal).

Prioritization Decisions

A legacy internal tool lacks MFA. Full remediation requires a migration to a modern auth provider. Document the timeline, restrict access to the tool to a named list of users, and require VPN as a compensating control.

Inherited Infrastructure

An acquired company's systems have known vulnerabilities. Document the gap, the remediation roadmap, and network segmentation as a compensating control.

Exceptions vs. Waivers

These terms are used interchangeably, but there is a useful distinction:

  • Exception — A one-time deviation from a control requirement, expected to be remediated.
  • Waiver — A formal, sometimes permanent decision that a control does not apply to a specific scope, or that an accepted risk will not be remediated.
Both need the same four elements. Waivers additionally need sign-off from a senior owner (CISO, VP Engineering, or equivalent).

Managing Exceptions in SecureSpect

SecureSpect's Exceptions & Waivers module provides:

  • A structured intake form capturing all four required elements
  • An approval workflow routing exceptions to the appropriate owner
  • Expiry reminders sent 30 and 7 days before the review date
  • An audit trail showing who approved what and when
  • Automatic linkage between exceptions and the affected SOC 2 controls

When your auditor asks "how do you manage accepted risks?", you can export a complete exception report with approval history in seconds.

Automate your SOC 2 evidence collection

Connect your AWS and GitHub environments and start collecting audit-ready evidence today. Free to start.

Start Free →More Articles