Research note
How much offboarding access removal is confirmed within the target window?
A confirmation study for offboarding access removal that separates a request sent from an account actually disabled and verified.
Published

Table of contents
Question and scope
This study asks what share of offboarding access removals are confirmed within the target window. It treats the system account as the unit and the removal time as the observation. The scope is one employment operations team and a fixed departure window. The result describes that setting and should not be read as a security certification.
The unit is one system account tied to one departing employee. An account is eligible when the employee had access during the 30 days before the last working day. Shared accounts are included only when the employee was a named user. Record the inclusion rule before reviewing.
Record whether the employee was on site, remote, or on leave during the final week. The work arrangement can affect which systems were used and which need a manual check. Report the arrangement with the result. That variable helps explain a missing account without assuming a process failure.
Definitions and evidence standard
Define the target window from the policy and the role. A standard departure may require removal by the end of the last working day, while a sensitive role may require an earlier time. Record the applicable window for each case. A single target for every role can hide a serious delay in a high-risk system.
Define confirmation as evidence that the account was disabled, not merely a request sent. Use a system timestamp, an administrator confirmation, or a manual check recorded by a named person. A ticket marked done without a system check is a request record, not confirmation. Record the decision and the date so the next reviewer can follow the same reasoning.
Record whether the employee had a role that required an earlier removal. A sensitive role may have a different target, and pooling it with a standard role can hide a serious delay. Report the role category with the result. Keep the supporting evidence with the case rather than in a separate note.
Sampling and measurement
Draw the sample from departures in the window and freeze the list. Include different roles and systems. If the team uses more than one identity system, report each separately. Record the number of employees, accounts, and systems reviewed.
Measure the number of accounts confirmed within the target, the number confirmed late, and the number with no confirmation. Report the median removal time and the range. Add the number of shared accounts that required a credential rotation. A single percentage without these counts hides where the delay sits.
If a system has no timestamp, record the manual check and the person who performed it. A manual check is weaker evidence than a system log, but it is better than a closed ticket. Report the evidence type with the confirmation. The reader should see how the result was established.
Findings and interpretation
Present the distribution before suggesting a cause. A cluster of late removals in one system may mean the owner is unclear. A cluster in one role may mean the target window is not defined. A cluster of unconfirmed accounts may mean the team relies on a request rather than a system check. Read the cases behind the largest cluster.
Compare the removal time with the last working day and the manager's confirmation. A late manager confirmation can push the removal past the target. A system outage can also delay a removal that was requested on time. Report the pattern with its uncertainty and avoid treating every late removal as a process failure.
Compare the confirmation time with the number of systems in the access set. An employee with many accounts has more chances for a late confirmation. Report the count beside the rate. The access set size is part of the risk.
Limitations
The study sees recorded accounts, not every access path. A local file, a shared drive, or a physical key may not appear in the identity system. The study also cannot determine whether a late removal was exploited. Those questions need a security review by the responsible owner.
The window may include a system migration or a policy change that affects the target. If the identity system changed during the period, the records may not be comparable. Record these limits with the result and keep the system extracts with the method. Review the result with the process owner before changing the rule.
Compare the confirmation time with the number of systems in each employee's access set. An employee with many accounts has more chances for a late confirmation. Report the count beside the rate. Do not compare a simple access set with a complex one as if they carried the same risk.
Practical next step
Choose one control that matches the most common gap, such as a role-based target, a named system owner, or a confirmation check before closure. Write the change, the owner, and the start date. Define the measure that will show whether it helped, using the same confirmation standard. Test it on the next set of departures.
Keep the before and after departures separate so the comparison is honest. Record the cases that were excluded and why. Review the result with the system owners and the manager. If the change does not help, record that result too. The purpose is a removal that is confirmed, not a ticket that is closed.
Test a role-based target with one system before applying it to every account. A target that fits a directory account may not fit a client portal. Record the system and the result. The next study can compare the same confirmation standard.
Comparing system types
Different systems may have different removal paths. A directory account may be disabled centrally, while a client portal may require a manual request. Report the count and the confirmation rate for each system type, and label small groups as descriptive only. State the limit beside the finding so the reader can judge the scope.
If one type shows a consistent delay, check whether its owner and target are defined. A type that looks worse may simply depend on a third party. Compare the process, not the administrator. The next study can test a type-specific owner or target.
Keep the access records in a restricted workspace because they may contain system and identity details. Publish only the aggregate counts and the system categories. If a client asks for the result, describe the method and the control rather than sharing raw account data. The study is an internal access tool, not a client-facing audit.
What the evidence does not show
The study does not establish that a late removal caused a security incident or that the employee accessed the system after leaving. It also does not measure whether the access was appropriate before departure. Those questions need a separate review. Use the same definition in the next review so the comparison stays honest.
Do not use the result to promise a client that every account will be removed on time or that no access risk will remain. Do not publish employee names or system credentials. Keep the sample size, the target definitions, and the review decisions with the result. If the client needs a security conclusion, use a different method.
Ask the system owner which missing confirmation would be most serious. That answer helps the team prioritize the repair. Report the priority with the system category. Not every unconfirmed account carries the same risk.
Using the result in a client conversation
A client may ask how the team handles offboarding access, and the study supports a careful answer. Describe the window, the number of accounts, the confirmation standard, and the control that was added. Do not say that every removal is confirmed or that no delay will ever occur. Explain that the measure covers recorded accounts and that the system owner reviews open items.
If the client asks for a commitment, offer a process commitment such as a role-based target, a named system owner, and a confirmation check. Record the commitment and the measure that will show whether it was met. Keep client-specific details out of any public write-up. The study is an internal access tool, not a security certification.
Keep the access records in a restricted workspace because they may contain system and identity details. Publish only the aggregate counts and the system categories. If a client asks for the result, describe the method and the control rather than sharing raw account data. Write the exception down rather than resolving it from memory.
Sources
References supplied with this research note.
| Source | Publisher | Context |
|---|---|---|
| U.S. Department of Labor, Fair Labor Standards Act | dol.gov | Primary reference supplied with this article. |
| U.S. Department of Labor, Recordkeeping | dol.gov | Primary reference supplied with this article. |
| Internal Revenue Service, Publication 15 | irs.gov | Primary reference supplied with this article. |
| NIST Cybersecurity Framework 2.0 | nist.gov | Primary reference supplied with this article. |