If you handle controlled unclassified information (CUI) for the Department of Defense, one document sits underneath everything else in your CMMC assessment: the system security plan. Assessors read it first, your SPRS score has to match it, and no other document can stand in for it.
What is a system security plan (SSP)?
A system security plan (SSP) is a document that describes a system's boundary, its environment, how each security requirement is implemented and how the system connects to other systems. For defense contractors, the SSP is required by NIST SP 800-171 requirement 3.12.4 and is the first document a CMMC Level 2 assessor reads.
In CMMC, the same requirement is numbered CA.L2-3.12.4. The CMMC Level 1 self-assessment does not call for an SSP, but Level 2 does. It also carries a hard rule: under 32 CFR 170.21, the SSP requirement cannot be placed on a plan of action and milestones (POA&M). You cannot promise to write it later.
NIST does not prescribe a format or a level of detail for an SSP. What it asks is that the plan conveys the information requirement 3.12.4 names. Our guide to CMMC and NIST 800-171 compliance explains where the SSP fits in the wider program.
What goes in a system security plan?
A usable SSP answers five questions an assessor will ask:
- What are you protecting? The CUI the system handles and where it lives.
- Where is the boundary? Which assets are in scope: those that process, store or transmit CUI, and those that protect them.
- What is the environment? Hardware, software, networks, cloud services and external service providers inside the boundary.
- How is each requirement met? A specific statement for each of the 110 NIST SP 800-171 Revision 2 requirements: who does what, with which tool or policy, and where the evidence is.
- What does it connect to? Other systems, partners and providers that exchange data with yours.
SSP template outline
NIST publishes a free CUI SSP template alongside SP 800-171 Revision 2, and it lets you mark each requirement as implemented, planned or not applicable. If you would rather build your own, this outline covers what an assessor looks for:
| Section | What to write | Evidence to point to |
|---|---|---|
| 1. System identification | System name, owner, purpose, and the types of CUI it handles | Contract clauses, data flow description |
| 2. Boundary and assets | What is in and out of scope, with an asset inventory by category | Network diagram, asset list |
| 3. Environment and connections | Hardware, software, cloud services, providers and external connections | Provider agreements, connection records |
| 4. Roles | Who owns, administers and approves the system and the plan | Org chart, role descriptions |
| 5. Requirement statements | One entry per requirement: how it is met, by whom, and its status | Policies, configurations, logs, training records |
| 6. Review log | Version, date, reviewer and what changed | Document history, approvals |
A template only gives you the headings. The value is in sections 2 and 5, where generic text has to become statements about your own systems.
SSP vs POA&M
The two documents are a pair. The SSP describes what is in place. The POA&M lists what is not yet in place, who will fix it and by when. They have to agree: an SSP that claims a control is fully implemented next to a POA&M that lists it as open tells an assessor that neither can be trusted. At Level 2, POA&Ms are only allowed for a limited set of requirements and only if the assessment score is high enough, so most of the work has to be finished in the SSP first.
Common SSP mistakes
- Copied template text. Statements that could describe any company do not show how your system works.
- A boundary that does not match reality. The plan says one thing and the network diagram, cloud accounts or provider list say another.
- Claims that do not match the score. Requirements marked implemented in the SSP but scored as not met in your SPRS score.
- No evidence trail. A statement with no policy, configuration or record behind it will not survive an interview.
- Forgetting providers. Cloud platforms and managed service providers that touch CUI belong inside the plan.
- Letting it go stale. The plan was accurate on the day it was written and nobody updated it after the next tool change.
How to write an SSP in five steps
- Scope the CUI. Identify where CUI enters, is stored and leaves, and draw the boundary around it.
- Inventory the assets. List what is inside the boundary and what protects it.
- Run a gap assessment. Score yourself against the 110 requirements so the plan reflects your real position.
- Write the statements. For each requirement, say how it is met, who owns it and where the evidence sits.
- Review and keep it current. Have an owner approve it, log each change and update it when your systems or providers change.
When the plan is ready, the 90-day C3PAO assessment readiness guide shows how it is reviewed in practice, and our CMMC 2.0 compliance guide covers the full path to certification. If you want help choosing a partner for the work, see how to choose a CMMC consultant.
Frequently asked questions
What is an SSP?
A system security plan is a document that describes a system's boundary and environment, how its security requirements are implemented and how it connects to other systems. For defense contractors it is required by NIST SP 800-171 requirement 3.12.4.
Is an SSP required for CMMC Level 1?
No. The Level 1 self-assessment does not require an SSP. Level 2, which covers CUI, does, and it cannot be deferred on a POA&M.
Is there an official SSP template?
NIST publishes a free CUI SSP template with SP 800-171, but it does not prescribe a format. Any structure works as long as it conveys what requirement 3.12.4 asks for and covers all 110 requirements.
Can the SSP go on a POA&M?
No. Under 32 CFR 170.21, the system security plan requirement is one of the requirements that cannot be placed on a POA&M, so the plan must exist at the time of assessment.
How often should an SSP be updated?
NIST says the plan must be updated periodically. In practice, update it whenever your boundary, tools or service providers change, and review it at least once a year.
Key takeaways
- An SSP describes your system boundary, environment, requirement-by-requirement implementation and connections.
- It is required for CMMC Level 2 and cannot be deferred on a POA&M.
- NIST offers a template but no fixed format; what matters is accurate, evidence-backed statements.
- The SSP, the POA&M and your SPRS score must agree with each other.

