Hardening your first VPS: five steps before you deploy anything
Engineering · 6 min read

A fresh server is an exposed server. Before you ship code, spend ten minutes locking the doors. Here is the checklist we run on every new instance.
1. Update and reboot
Patch the base image immediately. On Debian/Ubuntu: apt update && apt upgrade -y. Reboot if a kernel was updated so you are running patched code, not just patched files.
2. Create a non-root user
Never log in as root day to day. Add a user, give it sudo, and use SSH keys instead of passwords. Keys eliminate the entire class of brute-force password attacks.
3. Firewall defaults closed
Allow only the ports you serve — typically 22, 80 and 443. Everything else should be denied inbound. PoroHost ships a firewall preset you can enable in one click.
4. Fail2ban and key-only SSH
Rate-limit and ban repeated authentication failures, and disable password authentication in sshd_config once your key works. This turns the public internet’s scanning noise into nothing.
5. Snapshots before changes
Take a snapshot before any risky change. It is your undo button. Our NVMe RAID-10 storage makes hourly snapshots cheap and fast to restore.