8.33 Test information
Requires test information to be appropriately selected, protected and managed.
5
artefacts
1
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
- Logging of access to test environments holding sensitive information · SIEM / log platform
periodic reviewEvidence produced at each review
- Authorisation records where production information is used for testing, including who approved and for how long · Document repository
- Evidence of protection of test information equivalent to its classification, including access control and deletion after use · Identity provider / directory
- Records of the test data lifecycle, showing creation, use and removal · Document repository
governing documentDocuments that govern the control
- Rules on selecting test information, showing preference for synthetic or masked data over production copies · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform 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
- Production copies taken to test with approval never sought and removal never performed, so the copy persists for years
- Test environments open to a wider audience than production while holding the same data
- Test data protection assumed lower because the environment is called test, which is exactly backwards once real data is present
- No inventory of which test environments hold production derived data
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 sheet8.32 Change management · 8.34 Protection of information systems during audit testing