SSH hosting: secure access and practical precautions
Use SSH keys, verified host identities and restricted access to administer a server securely, with a recovery route for configuration changes.
SSH provides an encrypted connection for remote server administration. It can also support file transfers through SFTP and controlled forwarding of connections. It protects the communication channel, but it does not automatically secure a website, remove malware or replace operating system updates.
Verify the server's host key fingerprint using a trusted channel before accepting a first connection. Investigate unexpected host key changes instead of dismissing the warning. A legitimate reinstall can change a key, but the cause should be confirmed before continuing.
Use individual accounts and public key authentication where possible. Protect private keys with suitable device security and a passphrase, and remove access promptly when a key or account is no longer needed. Grant administrative privileges only to people and processes that require them.
Before tightening SSH settings, keep a working session open, test another connection and confirm access to the provider's recovery console. Restrict incoming connections to trusted networks when practical. Changing the default port may reduce automated scanning noise, but it is not a substitute for strong authentication and access controls.
Tools such as OpenSSH, PuTTY and WinSCP support different administration and transfer workflows. Keep clients and the server updated, review authentication logs and use forwarding only when needed. Combine SSH with application security, firewall rules and independent backups as part of regular server maintenance.