How to Write a System Security Plan for NIST 800-171

ISO Cloud Consulting editorial team
Blueprint-style illustration of a workshop floor plan with a dashed security boundary around one room

To write a System Security Plan for NIST SP 800-171, define the boundary of the environment that handles CUI, describe how it is built and connected, and write a specific, checkable statement for each of the 110 requirements. Keep it true to today, approve it, and update it whenever the environment changes.

Key facts

  • Required by NIST SP 800-171 Rev 2 requirement 3.12.4 for any system that handles CUI.
  • No point value in SPRS, but without a current SSP an assessment "could not be completed".
  • Cannot be placed on a POA&M for Conditional CMMC Level 2 status.
  • Must document every in-scope asset category and any external service provider's responsibilities.
  • Assessors test each statement through 320 objectives in NIST SP 800-171A.

What is a System Security Plan, in plain English?

An SSP is a written description of the environment where you handle CUI and how you protect it, requirement by requirement. It is the first document an assessor reads and the reference for every question they ask afterwards.

NIST SP 800-171 Rev 2 requirement 3.12.4 asks you to "develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems." Those four elements, boundary, environment, implementation and connections, are the skeleton of every good SSP.

What sections should an SSP have?

A practical SSP has seven sections. The table shows what each covers and the gap assessors most often find.

Section What it covers Common gap
1. System identification Name, owner, CAGE codes, contracts supported Missing CAGE codes, so the SSP cannot be tied to SPRS
2. Boundary and scope In-scope people, locations and assets by category; what is out of scope and why "Everything" in scope, or exclusions with no justification
3. Environment of operation Offices, shop floor, remote work, cloud services Remote work and personal devices not mentioned
4. Diagrams and data flows Network diagram, CUI flows in and out Diagram out of date or missing the IT provider's access
5. Connections and providers Interconnections, cloud and managed service providers, their responsibility matrices No customer responsibility matrix
6. Requirement statements All 110 requirements: status, implementation, responsible role, evidence Statements that restate the requirement
7. Governance Enduring exceptions, POA&M reference, version history, approval Unsigned, undated or never reviewed

How do you define the system boundary?

List every asset that handles CUI or protects the assets that do, then place each one in a CMMC asset category. The boundary is the line around everything in scope.

The CMMC rule defines five categories for Level 2:

  • CUI assets store, process or transmit CUI, such as CAD workstations and the file server holding drawings. Assessed against all requirements.
  • Security protection assets provide security functions, such as the firewall, identity service and backup system. Assessed against the relevant requirements.
  • Contractor risk managed assets could handle CUI but are prevented from doing so by your policies and practices. Documented in the SSP.
  • Specialized assets cannot be fully secured, such as CNC machines, test equipment and other operational technology. Documented and managed under your risk-based policies.
  • Out-of-scope assets cannot handle CUI and do not protect CUI assets. Be ready to justify why.

For a machine shop, the most useful scoping decision is usually an enclave: a small, separate environment where CUI lives, so the rest of the business stays out of scope.

How do you write a strong implementation statement?

A strong statement answers who, what, where, how often and what evidence proves it, in a few sentences. If an assessor cannot verify it by looking at something or asking someone, rewrite it.

Two examples for Harborline Precision Machining (fictional):

Requirement Weak statement Strong statement
3.3.1 Audit logs “Audit logs are enabled on all systems.” “Sign-in, file-access and administrator events from the enclave's 14 endpoints, file server and firewall are sent to the log service and kept for 12 months. Keystone Managed IT (fictional) reviews alerts daily; the IT lead reviews a summary weekly and records it in the log review register.”
3.8.3 Media sanitization “Media is disposed of securely.” “Drives leaving the enclave are wiped with the manufacturer's secure-erase tool and verified, or physically destroyed. Each is logged by serial number on the media disposal record, signed by the IT lead. Paper drawings go into the locked shred bin, emptied monthly by a vendor that issues a certificate of destruction.”

Keep a consistent pattern for every statement: status, how it is implemented, responsible role, provider responsibility if any, and evidence location.

How do you handle an IT provider or cloud service in the SSP?

Document what each provider does, what you still do, and where that split is written down. The CMMC rule requires the customer responsibility matrix (CRM) to be documented or referred to in your SSP.

