FedRAMP's Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER) rules become mandatory on December 7, 2026, for every cloud service offering that obtains or keeps a FedRAMP certification, under both Rev5 and 20x. A grace period runs to March 7, 2027; after that, offerings that do not follow the rules lose certification. These dates come from FedRAMP notice NTC-0014 and are current as of October 2026.
What FedRAMP announced
FedRAMP published notice NTC-0014 on June 16, 2026, as its response to CISA's BOD 26-04, issued on June 10, 2026. The notice says the monthly vulnerability scanning that most Rev5 services still rely on does not give agencies the assurance BOD 26-04 requires.
The notice moves the VDR and VER start date to December 7, 2026. The earlier plan was June 1, 2027, with a grace period to January 1, 2028. The December date matches the day agencies must start evaluating and remediating on BOD 26-04 timelines. For the directive itself and its deadlines, see our BOD 26-04 explainer.
Key dates
- June 10, 2026: CISA issues BOD 26-04.
- June 16, 2026: FedRAMP publishes NTC-0014.
- December 7, 2026: VDR and VER are mandatory; agencies begin evaluating and remediating on BOD timelines.
- March 7, 2027: the grace period ends. Until then an offering can keep its certification under a corrective action plan, and agencies are notified. After it, certification is revoked for offerings that do not follow the rules.
What the rules require
Evaluation (VER)
Providers must assess each vulnerability, not just score it:
- whether it is likely to be reachable from the internet (rule VER-EVA-EIR);
- whether it is likely to be exploitable (VER-EVA-ELX);
- any additional factors that change the risk (VER-EVA-EFA);
- exploits are assumed to be automatable unless evidence shows otherwise (VER-EVA-AIA).
The last point shifts the burden of proof. A provider that wants a vulnerability treated as less urgent has to document why it is not automatable.
Response (VDR)
Known Exploited Vulnerabilities (KEV) must be remediated on the BOD 26-04 timelines unless there is a valid technical reason not to (VDR-TFR-KEV). Providers must also keep mitigating and remediating over time (VDR-CSO-RES).
FedRAMP allows mitigation instead of a full fix: a provider may mitigate a vulnerability until it is no longer automatable or no longer internet-reachable. The notice also says the deadlines are maximums and that providers should mitigate and remediate much faster.
Checklist for providers and assessors
- Inventory which components are internet-reachable, and keep that record current. Reachability drives priority.
- Match your scanner output against the KEV catalog daily, not monthly. Our guides to EPSS and CVSS 4.0 help with the scoring side.
- Write down a decision for each finding: reachable or not, exploitable or not, and the evidence behind a "not automatable" claim.
- Define who can approve a technical exception to a KEV deadline, and what evidence they need.
- Check your current reporting against FedRAMP's Certification Data Sharing rules. The notice says providers not yet following them will receive more reporting guidance.
- Ask your third-party assessment organization (3PAO) how it will review the new evaluation records, so the first assessment after December 7 holds no surprises.
- If you cannot comply by December 7, plan the corrective action before then, with March 7, 2027 as the hard stop.
The notice said minor rule changes were possible and that the notice would be updated once the final 2026 Consolidated Rules were issued, so check the notice page for the current text. More background is in our cloud and vulnerabilities sections.
Frequently asked questions
When do FedRAMP VDR and VER become mandatory?
On December 7, 2026, for all offerings obtaining or maintaining FedRAMP certification, according to notice NTC-0014.
What happens after March 7, 2027?
The grace period under a corrective action plan ends, and certification is revoked for offerings that do not follow the rules.
Does monthly vulnerability scanning still satisfy FedRAMP?
FedRAMP states that legacy monthly scanning is insufficient for the assurance agencies need under BOD 26-04.
Do I have to fully patch every vulnerability?
Not always. Providers may mitigate a vulnerability until it is no longer automatable or internet-reachable, but KEV items follow BOD 26-04 timelines unless a valid technical reason applies.