6.5.6 Test data and accounts removed before production
Test data and test accounts are removed from system components before the system goes into production.
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
- Scanner output confirming no test accounts · Identity provider / directory
periodic reviewEvidence produced at each review
- Sample pre-production review · Document repository
- Sign-off evidence · Document repository
governing documentDocuments that govern the control
- Release checklist requiring removal · Policy repository / GRC workspace
- Post-go-live verification · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Identity provider / directory 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
- Test accounts left active in production
- No release checklist item
- Test data in production tables
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 Live PANs not used in pre-production · 7.1.1 All security policies and operational procedures that are identified in Requirement 7 are: • Documented. • Kept up to date. • In use. • Known to all affected parties