SSO-05 Exit strategy for the receipt of benefits
Define and document exit strategies for purchased services where the risk assessment found very high dependency, aligned with continuity planning and covering transition cost, impact, resource and timing analysis, assign
4
artefacts
0
held by a system
0
at each review
hard
to go live
Vendor register / contract 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
none for this control
governing documentDocuments that govern the control
- Documented exit strategy for each supplier rated as creating very high dependency · Vendor register / contract repository
- Transition cost and timeline estimate supporting one such exit strategy · Vendor register / contract repository
- Role assignment matrix naming who executes each transition activity · Policy repository / GRC workspace
- Defined service indicators and thresholds whose breach would start an exit · Vendor register / contract 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
- Exit strategies written only for contract expiry, not for sudden supplier failure
- No dependency threshold defined, so no supplier ever qualifies for an exit strategy
- Exit planning not reconciled with the continuity plans it is meant to support
- Criteria for judging a transition successful left undefined
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