SERVER1 / Search

What are you looking for?

Search services, pages and articles. Results appear after 2 characters.

View all articles
Security & SSL

Team SSH access: onboarding and offboarding

Define individual access, permissions and a verified recovery route. Plan SSH onboarding and offboarding without disrupting legitimate automation.

SERVER1.GE4 min read
Team SSH access: onboarding and offboarding

“Can you send the server password to our new developer?” sounds like a small onboarding request. It actually raises three questions: which person needs access, what work they may perform and how that access will end. A small team can answer them without building an elaborate identity platform. Start with individual ownership and a recovery path that does not depend on the person being onboarded.

A conversation between three roles

The project owner: “The developer needs to deploy one application. Does that require unrestricted administration of every service?” Describe the work in concrete terms: reading a project directory, publishing an approved release or inspecting a particular service. The administrator can then map that need to permissions. “Full access just in case” is a poor substitute for deciding who owns each operation.

The administrator: “We will verify the destination and the identity first.” Use the organisation's approved account and key process. A public key may be registered for access; the private key stays with its authorised holder and must not be copied into a ticket or team chat. Record the key fingerprint, owner, purpose and review date without collecting the private material.

The developer: “How will I know I reached the correct server?” Provide a verified way to check the host identity. Do not instruct the newcomer to suppress host-key warnings. A changed host key may have a legitimate explanation, but someone must establish it through the existing trusted channel before the developer proceeds.

The access record can stay small

  • Person or service identity, with a responsible owner.
  • Specific environment and approved work.
  • Public-key fingerprint or another non-secret reference.
  • Privilege boundary and any permitted administrative commands.
  • Review or expiry point, and the person who can revoke access.
  • A separately verified recovery route.

OpenSSH supports several ways to authorise users and keys. The actual server may use local key files, a command-based source, certificates or another managed arrangement. Inspect that ownership before editing anything. Removing a line from one file is not a complete offboarding procedure if another authorised source can still grant access.

When the colleague leaves

Begin with the inventory, not a mass deletion command. Identify personal access, shared credentials the person knew and automation that might accidentally run under their account. Separate each item's owner and replacement plan. Removing a personal account before moving a legitimate deployment job may break releases; keeping personal access indefinitely to avoid that problem leaves a different risk.

Revoking a key prevents relevant future authentication, but existing sessions and other credentials need their own review. Ask the administrator to assess active sessions, privileged access, application tokens and recovery paths within the authorised scope. Do not copy a departing colleague's private key into a new employee's laptop as a shortcut. Shared secrets, where they exist, require a separately planned change with the affected services considered.

Perform access changes with an approved procedure and a tested recovery route. Keep an existing administrator session available while a separately authorised new session verifies the intended result. Avoid altering the only working login method and assuming a management panel will rescue you. Recovery access must itself have been checked, not merely listed in an old document.

What should the team verify?

Check that the intended person can perform the approved work, cannot cross the agreed boundary and knows where to request additional access. For offboarding, record which paths were revoked and what remains pending. A successful SSH login does not validate deployment permissions, and a failed login from one route does not prove all access is gone.

Our guides on what root access means and why every process should not run as root explain the privilege boundary. When choosing an Unmanaged VPS, include this ongoing administration work in the team's plan. Access is a lifecycle with named responsibilities, not a password sent once and forgotten.

References: OpenSSH authorised-key documentation and server configuration reference. Available options depend on the installed version.

SERVER1.GE

Not sure which infrastructure fits this workload?

Tell us what you run, your expected traffic and current setup. We will help you narrow down the right option.

Relevant services
Choose by workload, not by habit.

Use the article context and your actual resource needs to compare the recommended options.