All documentation

Security

Access, SSH keys and account security

Control who can reach your servers and your account, and keep both locked down.

5 min read

Use SSH keys, not passwords

Password authentication is the most common way servers get compromised. Deploy with an SSH key and disable password login entirely:

/etc/ssh/sshd_config
PasswordAuthentication no
PermitRootLogin prohibit-password

Principle of least privilege

Give each person and each service only the access it needs. Create a separate user for applications instead of running everything as root, and use sudo for administrative tasks.

  • One SSH key per person — never share keys
  • Remove access promptly when someone leaves
  • Rotate keys periodically, especially after a lost device

Securing the control panel

Enable two-factor authentication on your Syniac account and require it for everyone on your team. The control panel is the keys to everything — treat it accordingly.

Firewalls

Only expose the ports your application actually serves. A typical web server needs 80 and 443 open to the world, SSH restricted to your office or VPN, and everything else closed.

TALK TO AN INFRASTRUCTURE ENGINEER

Need a hand with your setup?

Share your workloads, locations, and timeline. We’ll recommend the right mix of cloud, dedicated servers, and colocation.