What evidence do auditors commonly ask for on LOG-04 Audit Logs Access and Accountability?

Access control list for the log platform; Audit trail of access to the logs themselves; Periodic review of who can read and administer logs; Policy on protection of log information.

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

Broad read access to logs for all engineers

CSA CCM v4.1 · LOG - Logging and Monitoring

`LOG-04` Audit Logs Access and Accountability

Allow only authorised identities to reach audit logs and keep a record of each such access.

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

moderate

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

Audit trail of access to the logs themselves · SIEM / log platform

periodic reviewEvidence produced at each review

Periodic review of who can read and administer logs · SIEM / log platform

governing documentDocuments that govern the control

Access control list for the log platform · Policy repository / GRC workspace
Policy on protection of log information · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Broad read access to logs for all engineers
Access to logs not itself logged
Service accounts with log access left unreviewed

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-03 Security Monitoring and Alerting · LOG-05 Audit Logs Monitoring and Response