EvidenceSheet
PCI DSS v4.0.1 · Req 10: Logging and Monitoring

10.4.3 Exceptions and anomalies from log review addressed

Exceptions and anomalies found while reviewing logs must be addressed. Applies to all entities. As good practice, the guidance suggests the process consider how review work is recorded, how exceptions are ranked and prioritized, how they are reported and escalated, and who investigates and carries out remediation. Customized approach objective: suspicious or anomalous activity is acted on.

Source: PCI DSS v4.0.1, 10.4.3. 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
2
held by a system
1
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

  • Tickets or case records showing anomalies investigated and closed · SIEM / log platform
  • Metrics on open and closed log review exceptions · SIEM / log platform

periodic reviewEvidence produced at each review

  • Escalation records linking log findings to incident response · SIEM / log platform

governing documentDocuments that govern the control

  • Procedure for triage, prioritization, escalation and ownership of log review findings · 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

10.4.2.1 Periodic log review frequency set by targeted risk analysis · 10.5.1 Keep logs 12 months, latest three months online