12.4.2 Quarterly PCI compliance reviews (SP)
Additional requirement for service providers: reviews are performed at least once every three months to confirm that personnel are performing their tasks in accordance with all security policies and operational procedure
5
artefacts
1
held by a system
2
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
- Findings and remediation tickets · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Quarterly review reports with sign-off · Document repository
- Review meeting minutes · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Sampling methodology and coverage · Document repository
- Trend analysis across quarters · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Ticketing / ITSM on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Reviews not quarterly
- Sampling too narrow
- Findings not tracked
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.1 Executive management responsibility for the PCI DSS compliance program (service providers) · 12.4.2.1 Documentation of quarterly reviews (SP)