DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events.
5
artefacts
3
held by a system
0
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
- File integrity monitoring baseline and drift alerts · SIEM / log platform
- Hardware tamper detection telemetry · Document repository
- Patch and configuration drift dashboard · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- EDR coverage report by asset class · Policy repository / GRC workspace
- Software inventory reconciliation with allowlist · 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
- EDR exclusions accumulate without review
- FIM only on a subset of critical systems
- Ephemeral workloads outside the monitoring scope
- Drift alerts tuned out due to false positive volume
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 sheetDE.CM-06 External service provider activities and services are monitored to find potentially adverse events · GV.OC-01 The organizational mission is understood and informs cybersecurity risk management