8.8 Collect Command-Line Audit Logs
Collect command-line audit logs. Example implementations include collecting audit logs from PowerShell®, BASH™, and remote administrative terminals.
4
artefacts
3
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
- Evidence the safeguard is implemented: Collect Command-Line Audit Logs · SIEM / log platform
- Policy/standard covering CIS Control 8 (Audit Log Management) · SIEM / log platform
- Configuration / tooling output demonstrating the safeguard · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Records showing the safeguard is operating (logs, reports, reviews) · SIEM / log platform
governing documentDocuments that govern the control
none for this control
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
- Safeguard implemented for some assets but not all in scope
- No evidence of ongoing operation (point-in-time only)
- Implementation Group IG2 baseline not met
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 sheet8.7 Collect URL Request Audit Logs · 8.9 Centralize Audit Logs