All guides

CMMC · 5 min read · Updated Nov 10, 2026

Your System Security Plan in plain English: the zero-point requirement you can’t skip

NIST SP 800-171 requirement 3.12.4, the System Security Plan, is worth zero SPRS points but no assessment is complete without it. What goes in an SSP for a small defense supplier, in plain English.

By Brian D. Roach, founder of PolicyScore and 24-year U.S. Navy cyber veteran

The short version

In NIST SP 800-171 there is one requirement worth zero points in your SPRS score, and you can’t finish a valid assessment without it. It’s requirement 3.12.4, the System Security Plan (SSP). If you’re starting on 800-171, start here. Everything else hangs off it.

What the SSP is

The System Security Plan is a document that describes your environment as it actually is today. It answers three questions:

  • What systems are in scope? The computers, servers, cloud services and people that store, process or send Controlled Unclassified Information (CUI).
  • Where does the sensitive data live and move? Where CUI comes in (for example, drawings from a prime), where it’s stored, and where it goes.
  • How is each requirement met? For each of the 110 requirements, a short description of what you do, or a note that it isn’t met yet and is on your plan to fix.

Why a zero-point requirement matters so much

Most 800-171 requirements subtract 1, 3 or 5 points from your SPRS score when they aren’t met. Requirement 3.12.4 has no point value. That doesn’t make it optional.

Under the DoD Assessment Methodology, an assessment can’t be completed without a System Security Plan. Without an SSP, you have nothing to post, however good your controls are.

Describe the network you have, not the one you planned

The most common mistake is writing the SSP from a template or a project plan and never checking it against reality. An SSP that says “all remote access uses MFA” when the shop-floor PC still has remote desktop open is worse than having no SSP at all. Your SPRS score is a statement to the government, and the SSP is the evidence behind it.

A good test: could someone new to your company walk through the building and the cloud admin consoles with your SSP in hand and find that it matches?

What goes in a small supplier’s SSP

You don’t need a 200-page binder. For most small businesses, a clear document of 15 to 40 pages covers it:

  • System boundary: a simple list or diagram of what’s in scope, and what’s deliberately kept out (for example, a separate guest Wi-Fi).
  • Environment: office locations, the number of users, the main systems (email, file storage, ERP or CAD), and cloud services.
  • CUI flow: how CUI arrives, where it’s stored, who can reach it, and how it leaves.
  • Roles: who owns security decisions, who administers systems, and who your outside IT provider is.
  • Connections: links to other systems, such as a prime’s portal or a managed service provider’s remote tools.
  • Requirement-by-requirement status: for each of the 110 requirements, how it’s met, or a reference to the Plan of Action and Milestones (POA&M) item that will close it.
  • Review date: when the SSP was last checked and who approved it.

Keep it current

An SSP is a living document. Update it when something real changes: a new office, a new cloud service, a new IT provider, or a closed POA&M item. A once-a-year review is the minimum. Tying a review to each re-assessment is better.

Where PolicyScore helps

PolicyScore’s free NIST 800-171 assessment walks through all 110 requirements in plain language, shows the point value of each one as you answer, and tells you to make the SSP your first fix if you don’t have one. On Pro, it drafts your System Security Plan from your answers, notes and evidence, ready to edit in Word.

PolicyScore is a self-assessment tool, not a certification. Check your contract and the current DoD guidance for your situation.

Sources

  • NIST SP 800-171 Rev. 2, requirement 3.12.4 (System Security Plan)
  • DoD Assessment Methodology for NIST SP 800-171 (scoring and the SSP requirement)

Frequently asked questions

What is a System Security Plan (SSP) in NIST 800-171?
It is the document required by requirement 3.12.4 that describes which systems handle CUI, where that data lives and moves, and how each of the 110 requirements is met or planned.
How many SPRS points is the System Security Plan worth?
Zero. But under the DoD Assessment Methodology an assessment cannot be completed without an SSP, so without one you have no score to post.
How long should a small business SSP be?
For most small businesses, a clear document of 15 to 40 pages is enough. It should describe the network you actually have, not the one you planned.

Put this into practice

PolicyScore walks you through every step above, free to start.

General information, not legal, compliance or insurance advice. PolicyScore is a self-assessment tool and is not a C3PAO or an insurance producer.

See where you stand in 16 questions

Start with the free Cyber Readiness Score. No credit card needed, and your answers can pre-fill matching questions in the full assessments later.