Every FedRAMP-certified cloud service now has three weeks to move off scan-and-score vulnerability management, and the ones that ignore the switch will lose their certification next spring. FedRAMP Notice NTC-0017, published Nov. 10, tells providers they must migrate to the program's Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER) rules by Dec. 7, 2026, or file corrective action plans that show how and when they will get there. The notice also announces a quarterly security inbox test in early December that FedRAMP will use to collect migration progress reports.

The stakes are spelled out plainly. "Any cloud service that has not fully migrated to the VDR/VER and is not operating under a FedRAMP-approved Corrective Action Plan on March 8, 2027, will have its FedRAMP Certification revoked and be banned from FedRAMP for one year," the notice states.

Why FedRAMP Tied the Dec. 7 Deadline to CISA BOD 26-04

The date did not originate with this notice. On June 10, 2026, the Cybersecurity and Infrastructure Security Agency released Binding Operational Directive 26-04, "Prioritizing Security Updates Based on Risk," which set a deadline for moving the federal government away from patch prioritization built on CVE identifiers, CVSS severity scores and 30-plus-day response windows. Six days later, FedRAMP published NTC-0014, which aligned the VDR and VER deadlines with the directive and required all FedRAMP Certified cloud service offerings to migrate by Dec. 7.

NTC-0017 says the pressure has only grown since June. FedRAMP wrote that the urgency behind the "aggressive deadline" has increased, "with the recent Black October hammering this threat home across the global infosec community." Federal News Network described Black October as last month's spate of AI-driven security incidents and vulnerability disclosures.

The notice acknowledges that the June deadline demanded heavy work from providers, especially those that built government-specific versions of their offerings around traditional federal vulnerability management. Those approaches, FedRAMP wrote, focused almost entirely on CVE and CVSS scores "while disallowing the consideration of context, reachability, risk, or mitigation."

What Changes Under the VDR and VER Rules?

According to Federal News Network, the new rules affect more than 550 FedRAMP-certified providers and replace legacy requirements that relied on monthly scans and vulnerability severity scores. Providers must instead shift to an exposure- and threat-based approach that weighs factors such as whether a vulnerability is "likely reachable" over the internet and how exploitable it is.

For many providers, that means new tools as well as new processes. "It’s just such a drastic change from the way that they were doing it before," Matt Bruggeman, director of GTM Federal at A-LIGN, told Federal News Network. Bruggeman said many providers already used third-party scanning tools, but a lot of those vendors cannot meet the new requirements, forcing providers to look for replacements.

FedRAMP frames the migration as the start of a longer run of changes. The notice says the VDR/VER move "is only the first of many migrations that cloud service providers will need to make over the coming years; yearly paperwork exercises are no longer appropriate or sufficient in this era of continuously evolving threats."

Advertisement

How the Grace Period and Revocation Timeline Work

FedRAMP confirmed that the grace period it had previously announced for all certified services runs through March 7, 2027, and added several conditions:

FedRAMP VDR/VER migration dates
  1. Dec. 7 migration deadline
  2. Likely emergency test response deadline
  3. Finish after this date means remediation
  4. Grace period ends
  5. Revocation and one-year ban
Key dates set in FedRAMP Notice NTC-0017. Source: FedRAMP. GovConFeed graphic.
  • Any cloud service not fully migrated on Dec. 7 must explain the corrective actions it will take for each rule, including target timelines.
  • Any service planning to finish after Feb. 3, 2027, goes into remediation. Its Marketplace entry will read "FedRAMP Certified (In Remediation)" until it notifies FedRAMP that the migration is complete.
  • On March 8, 2027, any service that has not fully migrated and has no FedRAMP-approved Corrective Action Plan loses its certification and is banned from the program for one year.

FedRAMP will also offer an extended conditional grace period case by case. A service that needs to finish after March 7 must have its Corrective Action Plan approved by FedRAMP and agree to a red team assessment coordinated by the program. FedRAMP said it will begin working with those services in February.

The notice pairs the threat with a promise of restraint: "FedRAMP will not take unnecessary administrative action against FedRAMP Certified cloud services that are working safely and in good faith to migrate to the VDR/VER rules." FedRAMP said it anticipates only providers that have refused entirely to participate to face this level of administrative action.

Advertisement

Services still working toward certification face their own rules. After Dec. 7, any cloud service that receives an agency authorization to operate must support a VDR/VER Migration Progress Report along with its application for a new FedRAMP Rev5 Certification. After March 7, 2027, FedRAMP will not begin reviewing such a service unless it has fully migrated first. Agency-provided offerings are exempt from the VDR/VER rules because they are already bound by BOD 26-04.

The December Security Inbox Emergency Test

FedRAMP will collect progress reports through a quarterly Security Inbox Emergency Test. The notice says the message will likely go out between Dec. 1 and Dec. 10, with responses likely due Dec. 17, 2026, at 2 p.m. Eastern Time through a web form.

Each report must include the implementation status of every applicable VDR/VER rule, delivered as a Mini-Security Decision Record (Mini-SDR) available in CSV and JSON versions, with a Corrective Action Plan for any required rule not yet implemented. Providers must also supply sample machine-readable and human-readable vulnerability activity reports, each with at least five example vulnerabilities of each type. The samples must use examples rather than real vulnerabilities that are currently likely exploitable or internet-reachable.

Failing to answer the test carries its own penalty. A service that does not respond goes into "FedRAMP Certified (In Remediation)" status on the Marketplace for at least 30 days, and FedRAMP will notify all of its agency customers. The provider then has 30 days to supply the missing information and a Corrective Action Plan. Providers that miss that deadline will have their certification revoked.

What It Means for Contractors

Cloud providers holding a FedRAMP certification should treat Dec. 7 as a reporting deadline and Feb. 3 as the practical cutoff for avoiding a public remediation flag on the Marketplace. Any provider that cannot finish by Feb. 3 should expect its agency customers to see the "In Remediation" label, which they may weigh when deciding whether to keep using the service. Teams should build the Mini-SDR now, using the templates and validation scripts on FedRAMP's VDR/VER Migration Resources site, and confirm that the security inbox is monitored so the December test does not go unanswered.

Providers whose scanning vendors cannot produce exposure- and reachability-based output should budget for replacement tooling before the grace period ends. Prime contractors and resellers that bundle FedRAMP cloud services into agency solutions should ask their cloud partners for migration status, since a revoked certification would ripple into any contract that depends on it.

Sources