What evidence do auditors commonly ask for on LOG-05 Audit Logs Monitoring and Response?

SIEM correlation rules and anomaly detection configuration; Baselines of expected activity used for detection; Anomaly review procedure with response timeframes; Sample of detected anomalies with investigation and closure records.

What is the most common gap auditors find on LOG-05?

Logs collected but not correlated across sources

CSA CCM v4.1 · LOG - Logging and Monitoring

`LOG-05` Audit Logs Monitoring and Response

Build and keep the ability to correlate security audit logs across sources and watch them so that suspicious or anomalous activity departing from normal patterns is detected, and follow a defined process for reviewing and acting on anomalies promptly and appropriately.

Source: CSA CCM v4.1, LOG-05. 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.

artefacts

held by a system

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. 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

SIEM correlation rules and anomaly detection configuration · SIEM / log platform
Baselines of expected activity used for detection · SIEM / log platform

periodic reviewEvidence produced at each review

Sample of detected anomalies with investigation and closure records · SIEM / log platform

governing documentDocuments that govern the control

Anomaly review procedure with response timeframes · Policy repository / GRC workspace

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

Logs collected but not correlated across sources
No baseline of normal activity, so anomalies cannot be defined
Anomalies triaged without recorded outcome

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

LOG-04 Audit Logs Access and Accountability · LOG-06 Clock Synchronization