Supply-Chain Security · SC-Q10

Question: Is there an offboarding process to ensure data return, deletion, and access termination when a supplier relationship ends?

Why This Matters

Without structured termination steps, residual access or retained data can lead to data leakage and compliance violations.

Maturity

0 — Unaware
No formal offboarding process.
1 — Ad Hoc
Handled manually per case.
2 — Defined
Checklist for data return and access revocation.
3 — Managed
Offboarding workflow with sign-off and evidence.
4 — Integrated
Linked to contract expiry and asset registers.
5 — Optimized
Automated offboarding and confirmation dashboards.

How to Level Up

| From → To | Actions | |—|—| | 0 → 1 |Identify vendors with access to systems or data.| | 1 → 2 |Create termination checklist (data return, revocation, evidence).| | 2 → 3 |Implement workflow for approval and sign-off.| | 3 → 4 |Integrate with contract management and asset inventory.| | 4 → 5 |Automate reminders and verification steps. |

Enablers

Evidence

KPIs

Low-Cost / Open-Source Options (MSME)

| Purpose | Tool | Notes | |—|—|—| | Workflow | Odoo / n8n | Termination automation | | Storage | Nextcloud | Evidence repository | | Tracking | Airtable | Checklist register |

Common Pitfalls

Compliance Mapping

| Standard | Clauses / Notes | |—|—| | ISO/IEC 27001 | A.5.19 / A.5.32 (Data retention and deletion) | | DPDP Act 2023 | Sec 9 (Data erasure on withdrawal) | | NIST CSF 2.0 | DE.DP / PR.AC | | NIRMATA Mapping | SC-Q10 ensures secure vendor exit management. |