Skip to main content

FedRAMP Documentation: From SSP, SAP, SAR and POA&M to CR26

Reuse accurate implementation and assessment evidence while adopting the current package structure. Rev5 SDR records include control implementation, parameters, verification, validation and independent assessment information.

Written by Boundera Team|February 7, 2025|5 min read

Main question

How should Rev5 teams update SSP, SAP, SAR and POA&M work for CR26?

Updated October 26, 2026. For Rev5 teams carrying existing documentation and assessment work into CR26.

If your FedRAMP documentation is organized around an SSP, SAP, SAR and POA&M, start the refresh by identifying what each record tells you about the actual service. Reuse accurate implementation and assessment evidence, then check what the updated package needs.

CR26 introduces a Certification Package Overview (CPO) and a Security Decision Record (SDR) into Rev5. The CPO replaces the historical base SSP. The SDR captures maintained security decisions and applicable control information. Adoption is phased, so confirm the provider's stage before changing the working package. CPO requirements, SDR requirements.

Preserve the useful work in existing documents

Treat the following as a suggested migration worksheet, rather than a one-to-one replacement of every legacy file:

Existing materialWork to carry forwardQuestion for the updated record
SSP service descriptions and diagramsAccurate scope, resources, dependencies and data flowsDoes the package overview describe the current offering?
SSP control implementation narrativesMechanisms, activities, ownership and inheritanceDoes the control summary explain the actual implementation?
SAP assessment planningScope, methods, scheduling and evidence responsibilitiesIs the current assessment plan aligned with applicable requirements?
SAR assessment resultsFindings, reviewer conclusions and evidence referencesCan independent review and provider responses be traced?
POA&M and vulnerability recordsOpen work, decisions, owners and supporting evidenceDoes the current response and reporting record preserve the relevant history?

Check each carried-forward statement. An accurate historical description can still be wrong for a service that has since changed.

Build the Certification Package Overview

The CPO must be supplied in human-readable and JSON formats. It pulls together information required by applicable rules, including public information, services, relevant policies, resources and flows, third-party resources, cryptographic-module documentation and assessment information. Its metadata includes the accountable official, version, update time and source of update. CPO rules.

For implementation, identify the owner of each source record before assembling the overview. Link the overview to maintained information where your delivery method permits it. Review whether a change to a service, contact or dependency will reach the overview without a separate manual reconstruction.

Complete the Rev5 control records in the SDR

The SDR requires human-readable and JSON information for applicable FedRAMP rules. The Rev5-specific control summaries also cover organization-defined parameters, implementation status, mechanisms or activities, inheritance, provider verification and validation, independent verification and validation, responses to comments and control-specific artifacts where applicable. SDR-CSO-FRR and SDR-CSF-CTF.

An imported narrative is a starting point. Review every applicable control for missing values, an unsupported status, unclear inheritance and gaps between the implementation statement and its evidence.

Keep verification and validation distinct. The SDR asks whether the implementation is appropriate for the control and whether it is in place and working as intended. Rev5 SDR requirements.

For example, an internal access-control review could retain the configured restriction, an explanation of why it addresses the control, and a test showing that an unauthorized attempt is blocked. This is an illustrative evidence pattern; use a test appropriate to the actual control and environment.

Retain assessment traceability

Independent Verification and Validation requires providers to supply assessors with evidence of implementation and effectiveness. Its Rev5 rules also address recurring control coverage and controls with negative findings. IVV requirements.

As you reorganize records, keep the links between the control, assessment result, provider response and supporting artifact. Agree with the assessor how the updated records will be reviewed. Avoid losing a finding's context by copying only its final status into a new system.

Move vulnerability tracking into the current workflow

VER defines reporting fields for vulnerability evaluations, impact history, response targets and final disposition, with separate information for accepted vulnerabilities. VER reporting requirements.

Use existing findings as migration inputs and review them against the current workflow. Preserve identifiers and evidence where useful, reevaluate context where necessary, and keep response owners attached to the work. Coordinate the transition before retiring an existing deliverable.

Agency records have a separate purpose. FedRAMP's Rev5 package guidance tells agencies to maintain agency POA&Ms for risks and actions they are responsible for, rather than blindly copying provider vulnerabilities into them. Agency package guidance.

Plan CPO and SDR adoption separately

For new Rev5 applications, both rulesets have a January 1, 2027 adoption date. For existing providers, CPO has a July 1, 2027 milestone and SDR has an August 1, 2027 milestone. Their grace-period ends are tied to the first independent assessment started after the respective date. Official Rev5 schedule.

Schedule the work backward from the applicable dates and your assessment plan. Assign owners for missing implementation details, verification and validation statements, assessor responses and artifact references.

How Boundera supports the remaining work

Boundera supports importing a supported SSP Appendix A document. Its agentic Rev5 workflows help teams inspect control requirements, implementation information, linked policies and gaps, including verification and validation fields. The provider still writes and reviews the statements that explain its own implementation.

CR26 walkthroughs support work on applicable rules and their missing inputs. Native vulnerability tickets support response ownership and tracking. Boundera integrates with Jira. It also integrates with ServiceNow.

Book a demo to review a control that still needs implementation, verification or validation work. For the wider sequence, see the Rev5 modernization roadmap.

Frequently asked questions

Does importing an SSP complete the Security Decision Record?

No. Applicable Rev5 control summaries also address organization-defined parameters, implementation status, verification, validation, independent review and artifacts. Check each record for missing information.

Do CPO and SDR have the same existing-provider adoption date?

No. The Rev5 matrix gives CPO a July 1, 2027 ongoing-adoption milestone and SDR an August 1, 2027 milestone. Their grace periods are tied to the first independent assessment started after the respective date.

Next step

If you want to turn this guidance into an execution plan, the product side handles control mapping, SSP drafting, and evidence collection.

Related articles