Browse this section

Preparing secure SSH access

Use individually assigned access where practical so changes can be attributed and access can be revoked without affecting everyone. SSH keys are useful for authentication, but the private key must remain on a trusted device and be protected appropriately.

Before changing SSH settings

  • Confirm the expected server address, port and host-key fingerprint through the agreed handover channel.
  • Provide only your public key for installation. Never paste a private key into a ticket.
  • Test the new account in a second session before removing an existing access method.
  • Keep an authorised console or recovery method available while changing authentication or firewall rules.

Do not disable password access or restart the SSH service until the replacement method has been verified. For a connection failure, send the exact error, time and source IP without sharing secrets. Settings and service commands vary by operating-system release.

Further reading: Ubuntu: OpenSSH server

Was this guide helpful?

Related guides

Requesting a firewall rule without losing access

A firewall request should describe a required communication path, not simply ask to open all traffic. Both provider-side and operating-system rules may affect a connection. Plan the change …

TLS certificate issuance and renewal checks

A valid certificate needs the correct names, a trusted chain and a working renewal process. HTTPS protects the connection; it does not prove that the application itself is free of vulnerabi…

What to send us when you suspect a compromise

Treat unexpected administrator accounts, changed files or suspicious processes as evidence to investigate. A successful malware scan does not establish that a system is clean. Use a trusted…

Container ports and management interfaces

A container being reachable from its host does not mean it should be reachable from the Internet. Published container ports and host firewall settings must be reviewed together. Docker can …

Need help applying this to your service?

Tell us your service reference and what you need to achieve. Never include passwords or private keys in a ticket.

Contact support →
← All knowledgebase topics