Use named accounts and controlled keys

Give each administrator an individual account. Use a unique key for each person or system and protect private keys with a passphrase and secure storage.

Remove keys when access ends. Review authorised keys on user accounts and check for keys copied into deployment scripts or shared folders.

Reduce exposed administration paths

Restrict SSH to approved networks or a managed access gateway where practical. Disable direct root login when your operating system and workflow support safer administration.

Use multi-factor authentication for the hosting or cloud control plane. A non-standard port does not replace access control.

Monitor and test administrative access

Review successful and failed logins. Alert on new keys, unexpected accounts and access outside the normal work pattern.

Test that approved staff can use the documented recovery path before removing a fallback. Include SSH, cloud console and provider access in one review.