What evidence do auditors commonly ask for on LOG-11 Encryption Monitoring and Reporting?

Key management service metrics and dashboards; Internal reports on cryptographic control status (expiring certificates, keys due for rotation); Alerting on cryptographic failures; Review records of these reports.

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

Certificate expiry discovered only by outage

CSA CCM v4.1 · LOG - Logging and Monitoring

`LOG-11` Encryption Monitoring and Reporting

Set up and keep a capability to monitor and report internally on how the organisation's cryptography, encryption and key management rules and controls perform in operation.

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

Key management / PKI

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

Key management service metrics and dashboards · Key management / PKI

periodic reviewEvidence produced at each review

Internal reports on cryptographic control status (expiring certificates, keys due for rotation) · SIEM / log platform
Review records of these reports · SIEM / log platform

governing documentDocuments that govern the control

Alerting on cryptographic failures · Policy repository / GRC workspace

First move

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

Common gaps auditors find

Certificate expiry discovered only by outage
No reporting on key rotation compliance
Reports produced but not reviewed

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-10 Audit Records Protection · LOG-12 Transaction/Activity Logging