In this article
Access revocation, session closure and resource handover are separate checks; keep their evidence in one handover record.
A GPU operator handover should track who receives access, what it permits, when it expires and how the previous access is withdrawn. A list of SSH keys alone is incomplete if other accounts, control panels or active sessions remain in use.
Prepare the sequence before changing operators. The equipment owner should retain an agreed recovery route while avoiding shared credentials that make actions difficult to attribute.
Identify every access path
List operating-system accounts, SSH keys, management interfaces, container controls and any relevant service credentials. Record owners and purpose without copying secrets into the register. Public key fingerprints can identify keys without exposing private key material.
OpenSSH’s sshd documentation describes authorised keys and their options. Review the configuration actually used on the host. An account name in a spreadsheet does not establish the permissions enforced by the running service.
Agree on the handover sequence
| Stage | Evidence | Responsible party |
|---|---|---|
| New access prepared | Named account and key reference | Owner or administrator |
| Permission checked | Approved action succeeds | Receiving operator |
| Previous access withdrawn | Configuration change recorded | Administrator |
| Sessions reviewed | Agreed session state | Previous and new operators |
| Resource accepted | Readiness result | Equipment owner |
The sequence should preserve a recovery method and avoid an unnecessary access gap. It is a proposed working procedure, not a command to disable accounts without reviewing active work.
Verify withdrawal separately
Removing a key from the relevant authorisation path should not be confused with terminating every existing session or process. Record what was changed and which additional checks were performed. OpenSSH’s ssh-keygen documentation describes key identification and revocation mechanisms; applicability depends on the configuration.
Test that the withdrawn access no longer starts a new session through the intended path. Verify the new account independently. Do not infer either outcome merely because an administrator edited a file successfully.
Record the resulting resource state
Describe remaining workloads, data locations and changes made during the handover. An operator change is also a resource transition: another team needs to know whether the GPU, storage and environment are ready for the agreed task.
Unresolved access paths should remain listed with a responsible person and next action. Do not claim complete revocation while a management interface or shared secret remains unexplained.
A clear register supports a bounded pilot and makes the eventual return to the owner reviewable.
Continue with Offer Your GPU Server Without Relocating It and Close a GPU Pilot with a Data Cleanup Record.