6.5.5 Live PANs not used in pre-production
Live PANs are not used in pre-production environments except where those environments are included in the CDE and protected in accordance with all applicable PCI DSS requirements.
5
artefacts
1
held by a system
0
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
system holds itEvidence a system already holds
- Sample scans of test databases · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Policy prohibiting live PAN in test · Policy repository / GRC workspace
- Data masking or synthetic data process · Policy repository / GRC workspace
- Developer training on test data · HR system / LMS
- Exception register · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Vulnerability scanner / patch tooling 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
- Live PAN copied for debugging
- Masking incomplete
- No test data governance
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 sheet6.5.4 Roles and functions are separated between production and pre-production environments to provide accountability such that only reviewed and approved changes are deployed · 6.5.6 Test data and accounts removed before production