GovRAMP, formerly StateRAMP, is the US program that verifies cloud security for state and local government and education, filling the gap that federal-only FedRAMP leaves. It is based on NIST 800-53 and mirrors the FedRAMP model. It rebranded from StateRAMP in February 2025. Australia has no equivalent, because it runs a single national IRAP regime rather than separate federal and sub-national programs.
GovRAMP is the answer to a US-specific problem: FedRAMP only covers federal agencies, so state and local government needed their own cloud assurance program. For a cloud provider selling across US government, and comparing it to Australia, the structure is worth understanding.
What is GovRAMP?
GovRAMP is a non-profit run program that provides a standardised way to verify the security of cloud products and services used by US state and local government and education. It covers the same lifecycle as its federal cousin: security assessment, authorization and continuous monitoring, based on NIST SP 800-53 control baselines.
It exists because FedRAMP only covers US federal agencies. State governments, local governments and education institutions buy cloud services too, and they wanted the same kind of standardised assurance without each agency assessing every provider independently. GovRAMP fills that gap, giving the state, local and education market a shared verification program modelled on FedRAMP. For a cloud provider, it means one recognised status that many state and local agencies can rely on, rather than a separate security review for each. It is a US structure with no direct Australian parallel, for reasons covered below.
Why did StateRAMP rebrand to GovRAMP?
StateRAMP announced its rebrand to GovRAMP on 14 February 2025. The change reflects a broader mission: while the program began focused on US states, it had grown to serve local government and education as well, and the name StateRAMP no longer captured that reach.
The rebrand was handled to avoid disruption. The legal name of the organisation remains StateRAMP, now operating as GovRAMP, so existing contracts, memberships and authorizations continue unchanged. For a provider already in the program, nothing broke, the status carried over under the new name. The practical significance is mainly signalling: GovRAMP is making clear that it serves all levels of subnational government and education, not just state agencies, which matters as more jurisdictions look for a standardised way to assure the cloud services they buy. References to both StateRAMP and GovRAMP point to the same organisation and program.
How does GovRAMP relate to FedRAMP?
GovRAMP deliberately mirrors the FedRAMP model for the market FedRAMP does not serve. FedRAMP authorises cloud services for US federal agencies, and GovRAMP provides equivalent verification for state and local government and education. Both are built on NIST SP 800-53 control baselines and follow a similar assessment, authorization and continuous monitoring approach.
That alignment is intentional and useful. A cloud provider that has been through FedRAMP will recognise the structure of GovRAMP, and much of the underlying security work is shared, because both draw on the same NIST control catalogue. The difference is the market and the governing body: FedRAMP is a federal government program run through the General Services Administration, while GovRAMP is a non-profit serving the state, local and education sector. Some jurisdictions also recognise FedRAMP authorization toward GovRAMP status, given the shared foundation. For a provider building a US government cloud business, the two together cover the federal and the sub-national markets, and the shared NIST basis means the second is less work than the first.
Is there an Australian equivalent of GovRAMP?
No, and the reason is structural. Australia does not separate cloud authorization into federal and sub-national programs the way the US does with FedRAMP and GovRAMP. Australia runs a single national regime: systems holding government information are assessed against the Information Security Manual through an IRAP assessment, and that same mechanism applies regardless of whether the buyer is a Commonwealth agency or, where the framework is adopted, a state agency.
So there is no Australian GovRAMP, because there is no gap for it to fill. The state government cyber security frameworks are built on the Essential Eight and ISO 27001 rather than a separate cloud authorization scheme, and where a state agency needs assurance of a cloud service holding government data, the IRAP assessment against the ISM is the reference point, the same as at the Commonwealth level. For a US cloud provider entering the Australian government market, this is a simplification worth knowing: rather than navigating separate federal and state cloud programs, the Australian path centres on IRAP and the ISM. Cybernion helps cloud providers through that process with IRAP assessment and readiness.
Frequently asked questions
What is GovRAMP?
GovRAMP is a non-profit run program that provides a standardised way to verify the security of cloud products and services used by US state and local government and education. It covers security assessment, authorization and continuous monitoring, based on NIST SP 800-53 control baselines. It is the state, local and education counterpart to the federal FedRAMP program, filling the gap that FedRAMP, being federal only, does not cover.
Why did StateRAMP rebrand to GovRAMP?
StateRAMP announced its rebrand to GovRAMP on 14 February 2025, to reflect a broader mission across all levels of government and education rather than just US states. The legal name of the organisation remains StateRAMP, operating as GovRAMP, so existing contracts and memberships continue without disruption. The change signals that the program serves local government and education as well as state agencies.
How does GovRAMP relate to FedRAMP?
GovRAMP mirrors the FedRAMP model for the market FedRAMP does not serve. FedRAMP authorises cloud services for US federal agencies, while GovRAMP provides equivalent verification for state and local government and education. Both are based on NIST SP 800-53 control baselines and follow a similar assessment, authorization and continuous monitoring approach, so a provider familiar with one will recognise the structure of the other.
Who needs GovRAMP?
A cloud service provider that sells to US state or local government agencies or to the education sector may be asked to hold GovRAMP status, in the same way a provider selling to US federal agencies needs FedRAMP. A growing number of state governments require or prefer GovRAMP verification in their procurement, so for a cloud provider targeting that market it is increasingly the entry expectation.
Is there an Australian equivalent of GovRAMP?
No. Australia does not have a separate sub-national cloud authorization program the way the US separates FedRAMP for federal and GovRAMP for state and local. Australia runs a single national regime, where systems holding government information are assessed against the Information Security Manual through IRAP, and that same mechanism applies whether the buyer is a Commonwealth or, where adopted, a state agency. There is no Australian GovRAMP.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- StateRAMP Announces Rebrand to GovRAMP, GovRAMP, 14 February 2025
- GovRAMP, GovRAMP, 2026
- FedRAMP 20x, Federal Risk and Authorization Management Program, 2026
- Information Security Manual, Australian Signals Directorate, 2026
Last updated: 30 August, 2026
