6.5.6 Remove test data and accounts before production
Test data and test accounts must be taken off system components before the system is put into production. The testing procedures cover commercial packaged software as well as applications built in-house, including recently installed or updated ones. Leftover test records and accounts can reveal how an application works and give an attacker an easy foothold into the system and the account data it handles. It applies to all entities. Objective under the customized approach: test data and test accounts cannot be present in production environments.
Source: PCI DSS v4.0.1, 6.5.6. 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
none for this control
periodic reviewEvidence produced at each review
- Database queries or reports showing no test records in production · Source control / CI pipeline
- Release sign-off records confirming the removal step · Source control / CI pipeline
- Vendor software installation notes showing default or demo accounts removed · Identity provider / directory
governing documentDocuments that govern the control
- Go-live checklist including removal of test accounts and test data · Policy repository / GRC workspace
- Account listings from recently released production systems · Policy repository / GRC workspace
First move
Common gaps auditors find
- Default demo accounts left enabled after installing commercial software
- Test user accounts carried into production via configuration scripts
- Seed or dummy transaction data left in production databases
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.5 No live PANs in pre-production · 7.1.1 Requirement 7 policies and procedures maintained