Compensating Controls: What They Are, SOC 2 Examples and How to Document One

Reviewed by Ali Aleali, CISSP, CCSP · Last reviewed November 21, 2026

Compensating controls are alternative safeguards an organization puts in place when a required control cannot be implemented as written, chosen so the alternative meets the same risk objective as the original. A compensating control is legitimate when the record names the original control, the real constraint, the alternative, the evidence and a review date.

At a glance

  • Definition: an alternative safeguard that meets the risk objective of a required control the organization cannot implement as written.
  • Common SOC 2 cases: MFA not supported on a system, endpoint enforcement that breaks devices, no second developer for code review.
  • Required documentation: original control and objective, constraint, alternative, how the alternative meets the objective, evidence, owner, review date.
  • Formal worksheet: PCI DSS v4.0.1 Appendix C, Compensating Controls Worksheet.
  • Framework fit: SOC 2 CC5.1, CC6.1, CC8.1. ISO/IEC 27001:2022 clause 6.1.3.

What is a compensating control?

A compensating control is a different control that reduces the same risk a required control was designed to reduce, used because the required control cannot be implemented. The risk objective stays fixed. Only the mechanism changes.

Examples of compensating controls include:

  • IP allowlisting and complex passwords on a database that does not support MFA.
  • Automated security gates in a deployment pipeline when no second developer exists to review code.
  • Detection and reporting of endpoint settings when enforcement breaks the device.
  • Network segmentation and IDS/IPS monitoring on a system waiting for a vendor patch.

Two related terms come up in the same audit conversations:

TermWhat the term meansWho operates the control
Compensating controlAn alternative control that meets the risk objective of a required control the organization cannot implementThe organization
Risk acceptanceA documented decision to live with a residual risk for a defined period, often alongside compensating controlsThe organization (management approves)
Complementary user entity control (CUEC)A control a vendor's SOC 2 report assumes the customer operatesThe customer of the service organization

A risk acceptance and a compensating control usually travel together. The SOC 2 vulnerability risk acceptance guide covers the CVE-with-no-fix case in detail, and the CUEC guide covers controls a vendor expects the customer to run.

Compensating control or dodge: how can a team tell the difference?

A compensating control is legitimate when a real technical or business constraint blocks the original control and the alternative reduces the same risk to a similar degree. A compensating control is a dodge when the alternative is weaker, already required for other reasons, or written after the fact to cover a missed task.

Signs of a legitimate compensating control:

  • The constraint is specific and checkable: the database engine has no MFA support, the team has one developer, the endpoint agent breaks screensaver login on macOS.
  • The alternative targets the same threat. For a missing MFA control, the threat is stolen credentials, so the alternative must limit what a stolen password can do.
  • The alternative produces evidence on a schedule, so an auditor can test operation over the audit period.
  • An owner and a review date exist, so the control is revisited when the constraint goes away.

Signs of a dodge:

  • The constraint is cost or convenience with no attempt at the original control.
  • The alternative is a control the framework already requires for the same system, relabeled.
  • The alternative is a policy statement with no technical control or evidence behind the policy.
  • The record is written during audit fieldwork to explain a gap the team already knew about.

Key insight

A compensating control cannot fix a missed task retroactively.

PCI DSS v4.0.1 Appendix B states that a compensating control cannot address a requirement that was missed in the past. The same logic applies in a SOC 2 audit: a quarterly access review skipped two quarters ago is an exception, and no new control written today changes that.

How do you write compensating control documentation?

Compensating control documentation is a short record, usually in the risk register or control matrix, that answers six questions. My approach keeps each answer to two or three sentences.

  1. Original control and risk objective. Name the control as written (for example, MFA on all production data stores) and the risk the control exists to reduce (unauthorized access with stolen credentials).
  2. Constraint. State the technical or business reason the original control cannot be met, specific enough to verify.
  3. Alternative controls. List each compensating control and the system the control runs on.
  4. How the alternative meets the same objective. Explain why the combination reduces the same risk to a similar level.
  5. Evidence. Name the artifact an auditor can sample and how often the artifact is produced: configuration exports, pipeline run logs, monthly review sign-offs.
  6. Owner and review date. Assign a role and a date to revisit the constraint, usually at least annually and whenever the system changes.

How should a compensating control description read in a SOC 2 report?

A compensating control description in a SOC 2 report should describe what the control does, not why the team cannot do the standard thing. Compensating control descriptions appear in the SOC 2 report, and enterprise procurement teams read that report alongside the auditor.

