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.
5
artefacts
3
held by a system
0
at each review
easy
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Network flow telemetry coverage map by segment · Cloud console / configuration management
- 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
- IDS or NDR sensor inventory with placement diagram · Policy repository / GRC workspace
- Egress monitoring policy and exception register · Policy repository / GRC workspace
First move
Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.
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