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

10.3.4 File integrity monitoring on audit logs

Audit logs must be covered by file integrity monitoring or by change-detection tooling so that existing log data cannot be altered without an alert being raised. Applies to all entities. As good practice, the guidance recommends that the tooling alert when stored log content or log files are altered or removed, but not when new entries are appended. Objective under the customized approach: nobody can change the stored records of activity without an alert.

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

  • Log platform integrity features (hashing, signing) configuration · SIEM / log platform
  • Evidence alerts are routed to responders · SIEM / log platform

periodic reviewEvidence produced at each review

  • FIM or change-detection alert samples for modified or deleted log data · SIEM / log platform

governing documentDocuments that govern the control

  • FIM policy listing audit log files and directories as monitored objects · 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.3.3 Audit logs promptly backed up to central secure storage · 10.4.1 Daily review of security-relevant logs