# Recording an exception an auditor accepts

Canonical: https://remediationvsmitigation.com/guides/recording-an-exception-an-auditor-accepts/

To document a risk acceptance, keep eight items together: finding, exposure, reason, verified controls, dated plan, residual risk, signature and expiry. FedRAMP's rule VER-RPT-AVI supplies the reporting behind the first three, and NIST SP 800-37 and SP 800-40 supply items 4, 5, 7 and 8. Item 6 is this site's grouping (read 19 Nov 2026).

## The eight items

1. **The finding with its identifiers.** FedRAMP VER-RPT-AVI wants the provider's "internally assigned tracking identifier" and the time and source of detection ([VER-RPT-AVI](https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/)). Add the CVE; the FedRAMP POA&M template gained a CVE column on 27 Jun 2022 ([template post](https://www.fedramp.gov/archive/2022-06-28-update-poam-template/)).
2. **Exposure and likelihood.** Whether the flaw is internet-reachable, whether it is likely exploitable, and whether it is on the KEV catalog. The 2026 rule asks the first two as plain yes or no questions.
3. **The reason, in plain words.** The same rule asks for an "Explanation of why this is an accepted vulnerability". The wording table below shows weak and strong versions.
4. **Each control, with proof.** Description, owner, how it was checked and when. SP 800-37 expects plans to hold "an accurate description of implemented controls, including compensating controls" ([Task R-2](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf)), and SP 800-40 Rev. 4 asks that "no one uninstalls the patch, deactivates the additional security controls" ([Section 2.2](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf)).
5. **A plan with dates.** Tasks, resources, milestones and "scheduled completion dates" ([Task A-6](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf)); the [plan of action and milestones guide](https://remediationvsmitigation.com/guides/poam-plan-of-action-and-milestones/) has a filled entry.
6. **Residual risk against tolerance.** One sentence on the level left, set against the tolerance the policy states. See [residual risk after mitigation](https://remediationvsmitigation.com/guides/residual-risk-after-mitigation/).
7. **The signature of the right role.** SP 800-37 says "The explicit acceptance of risk is the responsibility of the authorizing official and cannot be delegated to other officials within the organization" (Task R-4). For other organizations see [who may sign](https://remediationvsmitigation.com/risk-acceptance-form/who-may-sign/) and [the risk owner](https://remediationvsmitigation.com/guides/risk-owner/).
8. **An end date and a review rule.** The authorization decision conveys "the authorization termination date or time-driven authorization frequency" (Task R-4). SP 800-40 Rev. 4 adds that exceptions "should be reviewed regularly" (Section 3.5.5). What happens on the date is in [exception expiry and renewal](https://remediationvsmitigation.com/guides/exception-expiry-and-renewal/).

The [filled example form](https://remediationvsmitigation.com/risk-acceptance-form/example/) shows one finding on the form itself; this page gives the reasoning behind each item and what an assessor asks of it. The [Risk Acceptance Form](https://remediationvsmitigation.com/risk-acceptance-form/) has 15 fields: 13 asked of every finding, which cover these eight items, plus a vendor field and a PCI field where they apply.

## What an assessor asks of each item

Questions an assessor or reviewer can put to a risk acceptance record, with the published text each rests on, read 19 Nov 2026. PCI SSC states it cannot approve a compensating control itself (FAQ 1046).

| Assessor's question | Evidence that answers it | Text behind the question |
|---|---|---|
| Who decided, and could they? | A named role, a signature, a date | SP 800-37 Task R-4: acceptance "cannot be delegated" |
| Is the control working today? | Owner, verification method, verification date for each control | SP 800-40 Rev. 4 Section 2.2 step c: "ensure they are functioning as intended" |
| Is the control enough for this requirement? | What the control protects and which other controls it depends on | PCI SSC FAQ 1046: a QSA decides whether a compensating control "is sufficient to meet the intent of a requirement during their review of all other controls in place" |
| Is the time allowed justified? | A written risk analysis that sets the time frame | PCI SSC FAQ 1597: vulnerabilities below critical and high-risk are addressed "in accordance with the entity's risk as defined and documented in a targeted risk analysis" |
| Does the record end, and is it revisited? | An expiry date and a review log | SP 800-37 Task R-4 termination date; SP 800-40 Rev. 4 Section 3.5.5 regular review |
| Is it still open on the books? | A row in the register, not a closed ticket | FedRAMP legacy playbook: approved exceptions "must be captured on the POA&M's Open tab and periodically reassessed" |
| Could a reader reproduce the attack from it? | Preconditions and controls only | FedRAMP VER-RPT-NID: disclose "sufficient information for informed risk-based decision-making" but nothing that "would likely lead to exploitation" |

Keep request samples, payload text and step lists out of the record. Name the preconditions (reachable, authenticated, version) and the controls. The [exception register](https://remediationvsmitigation.com/exception-register/) shows the reassessment as row history.

## Reason field: weak and strong wording

Patterns for the reason field; bracketed items are placeholders to fill from your own records.

| Weak entry | Why it fails | Stronger entry (pattern) |
|---|---|---|
| "Too hard to patch." | States an opinion; names no constraint, date or alternative | "Vendor has not released a fix; vendor email dated [date] says planned for [quarter]; controls A and B hold until then." |
| "Low risk." | Gives no basis and no tolerance statement | "Not internet-reachable (basis: [drawing, date]); not on the KEV catalog (version [x]); impact Moderate on our scale; within the stated tolerance for internal services." |
| "Business critical." | Says why the asset matters, not why the finding is accepted | "Replacing the component before [date] stops [named business process]; replacement scheduled for [date] in the plan." |

## A record built on a real finding

CVE-2026-75604 is a path traversal in the incremental cache of Next.js on Windows-hosted servers. The GitHub CNA's CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, a base score of 9.0: no sign-in is needed, but attack complexity is high. Vercel released the fixes, Next.js 15.5.24 and 16.3.3, on 25 Aug 2026, and NVD published its record on 1 Sep 2026. The vendor states there is no known workaround and says to upgrade immediately if the server is on Windows. CISA's SSVC data in the NVD record shows exploitation as none, and the CVE is not in the KEV catalog (feed version 2026.11.18, read 19 Nov 2026). The estate, owners, controls and dates below are the example's own, and the record is signed on 19 Nov 2026.

Exception EXC-2026-044 (example organization, finding facts are real)

1. **Finding:** CVE-2026-75604, Vercel Next.js, path traversal in the incremental cache on Windows hosts. Not in the CISA KEV catalog (feed 2026.11.18). Two Windows Server hosts run the benefits portal on Next.js 15.5.21 (Pages Router). Vendor fix: 15.5.24 (GHSA-p293-qw3h-jr36).
2. **Exposure and likelihood:** The portal is reachable only from corporate subnets and the VPN (firewall rules and drawing dated 18 Nov 2026). Not internet-reachable. On the KEV catalog: no. Likely exploitable: only by someone already on the internal network, and the vendor rates attack complexity high.
3. **Reason:** The fix is a version bump that needs a rebuild, a redeploy and a regression test of the enrollment pages. The open-enrollment change freeze runs to 27 Nov 2026, and the first window after it is 28 Nov 2026. The vendor lists no workaround, so exposure is cut by network scope and detection.
4. **Controls:** (a) Inbound access to both hosts allowed only from the corporate subnets and the VPN range. Owner: Network operations lead. Verified 18 Nov 2026 by reading the rule list. (b) A web-log alert on any request path containing an encoded backslash (%5c), the example's own choice of traversal indicator. Owner: Security operations lead. Verified 18 Nov 2026 with a harmless test request.
5. **Plan:** Task 1, upgrade both hosts to Next.js 15.5.24 or later, rebuild and redeploy, from 28 Nov 2026 (Web platform lead; needs 4 hours). Task 2, if not done by 30 Nov 2026, decide between a second window and a renewed acceptance (Web platform lead).
6. **Residual risk:** Moderate on the organization's three-level scale while controls (a) and (b) hold; within the Moderate tolerance in policy section 4.
7. **Signature:** Director of Member Services (business owner of the benefits portal) and Head of Security (roles), signed 19 Nov 2026. Who signs at Moderate is on [who may sign](https://remediationvsmitigation.com/risk-acceptance-form/who-may-sign/). The Head of Web Platforms owns the plan in item 5 and does not sign: the team that carries out the fix is not the one that accepts the risk it leaves.
8. **End and review:** Expires 4 Dec 2026, 15 days after signing. The expiry sits four days past the 30 Nov decision point in item 5 so that a second window, 2 Dec 2026, would still be covered; the plan date is a checkpoint, and after 4 Dec the acceptance lapses unless it is signed again. Review 26 Nov 2026. Reopen at once if control (a) or (b) fails its check or the hosts gain a route from outside the corporate network. If CISA adds the CVE to the KEV catalog, the acceptance is not renewed: the signers end it and the upgrade moves to the earliest possible window.

Two limits apply. First, a KEV listing during an acceptance means escalate, not renew. Where a directive applies, the KEV date binds: BOD 26-04 covers federal civilian agency assets, and the directive text describes no acceptance procedure that moves a KEV timeline, so an agency takes the question to the directive's contact, CyberDirectives@cisa.dhs.gov, and does not rely on an internal record. An organization outside the directive uses the listing as the trigger in item 8: the signers end the acceptance and the fix moves up. [Exception expiry and renewal](https://remediationvsmitigation.com/guides/exception-expiry-and-renewal/) shows that case on a KEV-listed CVE. Second, the reason depends on facts that can change: if a route to the hosts appears from outside the corporate network, the reasoning in item 3 no longer holds, which is why item 8 lists the reopen conditions.

## Sources

- FedRAMP 2026, VER-RPT-AVI and VER-RPT-NID: https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/ (read 19 Nov 2026)
- FedRAMP, Update to the POA&M template, 27 Jun 2022: https://www.fedramp.gov/archive/2022-06-28-update-poam-template/ (read 19 Nov 2026)
- NIST SP 800-37 Rev. 2, Tasks R-2, R-4 and A-6: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf (read 19 Nov 2026)
- NIST SP 800-40 Rev. 4, Sections 2.2 and 3.5.5: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf (read 19 Nov 2026)
- PCI SSC FAQ 1046, approval of compensating controls: https://www.pcisecuritystandards.org/faqs/1046 (read 19 Nov 2026)
- PCI SSC FAQ 1597, resolving and addressing vulnerabilities: https://www.pcisecuritystandards.org/faqs/1597 (read 19 Nov 2026)
- FedRAMP legacy POA&M playbook (reference only since 24 Jun 2026): https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/ (read 19 Nov 2026)
- CISA KEV catalog JSON feed, catalogVersion 2026.11.18 (CVE-2026-75604 not listed): https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 19 Nov 2026)
- CISA BOD 26-04, scope and contact: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (read 19 Nov 2026)
- NVD record for CVE-2026-75604 (CVSS vector, SSVC exploitation entry): https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-75604 (read 19 Nov 2026)
- GitHub advisory GHSA-p293-qw3h-jr36 (affected range 13.4.0 up to 15.5.24 and 16.3.3; no known workaround): https://github.com/vercel/next.js/security/advisories/GHSA-p293-qw3h-jr36 (read 19 Nov 2026)
- Next.js 15.5.24 and 16.3.3 releases (both published 25 Aug 2026): https://api.github.com/repos/vercel/next.js/releases/tags/v15.5.24 (read 19 Nov 2026)

Last reviewed 19 Nov 2026

## Related

- [Risk Acceptance Form: Free Template With 15 Fields](https://remediationvsmitigation.com/risk-acceptance-form/index.md)
- [Risk Acceptance Form Example: Filled-In Worked Sample](https://remediationvsmitigation.com/risk-acceptance-form/example/index.md)
- [Exception Register: 15 Columns, States and Blank CSV](https://remediationvsmitigation.com/exception-register/index.md)
- [Who Can Accept Risk: Signer by Standard (2026)](https://remediationvsmitigation.com/risk-acceptance-form/who-may-sign/index.md)
- [POA&M Example: A Filled Plan of Action and Milestones Entry](https://remediationvsmitigation.com/guides/poam-plan-of-action-and-milestones/index.md)
- [Who Is the Risk Owner for a Security Finding?](https://remediationvsmitigation.com/guides/risk-owner/index.md)
- [Residual Risk After Mitigation: Define, Estimate, Record](https://remediationvsmitigation.com/guides/residual-risk-after-mitigation/index.md)
- [Risk Exception Expiry: What Happens and How to Renew](https://remediationvsmitigation.com/guides/exception-expiry-and-renewal/index.md)
