DSP-15 Limitation of Production Data Use
Obtain the data owner's authorisation and treat the resulting risk before production data is copied into or used in a non-production environment.
4
artefacts
1
held by a system
2
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Authorisation records from data owners for production data use in non-production · Cloud console / configuration management
periodic reviewEvidence produced at each review
- The risk assessment and treatment applied, such as masking or subsetting · Cloud console / configuration management
- Records of removal once the need ended · Cloud console / configuration management
governing documentDocuments that govern the control
- Controls on non-production environments holding such data · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Production data copied to test environments as routine practice with no authorisation
- Masking applied inconsistently so some fields remain live
- Copies left in non-production indefinitely
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 sheetDSP-14 Disclosure of Data Sub-processors · DSP-16 Data Retention and Deletion