LOG-10 Encryption Monitoring and Reporting
Monitor the operation of cryptography, encryption and key management controls and report internally on how they are performing.
4
artefacts
2
held by a system
1
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
system holds itEvidence a system already holds
- The monitoring configuration covering cryptographic operations · SIEM / log platform
- Metrics or indicators reported, such as failed operations and expiring keys · SIEM / log platform
periodic reviewEvidence produced at each review
- Evidence reporting drove an action · SIEM / log platform
governing documentDocuments that govern the control
- Internal reports produced and their audience · 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
- Cryptographic operations unmonitored because the platform hides them
- Reports produced with no recipient who can act
- Monitoring covers availability only, not policy conformance
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