FedRAMP notice NTC-0017: the December 7 vulnerability-rules deadline and the March 8, 2027 revocation

FedRAMP’s November 10, 2026 notice tells certified cloud services how it will collect progress on the move to its new vulnerability rules due December 7, 2026, and that services neither migrated nor under an approved corrective action plan on March 8, 2027 lose certification.

NTC-0017 keeps the December 7, 2026 deadline and the grace period through March 7, 2027 that FedRAMP had already announced. It adds clarifications on how FedRAMP will treat providers that miss the deadline, what they must report, and how it will collect the reports [1]. This explainer covers where the deadline came from, what counts as migrated, the four dates, the progress report, and the cases that are handled differently.

Where the December 7 deadline came from

CISA released Binding Operational Directive 26-04, “Prioritizing Security Updates Based on Risk,” on June 10, 2026. FedRAMP responded on June 16, 2026 with NTC-0014, which made the VDR and VER rules mandatory for all cloud service offerings obtaining or maintaining FedRAMP Certification effective December 7, 2026 [2]. NTC-0014 says mandatory adoption had been planned for June 1, 2027, with a grace period to January 1, 2028, and that the directive brought it forward [2].

NTC-0014 maps the rules to the directive. For example, VER-EVA-EIR requires an evaluation of whether a vulnerability is likely reachable from the internet, VER-EVA-AIA requires providers to assume exploits are automatable unless they have evidence otherwise, and VDR-TFR-KEV requires known exploited vulnerabilities to be remediated on the directive’s timelines unless there are valid technical reasons not to [2]. FedRAMP says it confirmed with CISA that providers following the VDR and VER rules will meet or exceed the directive’s expectations [2]. Background: our explainers on BOD 26-04 and the FedRAMP Consolidated Rules for 2026.

What “fully migrated” means

FedRAMP’s migration resources site defines a service as fully migrated when all MUST and MUST NOT rules are fully implemented, and all SHOULD and SHOULD NOT rules are fully implemented or otherwise addressed [3].

The four dates

  • December 7, 2026: every service not fully migrated must explain, for each rule, the corrective actions it will take and target timelines [1].
  • February 3, 2027: any service planning to complete migration after this date is placed into remediation, and its Marketplace entry shows “FedRAMP Certified (In Remediation)” until it tells FedRAMP the migration is complete [1].
  • March 7, 2027: the grace period ends [1] [3].
  • March 8, 2027: a service that has not fully migrated and is not operating under a FedRAMP-approved Corrective Action Plan has its certification revoked and is banned from FedRAMP for one year [1].

FedRAMP says it will not take unnecessary administrative action against services working safely and in good faith to migrate, and that it expects revocation to affect only providers that refuse to take part [1]. It also offers an extended conditional grace period, case by case: a service may target completion after March 7, 2027 if FedRAMP approves its Corrective Action Plan and it agrees to a red team assessment coordinated by FedRAMP. FedRAMP says it will begin working with those services in February [1].

The progress report

Each applicable provider must submit a VDR/VER Migration Progress Report containing [1]:

  • Implementation status for each applicable rule, with a brief explanation and a rule-specific Corrective Action Plan where a required rule is not implemented, supplied as a Mini-Security Decision Record (Mini-SDR) in CSV or JSON.
  • A sample machine-readable activity report of the kind required by VER-RPT-PER, with at least five vulnerabilities of each type.
  • A sample human-readable monthly activity report of the kind required by VER-TFR-MHR, also with at least five of each type.

The samples must use examples in place of actual vulnerabilities that are currently likely exploitable or internet-reachable [1]. FedRAMP says the overall Corrective Action Plan can be generated from the Mini-SDR, and that schemas, templates, examples and validation scripts are on the migration resources site [1] [3]. Requirements may be added or changed until the test message is sent [1].

The Emergency Test, and what failure to respond costs

NTC-0017 is also the formal public notice of FedRAMP’s FY27 Q1 Security Inbox Emergency Test, the mechanism for collecting the reports through a web form. FedRAMP gives December 1 through December 10, 2026 as the likely window for sending the message and December 17, 2026 at 2 p.m. Eastern as the likely response deadline [1].

A service that fails to respond is placed in “FedRAMP Certified (In Remediation)” status for no less than 30 days, its Marketplace page notes the failure, and all agency customers are notified. It then has 30 days to supply the information with a Corrective Action Plan; a provider that does not respond within that period has its certification revoked [1].

Services handled differently

  • Services with an agency authorization in process: after December 7, 2026, a service that receives an agency ATO must support a progress report with its application for a new FedRAMP Rev5 Certification, and may receive a short-term certification with conditions if FedRAMP approves its plan. After March 7, 2027, FedRAMP will not begin reviewing such a service unless it has fully migrated [1].
  • Agency-provided offerings, such as those in the Marketplace’s By Government, For Government section, are exempt from the VDR and VER rules. FedRAMP notes they are already bound by BOD 26-04 and points to a forthcoming notice on a Class G certification [1].

In our view, agencies relying on a FedRAMP Certified service have a simple check once reports are due in December: whether the service’s Marketplace entry shows the In Remediation status. That is a practice suggestion, not a requirement.

This explainer describes FedRAMP’s notices as checked on November 14, 2026; it is not legal or contractual advice, and providers should rely on the notices and FedRAMP’s instructions.

Moraph’s teams help organizations with work like this. See our solutions.

Spotted an error? Tell us and we will check it and correct the explainer where needed.

  • FedRAMP
  • NTC-0017
  • Vulnerability Detection and Response
  • Vulnerability Evaluation and Reporting
  • BOD 26-04
  • cloud services
  • corrective action plan