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

10.4.2.1 Periodic log review frequency set by targeted risk analysis

The frequency for periodically reviewing logs of every other system component (those outside 10.4.1) must be set by the entity's own targeted risk analysis, and that analysis must be carried out in line with every element specified in Requirement 12.3.1. Applies to all entities. The guidance suggests criteria such as how complex the environment is, how many types of systems need evaluating and what those systems do. Objective under the customized approach: reviews of lower-risk components' logs happen often enough to address the entity's risk. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.

Source: PCI DSS v4.0.1, 10.4.2.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
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
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

none for this control

periodic reviewEvidence produced at each review

  • Approval record of the risk analysis and its review date · Document repository
  • Log review records demonstrating the chosen frequency is met · SIEM / log platform

governing documentDocuments that govern the control

  • Targeted risk analysis document for periodic log review frequency, meeting 12.3.1 · Policy repository / GRC workspace
  • Criteria used in the analysis (environment complexity, system types and functions) · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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 Periodic review of all other system component logs · 10.4.3 Exceptions and anomalies from log review addressed