# A compensating control already sits in front of the flaw

Canonical: https://remediationvsmitigation.com/decision-table/compensating-control-in-front/

Treat the finding as mitigated, not fixed, and write a fix date the day the control goes in. FedRAMP's 2026 rules say a fully mitigated vulnerability still exists until remediated, and a KEV due date stands even then. NIST SP 800-40 Rev. 4 lets an organization accept the risk by relying on existing controls.

Guidance points to: Mitigate now, fix later. Also allowed: Accept with a dated exception.

Signals: Exploit path blocked at a choke point; The vulnerable code or version is unchanged.

## The situation

A vendor fix exists and is not yet installed. Between an attacker and the vulnerable component sits a control you operate: a WAF rule, a network segment, an access restriction. The row applies once the control has been tested against this flaw. A control nobody tested is not yet a control, and the finding stays on whichever row its other facts select.

## The decision and its conditions

Mitigate now, fix later. The control covers the days before the fix, and the fix date is written when the control goes in, not after. Accept with a dated exception is the other allowed response, and it fits only where no fix will come, such as a vendor that never ships one (see the [risk acceptance form](https://remediationvsmitigation.com/risk-acceptance-form/)). The decision holds while four conditions hold:

1. The control was tested against this specific flaw, with a date and a named tester.
2. The control sits on every path to the component, not only the main one.
3. A fix date, an owner and a date to remove the control are on the record.
4. The control is tested again whenever its rule set, the product version or the network path changes.

## What the sources say a control is worth

Four issuers, six statements about a control in front of a flaw. Quotes read 19 Nov 2026.

| Source | What it says a control does | Quote |
|---|---|---|
| NIST SP 800-40 Rev. 4, Section 2.1 | Can support acceptance | "Accept the risk from vulnerable software as is, such as by relying on existing security controls to prevent vulnerability exploitation" |
| FedRAMP VER-EVA-EIR | Can change the exposure label | "once this prevention is in place the vulnerability should no longer be considered an internet-reachable vulnerability." |
| FedRAMP VDR-CSO-RES | Leaves the flaw in place | "A fully mitigated vulnerability will still exist (with negligible risk) until it has been remediated." |
| FedRAMP VDR-TFR-KEV | Does not excuse a KEV due date | "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)" |
| OWASP Virtual Patching Cheat Sheet | Covers only what it inspects | "A virtual patch reduces exposure only for traffic the enforcement layer inspects and attack variants its rules recognize." |
| PCI SSC FAQ 1046 | Is judged by the assessor | "QSAs are responsible to determine whether a compensating control is sufficient to meet the intent of a requirement" |

NIST and FedRAMP are not in conflict once each is read for its job. NIST describes what an organization may decide about its own risk. FedRAMP and CISA describe what a regulated party must be able to show. The same control can justify acceptance in a private risk register and still not satisfy a KEV due date. CISA's guidance goes further for agencies: "Aside from removing affected assets from the network, the only known technical mitigation to vulnerabilities in the KEV Catalog is to apply the required actions listed in the catalog." BOD 26-04 also sets the exposure value harder than FedRAMP does. "Publicly Exposed" is Yes if the asset is "accessible to unauthenticated or untrusted entities via public networks", and if any one method finds it exposed the value is Yes. A filter in front of an asset reachable from the internet is therefore not on its own a change to No, while FedRAMP lets a prevention in place drop the internet-reachable label. A restriction that leaves no public path at all is the case where the BOD 26-04 value can change, as the worked case shows.

## Worked case: CVE-2026-0322 on a PAN-OS firewall

CVE-2026-0322 is code injection in the PAN-OS management interface (CVSS 4.0 base score 8.6, from Palo Alto), worked through on the [access restriction](https://remediationvsmitigation.com/compensating-controls/access-restriction/) page. Here a firewall on 11.2.12 has its management interface open to the internet and gets the jump-box restriction; the fix is 11.2.13-h3 or 11.2.16.

CVE-2026-0322, PAN-OS on PA-Series, VM-Series and Panorama, read 19 Nov 2026. CISA's SSVC data on the record reads exploitation active, automatable no, technical impact total.

| Date | Event | Basis |
|---|---|---|
| 14 Oct 2026 | Palo Alto publishes the advisory with exploit maturity ATTACKED and notes very limited exploitation. CISA adds the CVE to the KEV catalog the same day, due 17 Oct 2026, forensic triage required | Palo Alto advisory; CISA KEV feed |
| 14 Oct 2026 | The team restricts the management interface to one jump box and tests from an outside network that the address no longer answers | Control and test date assumed |
| 17 Oct 2026 | KEV due date, 3 days after listing | CISA KEV feed |
| 28 Oct 2026 | Day 14. Table 1 date for a federal agency whose exposure value is now No: exposed, KEV, not automatable, total control is row 3 (3 days); unexposed is row 11 (14 days) | BOD 26-04 Table 1, counted |
| 24 Apr 2027 | Outer limit if the team were a FedRAMP provider and its evaluation date were 14 Oct 2026: 192 days later | VER-TFR-MAV, counted |

The control changes the answer differently under each rule. A federal agency that can show no other method finds the interface public moves from row 3 to row 11: 28 Oct instead of 17 Oct. The agency, not the catalog, makes the final exposure call, so the evidence of the test is the record. A FedRAMP provider gets no such move: VDR-TFR-KEV tells it to remediate by the CISA date, 17 Oct, "even if the vulnerability has been fully mitigated". Either way the fix date stays.

## What to record

- The control, where it sits on the traffic path, and the flaw it covers (CVE ID).
- The test: the variants tried, the result, the date and the tester.
- What the control does not cover, such as an internal route to the same service.
- The exposure value under the rule that binds you: internet-reachable or not under FedRAMP, Publicly Exposed under BOD 26-04.
- The fix date, the owner, the date the control is removed and the date of the last re-test.
- For a KEV entry, the due date and the log review that covers the time before the control existed.

Entries for a [WAF rule](https://remediationvsmitigation.com/compensating-controls/waf-rule/) and [network segmentation](https://remediationvsmitigation.com/compensating-controls/network-segmentation/) show these fields filled in. To prove the control holds, see [how to verify a mitigation](https://remediationvsmitigation.com/guides/verifying-a-mitigation-works/).

## When the usual answer is wrong

- **The flaw is added to the KEV catalog.** The due date replaces your fix date, and a provider's control does not move it, as on 14 Oct above. Go to [patch available and exposed](https://remediationvsmitigation.com/decision-table/kev-patch-available-exposed/).
- **The control sees only part of the traffic.** OWASP adds that "Code level fixes and Virtual Patching are NOT mutually exclusive" and that a passing test for one payload does not establish complete protection. A restriction on one interface does nothing for a path that reaches the service another way. Palo Alto's Threat IDs 510046 and 510047 for this flaw are called limited coverage by Palo Alto.
- **The control fails its re-test.** The finding returns to the row its other facts select, with no credit for the control.
- **The vendor never ships a fix.** Then the control becomes the stated mitigating factor in a dated exception, and the [residual risk after mitigation](https://remediationvsmitigation.com/guides/residual-risk-after-mitigation/) is what the approver signs for.

## Sources

- NIST SP 800-40 Rev. 4, Section 2.1: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf (read 19 Nov 2026)
- FedRAMP, VER-EVA-EIR and VER-TFR-MAV: https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/ (read 19 Nov 2026)
- FedRAMP, VDR-CSO-RES and VDR-TFR-KEV: https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/ (read 19 Nov 2026)
- OWASP, Virtual Patching Cheat Sheet: https://cheatsheetseries.owasp.org/cheatsheets/Virtual_Patching_Cheat_Sheet.html (read 19 Nov 2026)
- PCI SSC, FAQ 1046: https://www.pcisecuritystandards.org/faqs/1046 (read 19 Nov 2026)
- CISA, BOD 26-04, Appendix A, Publicly Exposed: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (read 19 Nov 2026)
- CISA, BOD 26-04 implementation guidance, alternative mitigation FAQ: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk (read 19 Nov 2026)
- Palo Alto Networks, CVE-2026-0322 advisory (fixed builds, mitigation, indicator addresses): https://security.paloaltonetworks.com/CVE-2026-0322 (read 19 Nov 2026)
- CISA, KEV JSON feed, catalog 2026.11.18, entry CVE-2026-0322: https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 19 Nov 2026)
- NVD record for CVE-2026-0322, including CISA SSVC entry: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-0322 (read 19 Nov 2026)

Last reviewed 19 Nov 2026

## Related

- [Decision Table: Remediate, Mitigate or Accept by Situation](https://remediationvsmitigation.com/decision-table/index.md)
- [KEV Entry, Patch Out, Internet-Exposed: 3 or 14 Days](https://remediationvsmitigation.com/decision-table/kev-patch-available-exposed/index.md)
- [WAF Rule as a Virtual Patch: Atlassian Case and Limits](https://remediationvsmitigation.com/compensating-controls/waf-rule/index.md)
- [Network Segmentation as a Mitigation: Cisco ISE Case](https://remediationvsmitigation.com/compensating-controls/network-segmentation/index.md)
- [When Virtual Patching Is Enough, and When It Is Not](https://remediationvsmitigation.com/guides/virtual-patching-and-when-it-is-enough/index.md)
- [How to Verify a Mitigation Works: Checks for 5 Real CVEs](https://remediationvsmitigation.com/guides/verifying-a-mitigation-works/index.md)
- [Residual Risk After Mitigation: Define, Estimate, Record](https://remediationvsmitigation.com/guides/residual-risk-after-mitigation/index.md)
