Evidence prep: the SSP is the assessment
An assessor cannot test what is not described. The System Security Plan tells the 3PAO what the system is, where its boundary sits, and how each control is implemented. Everything else in the assessment traces back to it.
Last updated: 2026-11-22.
The System Security Plan
The SSP is the core document of the authorization package. It describes the system, its authorization boundary, the data it handles, and how every control in the target baseline is implemented. Low runs about 125 controls, Moderate about 325, High about 421, so the document grows with the level. Writing it typically takes 3–6 months, and it is the phase where authorization schedules most often slip.
Who writes it matters. The CSP writes it, or a separate advisory firm writes it. The assessing 3PAO cannot: independence rules bar a 3PAO from writing the SSP for a system it will assess. FedRAMP publishes an SSP template, and the document is increasingly produced in machine-readable OSCAL rather than as a Word file.
What travels with the SSP
The SSP on its own is not a package. The attachments carry the detail:
- Policies and procedures per control family. One set for each of the 20 NIST SP 800-53 families, describing how the organization operates day to day, not how it wishes it did.
- Incident response plan. Roles, escalation, contacts, and evidence that it has been exercised.
- Contingency plan. Backup, recovery, and continuity for the federal environment.
- Configuration management plan. Baselines, change control, and how deviations are recorded and approved.
- Inventory. Every component in the boundary: systems, services, network devices, and their interconnections. An incomplete inventory is one of the first things an assessor notices.
OSCAL and the machine-readable mandate
OSCAL, the Open Security Controls Assessment Language, is NIST's machine-readable format for control catalogs, system security plans, assessment plans, and assessment results. NIST publishes the full 800-53 catalog in OSCAL. RFC-0024, issued January 13, 2026, mandates machine-readable OSCAL packages for all FedRAMP providers, with requirements effective September 30, 2026.
Under FedRAMP 20x, the direction is further toward machine-validated evidence: measurable Key Security Indicators replace narrative control documentation as the primary proof. KSI counts vary between sources and change as the rules dataset is updated, so this site publishes no settled number. The practical point for preparation is the same either way: evidence that a machine can validate beats evidence that only a human can read.
What assessors ask for first
The assessment opens with documentation review. The 3PAO builds its Security Assessment Plan from the SSP, so the SSP, the boundary definition, and the inventory are the first things the assessor works from. After that, the early requests follow a pattern:
- Recent vulnerability scan results for the operating system, databases, and web applications, with the POA&M showing how findings are tracked.
- Access records showing who can reach the federal environment, with what privileges, and when access was last reviewed.
- Configuration evidence tying the live systems to the written baselines.
- Log samples demonstrating that audit logging works and that someone looks at the output.
Having these ready before the assessment starts is the difference between a smooth opening and a first week spent hunting for files.
Evidence that holds up, and evidence that does not
Assessors test controls and ask for proof. Proof that holds up is dated, specific, and tied to the system in scope: scan output with timestamps, configuration exports, signed attestations, and logs that can be queried. Proof that does not hold up is generic: a vendor's marketing page, a policy nobody follows, a screenshot with no date, or a document describing a different environment. When a finding is remediated, closure needs evidence too, verified by a 3PAO at the next assessment.
Tooling that helps
GRC and compliance-automation platforms exist largely to make this work less manual: continuous control monitoring, automated evidence collection, SSP generation, and POA&M management. The main names in the FedRAMP space, one line each:
| Platform | What it does for evidence prep |
|---|---|
| Vanta | Automated evidence collection and continuous control monitoring, SSP generation, POA&M support, OSCAL export; supports Rev5 and 20x Low/Moderate. |
| Drata | Continuous monitoring and AI-assisted evidence collection across frameworks, including FedRAMP. |
| Secureframe | Compliance automation with OSCAL SSP generation and POA&M management. |
| Paramify | FedRAMP package and documentation automation; generates OSCAL SSPs and POA&Ms. Public pricing around $8,000–$60,000 per year. |
| RegScale | OSCAL-native GRC and continuous controls monitoring; compliance-as-code positioning. |
| Telos Xacta | Federal-native GRC and RMF platform with OSCAL profiles and authorization packages; built for agencies and DoD as well as CSPs. |
| Ignyte | Automated continuous monitoring and assessment across FedRAMP and other frameworks; the parent company is itself a FedRAMP 3PAO. |
| TalaTek | FedRAMP-accredited GRC platform for continuous monitoring and automated evidence, from a firm that is also a 3PAO. |
Tooling helps with collection and organization. It does not write a good SSP on its own, and it does not fix a control that is not implemented. Buy the tool for the evidence workflow, not as a substitute for the remediation work.
Frequently asked questions
How long does SSP writing take?
The documentation phase, SSP plus attachments, typically takes 3–6 months. It is the phase where schedules most often slip, usually because the SSP cannot be finished until the boundary is settled and the gaps are closed.
Do I need OSCAL, or is a Word SSP still accepted?
RFC-0024 mandates machine-readable OSCAL packages for all FedRAMP providers, with requirements effective September 30, 2026. New packages should be built in OSCAL. The FedRAMP templates and the NIST OSCAL catalog are the starting points.
What is a POA&M, and when do I need one?
The Plan of Action and Milestones tracks every open weakness with a unique ID, affected control, severity, asset, owner, milestones, scheduled completion date, status, and closure evidence. CSPs must use the FedRAMP POA&M template, and it is updated monthly as part of continuous monitoring. Starting it during the gap assessment saves rework.