Skip to content

Blog

FedRAMP's message to agencies: the risk is yours, and so is the bill

FedRAMP's Director shows understanding when cloud providers lack the money and staff to change, and offers agencies in the same position a reminder of their duties. As the program shifts work and risk to agencies, the law says supporting them is part of its job.

By FedXchange ·

On June 8, 2026, Pete Waterman, the Director of the Federal Risk and Authorization Management Program (FedRAMP), told the program's advisory committee about cloud providers that had not adopted FedRAMP's new process for reporting changes. He did not scold them. "Many cloud service providers have invested in a process that doesn't change," he said. "They don't have budget, funding, personnel, and staffing in order to make change." The situation, he said, "helped me understand something new," and FedRAMP would have to "push very hard" to move them (video, 30:32).

Twenty-five minutes later, Bill Hunt of the Securities and Exchange Commission described agencies in nearly the same terms. Agencies had just lost much of their security and engineering staff, he said, and many of the people who remain do not yet understand FedRAMP's changes. "The problem is skills and budget," he told the committee. Until that changes, agencies will not change their policies (video, 54:08). The captions show no answer to his point. The meeting moved on, and Waterman's next answer took a cloud provider's questions about FedRAMP 20x (video, 59:33).

That exchange captures a pattern in FedRAMP's public remarks this year. As the program rebuilds itself under the Office of Management and Budget (OMB) memo M-24-15 and FedRAMP 20x, it is handing agencies more of the work and more of the risk. When cloud providers struggle, FedRAMP treats it as a problem to solve. When agencies struggle, FedRAMP treats it as their failure.

The work is moving to agencies

Waterman's case starts from a fair point. For years, he told the committee, industry pushed agencies to treat a FedRAMP authorization as a substitute for their own duties under federal law and National Institute of Standards and Technology (NIST) standards: categorizing their information, tailoring controls, and deciding whether a service fits their use. That "created an intense amount of danger and risk," he said, which FedRAMP is now working to undo (video, 18:42).

The fix is to hand those decisions back. Agencies are to write their own system security plans instead of copying a provider's. "If you're not responsible and accountable for the control, it shouldn't be in your system security plan," he said (video, 27:21). They are to read providers' security data and judge it for themselves. "You can't just say FedRAMP said this," he told agencies at a FedRAMP Day event in March (video, 19:44). They are to accept notices of significant changes instead of approving each change in advance. And when providers begin publishing that security data in machine-readable form, agencies will need software to read it. "We need you to have tools to do that," he said (video, 17:28).

Each of these is sound risk management on paper. Each is also work that FedRAMP's old process did, or seemed to do, on agencies' behalf. And it lands on top of deadlines agencies have already missed. M-24-15 required every agency to have a governance, risk, and compliance automation tool and to update its cloud policies. "Most of the government has not" met those deadlines, Waterman said, and "none of those policies were updated" (video, 25:47).

Two standards

Waterman is not soft on cloud providers. Providers that run a scan once a month and call it security are "unacceptable," he said (video, 28:57). A large provider that refuses to share its security data with agency customers "won't be authorized anymore" (video, 14:23). But for providers, criticism comes with a plan: new standards, deadlines, and FedRAMP's direct authority to enforce them.

For agencies, it comes with a reminder. "That's not FedRAMP's job to make agencies do things," he told the committee when members raised slow adoption. FedRAMP issues the guidance and runs its part, "and then it's up to agencies to implement the other side." In the same answer, he pointed to inspectors general and the Government Accountability Office, which he said have begun faulting agencies for "not following FedRAMP's approach" (video, 43:44). In March he cited an inspector general who put an agency IT office on a corrective action plan for that reason (video, 19:44).

The tone holds across his appearances. When providers said their agency customers would never accept FedRAMP's new approach to vulnerabilities, his answer was simple: "they have to" (video, 57:37). On agency policies, he said: "Update your policies. Stop doing the same old stuff" (video, 20:05). On deadlines: "When you tell an agency they have up to 30 days to do something, they will take 30 days to do it" (video, 28:09). And on a capability FedRAMP had made nearly free, agencies "still won't be able to do it for all sorts of reasons sometimes" (video, 1:10:37). He also told the committee that June's would be FedRAMP's last extensive briefing to it, and that members "should be paying attention" to FedRAMP's public material instead (video, 17:03).

He has shown some understanding. In July, on the authorization letters agencies are supposed to send FedRAMP, he said that a "fairly significant portion" of the federal staff who used to send them "are gone," and that "sometimes it's hard for agencies to keep up with things" (video, 28:28). But that acknowledgment came with no change in what FedRAMP expects, and no new help.

What the law asks of FedRAMP

Waterman is right that FedRAMP cannot order agencies around. The FedRAMP Authorization Act of 2022 gives the General Services Administration (GSA), which runs FedRAMP, no power to compel an agency. OMB sets the policy, and agencies make their own authorization decisions.

But the same law does not leave agencies on their own. It directs GSA to develop "a process to support agency review, reuse, and standardization" of security assessments, to publish templates, best practices, and technical assistance, and to track its metrics "in a manner that minimizes the agency reporting burden" (44 U.S.C. 3609). Supporting agencies is not an extra that FedRAMP can drop when its budget shrinks. Congress wrote it into the program's job.

No money, and little patience for asking

FedRAMP's own squeeze is real. Waterman told the committee the program has about 30 staff, a third of what it had two years earlier, and a budget of about $10 million a year for the foreseeable future. He also told members that their past advice, that FedRAMP should get more money and do more things, is "not helpful advice that is worth any amount of time right now." FedRAMP would rely on "industry and agencies, but mostly industry, to fill the gap" (video, 23:27).

Agencies have no such option. At the committee's November 2 meeting, agency members said the new work comes back to agencies, that their resource limits have not changed, and that without funding it would be "an unfunded mandate" (video, 56:01). The committee added a line to its draft report saying its suggestions should take into account agencies' "significant financial and resource constraints" (video, 1:32:04).

The result is a program that is shrinking its own role, moving judgment and tooling to agencies, and pointing to auditors as the enforcement, at the moment agencies have the fewest people to do any of it.

FedRAMP's side

FedRAMP's leaders have a reasonable answer. The authorization decision always belonged to the agency under federal law; FedRAMP is ending a false sense of cover, not inventing a new duty. The program does run monthly meetings with agency liaisons and agency support groups (video, 16:17). In March, Waterman asked agencies to help build what they need, saying that many of them "have a lot of expectations from FedRAMP that we're not able to meet" (video, 55:26). Funding for agency security programs is up to OMB and Congress, not GSA. And agencies that refuse change notifications or insist on the highest FedRAMP label for every service do keep providers on the slow, government-only processes that M-24-15 set out to end.

All of that can be true, and agencies can still be carrying a heavier load than FedRAMP's tone admits. A program that sees providers' budget limits as a problem to solve could see agencies' the same way. It could start with what the law already asks for: model policies and plan language agencies can adopt, a low-cost way to read providers' security data, and a reporting process simple enough that a short-staffed office actually files its letters.

How we reported this

FedXchange read the captions of every FedRAMP and advisory committee video on YouTube. We quote Waterman only where the speaker is clear: his update to the committee on June 8, the committee's July 27 meeting, whose captions name each speaker, and FedRAMP Day passages where the speaker talks as FedRAMP. The captions are automatic, so each quote links to its moment in the video. This is an analysis of the public record, not a news report.

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.