Why departures create cybersecurity risk
Departing employees and contractors may retain access to cloud services, business applications, remote connections or physical facilities if responsibilities are divided across teams. Accounts can also remain active because service owners do not know the worker has left.
Article 21(2)(i) identifies HR security and access-control policies as minimum areas of risk-management measures. NIS2 does not set an identical number of hours for every offboarding task; applicable national rules and risk-based internal procedures must guide timing.
Create a complete inventory of access
Start from the individual's identity, assigned roles and connected systems. Include single sign-on, local application accounts, privileged identities, VPN access, API credentials, physical badges, shared secrets and accounts administered by outside providers.
A central identity system may not cover every resource. Work with application owners and suppliers to find exceptions, including direct accounts created for urgent work and access granted during temporary assignments.
Coordinate the triggering event
HR should communicate the departure or contract end through an approved confidential channel. The service owner and security team can then prepare account disablement, transfer of legitimate work and return of company assets.
Immediate-risk departures may require a different sequence from a planned retirement. Record who authorised any exceptional timing, the business reason and compensating controls. Avoid keeping a personal account active for handover when an approved alternative is available.
Disable credentials and secure information
Remove access through identity providers and verify downstream systems, including cached sessions, tokens and independently managed applications. Recover devices and badges, rotate shared secrets where appropriate and address any privileged credentials known to the individual.
Preserve business records in accordance with retention and privacy rules, without continuing unauthorised access to the former worker's accounts. Coordinate mailbox delegation, data ownership and device handling with authorised personnel.
Verify completion and learn from failures
Use reconciliations between HR departure records, account inventories and application owners. Sample completed cases to confirm deactivation across critical systems, not just closure of the HR ticket.
Log delays, unresolved exceptions and supplier dependencies, then assign corrective actions. Repeat verification after process changes. The objective is evidence that access is no longer available, not a completed checklist alone.
Points of clarification
Does NIS2 prescribe an identical HR screening or offboarding checklist for all entities?
No. The Directive provides an EU-level framework, while applicable national law and the entity's risks determine appropriate procedures.
Are HR forms enough to prove security controls work?
No. Test whether approved access is actually granted and removed across relevant systems.
What records are useful?
Role approvals, account and device inventories, training evidence, access changes, exceptions and verification records support accountability.