Cybersecurity · Nov 2026
Third-Party Access Offboarding: Revoke, Then Verify
A practical framework for CISOs to close supplier access across identities, service credentials, cloud and collaboration tools without disrupting critical operations.
Third-party access reviews fail when procurement tracks contract end dates while engineering tracks accounts and security tracks incidents. A supplier can finish its engagement yet retain an API token, an emergency VPN account, a service principal, or an invitation to a shared workspace. The business may consider the relationship closed, but the technical trust relationship is still active. Third-party access offboarding must therefore be a verified removal of permissions across systems, not a checkbox in the vendor management portal. A practical control links a contract, named sponsor, identity, technical entitlement, expiry date and evidence of revocation. It also separates human identities from non-human credentials, because a disabled employee account does not revoke a running integration.
Inventory actual entitlements, not just suppliers
Start from identity provider logs, privileged access management, cloud IAM, source repositories, ticketing, collaboration tools and network access. Export active external identities and map each to an accountable business sponsor. Then enumerate service accounts, OAuth grants, secrets, SSH keys, webhooks and delegated administrator roles created for the engagement. The register needs system, permission scope, last observed use, creation date, owner and expiry policy. Do not assume that a domain name reliably identifies a supplier; contractors may use personal addresses or subcontractors. Reconcile the register with accounts payable and procurement records, but keep exceptions visible. An unmatched identity is a control failure to investigate, not a reason to delete it blindly.
Use a risk-based revocation sequence
Revocation order matters because careless deletion can interrupt payroll, logistics or customer-facing services. First identify privileged interactive access, then shared accounts and standing remote connectivity, followed by non-human credentials and data-sharing links. For each entitlement, decide whether to disable immediately, rotate a secret, transfer ownership or migrate an integration before removal. Define a short emergency path for confirmed compromise, with an incident commander authorized to revoke without waiting for routine sign-off. In normal offboarding, obtain the business sponsor's confirmation of the final deliverables and the engineering owner's confirmation that critical dependencies have been replaced. The objective is to close exposure without creating an avoidable outage.
Measure the real time to revoke
Do not report that offboarding completed merely because a ticket was closed. Define the clock from the contractual termination trigger or emergency instruction to the moment the last effective entitlement is removed. Capture timestamps for identity disablement, token rotation, privileged role removal, VPN termination, repository access removal and shared-link invalidation. Where possible, validate with a denied access attempt from a controlled test identity, rather than relying only on administrative screenshots. Report median and worst-case revocation time separately, especially for high-privilege access. Record the number of orphaned accounts and permissions with no named sponsor. These measures reveal whether the process works under pressure.
Contract language should create an operational trigger
A termination clause is useful only if it produces timely action across procurement, HR, legal, security and engineering. Require notification of personnel changes, subcontractor changes, security incidents and contract expiration with defined notice periods. Specify the supplier's obligations to return data, delete retained copies when legally permissible, revoke its own downstream access and confirm completion. Keep internal responsibility explicit: the company must revoke its credentials regardless of the supplier's assurance. The contract should define a support window for migrating business-critical integrations and a process for disputed access. Legal wording cannot substitute for a technical inventory, but it can make owners accountable before the final day.
A hypothetical supplier exit exposes the blind spot
Consider a hypothetical finance-software integrator whose contract ends on Friday. The team disables two named consultant accounts and closes the purchase order. On Monday, an unattended scheduled job still authenticates through an OAuth grant created during the project, and an old shared folder remains externally accessible. No incident is assumed in this example; the point is that commercial completion and technical removal are different events. A correct closure would identify the OAuth grant, assign ownership of the job, rotate or revoke credentials, verify the replacement workflow, remove sharing and retain a time-stamped evidence pack. The example is illustrative, not a report of an actual client or breach.
Define a small but defensible evidence pack
The evidence pack should contain the supplier identifier, termination trigger, business sponsor, entitlement inventory, exception approvals, revocation timestamps, test results and final sign-off. Avoid exporting secrets into the pack; use credential identifiers or redacted references. Keep sensitive audit evidence in a restricted repository with a retention policy. Exceptions need an expiry date and compensating controls such as temporary read-only access, network restrictions and enhanced logging. A CISO should be able to answer three questions from this record: what access existed, what was removed, and what residual access was deliberately accepted. A board does not need raw log dumps, but it does need confidence that closure is testable.
Build the first 30-day control
In the first ten days, reconcile the ten highest-risk external suppliers against active identities and privileged entitlements. During days eleven to twenty, choose one completed engagement and conduct a retrospective offboarding test across cloud, code, collaboration and network systems. In the final ten days, automate a trigger from the contract lifecycle to an access-removal workflow, with a human approval step for service integrations that could interrupt production. Do not promise full automation until exceptions are understood. Review the exercise with procurement, engineering and security together. The deliverable is a small repeatable control with accountable owners, not a new dashboard that nobody trusts.
What leaders should ask every quarter
Ask for the count of active external privileged identities, the percentage mapped to current contracts, the age of orphaned grants and the worst-case time to revoke a terminated supplier. Compare these indicators over time rather than treating a single green status as assurance. An organization may reduce the number of vendors while increasing concentration of access in one highly privileged integration. Track both quantity and consequence. For adjacent controls, review SaaS exit readiness and action-level AI permissions. The NIST Cybersecurity Framework 2.0 and CIS Controls provide established governance and access-control references. This month, test one supplier exit end to end.