Most contractors know they need a System Security Plan. Far fewer have written one that holds up when an assessor starts asking questions. This guide covers what the plan has to say, how to build it, and how to keep it honest.
Quick Answer
A System Security Plan describes your system boundary, the environment it runs in, how you meet each NIST SP 800-171 requirement, and how your system connects to others. Write it from what your people and tools do today, assign an owner to every requirement, point to the evidence, and review it on a schedule. It is requirement 3.12.4 in NIST SP 800-171 Revision 2, which is the version CMMC uses now.
What a System Security Plan Is
NIST SP 800-171 requirement 3.12.4 asks organizations to develop, document, and periodically update system security plans. The plan has to describe four things, the system boundary, the environment the system operates in, how each security requirement is implemented, and the relationships with or connections to other systems.
Two details in the NIST wording are worth knowing. The plan can be several documents instead of one, and it is expected to point to existing policies and procedures instead of copying them. NIST also sets no required format or level of detail. That freedom is useful, but it also means nobody hands you a pass for a thin plan. The assessor decides whether what you wrote is enough.
The SSP matters beyond the paperwork. Under the DoD assessment methodology, an assessment cannot be completed without one, so it comes first. If you want the bigger picture of how the SSP, the POA&M, and your SPRS score fit together, our post on SSP, POA&M, and SPRS explained walks through it.
What Your SSP Has to Cover
| Section | What it should say |
|---|---|
| System boundary | Which systems, people, facilities, and services are in scope, and which are not. This is where you name where Controlled Unclassified Information is stored, processed, and transmitted. |
| Environment of operation | How the system is hosted and used day to day, including cloud services, remote work, and the external providers involved. |
| Requirement implementation | For each of the 110 requirements, how you meet it, with the tool, setting, or process named. |
| System connections | Other systems your boundary connects to, who runs them, and how the connection is controlled. |
| Roles and responsibilities | Who owns each requirement, and who approves changes to the plan. |
The boundary is the part that most plans get wrong, and every later section depends on it. If the boundary is vague, every implementation statement inherits that problem. The DoD CIO scoping guide for Level 2 sorts assets into categories, and a clear boundary uses them.
How to Write an SSP Step by Step
- Define the boundary firstMap where CUI enters, where it lives, and where it leaves. List the systems, people, and providers that touch it. Anything outside that line gets a short note explaining why it is out.
- Describe the environmentWrite a plain account of how the system is hosted and used. Name the cloud services, the remote access paths, and the outside providers, and say what each one handles.
- Record the connectionsList every other system your boundary talks to. For each one, say who runs it and what controls the link.
- Answer all 110 requirementsFor each one, write what you do, with what, and who does it. Name the real tool, setting, or process. A statement that only repeats the requirement tells the assessor nothing.
- Assign an owner to each requirementUse a role and a named person. Assessors interview these people, so they need to be able to explain their own control.
- Point to the evidenceNext to each statement, note where the proof lives, such as a configuration export, a policy, a log, or a training record.
- Reconcile it with the POA&MAny requirement that is not fully met belongs on the POA&M, not described as done in the SSP. The two documents have to agree.
- Review, approve, and date itHave leadership sign off, record the version, and set the next review date.
If you want a second set of eyes before an assessor sees it, a CMMC readiness assessment tests the plan against what your environment is doing.
What a Good Implementation Statement Looks Like
The difference between a weak statement and a strong one is specificity. Compare two answers to the same requirement on multifactor authentication.
Weak
The organization uses multifactor authentication for system access in line with policy.
Stronger
All users sign in to Microsoft 365 GCC High with an authenticator app. Conditional access blocks sign-ins without it. The IT manager reviews the policy each quarter.
Why it works
It names the tool, the setting, and the owner, so an assessor can check it in minutes.
One caution on length. NIST allows a plan to describe controls at a high level, but assessors test what you wrote against what they see. The more specific the statement, the easier it is to confirm, and the harder it is for a gap to hide behind loose wording.
Keeping the SSP Current
NIST says to update the plan periodically and does not give a number. Our advice is simple. Review it on a fixed schedule at least once a year, and update it any time something changes that touches a requirement. A new system, a new vendor, a cloud migration, a departed administrator, or a closed POA&M item can all make the plan wrong overnight.
The plan is also only as good as the evidence behind it. A statement nobody can back up is a liability, because an assessor will ask for the proof and then ask the control owner to explain it. Our post on best practices for CMMC assessment preparation covers how to test the plan before the assessment, and managed CMMC compliance covers keeping it current afterward.
Common SSP Mistakes
- Starting from a template and leaving the generic wording in place.
- Drawing the boundary too wide or too loosely, so scope is unclear.
- Repeating the requirement text instead of describing what the organization does.
- Describing a requirement as met in the SSP while the same item sits open on the POA&M.
- Naming control owners who have never seen the plan.
- Treating the plan as finished once it is signed.
Revision 2 and Revision 3
Revision 3 of NIST SP 800-171 moves the SSP requirement into a new Planning family as 03.15.02, and 3.12.4 from Revision 2 is withdrawn and incorporated there. CMMC currently assesses against Revision 2, so write to 3.12.4 now. A plan built on the four items above carries over without much rework. Our post on understanding Revision 3 covers what else changed.
A note on timing. In July 2026 the Department announced it was suspending the CMMC Phase II rollout. Phase I self-assessment requirements remain in place, and the DFARS 252.204-7012 obligations still apply to covered contractors. Self-assessments and select government-led assessments continue to enforce the Revision 2 requirements. See the Department announcement of July 13, 2026, 32 CFR Part 170, and DFARS 252.204-7025 for the details. Whichever way the rollout goes, a plan that matches how you operate is the same plan you will need.
CMMC Readiness AssessmentSee how your plan holds up against the way your environment really runs, before an assessor does.
Frequently Asked Questions
What is a System Security Plan?
Is an SSP required for CMMC?
What is the difference between an SSP and a POA&M?
How long should an SSP be?
How often does an SSP need to be updated?
Can I use an SSP template?
Does Revision 3 of NIST SP 800-171 change the SSP requirement?
Want a second opinion on your System Security Plan?
Sentinel Blue reviews SSPs against the way your environment runs, so gaps show up before an assessor finds them.