What evidence do auditors commonly ask for on LOG-08 Audit Logs Sanitization?

Documentation of log sanitisation features offered to customers (pattern detection, masking, tokenisation); Configuration of sanitisation rules for sample log sources; Test results showing sensitive values such as card numbers or personal identifiers removed from logs; Records of the protected store for original unaltered logs and its access log; Mapping of sanitisation rules to legal requirements such as GDPR or HIPAA.

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

Sanitisation applied only to application logs, not to platform or audit logs

CSA CCM v4.1 · LOG - Logging and Monitoring

`LOG-08` Audit Logs Sanitization

Define, put in place and assess technical measures that let service customers find sensitive data in logs and remove or tokenise it, so it is not exposed without authorisation, as the applicable law and regulation require.

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

Configuration of sanitisation rules for sample log sources · SIEM / log platform
Mapping of sanitisation rules to legal requirements such as GDPR or HIPAA · SIEM / log platform

periodic reviewEvidence produced at each review

Test results showing sensitive values such as card numbers or personal identifiers removed from logs · SIEM / log platform
Records of the protected store for original unaltered logs and its access log · Identity provider / directory

governing documentDocuments that govern the control

Documentation of log sanitisation features offered to customers (pattern detection, masking, tokenisation) · Policy repository / GRC workspace

First move

Start with the 2 of 5 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

Sanitisation applied only to application logs, not to platform or audit logs
No customer-configurable rules, so customer-specific sensitive data passes through
Original logs kept without restricted access

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-07 Logging Scope · LOG-09 Log Records