10.2.2 Required details recorded for each auditable event
For every auditable event in 10.2.1.1 to 10.2.1.7, audit logs must record: the user identification; the type of event; the date and time; an indication of success or failure; where the event originated; and the identity or name of the data, system component, resource or service affected (for example, name and protocol). Applies to all entities. Customized approach objective: enough data is captured to recognise successful and failed attempts and to establish, for each event type in 10.2.1, the user, action, timing, location and method.
Source: PCI DSS v4.0.1, 10.2.2. 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.
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
- SIEM parsing rules confirming the fields are extracted · SIEM / log platform
periodic reviewEvidence produced at each review
- Interview notes with log platform engineers on field completeness · SIEM / log platform
governing documentDocuments that govern the control
- Sample entries for each auditable event type showing all six fields · Policy repository / GRC workspace
- Log format or schema documentation for applications and devices · Policy repository / GRC workspace
First move
Common gaps auditors find
- Application logs omit the source address or originating host
- Events lack a success or failure flag
- Timestamps without time zone make date and time ambiguous
- Affected resource logged only as an internal ID with no readable name
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 sheet10.2.1.7 Logs capture creation and deletion of system-level objects · 10.3.1 Audit log read access limited to job need