Join our Newsletter — 33% off our NHI Course
Home› FAQ› NHI Lifecycle Management› How should security teams detect offboarding risk before…
NHI Lifecycle Management

How should security teams detect offboarding risk before an employee formally resigns?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 31, 2026 Domain: NHI Lifecycle Management

Security teams should look for behavioral drift before a leaver process begins. Rising export volume, widened access at the edges, and changes in working rhythm can signal intent even when permissions remain legitimate. The key is to compare each identity with its own historical baseline, because entitlement reviews often stay silent when actions are technically allowed.

What offboarding risk looks like before resignation is official

Pre-resignation offboarding risk is usually visible as behaviour drift, not as a formal HR event. Security teams should watch for people starting to act like they are winding down, such as exporting more data than usual, touching systems outside their normal pattern, or changing when and how they work. Those signals matter because they often appear while access is still technically legitimate.

The practical question is not whether someone has resigned, but whether their access pattern has changed enough to raise concern. A useful baseline is the person’s own historical behaviour, because entitlement review alone can miss legitimate but unusual activity. That makes this a detection problem as much as a leaver-process problem.

Which signals are most useful to baseline

The strongest early indicators are usually combinations of volume, scope, and rhythm. Rising export volume, new interest in edge-case permissions, unexplained access to repositories or file shares, and a shift toward atypical hours can be more telling together than any one signal on its own. Single events are often noise; repeated deviation from the individual baseline is what deserves attention.

Context matters. A spike in activity after a role change, project deadline, or incident response period may be harmless, while the same pattern in a stable role can be more concerning. Teams get better results when they compare a person against peers in the same function and against their own prior behaviour, rather than using a single universal threshold for everyone.

Useful signals also tend to cluster around data movement and permission edges. If a user is suddenly visiting systems they rarely touched before, requesting broader access, or moving toward tools that reduce observability, that combination is worth a closer look. The aim is to identify pattern change early enough to trigger review, not to treat every deviation as misconduct.

How to turn drift into an actionable security signal

Detection works best when security, HR, and line managers agree on what constitutes meaningful drift and who reviews it. A rule set that only watches for formal leaver notices will always be late. A better model is to surface changes in access behaviour, compare them with the person’s role and baseline, and decide whether the result warrants a privacy-aware check-in, a manager conversation, or a containment step.

Security teams should also separate normal access from legitimate risk. Someone can remain authorised and still be worth reviewing if their behaviour suggests they are preparing to leave, moving data, or testing what they can still reach. That distinction is important because the response may be to tighten observation or narrow exposure before any formal resignation occurs.

Where the environment supports it, pair behavioural signals with access governance evidence such as dormant entitlements, old project access, and recent privilege expansion. That helps you decide whether the drift is merely unusual or whether it is creating real blast radius. For broader lifecycle handling, the Joiner-Mover-Leaver (JML) Guide is useful because it connects movement in access patterns with the leaver controls that should already be in place.

Why leaver detection fails when teams rely on formal process alone

Most offboarding failures happen because the organisation treats resignation as the starting gun. By the time HR submits a leaver request, the risky part may already be over. A former role can still have valid access, cached sessions, service links, shared credentials, or lingering entitlements, which means technically permitted behaviour can still create exposure.

That is why teams need to think in terms of exposure windows. The longer a user keeps broad access while their behaviour is changing, the more opportunity there is for data extraction, account abuse, or misuse of legitimate access paths. The risk is highest when the user already knows where the valuable data lives and how the controls work.

Behavioural drift is not proof of malicious intent, but it is a reliable reason to shorten the response path. Once the pattern starts to change, the question becomes whether the organisation can still explain the activity as normal business need. If not, the control decision should move quickly from watchful waiting to targeted review.

Risk and Threat Considerations

Pre-resignation drift is risky because it can happen inside normal authorisation boundaries, which makes it easy to miss until data has already left or access has already been abused. The most common failure is assuming that an entitlement review will catch the problem, when the real signal is a change in how the person uses what they already have.

Failure mechanism: A user accumulates unusual access behaviour, expands data movement, or reaches beyond their usual working pattern while their access remains valid, allowing exfiltration or preparation for abuse before the leaver process starts.

Impact: Security teams lose the early-warning window, increasing the chance of data theft, account misuse, delayed containment, and avoidable cleanup after the departure is formalised.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while NIST CSF 2.0, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1020 — Data ExfiltrationBehavioural drift often includes rising export volume and possible exfiltration.
Recommendation — Hunt for abnormal data movement and review exfiltration paths when access patterns change.
NIST CSF 2.0DE.CM-01 — Networks and information systems are monitored to detect potential cybersecurity eventsEarly offboarding drift detection depends on continuous monitoring of user activity.
Recommendation — Monitor identity activity continuously and alert on meaningful deviation from baseline.
NIST SP 800-53 Rev 5AU-6 — Audit Record Review, Analysis, and ReportingInvestigating offboarding risk requires reviewing logs for unusual access and exports.
AC-2 — Account ManagementPre-resignation risk is reduced by governing account lifecycle and access changes.
Recommendation — Review audit logs for unusual access, export spikes, and privilege changes. Tighten account governance when behaviour shifts suggest impending offboarding.
CIS Controls v8CIS-8 — Audit Log ManagementDetection of pre-offboarding drift depends on usable logs and alerting signals.
Recommendation — Centralise and review logs that reveal anomalous user activity and data movement.

Practitioner Guidance

What to prioritise: Focus first on behaviour change, not resignation status. If a person’s access pattern shifts sharply, treat that as a review trigger even when there is no HR notice yet.

What to verify: Check whether the drift is consistent with role change, project activity, or incident work. If it is not, verify recent data export, privilege expansion, new destinations, and unusual login timing before deciding it is harmless.

Decision rule: If the user can still reach sensitive data or privileged systems and the behaviour shift has no clear business explanation, shorten the response path by escalating review, not by waiting for the formal leaver workflow to begin.

Practitioner takeaway: The useful signal is not departure itself, but a measurable change in how an identity behaves while access is still intact.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org