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

10.2.1 Audit logging enabled on all system components

Audit logging must be switched on and actively recording for every system component and for cardholder data. Applies to all entities. The guidance explains that logs feed alerts and other monitoring tools such as IDS and SIEM and give a history trail for investigating incidents, and it advises storing only essential information in logs because log content is itself sensitive. Customized approach objective: every activity affecting system components and cardholder data leaves a record.

Source: PCI DSS v4.0.1, 10.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
3
held by a system
0
at each review
easy
to go live
Endpoint management (MDM / EDR)
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

  • Audit policy or syslog configuration exports for sampled servers, network devices and databases · Endpoint management (MDM / EDR)
  • SIEM source health report showing last event received per device · Endpoint management (MDM / EDR)
  • Cloud provider logging configuration (for example trail or activity log settings) for in-scope accounts · Identity provider / directory

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Inventory of in-scope system components reconciled against log sources reporting to the SIEM · Policy repository / GRC workspace

First move

Automate the pull from your Endpoint management (MDM / EDR). Device compliance report from the MDM (encryption, EDR agent, OS version) on a daily pull.

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.1.2 Roles for logging and monitoring assigned and understood · 10.2.1.1 Logs capture individual user access to cardholder data