What requirement 3.12.4 says
The requirement, in the Security Assessment family of NIST SP 800-171 Revision 2, reads:
“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.”
The CMMC Level 2 requirements are identical to the requirements in NIST SP 800-171 Revision 2, even though NIST has withdrawn Revision 2 and replaced it with Revision 3.
What the plan must describe
From the requirement text, the plan describes:
- the system boundaries;
- the system environments of operation;
- how the security requirements are implemented;
- the relationships with or connections to other systems.
The CMMC rule's definition adds that the plan describes the security controls in place or planned and the system components included in the system.
Under the CMMC scoring rule, the plan describes each information system within the CMMC Assessment Scope.
32 CFR 170.19 also requires you to document in the plan how each in-scope asset category is treated: CUI assets, security protection assets, contractor risk managed assets and specialized assets.
If an external service provider handles CUI or security protection data for you, its use, its relationship to you and the services it provides must be documented in your system security plan.
Enduring exceptions, where full compliance is not feasible, must be documented in the plan, and an enduring exception described there with its mitigations is assessed as MET.
If the DoD CIO has adjudicated a requirement as not applicable, or an alternative measure as equally effective, the adjudication must be included in the plan to be considered in an assessment.
The NIST SP 800-171A objectives for 3.12.4
NIST SP 800-171A has eight assessment objectives for 3.12.4. The assessment determines if:
| Objective | 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. |
Under the CMMC scoring rule, a requirement is MET only when its objectives are satisfied based on evidence.
For 3.12.4, the documents NIST SP 800-171A lists for an assessor to examine include the system security plan itself and records of its reviews and updates.
Write the update frequency into the plan, and keep a dated record each time you review it.
What format it takes
NIST SP 800-171 says: “There is no prescribed format or specified level of detail for system security plans.” What matters is that the plan conveys the information 3.12.4 requires.
The plan need not be a single document: it can be a collection of documents, including ones that already exist.
NIST describes the plan as explaining, at a high level, how the controls meet the requirements, without detailed technical descriptions of their design or implementation.
Evidence has to be final: the CMMC scoring rule does not accept working papers, drafts, or unofficial or unapproved policies.
For a C3PAO assessment, the results entered in the CMMC instance of eMASS include the name, date and version of the plan.
Why there is no score without one
The methodology scores by reviewing a system security plan, so it is not possible to conduct the assessment without one.
The absence of a system security plan results in a finding that “an assessment could not be completed due to incomplete information and noncompliance with DFARS clause 252.204-7012.”
The DFARS 252.204-7012 guide covers the clause that finding names.
That is why 3.12.4, the requirement to have a system security plan, carries no point value in the template: without the plan there is no score, not a lower one.
Under DFARS 252.240-7997, the assessment clause DoD contracting officers have used since February 1, 2026, DoD posts its Medium and High assessment scores to SPRS for each system security plan it assesses.
The SPRS score guide and the calculator show how the rest of the score is worked out.
Why it cannot go on a POA&M
The CMMC rule is the same: an up-to-date system security plan must be in place at the time of assessment, and it is one of the requirements that can never go on a CMMC POA&M.
So the plan has to be in place and up to date before a CMMC Level 2 assessment, whether you assess yourself or a C3PAO does; the POA&M rules guide lists the other requirements that stay off a POA&M.
NIST SP 800-171 uses the plan for enduring exceptions, while individual, isolated or temporary deficiencies are managed through the plans of action in requirement 3.12.2.
How CMMCSync helps
The SSP Generator turns your organization profile and control statuses into a system security plan you can version and export. On Foundations (Free), exports carry a draft watermark; on Maintain, they do not. See the features page.
Sources
- NIST SP 800-171 Revision 2, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations
- NIST SP 800-171A, Assessing Security Requirements for Controlled Unclassified Information (June 2018)
- NIST SP 800-171 DoD Assessment Methodology, Version 1.2.1 (June 24, 2020)
- DoD class deviation 2026-O0025, FAR Overhaul Part 40 and DFARS Part 240 (effective February 1, 2026)
- DoD class deviation 2026-O0025, Revision 3 (September 3, 2026), with DFARS 252.240-7997 in Attachment 1
- 32 CFR 170.4, Acronyms and definitions
- 32 CFR 170.14, CMMC Model
- 32 CFR 170.17, CMMC Level 2 certification assessment and affirmation requirements
- 32 CFR 170.19, CMMC scoping
- 32 CFR 170.21, Plan of Action and Milestones requirements
- 32 CFR 170.24, CMMC Scoring Methodology
General information, not legal advice.