EvidenceSheet

10.1.2 Roles for logging and monitoring assigned and understood

Responsibilities for carrying out the activities in Requirement 10 must be written down, allocated, and understood by those who hold them. Applies to all entities. The guidance suggests these may sit inside policies and procedures or in separate documents, for example a RACI matrix, and that staff can be asked to acknowledge their assigned roles. Customized approach objective: day-to-day duties for every Requirement 10 activity are allocated, and staff are held accountable for keeping these controls running successfully and without interruption.

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

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

  • Signed acknowledgements of assigned logging responsibilities · Identity provider / directory
  • Interview records with staff who perform daily log review · Identity provider / directory

governing documentDocuments that govern the control

  • RACI matrix covering logging, log review, retention and time synchronization tasks · Policy repository / GRC workspace
  • Job descriptions or role charters for SOC analysts and log platform owners · 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.1.1 Requirement 10 policies and procedures maintained and in use · 10.2.1 Audit logging enabled on all system components