DE.CM-01 Networks and network services are monitored to find potentially adverse events
Networks and network services are monitored to find potentially adverse events. Control from NIST Cybersecurity Framework 2.0 framework, domain: DE - Detect.
Source: NIST CSF 2.0, DE.CM-01. 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
- DNS query analytics pipeline configuration · Source control / CI pipeline
- East-west traffic monitoring sample alerts · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Network flow telemetry coverage map by segment · Policy repository / GRC workspace
- IDS or NDR sensor inventory with placement diagram · Policy repository / GRC workspace
- Egress monitoring policy and exception register · Policy repository / GRC workspace
First move
Common gaps auditors find
- Encrypted traffic not inspected at chokepoints
- Container and service mesh traffic invisible
- Egress rules logged but not alerted on
- DNS sinkhole only covers known bad domains
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.AE-08 Incidents are declared when adverse events meet the defined incident criteria · DE.CM-02 The physical environment is monitored to find potentially adverse events