CA.L2-3.12.3 Security Control Monitoring
Monitor security controls continuously so their effectiveness is known on an ongoing basis rather than only at assessment time.
Source: CMMC 2.0, CA.L2-3.12.3. 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
- Monitoring output such as dashboards or periodic reports · SIEM / log platform
periodic reviewEvidence produced at each review
- Records of action taken when monitoring shows degradation · SIEM / log platform
governing documentDocuments that govern the control
- Continuous monitoring strategy naming controls, metrics and frequency · Policy repository / GRC workspace
First move
Common gaps auditors find
- Monitoring limited to the annual assessment
- Metrics collected but not evaluated against expectations
- Degradation detected without follow up
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 sheetCA.L2-3.12.2 Plan of Action · CA.L2-3.12.4 System Security Plan