Time Limits in the Vulnerability Rules, by Certification Class

This guide is based on the FedRAMP Consolidated Rules for 2026, version 2026.11.02.01, and the official schemas dated 2026-06-24. Rule identifiers are given in parentheses so you can check each statement.

These rules take effect on December 7, 2026, for obtaining and for keeping a certification. Providers have a grace period until March 7, 2027. Adoption has been optional since July 4, 2026. (VER info, VDR info)

How to read this guide

Each table row names the rule and its force word. MUST means required. SHOULD means recommended. MAY means optional. SHOULD NOT and MUST NOT are the negatives. The force word is stated in each row because it differs by class for some rules.

Classes are A, B, C and D. Many rules in the file have a separate wording per class under the heading “varies by class”. (VER-TFR-EVU, VDR-TFR-PVR)

Note on scope: the file’s description of the VER and VDR rule sets lists classes B, C and D as the classes they apply to, yet several rules carry a Class A wording. This guide reports the Class A wording as written. (VER info, VDR info)

1. Evaluation after detection

Evaluation means the three decisions in guide 1. The limit runs from detection. (VER-TFR-EVU)

Class Time limit Force
A 14 days (VER-TFR-EVU) SHOULD (VER-TFR-EVU)
B 7 days (VER-TFR-EVU) SHOULD (VER-TFR-EVU)
C 5 days (VER-TFR-EVU) SHOULD (VER-TFR-EVU)
D 2 days (VER-TFR-EVU) SHOULD (VER-TFR-EVU)

The rule applies to “ALL vulnerabilities”. (VER-TFR-EVU)

2. Mitigation and remediation by rating and category

Providers SHOULD partially mitigate, fully mitigate, or remediate a vulnerability to a lower N-rating within these times from evaluation. The time depends on the current N-rating, internet-reachability and likely exploitability. (VDR-TFR-PVR)

Terms: partially mitigated means the risk is reduced but still exists and the vulnerability is still detected. Fully mitigated means the likelihood or rating is reduced until negligible, but the vulnerability is still detected. Remediated means neutralized or eliminated and no longer detected. (FRD: Partially Mitigated Vulnerability, Fully Mitigated Vulnerability, Remediated Vulnerability)

The rule gives no timeframe for N1. N0 is not in the table. (VDR-TFR-PVR)

Class A (all rows SHOULD) (VDR-TFR-PVR)

Rating Internet-reachable and likely exploitable Not internet-reachable, likely exploitable Not likely exploitable
N1 none given none given none given
N2 96 days (VDR-TFR-PVR) 160 days (VDR-TFR-PVR) 192 days (VDR-TFR-PVR)
N3 32 days (VDR-TFR-PVR) 64 days (VDR-TFR-PVR) 192 days (VDR-TFR-PVR)
N4 8 days (VDR-TFR-PVR) 32 days (VDR-TFR-PVR) 64 days (VDR-TFR-PVR)
N5 4 days (VDR-TFR-PVR) 8 days (VDR-TFR-PVR) 32 days (VDR-TFR-PVR)

Class B (all rows SHOULD) (VDR-TFR-PVR)

Rating Internet-reachable and likely exploitable Not internet-reachable, likely exploitable Not likely exploitable
N1 none given none given none given
N2 96 days (VDR-TFR-PVR) 160 days (VDR-TFR-PVR) 192 days (VDR-TFR-PVR)
N3 32 days (VDR-TFR-PVR) 64 days (VDR-TFR-PVR) 192 days (VDR-TFR-PVR)
N4 8 days (VDR-TFR-PVR) 32 days (VDR-TFR-PVR) 64 days (VDR-TFR-PVR)
N5 4 days (VDR-TFR-PVR) 8 days (VDR-TFR-PVR) 32 days (VDR-TFR-PVR)

Class C (all rows SHOULD) (VDR-TFR-PVR)

Rating Internet-reachable and likely exploitable Not internet-reachable, likely exploitable Not likely exploitable
N1 none given none given none given
N2 48 days (VDR-TFR-PVR) 128 days (VDR-TFR-PVR) 192 days (VDR-TFR-PVR)
N3 16 days (VDR-TFR-PVR) 32 days (VDR-TFR-PVR) 128 days (VDR-TFR-PVR)
N4 4 days (VDR-TFR-PVR) 8 days (VDR-TFR-PVR) 64 days (VDR-TFR-PVR)
N5 2 days (VDR-TFR-PVR) 4 days (VDR-TFR-PVR) 16 days (VDR-TFR-PVR)

Class D (all rows SHOULD) (VDR-TFR-PVR)

Rating Internet-reachable and likely exploitable Not internet-reachable, likely exploitable Not likely exploitable
N1 none given none given none given
N2 24 days (VDR-TFR-PVR) 96 days (VDR-TFR-PVR) 192 days (VDR-TFR-PVR)
N3 8 days (VDR-TFR-PVR) 16 days (VDR-TFR-PVR) 64 days (VDR-TFR-PVR)
N4 2 days (VDR-TFR-PVR) 8 days (VDR-TFR-PVR) 32 days (VDR-TFR-PVR)
N5 12 hours (VDR-TFR-PVR) 1 day (VDR-TFR-PVR) 8 days (VDR-TFR-PVR)

The Class D statement uses the words “maximum timeframes”. The other classes say “timeframes”. (VDR-TFR-PVR)

Remaining vulnerabilities: providers SHOULD mitigate or remediate them during routine operations as the provider determines necessary. (VDR-TFR-RMN)

If full mitigation or remediation is not possible, providers SHOULD partially mitigate “promptly, progressively, and persistently”. (VDR-CSO-RES, note)

