11.5.1.1 Covert malware channel detection (SP)
Additional requirement for service providers: intrusion detection or prevention techniques detect, alert on, or prevent and address covert malware communication channels.
5
artefacts
0
held by a system
3
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- DNS, HTTP, and HTTPS inspection configuration · Cloud console / configuration management
- Threat intelligence feed subscription evidence · Document repository
- Tuning records · Document repository
governing documentDocuments that govern the control
- Sample detections of covert channels · Document repository
- Response runbooks · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- No covert channel detection
- Threat intel not used
- Encrypted traffic not inspected
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.5.1 IDS/IPS in place · 11.5.2 Change detection mechanism (FIM)