FedRAMP's new vulnerability rules start December 7.
We read FedRAMP's machine-readable Consolidated Rules, release 2026.11.02.01. Two rulesets reach Rev5 providers three and a half weeks before the January 1 wave, and they retire the provider POA&M.
- FedRAMP's VDR and VER rules take effect for Rev5 and 20x providers on December 7, 2026. A provider that misses it needs a corrective action plan; the grace period ends March 7, 2027.
- The provider POA&M goes away. Each finding gets an impact rating from N0 to N5, and anything not fully mitigated or remediated within 192 days of evaluation becomes an accepted vulnerability.
- Agencies keep their own POA&Ms. ISSOs should ask each provider about its December 7 status and decide how its monthly vulnerability report feeds the agency record.
On December 7, 2026, two FedRAMP rulesets become the standard for every certified cloud service offering, Rev5 and 20x alike. They are Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER). They arrive three and a half weeks before January 1, 2027, when most of the 2026 rules become mandatory. They also end the provider-side POA&M.
What the rules file says
FedRAMP publishes its Consolidated Rules for 2026 as a JSON file on GitHub, and the repository README calls it “the canonical rules dataset.” We read release 2026.11.02.01, dated November 2, and pulled the effective dates for the 15 rulesets on FedRAMP’s Rev5 deadline list. Three already apply. Ten reach their date for new certifications on January 1, 2027. Two reach it on December 7, 2026, and both carry the same status line: “Mandated by CISA BOD 26-04.” Both list 20x and Rev5 in their applicability.
The dates mean different things for different providers, and FedRAMP’s Rev5 deadlines page defines them. An offering that applies for certification after December 7 must adopt the rulesets “or FedRAMP Certification will be denied.” For an offering already certified, adoption by December 7 is expected, and a provider that misses it needs “a corrective action plan to adopt the ruleset by the end of the grace period.” For VDR and VER, the grace period ends March 7, 2027. After that, the page says, “FedRAMP Certification will be revoked.”
The provider POA&M is gone
FedRAMP’s own summary of the 2026 changes says: “Plans of Action & Milestones (POA&Ms) have been eliminated entirely and replaced with a list of Accepted Weaknesses.” The rules call these accepted vulnerabilities, and they set out how a finding becomes one.
Every detected vulnerability gets evaluated. The provider decides whether it is likely exploitable and whether it is internet-reachable, then assigns a Potential Agency Impact N-rating (PAIN) from N0 to N5. At the top, N5 means exploitation “could be expected to have a debilitating customer effect on more than one agency.” Providers “MUST assume the exploitation of vulnerabilities can be automated UNLESS they have evidence proving otherwise.” Anything not fully mitigated or remediated within 192 days of evaluation must be categorized as accepted, and accepted vulnerabilities are reported with an explanation of why.
Detection is also wider than a monthly scan. The detection rule names assessment, threat intelligence, vulnerability disclosure mechanisms, bug bounties and penetration testing, among others. One rule points the process at itself: providers “MUST treat problems or failures with their vulnerability detection and response processes as vulnerabilities.”
The clocks, for a Class C offering
Timeframes vary by certification class. We use Class C here, which FedRAMP describes as adequate “for use in most Low or Moderate impact agency information systems,” though it also warns agencies not to treat classes as one-for-one replacements for impact levels. A Class C provider should evaluate each vulnerability within 5 days of detection. The clock in the table below starts at evaluation, and the target is a lower rating. The rule asks providers to mitigate or remediate “to a lower Potential Agency Impact N-rating” within each window, which is a different target from closing the finding.
Class C timeframes to lower a vulnerability’s rating, in days from evaluation
| Rating | Reachable, exploitable | Not reachable, exploitable | Not likely exploitable |
|---|---|---|---|
| N5 | 2 | 4 | 16 |
| N4 | 4 | 8 | 64 |
| N3 | 16 | 32 | 128 |
| N2 | 48 | 128 | 192 |
“Reachable” means internet-reachable. Rule VDR-TFR-PVR, Class C variant, release 2026.11.02.01. N1 and N0 carry no timeframe. These are SHOULD timeframes.
Of the 36 VDR and VER statements that apply to a Rev5 Class C provider, 15 are MUST or MUST NOT. They include monthly verification of machine-based resources, a report to all necessary parties in a format “that is human readable at least monthly,” and a fixed list of fields for each open and each accepted vulnerability. Class C providers should also publish their vulnerability history in JSON, refreshed at least every 14 days.
What agency ISSOs and program offices can do this month
FedRAMP says agencies “must still perform Continuous Monitoring following the requirements in Circular A-130.” The provider’s POA&M goes away. The agency’s stays. VER tells agencies they should use provider-reported vulnerability information “to maintain Plans of Action and Milestones for agency security programs when relevant.” Our reading of what that means before December 7:
- Ask each provider where it stands. For every FedRAMP offering your systems inherit from, find out whether it will adopt VDR and VER by December 7 or work under a corrective action plan until March 7. Record the answer in the system’s continuous monitoring file.
- Decide how provider findings reach your POA&M. An accepted vulnerability with an N4 rating in a service you inherit from is your risk too. Write down which ratings trigger an agency POA&M entry and who signs off.
- Plan to read JSON. VER says agencies should “use automated processing and filtering of machine readable information from cloud service providers.” A monthly report read by hand will not keep up once several providers send them.
- Trace it to your controls. The current release maps the VDR and VER rules to 32 SP 800-53 controls and enhancements, among them RA-5, SI-2 and CA-8. That mapping is a starting point for updating inherited-control statements in your SSP.
- Check the contract language. Task orders and service agreements that require a provider’s monthly scan files and POA&M may name deliverables the provider will stop producing. Capture and contracts staff should read them now.
The January wave behind it
December 7 is the first of several Rev5 dates. Ten more rulesets, including Significant Change Notification, Incident Evaluation and Communication and Cryptographic Module Use, reach their date for new certifications on January 1, 2027. FedRAMP’s timeline says it will stop accepting new Rev5 applications on June 11, 2027. Its summary of the changes says existing Rev5 certifications remain active “until at least December 31, 2028.” Our reading: of all these dates, December 7 is the one that changes what lands in an ISSO’s inbox each month.
A note on method. We read the rules JSON with a short script that reproduces every count in this piece from the pinned release. Statement counts use the Class C variant where a rule varies by class, and include shared and Rev5 rules that apply to providers. The quotes on deadlines, changes and classes come from FedRAMP’s generated Markdown, built from the same release. For how short KEV deadlines have become under BOD 26-04, see our KEV clock analysis.
Common questions
Do the December 7 rules apply to Rev5 providers or only to FedRAMP 20x?
Do agencies still keep POA&Ms?
What is a PAIN rating?
What happens if a provider is not ready on December 7?
Sources
- FedRAMP, Consolidated Rules for 2026 (machine-readable JSON), release 2026.11.02.01From github.com/FedRAMP/rules, tag 2026.11.02.01. All counts and rule quotes come from this file; make_fedramp_vdr.py reproduces them. Accessed Nov 16, 2026.
- FedRAMP, rules repository READMEAccessed Nov 16, 2026.
- FedRAMP, rules CHANGELOG (release 2026.11.02.01, November 2, 2026)Accessed Nov 16, 2026.
- FedRAMP, Rev5 DeadlinesGenerated Markdown from github.com/FedRAMP/2026-markdown, built November 3, 2026 from rules release 2026.11.02.01. Accessed Nov 16, 2026.
- FedRAMP, What's Changing in 2026Same build of github.com/FedRAMP/2026-markdown. Accessed Nov 16, 2026.
- FedRAMP, Important Dates for the Consolidated Rules for 2026Same build of github.com/FedRAMP/2026-markdown. Accessed Nov 16, 2026.
- FedRAMP, Certification Classes (agency guidance)Same build of github.com/FedRAMP/2026-markdown. Accessed Nov 16, 2026.
Share on LinkedInFollow AusperSubscribe by RSS
Related reading
Working on this now?
Tell us where your program stands and we'll tell you what we would do next.
Talk to Ausper