EvidenceSheet
CMMC 2.0 · Security Assessment

CA.L2-3.12.4 System Security Plan

Develop, document and periodically update a system security plan describing system boundaries, the operating environment, how each requirement is implemented, and connections to other systems.

Source: CMMC 2.0, CA.L2-3.12.4. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CMMC 2.0 in the compliance library.

3
artefacts
1
held by a system
1
at each review
moderate
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Version history showing periodic update · Document repository

periodic reviewEvidence produced at each review

  • Approval record for the current version · Document repository

governing documentDocuments that govern the control

  • Current system security plan covering boundary, environment, implementation and interconnections · Policy repository / GRC workspace

First move

Start with the 1 of 3 artefacts that already live in a system (Document repository); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

CA.L2-3.12.3 Security Control Monitoring · CM.L2-3.4.1 System Baselining