Plan the exit before a relationship ends
Identify who owns the service, which systems and information the supplier controls, and whether continuity depends on proprietary formats or licensing. Record transition arrangements before terminating critical access.
An abrupt disconnection of a critical provider without replacement arrangements may create a service disruption. Coordinate the exit with service owners and business continuity teams.
Revoke identities and integrations
Inventory human accounts, service accounts, API tokens, VPN connections, remote support software and delegated permissions. Remove or rotate access at the appropriate transition stage and validate that the changes took effect.
Consider shared credentials and dependencies used by subcontractors. Contract expiry does not automatically revoke technical access.
Handle data return and secure deletion
Agree which data, logs, configurations and records must be transferred, retained or deleted under applicable legal and contractual requirements. Protect integrity and confidentiality during transfer and retain appropriate evidence of completion.
Do not promise complete deletion when independent legal retention duties still apply. Record exceptions and their basis.
Restore operational independence
Verify that internal teams or successor suppliers possess necessary administrative access, runbooks, encryption-key recovery arrangements and support contacts. Test critical functions after migration.
Review backup and incident-response boundaries. A departing provider may hold important recovery information even after production workloads have moved.
Close supplier findings and retain evidence
Reconcile outstanding incidents, vulnerabilities, assets and unresolved risk decisions. Keep offboarding approvals, access removal records, transfer checks and the final service owner's acceptance.
Article 21(2)(d) supports supplier relationship security throughout its lifecycle. NIS2 does not prescribe a single standard offboarding form; the controls should reflect the relationship, risk and applicable national law.
Questions on the text
Does NIS2 require the same process for every supplier?
No. Measures should be proportionate to the supplier relationship, relevant risks and any additional applicable requirements.
Why retain records of the process?
Records support internal accountability, follow-up action and appropriate supervisory evidence.