12.4.2.1 Documentation of quarterly reviews (SP)
Additional requirement for service providers: reviews per 12.4.2 are documented and include results, remediation actions, and review by personnel assigned responsibility for the PCI DSS compliance program.
5
artefacts
0
held by a system
3
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Sign-off by PCI program owner · Document repository
- Escalation records for unresolved items · Document repository
- Archive of past 12 months of reviews · Document repository
governing documentDocuments that govern the control
- Standardized review template completed each quarter · Document repository
- Remediation tracker with closure · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Reviews undocumented
- No remediation tracking
- No program owner sign-off
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 sheet12.4.2 Quarterly PCI compliance reviews (SP) · 12.5.1 Inventory of system components in scope