Skip to content

Blog

Let's Talk FedRAMP RFCs: why FedRAMP released six requests for comment at once in January 2026

In a short January 2026 video, FedRAMP's Director and Security Director explained why FedRAMP released six requests for comment on one day, with closing dates staggered from February 12 to March 11, 2026, and how to comment so FedRAMP can use it.

By FedXchange ·

Play the video: Let's Talk FedRAMP RFCs!
FedRAMP's video, on its governance tracker page. The player loads from YouTube only when you press play.

On January 14, 2026, the Federal Risk and Authorization Management Program (FedRAMP) posted a three-minute video, "Let's Talk FedRAMP RFCs!" In it, the FedRAMP Director and the FedRAMP Security Director explain why FedRAMP released six requests for comment (RFCs) on one day, January 13, 2026, and how to comment on them. The video's description says it supplements FedRAMP's blog post Realizing the FedRAMP Authorization Act.

The video came before FedRAMP issued the FedRAMP Consolidated Rules for 2026. At the time, FedRAMP used the term "FedRAMP authorization." The current terms are "FedRAMP Certification" and "FedRAMP Certified," as FedRAMP's What's Changing in 2026 page shows.

Two FedRAMP processes come up below. FedRAMP 20x is the newer one, built on Key Security Indicators and automated assessment. Rev5 is the older one, based on Revision 5 of the National Institute of Standards and Technology (NIST) Special Publication 800-53 controls.

In short:

  • What FedRAMP said. The six RFCs were closely related, so FedRAMP released them together. It staggered their closing dates so people had time to comment on each one.
  • Who it affects. Cloud service providers, assessors, and agency staff, judging by what the six RFCs cover.
  • What FedRAMP suggested. Read each RFC's background and motivation, read each RFC to the end, read all six together, and send comments, not questions, before each one closed. The first closed on February 12, 2026, and the last on March 11, 2026.
  • What happened next. All six are closed. FedRAMP's Notice 0004 gave its initial outcome for one of them, RFC-0020, and chose different terms from the ones it proposed.
Days each January 2026 request for comment stayed open
RFC-0019 Assessment costsDays open, RFC-0019 Assessment costs: 30 days30RFC-0020 DesignationsDays open, RFC-0020 Designations: 37 days37RFC-0021 MarketplaceDays open, RFC-0021 Marketplace: 37 days37RFC-0022 External frameworksDays open, RFC-0022 External frameworks: 44 days44RFC-0023 Rev5 ProgramCertificationsDays open, RFC-0023 Rev5 Program Certifications: 44 days44RFC-0024 Rev5 machine-readablepackagesDays open, RFC-0024 Rev5 machine-readable packages: 57 days57

Days from January 13, 2026, to each closing date on FedRAMP's RFC list: February 12, February 19, February 19, February 26, February 26, and March 11, 2026.

Show the numbers
Days open
RFC-0019 Assessment costs30
RFC-0020 Designations37
RFC-0021 Marketplace37
RFC-0022 External frameworks44
RFC-0023 Rev5 Program Certifications44
RFC-0024 Rev5 machine-readable packages57

Why did FedRAMP release six RFCs at once?

The Director opened by saying it would feel like a rough week for people who work on FedRAMP. A speaker said FedRAMP thought about releasing the RFCs one at a time over a couple of months. But they were all closely related and all ready, so FedRAMP released them together.

"We're dropping a lot of new proposed guidance updates." — FedRAMP Director

In the video, a speaker places the RFCs in FedRAMP's history. The FedRAMP Authorization Act was enacted on December 23, 2022. The Office of Management and Budget (OMB) issued memo M-24-15, "Modernizing the Federal Risk and Authorization Management Program," on July 25, 2024. The speaker said FedRAMP spent the last year carrying out that memo. The speaker called the proposals "the culmination of that work." (Words from the video.) FedRAMP's blog post says the changes are meant to be "the last major updates for the foreseeable future."

A speaker said FedRAMP staggered the closing dates so people would not have all six due on the same day. The Director credited the Security Director with that idea. The chart shows how long each one stayed open. FedRAMP's January 13 blog post listed February 19 as the closing date of RFC-0023, and its RFC list now shows February 26.

What did the six RFCs propose?

FedRAMP's blog post summarizes each one:

In the video, a speaker said the main four RFCs about the Marketplace started as one RFC that was too big, so FedRAMP split it up.

How should people comment on a FedRAMP RFC?

The two speakers gave three tips. The first was not to skip each RFC's background.

"don't skip the background and the motivation." — FedRAMP Security Director

A speaker said the backgrounds explain why FedRAMP is proposing a change now and how it will affect readers. One background tells where system security plans came from.

The second tip was to read the whole RFC before commenting. A speaker said FedRAMP often sees a comment about a point a third of the way through that the RFC answers later. The third tip was to read all six RFCs together, because they are so closely related.

The speakers also said not to ask questions in formal public comments. A speaker said: "We can't answer questions in comments. That's why it's called public comment, not public Q&A." (Words from the video.) The speaker pointed people with questions to FedRAMP's discussion forums and community working groups.

The video ends by pointing to fedramp.gov/rfcs for all the RFCs and to FedRAMP's change log.

What came of the six RFCs?

All six closed between February 12 and March 11, 2026. FedRAMP's Notice 0004, issued February 25, 2026, gave the initial outcome of RFC-0020. FedRAMP will not create separate designations, such as "FedRAMP Validated," for 20x and Rev5. It uses "FedRAMP Certification" and "FedRAMP Certified" for every path, and FedRAMP Certification Classes A, B, C, and D instead of numbered levels.

The Consolidated Rules for 2026 took effect on July 4, 2026, and FedRAMP will begin enforcing them after January 1, 2027. FedRAMP's 2026 definitions call "FedRAMP Certified" the current program term for a cloud service that meets the legal requirement to be FedRAMP authorized.

Sources

Share this post:LinkedInXEmail

Get new posts and federal governance by email

A weekly email on Fridays, an alert on the day the watch finds something new, or both. Free.

Send me
About

We use your address only to send what you choose, and every email has a one-click unsubscribe. Read the privacy notice.