Skip to content

Blog

FedRAMP's cost transparency video: what RFC-0019 proposed, and why it was dropped

In a January 2026 video, a FedRAMP speaker said FedRAMP would require advisory firms and assessors to share their prices. RFC-0019 proposed cost reporting for cloud providers and assessors. In February 2026, FedRAMP said it will not finalize or carry out those rules.

By FedXchange ·

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

On January 29, 2026, the Federal Risk and Authorization Management Program (FedRAMP) posted a short video, "FedRAMP Costs Transparency." In it, a FedRAMP speaker talked about a plan to make the price of FedRAMP assessment services public. The video asked viewers to comment on a request for comment (RFC), RFC-0019, Reporting Assessment Costs.

The video came out before FedRAMP issued the FedRAMP Consolidated Rules for 2026 on June 25, 2026. The video's description uses the term "FedRAMP authorization." FedRAMP's What's Changing in 2026 page explains that the current term is "FedRAMP Certification," so a cloud service is now "FedRAMP Certified."

In short:

  • What FedRAMP said. The speaker said FedRAMP would require advisory firms and independent assessors to share their pricing structure, in broad ranges.
  • What the RFC proposed. RFC-0019 proposed that cloud service providers report what their assessments cost, that assessors attest to the figures, and that FedRAMP take corrective action against those who did not report.
  • Who it would have affected. Cloud service providers and FedRAMP-recognized independent assessors.
  • By when. Comments closed on February 12, 2026. FedRAMP's Requests for Comment page now says the proposed rules "will not be finalized or implemented by FedRAMP." No one has to act on RFC-0019.
What happened to RFC-0019, Reporting Assessment Costs
1ReleasedFedRAMP released RFC-0019 on January 13, 2026.2VideoFedRAMP posted "FedRAMP Costs Transparency" on January 29, 2026,asking for comments.3Comments closedThe comment period closed on February 12, 2026.4OutcomeOn February 18, 2026, FedRAMP said it will not finalize or carry outthe proposed rules.

Sources: the FedRAMP video and its description, FedRAMP's Requests for Comment page, and FedRAMP notice NTC-0002.

Read the steps as text
  1. Released. FedRAMP released RFC-0019 on January 13, 2026.
  2. Video. FedRAMP posted "FedRAMP Costs Transparency" on January 29, 2026, asking for comments.
  3. Comments closed. The comment period closed on February 12, 2026.
  4. Outcome. On February 18, 2026, FedRAMP said it will not finalize or carry out the proposed rules.

What did the FedRAMP speaker say about costs?

The video's description sets out the problem. It says the cost of a FedRAMP authorization "is unknown as it varies based on a number of factors," such as impact level, assessment costs, and ongoing monitoring. It also says nothing required industry to report those costs to FedRAMP or to agency customers.

The speaker opened with this: "We want both advisory firms and independent assessors to share information about costs. And when I say we want, I say we're going to require." (Words from the video.)

The speaker said firms often ask how to break their prices down, for example by hours or by engagement. The speaker's answer was to keep it simple. A firm should decide on its pricing structure and state it, and a broad range is fine. The speaker said firms should list the specific services they offer and the range those services cost.

The speaker gave three reasons:

  • "That will help people find assessors." (Words from the video.)
  • People could search the FedRAMP Marketplace and sort by price.
  • FedRAMP could point questions it now gets at its info@ email address to the Marketplace, so people could do their own research.

What if a firm states one price and charges another?

The speaker expected that question. The speaker said that if a firm publicly gave a low price and then quoted a much higher one, someone would tell FedRAMP, and FedRAMP might email the firm to ask about it. The speaker compared the plan to California's rule that job listings show a salary range. A wide range is acceptable, the speaker said, but a firm that charges far outside it should have "a justification for that difference." (Words from the video.)

The speaker also said "we're not trying to be policemen or police people here." (Words from the video.) The speaker described the goal as helping the FedRAMP community and stakeholders.

What did RFC-0019 actually propose?

The RFC's own text, on FedRAMP's RFC-0019 page, differs from the video. It says "The FedRAMP Authorization Act requires FedRAMP to regularly review the costs associated with independent assessment services."

For the Rev5 path, FedRAMP's existing process based on the National Institute of Standards and Technology (NIST) Special Publication 800-53, Revision 5, the RFC proposed that:

  • cloud service providers submit a cost appendix to the security assessment report, covering the initial assessment, each annual assessment, and past costs;
  • independent assessors sign an attestation that the cost information is accurate; and
  • the rules take effect, tentatively, on March 25, 2026.

For FedRAMP 20x, FedRAMP's newer process, the RFC proposed that providers share summary costs for each assessment company, updated at least every six months. It would have applied to all 20x Phase 2 pilot participants and future 20x Validations.

The proposed corrective actions included denial of authorization, or of 20x Validation, for a provider with no initial cost report, with a three-month wait before resubmitting. For missing ongoing or past cost reports, they included public notice with a three-month grace period, then revocation of FedRAMP Certification or 20x Validation for at least six months. An assessor that failed to attest faced public notice with a three-month grace period, then loss of FedRAMP recognition for at least six months.

Two points differ from the video. The RFC page does not mention advisory firms. It also says FedRAMP "MUST NOT share any identified cost data" with the public or within the federal government unless a legal requirement makes it necessary. It does not describe a Marketplace sorted by price.

What does this mean for agencies and cloud providers now?

FedRAMP's Requests for Comment page lists RFC-0019 as closed on February 12, 2026, with this outcome: "The proposed rules from RFC-0019 Reporting Assessment Costs will not be finalized or implemented by FedRAMP."

FedRAMP explained the decision in notice NTC-0002, published February 18, 2026. The notice says the RFC drew 48 comments from 30 commenters. Commenters said, among other concerns, that cost reporting was a burden unrelated to authorization, that assessment prices are private business information, that companies might report false figures, and that costs vary too much to compare. FedRAMP said it would be able to rely only on limited publicly available information to review assessment costs. It said that if it reconsidered the decision, it would need a new public comment period.

So cloud service providers and assessors do not have to report assessment costs under RFC-0019. Agency staff who want to know what a FedRAMP Certification costs a provider can ask the provider.

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.