3. The 192-day accepted-vulnerability rule

Providers MUST categorize any vulnerability that is not or will not be fully mitigated or remediated within 192 days of evaluation as an accepted vulnerability. (VER-TFR-MAV)

This applies to all classes with no variation. (VER-TFR-MAV)

An accepted vulnerability is one the provider does not intend to fully mitigate or remediate, or one not fully mitigated or remediated within the maximum overdue period. (FRD: Accepted Vulnerability)

An overdue vulnerability is one the provider intends to fully mitigate or remediate but has not or will not within the recommended or required times. (FRD: Overdue Vulnerability)

The vulnerability detail schema says the 192-day clock “runs from” the evaluation-completed time. (schema: evaluationCompletedAt)

Accepted vulnerabilities are reported with the fields in guide 3. (VER-RPT-AVI)

4. When a vulnerability is treated as a reportable incident

A FedRAMP Reportable Incident is an incident that affects, or is likely to affect, the confidentiality or integrity of federal customer data. (FRD: FedRAMP Reportable Incident)

Two rules say when a vulnerability may or should be treated as one. In both, the treatment lasts until the vulnerability is a partially mitigated vulnerability at or below a stated rating. (VER-TFR-IRI, VER-TFR-NRI)

Case Class A Class B Class C Class D
Internet-reachable and likely exploitable, N-rating above 3: treat as reportable incident until partially mitigated at N3 or below MAY (VER-TFR-IRI) MAY (VER-TFR-IRI) SHOULD (VER-TFR-IRI) SHOULD (VER-TFR-IRI)
Likely exploitable, NOT internet-reachable, N-rating equal to 5: treat as reportable incident until partially mitigated at N4 or below MAY (VER-TFR-NRI) MAY (VER-TFR-NRI) MAY (VER-TFR-NRI) SHOULD (VER-TFR-NRI)

5. Known exploited vulnerabilities (KEVs)

A KEV is any vulnerability in CISA’s Known Exploited Vulnerabilities catalog, as defined in CISA BOD 26-04. (FRD: Known Exploited Vulnerability (KEV))

Requirement Force
Remediate KEVs by the due dates in the CISA catalog, even if fully mitigated, as required by BOD 26-04 or successor guidance (VDR-TFR-KEV) SHOULD (VDR-TFR-KEV)
Do not deploy or activate new machine-based information resources with KEVs (VDR-CSO-AKE) SHOULD NOT (VDR-CSO-AKE)

6. Detection and verification frequencies

Detection must be “persistent”. Persistent means repeating in cycles. It does not mean continuous or on a fixed schedule. (FRD: Persistently)

Providers SHOULD persistently run vulnerability detection at least this often. (VDR-TFR-PDD, VDR-TFR-PCD, VDR-TFR-PSD)

Resources Class A Class B Class C Class D
Likely to drift every 3 months (VDR-TFR-PDD) every month (VDR-TFR-PDD) every 14 days (VDR-TFR-PDD) every 7 days (VDR-TFR-PDD)
NOT likely to drift every 6 months (VDR-TFR-PCD) every 6 months (VDR-TFR-PCD) every month (VDR-TFR-PCD) every month (VDR-TFR-PCD)
Representative samples of similar machine-based resources every 14 days (VDR-TFR-PSD) every 7 days (VDR-TFR-PSD) every 3 days (VDR-TFR-PSD) once per day (VDR-TFR-PSD)

All cells in that table are SHOULD. (VDR-TFR-PDD, VDR-TFR-PCD, VDR-TFR-PSD)

Verification and validation of status:

Resources Class A Class B Class C Class D
Non-machine-based, all classes at least every 3 months, MUST (VDR-TFR-NMV) same same same
Machine-based, 20x offerings every month, SHOULD (VDR-TFR-MVX) every 7 days, MUST (VDR-TFR-MVX) every 3 days, MUST (VDR-TFR-MVX) no rule in the file
Machine-based, Rev5 offerings no rule in the file every month, SHOULD (VDR-TFR-MVF) every month, MUST (VDR-TFR-MVF) every month, MUST (VDR-TFR-MVF)

The two machine-based rows apply by offering type (20x or Rev5), not to all providers. (VDR-TFR-MVX, VDR-TFR-MVF)

7. The monthly report and the historical JSON

Requirement Class Force
Report detection and response activity to all necessary parties, in a consistent human-readable format, at least monthly (VER-TFR-MHR) all MUST (VER-TFR-MHR)
Report persistently, summarizing all activity since the previous report (VER-RPT-PER) all MUST (VER-RPT-PER)
Make recent historical activity available in JSON for automated retrieval; update at least every month (VER-TFR-MRH) A MAY (VER-TFR-MRH)
Same, update at least every month (VER-TFR-MRH) B SHOULD (VER-TFR-MRH)
Same, update at least every 14 days (VER-TFR-MRH) C SHOULD (VER-TFR-MRH)
Same, update at least every 7 days (VER-TFR-MRH) D SHOULD (VER-TFR-MRH)

“All necessary parties” always includes FedRAMP and every agency customer using the offering. It may include others. (FRD: All Necessary Parties)

For Classes B, C and D, the artifact is either the URL and access instructions for the JSON, or an explanation of why machine-readable content is not provided. For Class A it is the URL and access instructions. (VER-TFR-MRH)

The JSON format is in guide 3. (VER-TFR-MRH)

Open points in the sources

  • The rules give no timeframe for N1 and no N0 row. (VDR-TFR-PVR)
  • The rules do not say how evaluation, mitigation and acceptance times combine when they overlap. Each is stated separately. (VER-TFR-EVU, VDR-TFR-PVR, VER-TFR-MAV)