Vendor access and offboarding: define the outcome, owner, and test

Third parties can hold user accounts, API keys, support tunnels, shared mailboxes, devices, exports, backups, and copies at subcontractors. Cancelling the invoice does not remove those routes.

Offboarding should be designed during procurement. The contract and technical setup need a workable path to export required records, transfer ownership, revoke access quickly, retain logs, and confirm deletion.

Schedule a follow-up after the cutoff rather than treating the final meeting as proof of closure. Residual logins, renewal charges, forwarded mail, forgotten webhooks, and delayed backup deletion often appear only after normal vendor activity has stopped.

Give each important decision an owner and a test

Inventory identities and machines

Record named users, shared accounts, service accounts, tokens, certificates, VPN access, remote tools, devices, network rules, and administrator roles.

Map data beyond the main product

Include support tickets, email attachments, test environments, analytics, backups, local exports, subprocessors, and AI features.

Use time-bound least privilege

Vendor access should be approved for a task or support window, monitored where appropriate, and removed when the need ends.

Plan continuity before revocation

Transfer domains, repositories, encryption keys, documentation, code, billing authority, and operational knowledge before locking the old provider out.

Move from document to repeatable operation

  1. Open an offboarding record

    List contract end, internal owner, vendor contact, systems, accounts, data, assets, dependencies, legal holds, and the exact cutoff sequence.

  2. Export and validate

    Retrieve required data in a usable format, test that it opens, preserve necessary audit evidence, and confirm the successor can operate.

  3. Transfer control

    Move ownership of domains, cloud tenants, repositories, app stores, certificates, phone numbers, code signing, billing, and recovery routes.

  4. Revoke every access path

    Disable identities, rotate shared secrets and API keys, remove federation and remote tools, collect assets, close firewall rules, and invalidate sessions.

  5. Verify closure

    Review logs for residual use, obtain deletion and asset confirmation, monitor renewal charges, and schedule a later check for overlooked accounts or data.

Record what would prove the program works

Operating conditionBusiness consequenceOwner or evidence
Vendor used a shared admin accountActions and remaining knowledge are hard to attributeReplace it, rotate secrets, review logs, and move future work to named identities
API still works after user deletionMachine credentials have a separate lifecycleInventory and revoke tokens, certificates, webhooks, and service accounts
Vendor owns a domain or cloud tenantThe business may not control a critical assetTransfer ownership and recovery before announcing or enforcing cutoff
Provider says backups cannot be deleted nowRetention may outlast active serviceObtain the schedule, controls, exceptions, and contractual confirmation in writing

Sources for Vendor access and offboarding

Confirm current instructions and limits for this specific task before acting.

Remove the vendor's routes back into the business

Start from the access that exists, not the contract alone. Inventory named users, shared accounts, API keys, OAuth grants, remote support tools, VPN access, service accounts, devices, physical access, data feeds, backups, and subcontractors. An expired portal login does not revoke a token or integration that continues to run.

Decide what must be returned, transferred, retained, or destroyed. Export business records in a usable format, move ownership of domains and repositories, preserve evidence required for operations or disputes, and obtain a clear account of remaining copies. Verify contractual and legal requirements before demanding deletion of records the business must retain.

Close offboarding with evidence from both sides. Confirm access revocation in the systems that granted it, rotate shared secrets, test replacement workflows, and record the vendor's deletion or return statement. Keep an owner and review date for unresolved backups, legal holds, or dependencies rather than marking the vendor complete prematurely.

Questions owners should settle in advance

When should offboarding begin?+

At procurement for the exit terms, and operationally well before the end date when transfer or replacement is required. Urgent security revocation may need an immediate path.

Is a deletion certificate proof that all data is gone?+

It is useful evidence, not independent proof. Pair it with clear contractual scope, retention details, technical revocation, log review, and risk-based verification.

Should vendor accounts be deleted or disabled?+

Disable promptly to stop access and preserve logs, then delete according to audit, legal, and retention needs after ownership and evidence are settled.

Connect the program to its operational dependencies

Connect this decision to the owners, evidence, and recovery process that keep operations moving. Use the Business cybersecurity basics hub for the complete topic pathway, then continue with Security vendor evaluation checklist, Small-business security policy, and Small-business incident response plan.

Map the records and systems that must return or be deleted with the customer data protection guide.