,

FedRAMP VDR/VER Migration: What Certified Providers Need to Do Before December 17

November 16, 2026 | By Kylie Hunter
FedRAMP VDR/VER

If your team hasn’t dug into FedRAMP’s new Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER) rules yet, now is the time. In Notice NTC-0017, published November 10, FedRAMP confirmed that every FedRAMP Certified cloud service has to report its migration progress. The vehicle is a Security Inbox Emergency Test expected in early December, with responses likely due December 17.

I want to walk through what the notice says and what’s at stake. More than that, I want to share how I think teams should approach it, because there’s no silver bullet here.

How we got here     

This traces back to CISA. In June, CISA issued Binding Operational Directive 26-04, which moves the federal government away from CVE/CVSS score-based prioritization and its 30+ day response windows, and toward patching based on actual risk. The thinking is that attackers, increasingly using AI, are shrinking the gap between a patch release and exploitation.

FedRAMP followed on June 16 with NTC-0014, aligning the VDR and VER rules with that directive and setting December 7, 2026 as the date every FedRAMP Certified service must be migrated. NTC-0017 adds that the threat has only intensified since, pointing to the recent Black October events, and frames this as the first of several migrations to expect as yearly paperwork gives way to automated, continuous assurance.

The dates that matter

Date

What happens

Dec 1 to 10, 2026

Likely window for FedRAMP to send the FY27 Q1 Emergency Test to the Security Inbox

Dec 7, 2026

Deadline to be fully migrated to VDR/VER

Dec 17, 2026, 2pm ET

Likely deadline to respond to the Emergency Test

Feb 3, 2027

Plan to finish after this date and the service moves to “FedRAMP Certified (In Remediation)” on the Marketplace

Mar 7, 2027

Grace period ends

Mar 8, 2027

No full migration and no approved Corrective Action Plan means revoked certification and a one-year FedRAMP ban

The December dates are described as likely, not final. FedRAMP says it will publish exact details on its FY27 Q1 Emergency Test page.

What FedRAMP is asking for

The progress report goes in through a web form and has three parts:

  1. A VDR/VER Mini-Security Decision Record (Mini-SDR): the implementation status of each applicable rule, with a short explanation. Anything required but not yet implemented needs its own Corrective Action Plan (CAP) and timeline.
  2. A machine-readable sample report of the kind required by VER-RPT-PER (Persistent Reporting).
  3. A human-readable sample report of the kind required by VER-TFR-MHR (Monthly Activity Report).

Both sample reports need at least 5 vulnerabilities of each type, and they have to use example data, not real vulnerabilities that are currently likely exploitable or internet reachable. FedRAMP has published CSV and JSON versions of the Mini-SDR, with examples and validation scripts, on its VDR/VER Migration Resources site. Requirements could still change until the test goes out, so keep an eye on it.

What’s at stake, and what isn’t   

FedRAMP isn’t out to yank certifications. If you can say you have a plan and you can execute on it before February 3, 2027, you won’t be put into public remediation at all.

Where providers get into trouble is by not responding at all. A certified service that doesn’t respond to the Emergency Test goes into “FedRAMP Certified (In Remediation)” on the Marketplace for at least 30 days, with a public note that it failed an emergency test, and all agency customers are notified. The provider then has 30 days to submit the required information and a CAP, and to pass a follow-up Security Inbox test. Miss that window and the certification is revoked.

The migration deadlines follow the same pattern. If you’re not fully migrated by December 7, you explain your corrective actions and timelines for each rule. If you plan to finish after February 3, you go into remediation. And if you have neither a full migration nor an approved CAP by March 8, 2027, you lose certification and are barred from FedRAMP for a year.

There’s also room to work with FedRAMP past March 7. It will consider an extended conditional grace period case by case, with an approved CAP and agreement to a red team assessment coordinated by FedRAMP, and those conversations begin in February. Only providers that refuse to participate at all are expected to face the harshest outcomes.

