DSP-17 Sensitive Data Protection
Apply protective measures to sensitive data at every stage of its lifecycle, from creation through to destruction.
4
artefacts
0
held by a system
1
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
none for this control
periodic reviewEvidence produced at each review
- Evaluation evidence that the measures operate · Document repository
governing documentDocuments that govern the control
- The lifecycle stages identified and the protection applied at each · Document repository
- Technical measures such as encryption, tokenisation or access restriction per stage · Document repository
- Coverage across systems holding sensitive data · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Protection concentrated at rest with data in use or in transit unprotected
- Sensitive data in logs, caches or exports left out of scope
- Measures deployed but never evaluated for effectiveness
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-16 Data Retention and Deletion · DSP-18 Disclosure Notification