DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially…
Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
Source: NIST CSF 2.0, DE.CM-09. 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 NIST CSF 2.0 in the compliance library.
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
- EDR coverage report by asset class · Endpoint management (MDM / EDR)
- 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
- Software inventory reconciliation with allowlist · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
none for this control
First move
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