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.
3
artefacts
2
held by a system
1
at each review
easy
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Continuous monitoring strategy naming controls, metrics and frequency · SIEM / log platform
- Records of action taken when monitoring shows degradation · SIEM / log platform
periodic reviewEvidence produced at each review
- Monitoring output such as dashboards or periodic reports · SIEM / log platform
governing documentDocuments that govern the control
none for this control
First move
Automate the pull from your SIEM / log platform. Retention and alert rules exported from the SIEM; review evidence is the closed-alert record with reviewer and time.
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