CA.L2-3.12.1 Security Control Assessment
Assess the security controls in place periodically to determine whether they are effective as implemented.
Source: CMMC 2.0, CA.L2-3.12.1. 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.
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
none for this control
periodic reviewEvidence produced at each review
- Assessment plan defining scope, method and frequency · Policy repository / GRC workspace
- Completed assessment results per control · Document repository
- Evidence assessments cover effectiveness and not just presence · Document repository
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Assessment confirms a control exists without testing whether it works
- Scope excludes parts of the CUI environment
- No defined periodicity so assessments lapse
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