Enterprise delivery credentials
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
Why it persists
Deprovisioning reads from the wrong list
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
An offboarding process starts with a leaver record and works outward to the systems that leaver had. That is the correct direction for the accounts the identity directory knows about, and it is completely blind to everything else — because the process can only revoke access it can enumerate, and it enumerates from the directory.
The access that survives is therefore always the access that was never in the directory in the first place. A shared operations login whose password is in a team document. A personal access token generated for a deployment script and attached to an individual. A cloud console user created by hand during an early project. A supplier portal where the account is the person's work email and the vendor has no idea they left. None of these appears on any list the offboarding process reads.
This is also why the finding recurs after being closed. An organisation cleans up thoroughly, passes the next assessment, and eighteen months later is in the same position — because what was fixed was a backlog rather than the direction the process runs in. The control that holds is one that periodically enumerates access from the systems themselves and reconciles that against the people list, rather than the other way round.
Where to look
Six places access outlives employment
Shared and service logins
The operations account, the deployment account, the account for the system that does not support individual users. Disabling a person changes nothing here; the credential is in a document, a password manager entry or somebody's memory.
Personal access tokens and keys
Generated by an individual for automation, tied to their identity, and frequently outliving the account that created them because the system treats the token as its own principal.
Cloud console and CLI users
Created by hand before federation was set up, never migrated when it was, and holding long-lived access keys that no directory disable touches.
Vendor and partner portals
Support portals, licensing consoles, hosting panels, payment gateways. Registered to an individual's work address, invisible to IT, and the vendor has no way to know anything changed.
Physical and remote access
A building card, a VPN profile on a personal device, a certificate issued to a laptop that was never returned. These are owned by different teams from the ones that run the directory.
Code and data they still hold
A repository forked to a personal account, an export sent to a personal address, a document shared to an external email. Not access in the technical sense, and worth including in the same review because the exposure is identical.
The fix
A clean-up, then a control that holds
1 · Enumerate from the systems, not the directory
Pull the user list out of every system that has one — cloud accounts, code hosting, SaaS applications, vendor portals, the VPN, the building system — and reconcile against the current people list. The output is uncomfortable the first time. A list of live access no directory review would have produced.
2 · Rotate rather than only disable
Every shared credential a leaver held is rotated, and every token they generated is revoked at the system that honours it. Disabling their named account does neither. The access that survives an account disable is closed too.
3 · Attach every system to an owner
Each system in the inventory gets a named person responsible for its access list. Systems without one are where the next backlog accumulates, and they are usually the vendor portals. A review that can actually be assigned rather than announced.
4 · Review on a cycle, from the estate
Quarterly for systems holding sensitive data, annually for the rest, always sourced from the system's own user list. Record that it happened — the record is what an assessor asks for, and its absence is the finding even when the review is running. A control that closes the finding and keeps it closed.
Scope
What the discovery covers
What we do
- Enumerate access from each system's own user list, which is the only direction that finds what the directory never held.
- Include the access that is not technical — data taken to personal accounts — because the exposure is the same.
- Leave behind a review process with named owners, rather than a one-off list that becomes a backlog again.
Access review is a control most national frameworks require in some form, and the evidence assessors ask for is the dated record of the review rather than the access list itself. Design the process so it produces that record without extra effort.
Primary sourceCommon questions
What buyers ask
How far back should the first clean-up go?+
Do not scope it by date — scope it by system. Enumerate every system's current user list and reconcile it against the current people list, and whatever is left over is in scope regardless of when it was created. Scoping by leaver date requires a complete leaver record going back years, which is exactly the thing that is missing in organisations with this problem.
Can identity governance tooling solve this?+
It helps considerably with the systems it is integrated with, and not at all with the ones it is not — which is where the problem lives. The tool will run beautiful quarterly campaigns across your directory-connected applications while the vendor portal registered to a former manager stays exactly as it was. Integration coverage is the number to ask about, not the feature list, and the systems hardest to integrate are usually the ones holding the surviving access.
What is the quickest thing worth doing this week?+
Pull the user list from your cloud accounts, your code hosting and your two or three most important SaaS applications, and read them against the current staff list. That is a few hours of work across four systems and it finds most of what a full discovery would, because those four are where the long-lived credentials sit. It also produces the evidence that makes the case for doing the rest properly.
In this cluster
Run an access discovery
A one-off discovery across the estate that lists live access no directory review would have shown, followed by a review process that keeps it closed.
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly
