FedRAMP deviation requests

FedRAMP's legacy deviation request form covered false positives, risk adjustments and operational requirements, and FedRAMP would not approve an operational requirement for a high-risk vulnerability. The 2026 Rev5 rules, required for certification from 7 Dec 2026, use none of the three terms: a vulnerability not fixed within 192 days of evaluation is reported as accepted.

  1. RemediateCovered here
  2. Mitigate now, fix laterCovered here
  3. Accept with a dated exceptionCovered here

The three types in the legacy form

The form's own notice reads "23 Jun 2026" and calls it a legacy document "being replaced by the FedRAMP Consolidated Rules for 2026". FedRAMP's legacy documentation site marks every page reference only from 24 Jun 2026, the day the 2026 rules launched.

From the FedRAMP Vulnerability Deviation Request Form (legacy), read 19 Nov 2026.
TypeForm definitionLimit or evidence
False positive (FP)"A finding that incorrectly indicates a given condition exists when it does not.""It must be justified through documented explanation and evidence."
Risk adjustment (RA)"A reduction in the scanner-cited risk level of a finding." Done through compensating controls that reduce likelihood and impactRationale, evidence and CVSS environmental metrics
Operational requirement (OR)"A finding that cannot be remediated, often because the system will not function as intended.""FedRAMP will not approve an OR for a high-risk vulnerability"; the provider may request an RA with it
RA and OROne request can justify bothBoth sections completed

What the form asked for

One POA&M item per row, with a fixed set of fields: tool-provided description and recommended action, initial risk level, original detection date, requested risk level, "DR Rationale", "Evidence Description" and "List of Evidence Attachments". An operational requirement asks the provider to "Explain the limitations that prevent the vulnerability from being fixed. Include negative operational impacts of remediation." A Moderate vulnerability not reduced to Low needs an explanation of "why the authorizing official should accept the risk without mitigating it."

A risk adjustment is argued with the CVSS environmental metrics: attack vector, complexity, privileges, user interaction, and impact on confidentiality, integrity and availability, plus a remediation level ("Official fix", "Temporary fix", "Workaround" or "Unavailable"). Each metric needs a sentence on the control that changes it, such as a management network reachable only through a jump host.

Pending is not approved

The form says "FedRAMP adjudicates each DR individually". A provider may mark the matching POA&M item Pending after submitting, "while waiting for FedRAMP adjudication; however, they may only treat the vulnerability differently after FedRAMP approves the DR." Status values are Pending, Approved, Rejected and Withdrawn. The legacy POA&M playbook adds that "Approved ORs are still considered open risks" and must be reassessed periodically.

Vendor dependencies were handled beside the types. The form says a high-risk one "must be risk-adjusted to a lower risk rating and an RA DR must be submitted"; the playbook says VDs "are not considered deviation requests and do not require approval" and that high-risk VDs must be mitigated to a Moderate level within 30 days. Read them together: the DR is needed only for the risk adjustment, not for the dependency.

What the 2026 rules use instead

On 19 Nov 2026 the phrases "deviation request", "risk adjustment" and "operational requirement" had no match in FedRAMP's Vulnerability Detection and Response rules, Vulnerability Evaluation and Reporting rules or 2026 definitions, and neither rule page contains the word "approve". The provider evaluates, reports a state and does not wait for a decision. The pairing below is this site's reading, not a FedRAMP mapping.

Mapping drawn by this site from the 2026 rule pages, read 19 Nov 2026. The rules are required for Rev5 initial and ongoing certification from 7 Dec 2026; the grace period ends 7 Mar 2027.
Legacy type2026 mechanismRule
False positiveEvaluate for false positives (SHOULD)VER-EVA-EFP
Risk adjustmentPartial or full mitigation, with each reduction in the Potential Agency Impact N-rating reportedVDR-TFR-PVR, VER-RPT-VDT
Operational requirementAccepted vulnerability: not fully mitigated or remediated within 192 days of evaluation, with an explanationVER-TFR-MAV, VER-RPT-AVI
Vendor dependencyNo separate term found on 19 Nov 2026none

