The Seat That Never Left: A Post-Tax-Season VPN Offboarding Audit
Photo: Internet Archive Book Images, No restrictions, via Wikimedia Commons
Offboarding is usually treated as an HR event: return the laptop, collect the badge, close the payroll record. For an accounting firm, it is also an identity event. Every seasonal preparer, intern, and contract reviewer who touched the VPN during the 2026 filing season left behind a small constellation of access rights. When the work ends, the person leaves. The VPN seat often does not.
The ghost seat is an identity, not a person
A ghost seat is any active credential that still authenticates after the worker has no business reason to reach client files. It may be a named VPN account, an MFA enrollment tied to a personal phone, a client certificate installed on a home laptop, or a shared login that three people used because the firm never issued individual accounts. The risk is not theoretical. A departed preparer who can still reach the document management system is a confidentiality incident waiting for a trigger.
The problem is structural. Accounting firms add capacity quickly in January and shed it just as quickly in April. HR closes the personnel file. The VPN administrator closes the account only if someone remembers, and the firm has a reliable list of every credential the worker received. Few small firms do.
Reconcile HR dates against four access layers
A defensible offboarding audit starts with a single reconciliation table. Pull the termination or contract-end date from HR, then compare it with the following access layers.
| Access layer | What to export | Common failure |
|---|---|---|
| VPN user account | Username, creation date, last login, assigned groups | Account disabled in one console but active in a legacy concentrator |
| MFA enrollment | Device name, enrollment date, phone number or authenticator | MFA device belongs to the worker and is never removed |
| Client or device certificate | Certificate common name, issue date, expiration, revocation status | Certificate remains valid after the user account is disabled |
| Shared credential | Account owner, vault record, last checkout, rotation date | Shared login is used by multiple seasonal staff and never rotated |
The table should include a column for the business owner: the partner, manager, or IT lead who can attest that access is no longer needed. Without an owner, the audit becomes a list of unresolved questions.
Set the calendar before the next season
A post-season audit in November 2026 should not wait for the January 2027 ramp-up. The following calendar is realistic for a small firm with fewer than fifty VPN users.
- November 2026: freeze the seasonal roster. Export HR termination dates for every 2026 seasonal worker, intern, and contractor. Export VPN accounts, MFA enrollments, certificate inventory, and shared-credential vault records.
- December 2026: reconcile the four lists. Mark every account with no matching active worker. Disable VPN accounts first, then revoke certificates, then remove MFA devices. Rotate any shared credential that was used by a departed worker.
- Early January 2027: run a pre-season access attestation. Every partner or manager confirms that each active VPN user still has a client-facing role. New seasonal staff receive named accounts, not shared logins.
- February through April 2027: conduct a weekly exception review. Look for accounts with no login in thirty days, MFA changes, and certificate use from unexpected devices. The review should take minutes, not days.
- May 2027: repeat the post-season audit within thirty days of the last seasonal departure. Do not wait until the next November.
When the audit finds a ghost
A ghost seat is an incident until proven otherwise. Preserve the account record, last-login data, and any MFA or certificate history. Ask whether the credential was used after the termination date. If it was, treat the matter as a potential confidentiality event and follow the firm's incident-response policy. Do not simply delete the account and move on.
For accounts with no evidence of post-termination use, document the disablement date, the revoker, and the ticket or audit reference. That record matters for cyber-insurance renewals, client security questionnaires, and peer review. Insurers increasingly ask not whether a firm has offboarding controls, but whether it can show them operating.
Keep the evidence short and repeatable
The goal is not a perfect identity-governance program. It is a repeatable control that a small firm can run twice a year. One reconciliation workbook, one owner per access layer, and one calendar entry per season are enough to start. The alternative is a ghost seat that survives until a client, an insurer, or an adversary finds it first.