FSCAC, November 2024: members rework draft advice on small-business barriers and faster FedRAMP reviews
On November 14, 2024, the Federal Secure Cloud Advisory Committee kept drafting its 2024 advice to the GSA Administrator. Members put money first, struck one idea, and proposed asking OMB when agencies may use offerings waiting in FedRAMP's queue. It took no vote.
By FedXchange ·
Play the video: November 14 2024 Open FSCAC MeetingOn November 14, 2024, the Federal Secure Cloud Advisory Committee (FSCAC) held a three-hour virtual meeting. The FSCAC is the advisory committee that Congress required in the FedRAMP Authorization Act, part of the National Defense Authorization Act for Fiscal Year 2023. It gives advice and recommendations to the Administrator of the General Services Administration (GSA), the FedRAMP Board, and agencies. FedRAMP is the Federal Risk and Authorization Management Program. The committee's recommendations are advice. They do not change FedRAMP's rules.
The Federal Register notice said the meeting was for "continued deliberations" on an initial draft of recommendations on two priorities. The first was barriers to entry for cloud service providers, with a focus on small businesses, third party assessment organizations (3PAOs), and small and large agencies. The second was ways to expedite the authorization process.
The meeting came before the FedRAMP Consolidated Rules for 2026. At the time, FedRAMP and the committee used the term "FedRAMP authorization." Today FedRAMP calls it a "FedRAMP Certification," and a certified service is "FedRAMP Certified," as FedRAMP's What's Changing in 2026 page explains. This post uses the 2024 terms when it reports what members said.
In short:
- What the committee discussed. Members kept editing a draft report to the GSA Administrator. They talked about agency sponsorship, cost, reciprocity with other programs, and the size of the control baseline.
- What members changed. They moved "reduce the time to authorization" from the first priority to the second. They struck a proposal to split authorization into smaller approval stages. They moved financial and resource support to the top of the second priority.
- A question for the Office of Management and Budget (OMB). Members proposed that FedRAMP engage OMB to clarify when an agency may use an offering that has an agency authorization and is waiting in FedRAMP's review queue.
- What it means for agencies and cloud providers. Nothing changed. The chair said nothing is final until an official vote. The committee took no vote at this meeting.
- What came next. The chair said FedRAMP would present at the committee's first meeting of the new year. GSA's meetings page shows that the February 26 and 27, 2025, meeting was canceled. It lists only draft versions of the 2024 recommendations memo.
Sources: the November 14, 2024, meeting video, GSA's agenda and minutes, and GSA's draft 2024 recommendations memo. These are draft recommendations, not FedRAMP rules.
Read the steps as text
- Public comment. Three speakers asked for scale-aware continuous monitoring triggers, IL4 and IL5 reciprocity, and more queue transparency.
- Priority 1. Members moved "reduce the time to authorization" to Priority 2 and asked that agency sponsorship stand as its own recommendation.
- Priority 2. Members struck the proposal to split authorization into smaller approval stages.
- OMB question. Members proposed asking OMB when agencies may use an offering that waits in FedRAMP's queue.
- Money first. Members moved financial and resource support to the top of Priority 2.
- No vote. The chair said nothing is final until an official vote at a future meeting.
What did the public ask the committee to do?
Three people spoke in the public comment period. GSA's agenda and minutes list them.
- Continuous monitoring triggers. A speaker for the cloud service provider community said a provider with five or more unique vulnerabilities older than 30 days normally gets a detailed finding review. The speaker said the rule applies the same way to a provider with 100 hosts and one with a million. The speaker asked the committee to recommend triggers that adapt to scale.
- Reciprocity with the Department of Defense (DoD). The Executive Director of the Cloud Service Providers Advisory Board asked the committee to recommend that DoD's Impact Level 4 and 5 (IL4 and IL5) approvals be brought into the FedRAMP process.
- Queue transparency. A principal at TandemGov asked the committee to recommend that GSA show on the FedRAMP Marketplace where a product is in the review queue, so companies can make better investment decisions.
Why is agency sponsorship a barrier to entry?
A member from a 3PAO said that, at the time, a provider could reach FedRAMP authorization (now FedRAMP Certification) only through an agency sponsor:
"agency sponsorship is the only way to get into a FedRAMP-authorized status at this point" — FSCAC member from a third party assessment organization
The member said agencies are increasingly unwilling to sponsor. Members agreed that sponsorship should be its own recommendation. A member from Databricks asked what it would take to get more agencies to sponsor. The member from the Securities and Exchange Commission (SEC) answered:
"Money, that would be the answer to your question, money. Appropriations are tight. Appropriations are increasingly tight." — FSCAC member from the Securities and Exchange Commission
Other members asked for clearer, more prescriptive guidance up front. That guidance would cover prerequisites, time, cost, and how to find a sponsor. The member from GSA said a provider had spent a year building a service on the belief that one of the scope exceptions in OMB memo M-24-15 applied, and then learned it needed FedRAMP authorization (now FedRAMP Certification). Section III of that memo, "Scope of FedRAMP," lists the categories that are out of scope. The member asked for specific guidance on those exceptions.
Members also discussed reuse of StateRAMP packages and of DoD's work. The DoD member described how DoD reuses FedRAMP evidence and said DoD had piloted a "low touch" review with FedRAMP.
Should the FedRAMP baseline have fewer controls?
Members disagreed at first. The SEC member said FedRAMP exists to remove duplicate work from agencies, so it should assess as many controls as it can:
"We cannot reduce the amount of controls that the FedRAMP team is responsible for. We can certainly change how we talk about those controls." — FSCAC member from the Securities and Exchange Commission
The GSA member said the baseline should match the risks of the data and the environment:
"there is a clear opportunity to allow us to have more of a threat-informed, risk-based, environment-sensitive set of controls that are more appropriate." — FSCAC member from GSA
GSA's draft memo, updated November 19, 2024, keeps a recommendation for risk-based minimum baselines, developed with the Cybersecurity and Infrastructure Security Agency (CISA), the National Institute of Standards and Technology (NIST), OMB, and sponsoring agencies.
Can agencies use a service before FedRAMP finishes its review?
The SEC member first worried that recommending partial use would conflict with M-24-15. Later the member noted the memo says agencies "must obtain and maintain a FedRAMP authorization," not that they must have it before first use. The member supported the idea but asked that OMB confirm it. In 2024, OMB's term was FedRAMP authorization; the current term is FedRAMP Certification. The GSA member described GSA's own interim authorizations for low and moderate systems, which let GSA use a service on a risk basis while the provider finishes the full process.
The DoD member then proposed wording: the FedRAMP Program Management Office (PMO) would engage OMB "to clarify when a CSO can be used" after agency authorization, when it enters the PMO queue. A CSO is a cloud service offering. GSA's draft memo includes a recommendation to clarify with OMB when a CSO can be used during the PMO queue.
What about paying to move faster?
Members debated cost-sharing and fees. The SEC member and the DoD member opposed charging providers more. The SEC member said paid priority would favor the largest providers over small businesses. A member from NIST said its cryptographic module program charges test laboratories, not vendors, and suggested the committee explore feasibility with guardrails for fairness. The chair asked each member to bring ideas for a cost-sharing model, "taking ethics into account," to the next meeting.
Members also asked for a FedRAMP update and a panel on the Open Security Controls Assessment Language (OSCAL), with speakers from providers, government, and 3PAOs.
Sources
- FedXchange tracker: November 14 2024 Open FSCAC Meeting
- YouTube: November 14 2024 Open FSCAC Meeting
- GSA: FSCAC November 14, 2024, public meeting agenda and minutes
- GSA: FSCAC's 2024 FedRAMP recommendations to the GSA Administrator (draft)
- GSA: Federal Secure Cloud Advisory Committee meetings
- GSA: Federal Secure Cloud Advisory Committee
- Federal Register: FSCAC notification of upcoming meeting, October 16, 2024 (2024-23788)
- FedXchange tracker: OMB M-24-15, Modernizing the Federal Risk and Authorization Management Program
- OMB: M-24-15 (PDF)
- FedXchange tracker: FedRAMP Authorization Act (Public Law 117-263, section 5921)
- FedXchange tracker: FedRAMP Consolidated Rules for 2026
- FedRAMP: What's Changing in 2026
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.