Compensating controls vs mitigating controls
A mitigating control lowers the risk of a vulnerability; a compensating control meets a stated requirement another way. NIST defines them separately, and PCI SSC lists a compensating control as one way to address a finding. A worked PCI DSS example below uses CVE-2026-0322 and a 13 Nov 2026 planning date. Read 19 Nov 2026.
On this page
Two definitions, two jobs
NIST SP 800-160 Vol. 2 Rev. 1 defines mitigation as "A decision, action, or practice intended to reduce the level of risk associated with one or more threat events, threat scenarios, or vulnerabilities." The object is a risk or a vulnerability. SP 800-53 Rev. 5 defines compensating controls as the controls "employed in lieu of the controls in the baselines described in NIST Special Publication 800-53B that provide equivalent or comparable protection for a system or organization" (NIST CSRC glossary). The object is a required control.
A mitigating control answers "what lowers this risk?" A compensating control answers "what meets this requirement another way?" The same action can be both. Limiting a firewall's management interface to one jump box lowers the risk of a flaw in that interface (mitigating) and, if a standard requires the patch within a stated window, may also be offered as the substitute for the patch (compensating). The label depends on which question the record answers.
The glossary carries a second mitigation definition, from SP 800-216: "The temporary reduction or lessening of the impact of a vulnerability or the likelihood of its exploitation." This page uses the SP 800-160 wording because the comparison is about risk and requirements. The difference between remediation and mitigation uses the SP 800-216 wording because that question is about whether the flaw is still there.
How standards treat a compensating control
| Publisher | Wording read on 19 Nov 2026 | What it shows |
|---|---|---|
| NIST CSRC glossary (SP 800-53 Rev. 5) | Controls "employed in lieu of the controls in the baselines ... that provide equivalent or comparable protection" | Tied to a baseline requirement |
| PCI SSC FAQ 1597 (May 2025) | "Addressed - the entity determines whether to resolve the vulnerability or to mitigate the risk by addressing the vulnerability in another way (e.g., with a compensating control or by disabling a vulnerable service)." | A compensating control is one way to address a finding that is not resolved |
| PCI SSC FAQ 1046 (April 2012) | "QSAs are responsible to determine whether a compensating control is sufficient to meet the intent of a requirement" | The assessor decides, not the Council |
| FedRAMP legacy playbook (reference only after 24 Jun 2026) | "High-risk VDs must be mitigated to a Moderate level through compensating controls within thirty (30) days." | Compensating controls used as the means of mitigation |
PCI SSC and the FedRAMP playbook use a compensating control as a means of mitigation, while NIST ties the term to a baseline requirement. Quote any one of them with its publisher named. How FedRAMP's 2026 rules and CISA word the remediation side is in the difference guide.
Worked example: one flaw, two record lines
An invented merchant runs a PAN-OS firewall in its card data environment. Palo Alto Networks published fixed builds for CVE-2026-0322 on 14 Oct 2026 (advisory), and CISA added the flaw to its Known Exploited Vulnerabilities catalog the same day with a due date of 17 Oct 2026 (KEV feed, version 2026.11.18). The merchant rates the flaw critical for its own environment, which PCI DSS Requirement 6.3.1 lets it do: FAQ 1597 says the requirement does not oblige an entity to accept a rating assigned by an outside source.
Requirement 6.3.3 gives critical patches one month from release (FAQ 1597), which ends on 14 Nov 2026. FAQ 1572 words the same requirement as "30 days of release"; 30 days from 14 Oct is 13 Nov 2026. The merchant plans to the earlier date, 13 Nov 2026, and uses it below. A change freeze blocks installs until 30 Nov. On 15 Oct the network team limits the management interface to a single jump box, the step Palo Alto describes: the vendor rates the flaw CVSS 4.0 8.5 with the jump box against 8.6 without it.
Line 1, mitigation (answers: what lowers this risk?)
- Finding: CVE-2026-0322 on fw-cde-01 (sample name).
- Control: management interface reachable only from jump box JB-02, in force from 15 Oct 2026.
- What it changes: the network path to the interface. What stays: the flaw, and any account that can reach JB-02.
- Vendor rating: CVSS 4.0 8.5 with the jump box, 8.6 without.
- Ends: when a fixed build for the firewall's release train is installed and
show system infoshows it.
Line 2, compensating (answers: what meets the requirement another way?)
- Requirement: PCI DSS 6.3.3, critical patch within one month of release (14 Nov 2026; 30 days is 13 Nov). Planning date 13 Nov 2026.
- Why it cannot be met as written: change freeze until 30 Nov 2026.
- Substitute: the controls offered, and the reasoning that they give equivalent or comparable protection.
- Accepted by: the QSA, name and date, before 13 Nov 2026.
- Ends: the day the fixed build is installed.
The jump box alone is a thin basis for line 2. The vendor's rating moves by 0.1, and the flaw stays reachable by anyone who holds a session on the jump box. The QSA decides whether a control meets the intent of the requirement (FAQ 1046), so line 2 needs more than line 1, for example controls that detect use of the interface.
The date matters as much as the content. FAQ 1572 names "not installing a critical security patch within 30 days of release" among the periodic activities that cannot be performed retroactively, and says an assessor may still mark the requirement In Place only if the entity has corrected course and the assessor has assurance of four things, including that the miss was an "exceptional circumstance". The substitute is therefore agreed before 13 Nov, not written after it.
A control does not close the finding
FedRAMP's 2026 rules say providers "SHOULD remediate Known Exploited Vulnerabilities according to the due dates in the CISA Known Exploited Vulnerabilities Catalog (even if the vulnerability has been fully mitigated)" (VDR-TFR-KEV). Neither kind of control closes a finding on its own. The finding closes when the flaw is removed, or when a dated acceptance is recorded in the exception register.
Sources
- NIST CSRC glossary, mitigation (SP 800-160 Vol. 2 Rev. 1; SP 800-216), read 19 Nov 2026
- NIST CSRC glossary, compensating controls (SP 800-53 Rev. 5), read 19 Nov 2026
- PCI SSC FAQ 1597 (May 2025), read 19 Nov 2026
- PCI SSC FAQ 1572 (June 2025), read 19 Nov 2026
- PCI SSC FAQ 1046 (April 2012), read 19 Nov 2026
- FedRAMP 2026 Vulnerability Detection and Response rules, VDR-TFR-KEV, read 19 Nov 2026
- FedRAMP legacy playbook, POA&M, read 19 Nov 2026
- Palo Alto Networks advisory CVE-2026-0322, read 19 Nov 2026
- CISA KEV feed, catalog version 2026.11.18, read 19 Nov 2026
Last reviewed