EvidenceSheet

DSP-09 Data Protection Impact Assessment

Assess the privacy impact of personal data processing, examining where the risk comes from, what kind of risk it is, how specific it is to this processing and how severe it could be, wherever law or good practice calls f

4
artefacts
0
held by a system
4
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

  • Completed data protection impact assessments for relevant processing · Document repository
  • The trigger criteria that decide when an assessment is required · Document repository
  • Risk treatment arising from each assessment · Policy repository / GRC workspace
  • Sign-off by the accountable privacy authority · Data governance / DLP tooling

governing documentDocuments that govern the control

none for this control

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

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 sheet

DSP-08 Data Privacy by Design and Default · DSP-10 Sensitive Data Transfer