At one identity verification SaaS company with fewer than ten people, the draft control description for code change approvals opened with due to organizational constraints, independent code review is not performed. The CTO saw the problem immediately: large enterprise clients had already questioned the team's development practices, and that phrase reads as too small to do this properly. The rewrite kept the same mechanism and dropped the apology:

Draft wordingRewritten wording
Due to organizational constraints, independent code review is not performed. Automated testing and periodic management reviews are used in place of code review.Code change approvals and segregation of duties are enforced through mandatory automated security scanning and periodic management reviews.

Same control, same evidence, but the second version reads as a deliberate design choice. The risk register record still names the constraint, because the auditor needs the constraint to judge the fit.

Free download · Google Doc

Compensating Control Record Template

The six-part record with evidence, approval and review history sections, a filled example for a database without MFA, and a mapping to SOC 2, ISO 27001 and PCI DSS. Enter your email to get it.

What are real compensating control examples from SOC 2 engagements?

The three compensating control examples below come from SOC 2 readiness work at small and mid-sized companies.

What compensates for a database that does not support MFA?

A database that does not support MFA can pass a SOC 2 audit with compensating controls that limit what a stolen password can do, recorded as a formal exception in the risk register. SOC 2 CC6.1 asks for logical access controls appropriate to the risk and does not name MFA as mandatory for every system.

At a Series A fintech, one database system had no native MFA support. The team recorded the gap as a risk entry with these compensating controls:

  • Complex password requirements on every database account.
  • IP allowlisting, so connections come only from approved network locations.
  • Risk acceptance of the residual risk by management, with the decision dated in the risk register.

The risk register entry gave the auditor a traceable decision. The team also kept formally accepted risks apart from risks with active mitigation tasks, so the auditor did not expect remediation evidence for an accepted risk. The SOC 2 CC6.1 guide covers the rest of the logical access criterion. For systems that do support MFA, a phishing-resistant method is the stronger target, and the Entra ID passkeys guide covers that rollout.

What compensates when endpoint password enforcement breaks laptops?

When endpoint password enforcement breaks devices, the compensating control is to switch the endpoint management tool from enforcement to detection, then review compliance reports on a schedule and flag non-compliant devices for remediation. The auditor wants evidence that password requirements exist and are monitored, not proof of one specific enforcement mechanism.

At another identity verification SaaS company with fewer than ten people, the endpoint management integration forced a password reset every time the screensaver activated on Mac laptops. Disabling enforcement kept the laptops usable but left a password policy with no technical control and no evidence.

The compensating control chain the team adopted:

  1. The password policy defines the requirements.
  2. The endpoint management tool detects and reports each device's password settings.
  3. A periodic review checks the compliance report against the policy.
  4. Non-compliant devices get flagged and tracked to remediation.

While the integration was being fixed, the team collected screenshots of password settings from each user as interim evidence. Screenshots are a weak, manual control, so the record should give the interim control a short review date.

What replaces peer code review for a single developer?

For a single-developer company, the compensating control for peer code review is a set of automated gates in the deployment pipeline that block a release when a critical or high-severity issue is found. Under SOC 2 CC8.1, changes must be authorized, tested and approved. The developer authorizes, the automated scans test, and the passing gates record approval.

At a workflow SaaS company of 15 to 20 people, one developer had written every line of code for twenty years. The starting point:

  • Local git on a laptop, backed up as zip files to a network drive.
  • A 30-step deployment checklist in a spreadsheet, a sign of real discipline with no audit trail.
  • QA sign-off by phone call, with no written record or timestamp.
  • No independent code review and no automated security testing.

The compensating controls the team put in place:

  • Static application security testing (SAST) on every change.
  • Software composition analysis (SCA) for vulnerable dependencies.
  • Secret detection to block committed credentials.
  • Blocking rule: any critical or high-severity result stops the deployment.
  • Penetration test aligned to releases: the team released quarterly and already ran quarterly penetration tests, so every production release received dynamic testing.

The SOC 2 CC8.1 guide covers the full change management criterion, and the ticket-based change management guide covers teams that run changes through a ticketing system without CI/CD.

Watch out

A compensating control that only exists on paper fails the audit.

In both the endpoint and single-developer cases, the starting state was a policy or a disciplined habit with no record. The compensating control only counts once the control produces dated evidence an auditor can sample across the audit period.

What does PCI DSS say about compensating controls?

PCI DSS has the most formal compensating control process of the common frameworks. Appendix B of PCI DSS v4.0.1 sets the criteria, and Appendix C provides the Compensating Controls Worksheet the entity must complete for each requirement met through compensating controls. The assessor reviews each compensating control at every annual assessment.

