EvidenceSheet
PCI DSS v4.0.1 · Appendix A3: Designated Entities Supplemental Validation (DESV)

A3.5.1 Methodology for prompt detection of attack patterns

A methodology must be implemented to promptly identify attack patterns and undesirable behaviour across systems, including: spotting anomalies or suspicious activity in real time; prompt alerts to responsible personnel when suspicious activity or an anomaly is detected; and handling of alerts according to written response procedures. Related PCI DSS requirements: 10 and 12. Guidance: centrally managed or automated log correlation (such as SIEM, FIM or change detection) collecting logs from critical system components and security systems is a common approach. Applies only to designated entities. Objective under the customized approach: not eligible for the customized approach; only the defined approach can be used.

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

5
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

  • On-call rota and alert escalation records · SIEM / log platform
  • Sample correlated alerts with response tickets · SIEM / log platform
  • Incident response procedures referencing alert handling · SIEM / log platform

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Security monitoring and correlation methodology document · Policy repository / GRC workspace
  • SIEM correlation rule catalogue and log source coverage list · 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

A3.4.1 Six-monthly review of user accounts and access privileges