FedRAMP's definition of an accepted vulnerability (FRD-ACV) is "A vulnerability that the provider does not intend to fully mitigate or remediate, OR that has not or will not be fully mitigated or remediated within the maximum overdue period". What closes each state is on the exception register, and the longest periods are on maximum durations.

Worked example: an operational requirement under the 2026 rules

The provider, Class C certification and asset are invented for illustration. The CVE, the Apache advisory and the KEV dates are real. Apache announced CVE-2026-90436 on 6 Nov 2026: Axis 1.x through 1.4 is end of life, "we recommend you migrate to a different SOAP engine", and "The Apache Axis project does not expect to create an Axis 1.x release fixing this problem." CISA added it to the KEV catalog on 18 Nov 2026 with a due date of 21 Nov 2026. The legacy POA&M playbook describes the case as an OR where "a vendor explicitly indicated it does not intend to offer a fix".

Day counts from the Class C table in VDR-TFR-PVR and the 192-day rule in VER-TFR-MAV, read 19 Nov 2026. Dates counted from 19 Nov 2026.
DateEventRule and result
18 Nov 2026Scanner finds Axis 1.4 on the partner SOAP gatewayDetection time and source recorded (VER-RPT-VDT)
19 Nov 2026Evaluation complete: internet-reachable, likely exploitable (it is on the KEV list), exploitation assumed automatable, rated N4VER-EVA-EIR, VER-EVA-ELX, VER-EVA-AIA, VER-EVA-EPA
20 Nov 2026Gateway moved behind the partner VPN; no longer internet-reachable; re-rated N3Reduction reported with its time and rating (VER-RPT-VDT)
23 Nov 2026End of the Class C window for N4 with LEV and IRV (4 days from evaluation); the 20 Nov reduction came firstVDR-TFR-PVR (SHOULD partially mitigate, fully mitigate or remediate)
21 Dec 2026Class C window for N3 with LEV and NIRV is 32 days from evaluationVDR-TFR-PVR
30 May 2027192 days from evaluation: the last day before the item must be marked accepted if still openVER-TFR-MAV

Two outcomes follow. If the replacement SOAP engine goes live on 15 Mar 2027 (116 days after evaluation), the item is remediated and never becomes an accepted vulnerability; the monthly report carries its reductions and the estimated time of the next one. If cutover slips past 30 May 2027, or the provider decides earlier that it will not migrate, the item is accepted and reported with the record below. The old form would have asked FedRAMP to approve an OR and an RA together; now the provider writes the explanation itself and reports it.

Accepted vulnerability record (fields of VER-RPT-AVI, illustrative values)

  1. Tracking identifier: SOAP-GW-0412
  2. Time and source of detection: 18 Nov 2026, authenticated scan of the partner SOAP gateway
  3. Time of completed evaluation: 19 Nov 2026
  4. Internet-reachable: No, since 20 Nov 2026 (partner VPN only)
  5. Likely exploitable: Yes (CVE-2026-90436, KEV entry added 18 Nov 2026)
  6. Currently estimated Potential Agency Impact N-rating: N3
  7. Explanation of why this is an accepted vulnerability: Apache has said no Axis 1.x fix will be released; cutover to the replacement engine was not complete 192 days after evaluation (30 May 2027). Cutover now planned for 30 Sep 2027.
  8. Supplementary information: VPN-only access, WAF rule on the gateway, monitoring of the gateway's outbound connections, review on the first of each month.

The KEV catalog entry still asks for action by 21 Nov 2026, and VDR-TFR-KEV says providers SHOULD remediate KEVs by the catalog due dates "even if the vulnerability has been fully mitigated". Where the fix does not exist, the record above is where that gap is written down. The same gap in a POA&M is covered in the POA&M guide, and a scanner finding that is simply wrong goes through false positive handling.

Sources

Last reviewed