11.5.1 IDS/IPS in place
Intrusion detection or intrusion prevention techniques are used to detect or prevent intrusions into the network, monitoring all traffic at the CDE perimeter and at critical points within the CDE.
5
artefacts
2
held by a system
1
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
- Signature update logs · SIEM / log platform
- Sample alerts and triage tickets · SIEM / log platform
periodic reviewEvidence produced at each review
- Tuning records · Source control / CI pipeline
governing documentDocuments that govern the control
- IDS/IPS architecture diagram with sensor placement · Policy repository / GRC workspace
- Coverage matrix at CDE perimeter and critical points · Policy repository / GRC workspace
First move
Start with the 2 of 5 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
- Coverage gaps
- Signatures stale
- Alerts untriaged
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 sheet11.4.7 Multi-tenant pen test support · 11.5.1.1 Covert malware channel detection (SP)