EvidenceSheet

11.5.1 IDS/IPS monitoring of CDE traffic

Network intrusions must be detected and/or prevented, using IDS and/or IPS techniques, in such a way that: all traffic at the CDE perimeter is monitored; all traffic at critical points inside the CDE is monitored; personnel receive alerts about suspected compromises; and every detection and prevention engine, baseline and signature is kept up to date. Guidance (definition): critical points can include network security controls between segments (for instance between a DMZ and the internal network, or between networks inside and outside scope) and points guarding connections from less trusted to more trusted components. Objective under the customized approach: mechanisms that detect suspicious or anomalous network traffic in real time, which may point to threat actor activity, are in place, and their alerts are acted on by staff or by automated responses that prevent system components being compromised by the detected activity.

Source: PCI DSS v4.0.1, 11.5.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.

4
artefacts
3
held by a system
0
at each review
easy
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

  • IDS/IPS configuration and signature update history · Cloud console / configuration management
  • Sample alerts and the tickets showing personnel responded · SIEM / log platform
  • Alert routing configuration to the SOC or on-call staff · SIEM / log platform

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Network diagrams marking IDS/IPS sensor placement at the CDE perimeter and critical internal points · Policy repository / GRC workspace

First move

Automate the pull from your SIEM / log platform. Retention and alert rules exported from the SIEM; review evidence is the closed-alert record with reviewer and time.

Common gaps auditors find

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.4.7 Multi-tenant providers support customer penetration testing · 11.5.1.1 Service providers detect covert malware channels