# FedRAMP Patch Management Policy Template

Canonical: https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/
Last reviewed: 19 Nov 2026

## FedRAMP patch management policy

FedRAMP's Vulnerability Detection and Response rules become mandatory for initial and ongoing certification on 7 December 2026, with a grace period to 7 March 2027. Timeframes run from 12 hours to 192 days by class, and the older 30, 90 and 180 day text sits in the legacy playbook.

### Timeframes in the 2026 rules

The Consolidated Rules for 2026 launched on 24 June 2026, with control mappings updated on 13 October 2026. Rule VDR-TFR-PVR says providers SHOULD partially mitigate, fully mitigate or remediate vulnerabilities to a lower potential agency impact within timeframes from evaluation. The table gives the maximum days read on the Rev5 page on 19 Nov 2026 for the four Potential Agency Impact levels. The page does not expand its column abbreviations; the labels below read them from the factors the rule names, internet reachability and likely exploitability. The 20x per-class tables were not compared line by line.

| Class | Vulnerability condition | N5 | N4 | N3 | N2 |
|---|---|---|---|---|---|
| A and B | Likely exploitable, internet-reachable (LEV + IRV) | 4 | 8 | 32 | 96 |
| A and B | Likely exploitable, not internet-reachable (LEV + NIRV) | 8 | 32 | 64 | 160 |
| A and B | Not likely exploitable (NLEV) | 32 | 64 | 192 | 192 |
| C | Likely exploitable, internet-reachable (LEV + IRV) | 2 | 4 | 16 | 48 |
| C | Likely exploitable, not internet-reachable (LEV + NIRV) | 4 | 8 | 32 | 128 |
| C | Not likely exploitable (NLEV) | 16 | 64 | 128 | 192 |
| D | Likely exploitable, internet-reachable (LEV + IRV) | 12 hours | 2 | 8 | 24 |
| D | Likely exploitable, not internet-reachable (LEV + NIRV) | 1 | 8 | 16 | 96 |
| D | Not likely exploitable (NLEV) | 8 | 32 | 64 | 192 |

Maximum days (class D N5 in hours) from evaluation, SHOULD wording. Source: FedRAMP Rev5 VDR rules page, read 19 Nov 2026. Class D is the only row that uses hours.

Two further rules matter for drafting. VDR-TFR-KEV: providers SHOULD remediate Known Exploited Vulnerabilities according to the CISA catalog due dates, as required by BOD 26-04 or any successor guidance. VDR-TFR-RMN: providers SHOULD mitigate or remediate remaining vulnerabilities during routine operations as the provider determines necessary, which leaves timing to the provider.

### Dates and the older text

The 20x page shows the status as Required, mandated by BOD 26-04: optional adoption from 4 July 2026, initial and ongoing certification from 7 December 2026, grace period ending 7 March 2027 ([20x rules](https://www.fedramp.gov/2026/providers/20x/rules/vulnerability-detection-and-response/)). Notice NTC-0014 of 16 June 2026 gives the same dates. BOD 26-04 itself, issued 10 June 2026, revoked BOD 19-02 and BOD 22-01.

The legacy playbook, in the legacy section of the site, states that critical and high risks are remediated within 30 days of discovery, moderate within 90 and low within 180, and that high-risk items must be mitigated to a moderate level through compensating controls within 30 days. That text is attributed to this legacy page only; the Continuous Monitoring Strategy Guide was not opened by name, and the 2026 VDR page does not mention 30, 90 or 180 days.

### The template

```text
## FedRAMP variant: paste over the same-numbered sections of the general policy

## 1. Purpose and scope

1.1 This policy applies to the cloud service offering [name], FedRAMP [Rev5 / 20x] certification class [A / B / C / D], and to all supporting systems in its authorization boundary.
1.2 Legacy authorizations: until [date] the legacy remediation requirements apply to POA&M items; from the mandatory date the Vulnerability Detection and Response (VDR) rules apply.

## 4. Severity and patch windows

4.1 Timeframes are maximums measured from evaluation of the vulnerability, by the Potential Agency Impact level (N5, N4, N3, N2) and the vulnerability's internet reachability and likelihood of exploitation. They are copied from the FedRAMP rules page dated [read date] into Appendix 1 and re-read at each review.
4.2 Known Exploited Vulnerabilities are remediated by the due date shown for the entry in the CISA catalog, as required by BOD 26-04 or any successor guidance.
4.3 Other vulnerabilities are mitigated or remediated during routine operations as the provider determines necessary, within the company standard of the general policy (class 4: 90 days; class 5: 180 days).
4.4 Where the SHOULD wording of a rule is not followed, the provider records the reason and the alternative (Annex A).

## 8. Reporting and metrics

8.1 Reports show, for each class and impact level, the vulnerabilities evaluated, the timeframe applicable, the date mitigated or remediated, and any past timeframe.
8.2 Legacy: POA&M items show scheduled completion against 30 days (critical and high), 90 days (moderate), 180 days (low), from discovery.

```

### Using it

Keep Appendix 1 as a dated copy of the live rules page; the rules are SHOULD statements and may change. For the cross-framework picture see the [FedRAMP row of the patch window table](https://patchmanagementpolicy.com/patch-windows/fedramp/) and the [BOD 26-04 page](https://patchmanagementpolicy.com/patch-windows/cisa-bod-26-04/). The [general policy](https://patchmanagementpolicy.com/templates/patch-management-policy-template/) supplies the remaining sections.

### Sources

- [FedRAMP, Consolidated Rules for 2026, Rev5, Vulnerability Detection and Response](https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/), read 19 Nov 2026
- [FedRAMP, Consolidated Rules for 2026, 20x, Vulnerability Detection and Response](https://www.fedramp.gov/2026/providers/20x/rules/vulnerability-detection-and-response/), read 19 Nov 2026
- [FedRAMP, legacy Rev5 playbook, POA&M, Remediation Requirements](https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/), read 19 Nov 2026
- [FedRAMP, notice NTC-0014 (16 June 2026)](https://www.fedramp.gov/notices/0014/), read 19 Nov 2026
- [CISA, BOD 26-04, Prioritizing Security Updates Based on Risk (10 June 2026), Required Action 6 and Table 1](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk), read 19 Nov 2026
- [CISA, Known Exploited Vulnerabilities Catalog page](https://www.cisa.gov/known-exploited-vulnerabilities-catalog), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [FedRAMP 2026 Patch Timeframes: 12 Hours to 192 Days](https://patchmanagementpolicy.com/patch-windows/fedramp/)
- [CISA BOD 26-04 Remediation Timelines, Row by Row](https://patchmanagementpolicy.com/patch-windows/cisa-bod-26-04/)
- [General Patch Management Policy Template, Full Text](https://patchmanagementpolicy.com/templates/patch-management-policy-template/)
- [Patch Management Compliance Dates: 7 Dec 2026 and Back](https://patchmanagementpolicy.com/dates-to-know/)
