What evidence do auditors commonly ask for on 11.5.1.1 Service providers detect covert malware channels?

Configuration of DNS monitoring, egress filtering or IDS rules targeting C2 and tunneling; Sample detections or test results showing covert channel alerts fire; Incident response plan section defining the response to covert channel detection; Training or threat intelligence records showing staff knowledge of malware communication techniques.

What is the most common gap auditors find on 11.5.1.1?

DNS traffic to external resolvers not inspected

PCI DSS v4.0.1 · Req 11: Test Security Regularly

`11.5.1.1` Service providers detect covert malware channels

Service providers must apply intrusion-detection and/or intrusion-prevention methods that find the covert channels malware uses to communicate, raise alerts on them or block them, and deal with them, such as DNS tunneling to command-and-control servers. Guidance: placement should consider critical network locations and likely covert channel routes; helpful methods include real-time endpoint scanning, egress filtering, allow listing, data loss prevention and network security monitoring, and organizations should keep up-to-date knowledge of how malware operates. Applicability: applies only when the assessed entity is a service provider. Objective under the customized approach: mechanisms spot covert traffic to command-and-control systems and either alert on it or stop it, and alerts are handled by staff, or automatically in a way that blocks such traffic. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.

Source: PCI DSS v4.0.1, 11.5.1.1. 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 PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.

artefacts

held by a system

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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

Configuration of DNS monitoring, egress filtering or IDS rules targeting C2 and tunneling · SIEM / log platform

periodic reviewEvidence produced at each review

Sample detections or test results showing covert channel alerts fire · SIEM / log platform
Training or threat intelligence records showing staff knowledge of malware communication techniques · HR system / LMS

governing documentDocuments that govern the control

Incident response plan section defining the response to covert channel detection · Policy repository / GRC workspace

First move

Start with the 1 of 4 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

DNS traffic to external resolvers not inspected
Incident response plan has no playbook for command-and-control detection
Detection rules deployed but never tested

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 sheet

11.5.1 IDS/IPS monitoring of CDE traffic · 11.5.2 Change detection on critical files