Home / Privacy Hosting Guides / The First Hour of VPS Hardening: A Checklist
Operations

The First Hour of VPS Hardening: A Checklist

Most compromised servers fall to opportunistic scans in their first days online, not to targeted attacks. This ordered checklist covers the first hour on a new VPS: SSH keys, a firewall, fail2ban, automatic updates, and attack-surface trimming.

No KYC
Crypto Only
No Logs
DMCA Ignored
Full Root
NVMe SSD

A fresh VPS is scanned and probed within minutes of coming online. The good news: an hour of ordered hardening stops the overwhelming majority of opportunistic attacks. This is the checklist, in the order that matters, for a new privacy-focused server.

1. Lock down SSH first

Create a non-root user with sudo, add your public key, and then disable password authentication and root login in sshd_config (PasswordAuthentication no, PermitRootLogin no). Keys-only SSH alone defeats the password-guessing that makes up most of the noise hitting your server. Restart SSH and confirm a new session works before closing your current one.

The First Hour of VPS Hardening: A Checklist
The ordered hardening steps that stop the overwhelming majority of opportunistic attacks.

2. Put a firewall in front

Default-deny inbound, allow only what you need. With ufw: deny incoming, allow outgoing, then allow your SSH port and the specific service ports you run. A firewall turns "every open port is a target" into "only the doors you chose exist," which shrinks the attack surface dramatically.

3. Add fail2ban

Install fail2ban to watch auth logs and temporarily ban IPs that fail repeatedly. Even with keys-only SSH, it cuts log noise and blunts brute-force attempts against any service you expose. The defaults are sensible; enable the sshd jail and any jails for services you run.

4. Turn on automatic security updates

Enable unattended-upgrades (Debian/Ubuntu) so security patches land without you remembering. The single most common way servers are compromised is a known vulnerability that had a patch available — automating updates closes that window while you sleep.

5. Reduce the attack surface

Uninstall services you do not use, bind local-only daemons to 127.0.0.1, and check what is listening with ss -tlnp. Every listening service is a potential entry point; the fewer you run and expose, the less there is to attack. Then set up off-box backups so a compromise is recoverable, not catastrophic.

The hour, summarised

Keys-only SSH, a default-deny firewall, fail2ban, automatic updates, and a minimal listening surface. None of it is exotic, all of it is fast, and together it stops the automated attacks that account for nearly all real-world compromises. Do it before you deploy anything that matters.

FAQ

VPS hardening FAQ

01 What is the most important first step on a new VPS?

Disable password SSH and use keys only, with root login off. Password-guessing is the bulk of the automated noise hitting a new server, and keys-only SSH defeats it outright. Do this before anything else.

02 Do I still need fail2ban if I use SSH keys?

Yes — it reduces log noise and protects any other service you expose, not just SSH. Keys-only SSH stops password brute-force on SSH, but fail2ban blunts attacks across the board and keeps your logs readable.

03 Which firewall should I use?

On Debian/Ubuntu, ufw is the simplest: default-deny inbound, allow outbound, then open only your SSH port and the specific services you run. The tool matters less than the default-deny posture.

04 Are automatic updates safe to enable?

For security updates, yes — unattended-upgrades applies patches without breaking configs in the vast majority of cases, and the risk of an unpatched known vulnerability is far greater. Keep backups and it is a clear win.

05 How do I know what is exposed?

Run ss -tlnp to list listening sockets and the processes behind them. Anything bound to 0.0.0.0 is reachable from the internet; bind what should be local to 127.0.0.1 and firewall the rest.

06 Can I really harden a server in an hour?

Yes. Keys-only SSH, a firewall, fail2ban, automatic updates and a minimal listening surface take well under an hour and stop the overwhelming majority of opportunistic attacks. Deeper hardening can follow, but this is the high-value first pass.

Deploy a server worth hardening

Offshore VPS and dedicated servers with full root, deployed in under five minutes — pay in crypto, no identity required.

VPS Plans Offshore Hosting Pricing