If a cloud service stores or processes CUI, it must be FedRAMP Moderate authorized or meet equivalent security requirements, as DFARS 252.204-7012 requires. If a managed IT provider administers your systems, its services are part of your assessment scope. In each requirement statement, name which party does what. "Handled by our MSP" is not a statement; "The MSP patches servers monthly under the CRM; the IT lead verifies the patch report each month" is.

How do you write an SSP, step by step?

Work from scope to statements to evidence, in that order. Writing statements before the boundary is settled wastes the most time.

  1. Confirm CUI. Identify which contracts and documents involve CUI, and confirm with the customer in writing.
  2. Inventory and categorize. List every asset and place it in one of the five categories.
  3. Draw it. Produce the network diagram and CUI data flows, including remote access and provider connections.
  4. Collect CRMs. Get responsibility matrices from every cloud and managed service provider.
  5. Draft statements family by family. Work through all 14 families. Write what is true today and mark gaps as not met.
  6. Verify against evidence. Open each setting or record a statement names. Fix whichever is wrong.
  7. Link the POA&M. Every not-met requirement gets a POA&M entry.
  8. Approve and schedule review. Have leadership approve and date it, and set the next review before your annual affirmation.

How much detail is enough?

Enough for an assessor to know exactly what to look at and whom to ask, and no more. Most good statements are three to six sentences.

A useful test is to hand a statement to someone outside IT and ask them to find the evidence. If they can go straight to the right screen, log or record, the statement is detailed enough. If they need to ask which system, which people or how often, add that detail. Do not paste configuration dumps or screenshots into the plan itself; point to where they are stored. Long, generic text makes the plan harder to verify, and assessors tend to read it as a sign that the plan was copied rather than written.

How often should you update the SSP?

Review it in full at least once a year, before your affirmation, and update it whenever the environment changes. Requirement 3.12.4 says "periodically", and a plan that no longer matches the system does not meet it.

Typical triggers for an update are a new system or cloud service, a change of IT provider, an office or shop-floor move, a new contract that brings in new kinds of CUI, and every closed POA&M item. Keep a version history with dates and approvers, so you can show when each change was made and who signed it off.

What SSP mistakes do assessors see most?

  • Aspirational statements. Describing the planned setup instead of the current one.
  • Copied text. Statements from a sample that name products or roles you do not have.
  • Silent specialized assets. CNC controllers and test equipment left out entirely.
  • Stale content. An SSP approved once and never updated, though 3.12.4 requires periodic updates.
  • No owner. Nobody inside the company can explain it, because a provider wrote it.

The NIST 800-171 System Security Plan (SSP) Template ($99) gives you the structure and prompts; see the SSP template page for what a good statement looks like. To score the result, use our SPRS scoring guide, or get the SSP with the scoring workbook and POA&M tracker in the CMMC Level 2 Starter Bundle ($175, was $207). A template helps you prepare; the plan must describe your own system.

Last reviewed: 29 September 2026. CMMC rules are still moving. Check your contract, your prime's flowdown and the current rule before you rely on any date.

Back to blog

Frequently asked questions

Who should write the System Security Plan?

Someone inside the company who understands how your systems actually run, usually the IT lead or operations manager, with input from your IT provider. Outside help is useful for structure and review. Ownership should stay internal, because assessors interview your staff and the Affirming Official relies on the plan being accurate.

Can one SSP cover several locations?

Yes, if they form one system with a shared boundary, common controls and one owner. Describe each location's environment, physical protections and connections. If sites run very different systems or have separate IT, separate SSPs can be clearer, and each must be tied to the CAGE codes it supports in SPRS.

Should the SSP include requirements we have not implemented yet?

Yes. Every one of the 110 requirements needs an entry. For gaps, state plainly that the requirement is not met, describe what is in place today, and reference the POA&M item with its target date. Hiding gaps makes the plan inaccurate, and an inaccurate plan undermines both your score and your affirmation.

What evidence should the SSP point to?

Evidence that proves each statement: configuration exports or screenshots, access review records, training completion records, visitor logs, scan reports, disposal records and approved policies. Name the evidence and where it is stored rather than pasting it into the plan. That keeps the SSP readable and lets assessors go straight to the proof.

Templates that do this job

Editable Word and Excel files. Instant download. Licensed for one organization.