Free tool · 25 questions · about 6 minutes
Would your SSP hold up in front of an assessor?
Your System Security Plan (SSP) is the one CMMC document you can't defer to a POA&M. Answer questions about it, never upload it, and see where an assessor would stop: each red flag lands on the section of the plan it belongs to.
No uploads, ever. Your answers stay in your browser. Nothing is sent unless you ask for the outline.
Answer about your plan · don't upload it
Have your System Security Plan open beside you. "Partly" and "Not sure" are fine answers: both raise a flag worth checking.
1. Plan identification and approval
2. System boundary
3. Environment of operation
4. Asset inventory and categories
5. Connections and external providers
6. How each requirement is implemented
7. Open items and the POA&M
8. Review and update
One more thing
Your answers stay in this browser tab. Nothing is sent unless you ask for the outline below.
Fig. · Your System Security Plan
System Security Plan
- 1Identification
- 2Boundary
- 3Environment
- 4Assets
- 5Providers
- 6110 requirements
- 7POA&M
- 8Upkeep
Answer the questions to see where your SSP would draw an assessor's attention.
What the SSP requirement asks · NIST SP 800-171 Rev. 2, 3.12.4 · as of Nov 5, 2026
The eight things an assessor checks
Assessment objectives, NIST SP 800-171A · Determine if:
- 3.12.4[a]a system security plan is developed.
- 3.12.4[b]the system boundary is described and documented in the system security plan.
- 3.12.4[c]the system environment of operation is described and documented in the system security plan.
- 3.12.4[d]the security requirements identified and approved by the designated authority as non-applicable are identified.
- 3.12.4[e]the method of security requirement implementation is described and documented in the system security plan.
- 3.12.4[f]the relationship with or connection to other systems is described and documented in the system security plan.
- 3.12.4[g]the frequency to update the system security plan is defined.
- 3.12.4[h]system security plan is updated with the defined frequency.
The outline's eight sections
1. Plan identification and approval
Says which system the plan covers, who owns it and who approved this version.
3.12.4[a]; ForgePoint practice
2. System boundary
Draws the line around everything that handles CUI, and says what is outside it.
3.12.4[b]
3. Environment of operation
Describes where and on what the system runs.
3.12.4[c]
4. Asset inventory and categories
Lists the assets in scope and sorts them into the CMMC Level 2 asset categories.
32 CFR 170.19(c)(1), Table 3
5. Connections and external providers
Names every other system this one connects to and every provider that handles CUI or security data.
3.12.4[f]; 32 CFR 170.19(c)(2)
6. How each requirement is implemented
For each of the 110 requirements: how it is met today, by whom, and with what evidence.
3.12.4[d], [e]
7. Open items and the POA&M
Keeps known gaps in the plan of action, not hidden in the SSP's prose.
3.12.2; 32 CFR 170.21
8. Review and update
Says how often the plan is reviewed and records that it was.
3.12.4[g], [h]
Sources
- NIST SP 800-171 Rev. 2, requirement 3.12.4 (NIST CSRC)
- NIST SP 800-171A (June 2018), 3.12.4 assessment objectives, p. 52 (withdrawn May 14, 2024; superseded by SP 800-171A Rev. 3)
- 32 CFR 170.19, CMMC scoping: asset categories and external service providers (eCFR)
- 32 CFR 170.21, Plan of Action and Milestones requirements (eCFR)
- 32 CFR 170.24, CMMC Scoring Methodology (eCFR)
NIST withdrew SP 800-171A (June 2018) on May 14, 2024, together with SP 800-171 Rev. 2; DoD still requires Rev. 2. Questions marked "ForgePoint practice" are our recommendations, not requirements.
Questions
System Security Plans, answered
What does a CMMC Level 2 System Security Plan have to contain?
- NIST SP 800-171 requirement 3.12.4 asks for 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, and that are periodically updated. Its assessment objectives also check that requirements marked not applicable are identified and approved, and that the update frequency is defined and followed.
Can the SSP go on a POA&M?
- No. The CMMC rule names the System Security Plan (CA.L2-3.12.4) among the requirements that may never be placed on a Level 2 POA&M, and without a current SSP an assessment can't be completed.
Do I have to describe my MSP in the SSP?
- If an external service provider handles your CUI or security protection data, the CMMC rule requires the relationship to be documented in your SSP and described in the provider's service description and customer responsibility matrix.
Do I upload my SSP?
- Never. You answer questions about it; the plan stays with you. Please don't send CUI, contracts, credentials or security evidence to ForgePoint.
Is the result an SPRS score?
- No. It reflects your own answers about your SSP, weighted by ForgePoint. It isn't an assessment, an SPRS score or a determination that any requirement is met.
What's in the SSP outline template?
- A Word document in the same eight sections as the review, with guidance for each, a fill-in table for all 110 NIST SP 800-171 Rev. 2 requirements (status, how it's met today, who does it, evidence) and appendices for assets, providers, connections and change history.
What happens to my answers?
- They stay in your browser tab. If you ask for the outline, ForgePoint keeps your name, work email, company, the suggested next step and the date in its CRM, not your answers, and the PDF report is drawn on request and not kept.
Where it leads