Under Appendix B, a compensating control must:

  • Meet the intent and rigor of the original PCI DSS requirement.
  • Provide a similar level of defense as the original requirement.
  • Be above and beyond other PCI DSS requirements, so an existing requirement for the same item does not count.
  • Address the additional risk of not meeting the original requirement.
  • Address the requirement currently and in the future, never a requirement missed in the past.

The Appendix C worksheet has six rows:

  • Constraints
  • Definition of Compensating Controls
  • Objective
  • Identified Risk
  • Validation of Compensating Controls
  • Maintenance

SOC 2 and ISO 27001 have no mandated worksheet, but the PCI DSS worksheet works as a template for any framework. Truvo's PCI DSS compliance service covers compensating control worksheets for SaaS and fintech teams.

How do compensating controls map to SOC 2 and ISO 27001?

A well-documented compensating control gives the audit team evidence for several criteria at once, as a byproduct of the risk decision. The mapping below covers the examples in this guide.

Compensating control evidenceSOC 2 criteriaISO/IEC 27001:2022
Risk register entry with constraint, alternative and acceptanceCC3.2 risk identification and analysisClause 6.1.3 information security risk treatment
Alternative controls where segregation of duties is not practicalCC5.1 control selection and developmentAnnex A 5.3 segregation of duties
IP allowlisting and password rules for a system without MFACC6.1 logical access securityAnnex A 8.5 secure authentication
Endpoint detection reports and remediation ticketsCC6.1 logical access securityAnnex A 8.1 user endpoint devices
Pipeline gate logs (SAST, SCA, secret detection)CC8.1 change managementAnnex A 8.32 change management

The CC5.1 point of focus on segregation of duties expects alternative controls where separation is not practical. The SOC 2 CC5.1 guide covers control selection in more depth.

What steps put a compensating control in place?

My approach to putting a compensating control in place runs in six steps:

  1. Confirm the constraint. Test the original control first and record why the control fails: vendor documentation, a failed configuration, headcount.
  2. Name the threat. Write down what the original control stops, in one sentence.
  3. Pick alternatives that stop the same threat. Prefer technical controls with logs over manual checks.
  4. Write the six-part record in the risk register or control matrix, in plain wording that describes the control.
  5. Collect evidence from day one. Set the schedule for configuration exports, review sign-offs or pipeline logs.
  6. Set the review date. Revisit when the vendor adds support, the team grows or the system changes, and retire the compensating control once the original control is possible.

Get Compensating Controls Audit-Ready

An effective security program documents every exception before the auditor asks. We help small teams write compensating controls that hold up.

Why do compensating controls matter beyond the audit?

Compensating controls are part of the security design. A database with IP allowlisting is harder to reach with a stolen password than the same database with no alternative control. A well-written record gives the auditor a testable control, the enterprise buyer a clear description and the team a date to revisit the constraint. Truvo's SOC 2 compliance service includes writing these records as part of readiness work.

Frequently Asked Questions

What is a compensating control?

A compensating control is an alternative safeguard used when a required control cannot be implemented as written. The compensating control must reduce the same risk the original control targets, to a similar degree, and produce evidence an auditor can test.

What are examples of compensating controls?

Common compensating control examples include:

  • Complex passwords plus IP allowlisting for a system without MFA.
  • Endpoint detection and periodic compliance reviews when password enforcement breaks devices.
  • Automated SAST, SCA and secret detection gates in place of peer code review.

Does SOC 2 allow compensating controls?

Yes. SOC 2 does not prescribe specific mechanisms such as MFA on every system. Criteria such as CC6.1 and CC8.1 ask for controls appropriate to the risk, and the CC5.1 point of focus on segregation of duties expects alternative controls where separation is not practical. The auditor tests whether the compensating control reduces the same risk and operates across the audit period.

What should compensating control documentation include?

Compensating control documentation should include these items:

  • The original control and the risk the original control addresses.
  • The constraint that prevents implementation.
  • The alternative controls and how they meet the same objective.
  • The evidence an auditor can sample.
  • An owner and a review date.

PCI DSS v4.0.1 Appendix C provides a six-row worksheet with the same structure.

What is the difference between a compensating control and a risk acceptance?

A compensating control is an alternative safeguard that reduces a risk. A risk acceptance is a management decision to live with the residual risk that remains for a defined period. The two often appear together: a risk register entry records the gap, the compensating controls that reduce the risk and the approval of whatever risk is left.

Ready to Start Your Compliance Journey?

Get a clear, actionable roadmap with our readiness assessment.

Contact Us

Share this article:

Sample SOC 2 Control List

Input your email to download the list.

About the Author

Former security architect for Bank of Canada and Payments Canada. 20+ years building compliance programs for critical infrastructure.