FedRAMP
Federal Risk and Authorization Management Program
Choose a FedRAMP certification path for a cloud service used by U.S. federal agencies.
Who it applies to
Cloud service providers and agencies evaluating a cloud service offering for U.S. federal information within FedRAMP scope.
What you’ll produce
FedRAMP certification for the offering and class, with agency authorization decisions handled separately.
Check the 2026 Consolidated Rules before using legacy Rev5 documentation. Eligibility, permitted evidence and submission routes differ by class and program.
Run the project
Go to the roadmapDecisions for leadership
- Which agency needs which offering?
- Get the intended agency use case, data classification and required certification class. Compare eligible 20x and Rev5 paths against the current rules. Confirm agency dependencies before promising a Marketplace status or date.
- Can we operate the boundary we plan to sell?
- Ask Engineering to price isolation, identity, logging, hosting dependencies and evidence automation. Assign an owner for shared responsibilities and future significant changes.
- Can we fund the work after the first review?
- Reserve capacity for independent assessment where required, fixes, reassessment and recurring monitoring. Name the support owner who will keep evidence, contacts and provider dependencies current.
How to spend the first week
- Ask the federal account lead to bring the documented use case. Draw the offering with cloud accounts, management plane, remote support, external services and flows of federal information.
- Read the current provider rules for the proposed path and class. Write down who applies and which Marketplace, assessment freshness and agency requirements the team must meet.
- Meet with Engineering, the federal lead and the assessor where applicable. Give each boundary question and assessment dependency an owner and a decision date.
What to review each week
Review assessment blockers, open findings by due date, required evidence freshness and monitoring coverage. Flag Marketplace and agency milestones separately.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
FedRAMP 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 Confirm scope, class and path · Cloud program lead + agency partner [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 federal account lead to bring the documented use case. Draw the offering with cloud accounts, management plane, remote support, external services and flows of federal information. 2. Read the current provider rules for the proposed path and class. Write down who applies and which Marketplace, assessment freshness and agency requirements the team must meet. 3. Meet with Engineering, the federal lead and the assessor where applicable. Give each boundary question and assessment dependency an owner and a decision date.
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.
How this works in practice
Two questions to check scope
- Which service offering and class are in scope, and which program route is available?
- Which responsibilities stay with the buying agency even after the offering is certified?
Worked scenario
A cloud vendor separates the government offering from its commercial environment and maps identity, development and operations dependencies that cross the boundary. It confirms the route and class before commissioning assessment work.
What to read next
- NIST Risk Management Framework
Understand the agency’s separate system authorization process.
- CMMC
Check whether a separate defense contract imposes its own assessment obligations.
Official milestones
See the deadline calendar- 31 Aug 2026
20x Class B and C pipeline opens
FedRAMP began accepting applications for these 20x certifications.
Official reference (opens in a new tab) - 1 Jan 2027
Mandatory adoption of 2026 rules
Check area-specific effective dates and applicability.
Official reference (opens in a new tab) - 11 Jun 2027
End of new Rev5 applications
FedRAMP’s published end date for accepting new Rev5 certification applications.
Official reference (opens in a new tab)
- 01Confirm scope, class and pathCloud program lead + agency partner · ~21 days
- 02Implement controls and prepare evidenceCloud security + control owners · ~75 days
- 03Complete independent assessmentIndependent assessor + engineering · ~60 days
- 04Submit and respond to reviewCompliance lead + FedRAMP or agency · ~60 days
- 05Maintain continuous assuranceCloud operations + agency stakeholders · ~30 days
Step by step
Checklist, instructions and 15 templates.
View plan as a table
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Confirm scope, class and path | Cloud program lead + agency partner | Before committing to assessment | Set a start date | System boundary; Class rationale; Path and agency dependencies | Open |
| Implement controls and prepare evidence | Cloud security + control owners | Before independent assessment | Set a start date | Responsibility matrix; Control evidence; Monitoring plan | Open |
| Complete independent assessment | Independent assessor + engineering | As scheduled with assessor | Set a start date | Assessment evidence; Assessment report; Remediation plan | Open |
| Submit and respond to review | Compliance lead + FedRAMP or agency | Program-dependent | Set a start date | Submission package; Response log; Decision and listing details | Open |
| Maintain continuous assurance | Cloud operations + agency stakeholders | Throughout certification | Set a start date | Monitoring evidence; Updated findings; Change decisions | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
- 01
Confirm scope, class and path
Document federal use, data types and the offering boundary. Confirm class and eligibility for 20x or the applicable Rev5 path with current rules.
How to do this step
Before you start
Agency use case, service and data-flow diagrams, feature inventory, cloud dependencies and current class/path rules.
- Tag the systems that handle federal information and the services that can influence their security. Include the control plane, service operators and external services.
- For every shared service, record the function it performs, what evidence the provider can supply and what your team must operate. Validate inherited protections at the actual service and region level.
- Write the path decision with supported class, agency commitments, Marketplace listing requirements and assessor needs. Assign an owner to each unanswered dependency.
What a reviewer should see
A reviewer can follow a federal request through the offering and see the corresponding account, service and evidence owner.
When to escalate
Escalate unconfirmed eligibility, an unsupported inherited control, or a sales proposal covering a wider service than the technical boundary.
What to produce
System boundaryMemo
Gather first
- Federal use case and data categories
- Cloud inventory and network or service diagrams
- Administrative access routes, provider agreements and responsibility records
- Rules for the proposed path and class
How to prepare it
- Follow federal information from the public endpoint through compute, storage, logs, exports, backups and support. Give each component an identifier and record owning team, account or tenancy, region and information handled.
- Mark the control plane, remote administration and services that can change the offering or affect its security. Record shared and external services with exact interfaces and identify which protections your provider supplies.
- Review proposed exclusions against the rules for your path and class. Document evidence, unresolved assumptions, who can decide and the required review before finalizing scope. Update the diagram and inventory together.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Offering and decision
- Harbor Case Exchange, US federal tenant. Boundary BND-006 v3 approved for assessment planning. Certification class and route tracked separately in PATH-014.
- Federal information flow
- Agency user → agency SSO and US API gateway → tenant API and case database → encrypted US backups. Application logs in SEC-LOG-01 contain agency account IDs and are part of the boundary analysis.
- Components and people
- Gateway G-01, production account A-12, database DB-06, backup vault BK-02 and operations roles SRE-ADMIN and SEC-ONCALL. Service Operations owns the inventory.
- Shared services and evidence
- Dedicated deployment runner DEP-05 administers A-12. The team owns runner configuration and approvals. Cloud hosting responsibilities are recorded in RACI-07 with a dated coverage reference.
- Excluded services and rationale
- Public marketing site. Separate account and deployment chain. No path to tenant data or administration. Boundary review cites architecture and isolation test NET-08.
- Decision record and follow-up
- Security Architect and service owner signed BND-006 on October 6. Confirm external identity treatment with the assessor. Reopen on identity, backup region or support access changes.
Check before handing it over
An inventory row and drawing agree for every named interface. The reviewer can see why an exclusion is supportable and where shared or inherited responsibility begins.
Provide the approved boundary, inventory, data flows and open decisions to control owners and the applicable assessor through the agreed secure route.
Class rationaleSpreadsheet
Gather first
- Official rules or contract and version
- Product, organization or processing facts
- Jurisdiction and exception criteria
How to prepare it
- Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
- Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
- Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Requirement or decision
- REG-05, determine whether the new processing activity requires an assessment.
- Source and trigger
- Current regulator guidance, high-risk processing indicators
- Facts and evidence
- New dataset includes sensitive attributes. Data map P-024.
- Outcome and rationale
- Assessment required before release. Privacy lead to confirm scope.
- Owner and review
- Product privacy owner, reassess before launch and on new purposes.
Check before handing it over
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
Path and agency dependenciesSpreadsheet
Gather first
- Official rules or contract and version
- Product, organization or processing facts
- Jurisdiction and exception criteria
How to prepare it
- Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
- Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
- Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Requirement or decision
- REG-05, determine whether the new processing activity requires an assessment.
- Source and trigger
- Current regulator guidance, high-risk processing indicators
- Facts and evidence
- New dataset includes sensitive attributes. Data map P-024.
- Outcome and rationale
- Assessment required before release. Privacy lead to confirm scope.
- Owner and review
- Product privacy owner, reassess before launch and on new purposes.
Check before handing it over
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
- 02
Implement controls and prepare evidence
Document inherited controls and customer responsibilities. Establish scanning, incident response and monitoring. Prepare path-specific evidence such as Rev5 system security plans or 20x indicator evidence.
How to do this step
Before you start
Approved boundary, applicable rule and control set, provider responsibility matrix, asset inventory and current monitoring design.
- Map required behavior to the system that enforces it, the accountable team and the test that demonstrates it. For Rev5, keep implementation statements and responsibility allocations aligned with the package.
- For a 20x route, implement the required validation and reporting in the prescribed data format and test what happens when an observation fails or becomes stale.
- Demonstrate an operational use case such as scanning a new asset. Trace it from deployment through inventory, scan result, owner assignment and closure evidence.
What a reviewer should see
A monitoring run shows the assessed inventory and the coverage calculation. An absent or failed result becomes an assigned finding with source evidence.
When to escalate
Bring incomplete coverage or a gap in cloud-provider evidence to the technical lead before booking assessment.
What to produce
Responsibility matrixMemo
Gather first
- Named roles, on-call contacts and authority
- Realistic use cases and deadlines
- Service and vendor dependencies
How to prepare it
- Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
- Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
- Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Event or activity
- Unusual activity detected in support export portal
- First action and owner
- On-call engineer opens a restricted incident case and preserves logs.
- Decision owner and backup
- Privacy lead or legal duty contact will determine reporting.
- Handoff and clock
- Send incident ID, UTC timestamp and known scope immediately.
- Validation
- Exercise completed and backup contact reached.
Check before handing it over
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Control evidenceSpreadsheet
Gather first
- Control descriptions and test request
- Source system records
- Defined period and evidence access rules
How to prepare it
- Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
- Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
- Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Evidence ID
- EV-021
- Control or request
- AC-04, October administrator review
- Period and scope
- 1 to 31 Oct 2026 UTC, production tenant
- Source and capture
- IAM export filtered to active elevated roles
- Link or record ID
- Restricted workpaper EV-021 plus ticket IAM-114
- Reviewer and status
- Security assurance, verified
Check before handing it over
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Monitoring planMemo
Gather first
- Approved scope
- Governing requirements and risks
- Teams, service dependencies and review gates
How to prepare it
- State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
- For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
- Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Purpose
- Identify failed production backup jobs and restore service data.
- Scope
- Production billing databases and backup vault
- Activity and timing
- On-call reviews daily job alerts and runs a quarterly restore test.
- Evidence and exception
- Keep job records and restore test output. Page the service owner if a job fails.
- Owner and approval
- Operations lead owns. Service owner approves.
Check before handing it over
A person who receives the plan can tell when to act, what to check and where to save the result.
Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.
- 03
Complete independent assessment
Use the assessment method required by the path. Resolve findings, document remaining risks and compile the package in the current submission format.
How to do this step
Before you start
Current package, inventory, boundary, test users, secure access procedure and assessor engagement where applicable.
- Agree scope, environment and timing with the independent assessor where required. Record which team can answer each request and recreate evidence safely.
- Keep original test observations. Triage findings with the secure evidence references, impacted assets, remediation owner and retest date.
- Reconcile the assessor’s final artifacts against the current boundary and applicable freshness requirements. Confirm which findings remain open and how they are reported.
What a reviewer should see
Assessment results and remediation records use the same asset and finding identifiers, with a dated retest or open status for each finding.
When to escalate
Notify the lead if the environment drifted after testing, assessment evidence is stale, or a finding prevents an accurate package.
What to produce
Assessment evidenceSpreadsheet
Gather first
- Control descriptions and test request
- Source system records
- Defined period and evidence access rules
How to prepare it
- Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
- Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
- Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Evidence ID
- EV-021
- Control or request
- AC-04, October administrator review
- Period and scope
- 1 to 31 Oct 2026 UTC, production tenant
- Source and capture
- IAM export filtered to active elevated roles
- Link or record ID
- Restricted workpaper EV-021 plus ticket IAM-114
- Reviewer and status
- Security assurance, verified
Check before handing it over
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Assessment reportIssuer document
Gather first
- Correct portal or issuer contact
- Approved scope and submission record
- File access and sharing requirements
How to prepare it
- Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
- When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
- Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Document expected
- Issuer’s final decision or confirmation
- Reference
- Official portal or case ID
- Received and verified by
- Compliance coordinator, 2026-11-10
- Scope and conditions
- Matches the agreed service boundary and version. Follow-up recorded separately.
- Location and access
- Restricted evidence folder, named reviewers only
Check before handing it over
The original can be traced to the issuer and its scope and date match the engagement or application.
Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.
Remediation planSpreadsheet
Gather first
- Finding, risk or test exception
- Root-cause analysis
- Named owner, due date and expected evidence
How to prepare it
- Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
- Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
- Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Finding or risk
- F-008, a departed contractor retained production access
- Cause and effect
- HR event never reached IAM. Admin access remained active.
- Action and owner
- Revoke access and alert on failed HR sync. IAM lead.
- Due and status
- 2026-11-28, in progress
- Closure test
- Simulate departure and verify access disappears within policy
- Approver and evidence
- Risk owner, ticket IAM-114 and retest results
Check before handing it over
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
- 04
Submit and respond to review
Submit the required package and track review questions. Record the certification decision and support agency-specific authorization needs.
How to do this step
Before you start
Current package in the path-specific format, official application prerequisites, agency evidence where applicable and assessment results.
- Have a second person check required artifacts, versions, secure links and agency documents against the path’s current checklist. Confirm which provider contact will submit.
- Log each review request, who owns it, its due date and the artifact version changed. Update related package records together when one response changes the boundary or risk position.
- When a decision is issued, verify the exact Marketplace status, offering and class. Give Sales approved wording and route agency authorization questions through the agency contact.
What a reviewer should see
The response log links the original reviewer question to the approved answer and specific revised artifact. The decision and listing are separately recorded.
When to escalate
Escalate a submission prerequisite the team cannot substantiate or a discrepancy between the Marketplace listing and customer-facing claims.
What to produce
Submission packageMemo
Gather first
- Applicable FedRAMP rules for the selected path and class
- Verified boundary, current assessor artifacts and evidence index
- Program or agency submission instructions
How to prepare it
- Get the current package checklist for your specific path. For Rev5, map applicable SSP, assessment and remediation artifacts. For 20x, use the current class rules and required formats.
- Reconcile the offering boundary, class, evidence period and revision across documents. Verify assessment ownership, machine-readable files where applicable and unresolved risk decisions.
- Ask the submission owner to run a final check against the program portal. Keep a receipt and route review questions through a log with owners and due dates.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Program path
- Enter the confirmed FedRAMP certification path and class.
- Package artifact
- Identify the issuer’s required item and exact version.
- Owner and reviewer
- Named CSP submission lead and independent assessor where required.
- Review checks
- Offering name and boundary consistent across assessor and provider materials.
- Submission receipt
- Enter the official receipt and point of contact after submission.
Check before handing it over
The package matches the current path, and every index item is complete or documented under an allowed exception.
Submit through the current official route and record follow-up. The worksheet helps prepare the package.
Response logSpreadsheet
Gather first
- Case, change or communication records
- Required fields and timing
- Named case owner and authorized recipients
How to prepare it
- Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
- Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
- Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Record ID
- REQ-022
- Event and date
- Verified access request received 2026-11-07 UTC
- Owner and target
- Privacy operations, internal review by 2026-11-23
- Decision and status
- Approved response, sent securely
- Completion evidence
- Case delivery record, 2026-11-24
- Follow-up
- None, approved by the reviewer
Check before handing it over
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.
Decision and listing detailsIssuer document
Gather first
- Correct portal or issuer contact
- Approved scope and submission record
- File access and sharing requirements
How to prepare it
- Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
- When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
- Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Document expected
- Issuer’s final decision or confirmation
- Reference
- Official portal or case ID
- Received and verified by
- Compliance coordinator, 2026-11-10
- Scope and conditions
- Matches the agreed service boundary and version. Follow-up recorded separately.
- Location and access
- Restricted evidence folder, named reviewers only
Check before handing it over
The original can be traced to the issuer and its scope and date match the engagement or application.
Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.
- 05
Maintain continuous assurance
Perform monitoring, supply update artifacts on the applicable cadence and route significant changes through the required process.
How to do this step
Before you start
Decision and conditions, monitoring rules, production inventory, current findings and deployment schedule.
- Set recurring ownership for reporting, evidence refresh, incident contacts and findings. Test what happens when a feeder system stops producing evidence.
- Check proposed service changes against the applicable change rules before rollout. Document whether the boundary, controls or assessment evidence must change.
- Reconcile inventory, open findings and assurance evidence on the applicable cadence, and keep the records available for agency or FedRAMP review.
What a reviewer should see
A recently deployed component can be traced to a change decision, current inventory and a working monitoring check.
When to escalate
Escalate missed reporting, unmonitored new assets or an impending change affecting how agencies rely on the package.
What to produce
Monitoring evidenceSpreadsheet
Gather first
- Control descriptions and test request
- Source system records
- Defined period and evidence access rules
How to prepare it
- Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
- Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
- Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Evidence ID
- EV-021
- Control or request
- AC-04, October administrator review
- Period and scope
- 1 to 31 Oct 2026 UTC, production tenant
- Source and capture
- IAM export filtered to active elevated roles
- Link or record ID
- Restricted workpaper EV-021 plus ticket IAM-114
- Reviewer and status
- Security assurance, verified
Check before handing it over
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Updated findingsSpreadsheet
Gather first
- Finding, risk or test exception
- Root-cause analysis
- Named owner, due date and expected evidence
How to prepare it
- Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
- Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
- Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Finding or risk
- F-008, a departed contractor retained production access
- Cause and effect
- HR event never reached IAM. Admin access remained active.
- Action and owner
- Revoke access and alert on failed HR sync. IAM lead.
- Due and status
- 2026-11-28, in progress
- Closure test
- Simulate departure and verify access disappears within policy
- Approver and evidence
- Risk owner, ticket IAM-114 and retest results
Check before handing it over
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
Change decisionsMemo
Gather first
- Agenda or decision request
- Current performance measures and findings
- Proposed actions and participants
How to prepare it
- Write what decision is needed and list the reports or records the decision maker reviewed. Capture the date, people and decision authority.
- Record the decision, alternatives considered, any remaining risk and exactly who will do what by when.
- Send notes for factual review. File the approved record and add actions to the working tracker so progress reaches the next review.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Item
- Approve a fix for the missing access-removal retry.
- Inputs reviewed
- September test results and IAM incident root-cause notes.
- Decision
- Approve automatic retry plus daily reconciliation.
- Action and due date
- Platform lead to ship and test by 2026-11-28.
- Residual risk and follow-up
- Manual review remains until rollout. Check at December meeting.
Check before handing it over
The minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.
Common questions
Should we use FedRAMP 20x or Rev5?
Check the current rules by offering class and eligibility. Each path has different package and assessment requirements. Record the proposed path, program or agency dependencies, and assessor role before building evidence.
FedRAMP · 2026 Consolidated Rules timeline (opens in a new tab)What work continues after certification?
You need to keep the offering within its approved boundary, run monitoring and incident processes, keep required evidence current, and follow the applicable rules for changes and ongoing submissions.
FedRAMP · 2026 Consolidated Rules timeline (opens in a new tab)Official sources
- FedRAMP · 2026 Consolidated Rules timeline (opens in a new tab)
- FedRAMP · 20x (opens in a new tab)
- FedRAMP · Rev5 agency path (opens in a new tab)
- FedRAMP 2026 certification path selection (opens in a new tab)
- FedRAMP Rev5 certification rules (opens in a new tab)
- FedRAMP 20x certification packages (opens in a new tab)