PI-02 Contractual agreements for the provision of data
Fix in the contract what data is returned when the relationship ends, in which format and scope, the period allowed for handover, the point at which customer access ceases and deletion begins, and the customer's own coop
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
- Review note confirming the exit terms still match current legal requirements · Document repository
governing documentDocuments that govern the control
- Contract or annex specifying data format, scope and the return period on termination · HR system / LMS
- Clause naming the moment customer access ends and erasure commences · Document repository
- Written statement of what the customer must do to cooperate during exit · 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
- Terms promise data return without naming a format, leaving the choice to provider discretion
- No deadline stated between the end of the relationship and the handover of data
- Customer obligations left undefined, so exit stalls the moment customer action is needed
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 sheetPI-01 Documentation and safety of input and output interfaces · PI-03 Secure deletion of data