CA.L2-3.12.4: System Security Plan Assessment Guide

Official reference

The requirement

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.

DoD CMMC Assessment Guide, Level 2, version 2.13. CA.L2-3.12.4; requirement and objectives, printed page 208 ↗

Assessment objectives

What must be established

Determine if each applicable objective is satisfied. The labels below follow the cited DoD assessment guide.

[a]
a system security plan is developed;
[b]
the system boundary is described and documented in the system security plan;
[c]
the system environment of operation is described and documented in the system security plan;
[d]
the security requirements identified and approved by the designated authority as non-applicable are identified;
[e]
the method of security requirement implementation is described and documented in the system security plan;
[f]
the relationship with or connection to other systems is described and documented in the system security plan;
[g]
the frequency to update the system security plan is defined; and
[h]
system security plan is updated with the defined frequency.

MET requires evidence that all applicable objectives are satisfied. Final, approved evidence is needed. A NOT APPLICABLE determination needs a scope-based basis and is equivalent to MET for scoring. Enduring exceptions and temporary deficiencies have specific conditions under 32 CFR 170.24; they are not a general permission to defer implementation.

GAVII Cybersecurity assessment approach

Connect the objective to the evidence

Use the SSP as the map connecting assets, information flows, responsibilities, and safeguards. A template filled with future intentions does not describe the current system, and an up-to-date SSP is required to complete the assessment.

Assessment focus: objectives [a], [b], [c], [d], [e], [f], [g], [h]. Use the methods together; a single example does not establish every objective.

Examine

Review the SSP, boundary and data-flow diagrams, implementation descriptions, connected systems, and revision records.

Interview

Who maintains the SSP when systems, providers, or implementation responsibilities change?

Demonstrate or test

Select an implementation statement and trace it to the actual configuration and responsible owner, then reconcile a recent change.

Evidence gaps to look for

The SSP describes an obsolete boundary.
Generic statements cannot be connected to actual implementation or provider responsibilities.

GAVII Cybersecurity’s examples illustrate ways to examine, interview, and test. They are not a mandatory artifact list or a guarantee of an assessment result. Combine methods and address every applicable objective in the actual scope.

Assessment constraints

Scoring and POA&M eligibility

Assessment prerequisite

An up-to-date SSP must be in place at assessment. Without it, the assessment cannot be completed because required information is missing. Do not treat this prerequisite as an ordinary 1-point deduction.

Scoring rule ↗

POA&M: Not eligible

This requirement is explicitly excluded by 32 CFR 170.21(a)(2)(iii); it cannot be deferred on the POA&M used for Conditional Level 2 status.

POA&M rule ↗

Conditional Level 2 requires a score of at least 88 out of 110 and satisfaction of every eligibility condition. A 1-point requirement is not automatically eligible. The permitted POA&M must be closed through the appropriate closeout assessment within 180 days of the Conditional CMMC Status Date. An operational remediation plan does not confer Conditional Status.

Assessment planning

Location and observation

Not specifically listed in CAP P.11

This requirement is not specifically listed in CAP P.11. That does not establish that remote assessment is sufficient: the Lead CCA and C3PAO determine an adequate approach for the actual scope and evidence.

CAP §P.11, pages 10–11 ↗

Check the source

References and related requirements

DoD CMMC Assessment Guide, Level 2 ↗CA.L2-3.12.4; requirement and objectives, printed page 208. 2.13, September 2024.
32 CFR 170.24: Assessment findings and scoring ↗170.24(b) and (c)(2). Current electronic Code of Federal Regulations.
32 CFR 170.21: POA&M eligibility and closeout ↗170.21(a)(2) and (b). Current electronic Code of Federal Regulations.
NIST SP 800-171 Rev. 2 ↗Requirement 3.12.4. February 2020, updated January 2021.
NIST SP 800-171A ↗Assessment procedure 3.12.4. June 2018.
Cyber AB CMMC Assessment Process (CAP) ↗P.11, printed pages 10-11; Level 2 certification assessment-location planning. 2.0, December 2024.

Program timing and contract applicability can change independently of these requirements. Check current DoD program notices and your solicitation or contract before making a compliance decision. Open the official DoD resource hub.

System Security Plan