SI.L2-3.14.6 Monitor Communications for Attacks
Watch organizational systems, and both inbound and outbound traffic, for attacks and for indicators that an attack may be developing.
3
artefacts
1
held by a system
2
at each review
moderate
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
- Monitoring capability configuration covering inbound and outbound traffic · SIEM / log platform
periodic reviewEvidence produced at each review
- Detection rules or signatures and their tuning records · Document repository
- Records of detected events and the response taken · Document repository
governing documentDocuments that govern the control
none for this control
First move
Start with the 1 of 3 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Inbound traffic monitored while outbound is not
- Monitoring deployed but alerts unreviewed
- Encrypted traffic unmonitored with no compensating visibility
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 sheetSI.L2-3.14.5 System & File Scanning · SI.L2-3.14.7 Identify Unauthorized Use