GovRAMP authorization for state and local cloud procurement
Scope the cloud offering, prepare evidence for an approved assessor and work with GovRAMP and a sponsoring body. Government buyers can use the same process to confirm what a listing covers.
Plan approval around the independent assessment, PMO review and sponsor decision. GovRAMP publishes ongoing monthly monitoring and an annual assessment for Authorized and Provisionally Authorized offerings. Confirm review dates with the PMO and assessor.
Reviewed
Inside this guide
5 steps · 5 templates
Who it applies to
Providers and U.S. public sector buyers evaluating a cloud offering under GovRAMP, formerly StateRAMP. Check the purchasing entity’s requirements, accepted status and impact level for the intended service.
What you’ll produce
A scoped offering, tested security package, documented approval and public listing when verified, with evidence for ongoing monitoring.
Confirm which GovRAMP status and scope the buyer accepts. A Provisionally Authorized decision can carry agreed remediation conditions for an interconnected technology or another identified issue under the framework.
Which path and official decision does the business need?
Confirm intended market or customer, covered product or service, and the required approval route. Fund evidence, test or assessment work, and time to respond to reviewers.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
Write down the proposed route, what eligibility depends on and who can verify it. Pull a representative test, evidence record or service use case to check the boundary.
Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor outstanding evidence, external dependencies and authority responses due. Bring changes to the assessed product or service to the decision owner.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
GovRAMP kickoff brief
Business reason and required outcome [Contract, obligation or approval]
Scope and exclusions [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones [Date, source and owner]
Executive sponsor and authorized signer [Names]
Project lead and backup [Names]
First workstream Agree the offering boundary and target status · Provider security architect + product owner + government buyer [Name and due date]
People, effort and external costs [Estimate, owner and contingency]
Evidence folder and reviewer access [Location, access owner and review date]
Decisions and blockers [Item, options, owner and decision date]
First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Write down the proposed route, what eligibility depends on and who can verify it. Pull a representative test, evidence record or service use case to check the boundary.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START
How this works in practice
Two questions to check scope
Which hosting environments, providers, integrations and customer responsibilities fall inside the offering you will sell?
Is the buyer asking for a particular impact level and status, and can procurement trace that requirement to the final listing?
Worked scenario
A fictional state agency buys a records platform with separate commercial and government environments. The provider scopes the government environment, records a connector dependency, and gives the agency the authorization ID and written scope before award.
Reuse the underlying security management evidence where it fits the GovRAMP control scope.
FROM THE SOURCE
Cases and numbers
GovRAMP · PMO fee schedule effective January 2027
$1,610Annual Authorized or Provisional PMO review fee in the under $1 million revenue tier
Set separate budgets for review, monitoring and assessment
The January 2027 schedule also lists $268 per month for applicable monitoring in that tier. Use the correct revenue band and budget for membership and an independent assessor separately.
What to check Ask finance to use the published schedule effective for the expected review and monitoring period.
300+NIST controls in GovRAMP’s Authorized and Provisional assessment description
The framework describes an assessment of more than 300 controls
The applied baseline depends on impact level and scope. The independent report and the official listing identify what is covered for a particular offering.
What to check Check the exact offering and impact shown in the public listing before relying on an authorization claim.
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
01
Agree the offering boundary and target status
Who Provider security architect + product owner + government buyerWhen Before assessment scoping or a procurement commitment
Map the offering, data, environments, subcontractors and shared controls. Confirm the impact level and status with the intended buyer. Document dependencies and identify a government sponsor or the GovRAMP Approvals Committee route.
What to produce
GovRAMP offering scope and route memoDecision memo
Gather first
Service proposal
Agency requirements and data classifications
Architecture and integrations
Current GovRAMP assessment framework
How to prepare it
Identify the legal provider, offering, deployment environments and consumers. Map where government data is processed, stored and administered.
Record the authorized boundary and each shared or interconnected service, with the responsible owner and supporting status where applicable. Agree which impact level and target status the buyer requires.
Confirm the available sponsor route, approved assessor and review prerequisites. Get sign-off from the product and compliance leads on scope and open dependencies.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional boundary row
The agency deployment uses the government environment and its recovery service. The security lead records the handling of one third-party integration in the scope memo.
Fictional decision
The buyer confirms Moderate is the target. Compliance assigns an owner to verify the shared provider’s evidence before the assessment scope is finalised.
Check before handing it over
Every material dependency and buyer requirement maps to the proposed offering, evidence and a named owner.
Share the agreed scope with the assessor, PMO contact and procurement owner.
Who Compliance lead + system owners + supplier assuranceWhen Before handing the package to the assessor
Assemble the System Security Plan, control implementation evidence, boundary and data flow material using current templates. Assign owners and close evidence gaps. Confirm permission to share scoped supplier material.
What to produce
GovRAMP control and evidence workbookSpreadsheet
Gather first
Approved scope
Current GovRAMP SSP and control templates
Service diagrams
Control owner evidence
Supplier responsibilities
How to prepare it
Create one row per applicable control and map the responsible owner, implementation and evidence to the exact scoped environment. Record inherited and customer responsibilities explicitly.
Gather dated operating evidence and compare the documents with what is deployed. Reference the approved SSP section and restrict access to sensitive evidence.
Have a second reviewer select a few controls to trace from the statement to the supporting records. Assign dated actions for evidence gaps and outdated descriptions.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional control evidence
The access owner supplies the current entitlement review and matching approval records for the government environment.
Fictional gap
A diagram omits a managed service. The architect updates the boundary and the control owner attaches the applicable evidence and review decision.
Check before handing it over
An assessor can reproduce the route from a control claim to current, scoped evidence and its owner.
Give the reviewed workbook, approved SSP and evidence access to the approved 3PAO.
Who Approved 3PAO + provider assurance lead + control ownersWhen During testing and before submitting the security package
Agree the assessment scope and plan. Coordinate evidence requests and reviewed results. Reconcile findings to the Security Assessment Report and the Plan of Action and Milestones, with owners and due dates.
What to produce
GovRAMP assessment and remediation fileSpreadsheet
Gather first
Agreed scope and assessment plan
Assessor evidence requests
Test results
Draft and final report
Current remediation plan
How to prepare it
Reconcile the assessment plan to the package and boundary. Record the tests performed and the follow-up evidence requested by the independent assessor.
For each finding, capture the related control, report reference, affected scope, owner, corrective action and due date. Record accepted deviations or conditions through the official decision process.
Attach the approved retest or closure evidence where applicable. Reconcile open items and response dates before handing over the final report and remediation plan.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional finding row
One sampled privileged access review is missing a sign-off. The control owner updates the review workflow and supplies dated retest evidence.
Fictional sign-off
The provider and assessor reconcile the final report to the active action list and preserve the evidence behind a closed finding.
Check before handing it over
Every reported issue has a traceable disposition, supporting evidence and a named owner for any remaining work.
Send approved package components and open actions to the PMO submission owner.
Who Provider compliance lead + PMO + sponsoring bodyWhen When the package is complete and before the buyer relies on status
Submit the required documents and Security Review Request. Track PMO questions and the sponsoring decision. Verify the listed offering, status, impact level and identifier against the proposed contract.
What to produce
GovRAMP submission and buyer verification recordDecision log
Gather first
Approved security package
Security Review Request
PMO and sponsor communications
Official product list
Draft contract scope
How to prepare it
Record the package version and submission date, the review channel and the sponsor route. Assign owners and response dates for PMO follow-ups.
Save the notice of decision and any conditions. Compare the official listing and identifier with the contracted service, impact level and required status.
Record written resolution for any proposed feature, environment or dependency outside the supplied scope and assign ongoing verification before renewal.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional listing check
Procurement matches the status and identifier to the government offering and records the supporting boundary and date of review.
Fictional clarification
The bid includes an optional analytics module. Procurement asks the provider to show which listing and scope cover that module before accepting it.
Check before handing it over
The actual offering, public listing, sponsor decision, and contract requirements can be checked against one another.
Share the verified record with procurement and the provider’s monitoring owner.
Who System owner + continuous monitoring lead + independent assessorWhen Monthly, annually and when a significant change is proposed
Schedule monitoring, recurring assessment and review of significant changes. Keep current remediation and evidence records, coordinate required updates with GovRAMP and prepare the next annual assessment.
What to produce
GovRAMP monitoring and change calendarSpreadsheet
Gather first
Current verified status
PMO monitoring instructions
Annual assessment requirements
Active remediation items
Change calendar
How to prepare it
List required recurring evidence and the PMO submission details. Assign accountable owners and separate the monthly monitoring tasks from the annual review.
Record the evidence version, review, delivery receipt and pending actions each cycle. Keep the current remediation dates and decisions in sync with the reporting package.
Route significant changes through the official assessment process. Record which evidence or scope must be rechecked and who owns any required review.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional monthly row
The monitoring lead reconciles the month’s evidence and outstanding remediation, obtains approval and retains the submission receipt.
Fictional change row
Product proposes moving a processing service. The owner records the affected boundary and seeks assessment guidance before the change is authorised.
Check before handing it over
Every recurring submission and significant change has an owner, date, evidence reference and status.
Use the calendar in the operating review and give the annual evidence pack to the assessor and PMO contact.
Match each government hosting service to its required assurance level, actual sites and certification evidence. Prepare a provider assessment pack and check the registration pause before committing to a bid or launch date.