LOG-03 Security Monitoring and Alerting
Identify and watch security-relevant events in applications and the infrastructure beneath them, and set up a system that raises alerts to the responsible stakeholders based on those events and related metrics.
Source: CSA CCM v4.1, LOG-03. 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 CSA CCM v4.1 in the compliance library.
Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.
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
- SIEM alert rules and routing to named responders · SIEM / log platform
- Alert metrics (volume, time to triage) reported to management · SIEM / log platform
- Sample alerts with triage records · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- List of monitored security events and use cases · Policy repository / GRC workspace
First move
Common gaps auditors find
- Application layer events not collected, only infrastructure
- Alerts sent to an unmonitored mailbox
- No metrics on alert handling
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 sheetLOG-02 Audit Logs Protection · LOG-04 Audit Logs Access and Accountability