Who else is affected  
  • Services with an agency ATO, pursuing Rev5 certification. After December 7, an application for a new Rev5 Certification must include a VDR/VER Migration Progress Report. A service that hasn’t fully migrated can still qualify for a short-term certification with conditions if FedRAMP approves its CAP. After March 7, 2027, FedRAMP won’t start a review unless the service has fully migrated first. 
  • Agency-provided offerings. Offerings listed under By Government, For Government on the Marketplace are exempt from VDR/VER. They’re already bound by BOD 26-04 and are expected to move to a forthcoming FedRAMP A-130 Class G Certification, with more detail coming in a notice on the outcome of RFC-0032. 
There is no silver bullet   

No single tool gets you through VDR/VER. There are some really good tools out there, and the right ones, combined with thoughtful processes and planning, can make implementation much easier. But they’re still tools, and what you get out of them depends on how you leverage them. A good platform dropped into a program with no plan behind it mostly just produces more data.

It’s a people problem first   

The teams having the hardest time aren’t necessarily the ones with the weakest tooling, they’re the ones where engineers, security researchers, infrastructure teams, and compliance all sit in separate places. Each group holds a piece of what these rules ask for and nobody owns the whole picture, so detection, evaluation, remediation and reporting end up in different systems, and the time between those hand-offs is where deadlines slip away.

That orchestration is hard, and the only real way through it is to bring the right people to the table to problem-solve around these rules together. With the holidays coming up, that gets harder every week, so it’s worth starting before the test lands.

Where I think this should go

December is the near-term goal, but I keep thinking about what a good end state looks like. It’s not where most programs are today, so I’d treat it as a direction more than a checklist. A few principles I’d build toward:

  • Work with the scanners you already have. Most programs are a patchwork: one tool knows what’s internet reachable, another knows what’s exploitable, a third only knows a severity. Take what each source knows, fill in the blanks as best you can, and label what was inferred rather than known.
  • Trust systems of record over spreadsheets. Cloud provider data and tags, your CMDB, and your asset management platforms stay current without someone remembering to update them. A spreadsheet doesn’t.
  • Decide once, apply everywhere. If you’re making the same call twice, it should become a standing rule, so a new asset doesn’t mean new manual effort.
  • Machines propose, humans confirm. An estimate isn’t an evaluation. Someone accountable should stand behind what goes to an agency.
  • Leave a trail. Every rating and decision should say who or what made it, on what signal, and when. That record is what an assessor reads.
  • Fail safe, never fail silent. When something is unknown, assume the conservative answer, and show exactly what’s unknown and what resolving it would be worth.
  • Explain any rating in a sentence, including what would change it.

Do that classification work once and it should pay off well beyond FedRAMP, across the other frameworks you answer to.

What I’d do between now and December 17

Beyond the obvious housekeeping, I’d focus on a few things:

  • Get engineering, security, network and compliance in the same conversation this month, before holiday calendars fill up.
  • Be honest about where you stand on each applicable rule, draft the Mini-SDR, and write a rule-level CAP for any gap. A credible plan is what keeps you out of public remediation.
  • Decide early whether you can finish by February 3. If not, start the conversation with FedRAMP about a CAP.
  • Make sure the Emergency Test can’t get lost in a shared mailbox, and that someone owns the response with an internal deadline ahead of December 17, 2pm ET.
The bottom line

December 7 is the migration deadline, December 17 is the likely reporting deadline, and March 8 is where certification is on the line. What FedRAMP wants to see in between is a credible plan and the follow-through, not a perfect program overnight. The teams that do well will be the ones that treated this as a cross-team problem early, used their tools with intention, and didn’t let the Emergency Test sit unread in an inbox over the holidays.

To find out how RegScale innovation can help your company’s GRC function, book a demo today.  

Ready to get started?

Choose the path that is right for you!

Skip the line

My organization doesn’t have GRC tools yet and I am ready to start automating my compliance with continuous monitoring pipelines now.

Supercharge

My organization already has legacy compliance software, but I want to automate many of the manual processes that feed it.