Skip to content
← Back to blog
Quickstart

Secure Your VPS in 10 Minutes

April 24, 2026·8 min read

The starting point

You just spun up a fresh Ubuntu 24.04 or Debian 12 VPS. Maybe Hetzner, maybe DigitalOcean, maybe Oracle Cloud free tier. SSH works on port 22, root login is enabled, and the firewall is open. Scanners find a new public IP fast, and the first SSH brute-force attempts usually arrive within minutes.

The plan: install InnerWarden's host stack, read its hardening report, apply the fixes that fit, wire up phone alerts. On a small box with a decent connection it fits in a coffee break.

Open an SSH session and stay there. We will not reboot.

Minute 1 to 3: install

The host stack is InnerWarden Pro, the paid tier, and it runs on Linux. One command with your licence: the installer verifies and installs the binaries, creates the systemd units, and starts the sensor and agent in monitor mode, so nothing is blocked until you decide it should be.

curl -fsSL https://www.innerwarden.com/install | sudo bash -s -- --license=/path/to/license.txt

The licence selects the paid tier; without it the same command installs the free one. The sensor loads its eBPF programs into the kernel and the agent serves its dashboard on 127.0.0.1:8787, loopback only. Beyond the licence, no external accounts or API keys are needed to start. Every step, including how to check the installer before you run it, is in Install and first run.

Sanity check:

sudo systemctl status innerwarden-sensor innerwarden-agent

Minute 3 to 5: read the hardening report

Before changing anything on the box, get an honest picture of where it stands.

sudo innerwarden system harden --verbose

You will get a score out of 100 and a list of findings, each with the fix. Common findings on a fresh install: SSH root login on, password authentication on, no firewall, no automatic security updates, default sysctl values for network hardening.

The report is read-only. It writes nothing, changes nothing, touches no service. Run it as many times as you want.

Minute 5 to 7: apply the fixes yourself

The hardening advisor never changes the system on its own: you apply what it recommends, one finding at a time, and skip anything that does not fit your setup. The usual first three are key-only SSH, a default-deny firewall and automatic security updates.

One important note before you touch sshd: have your SSH key already in~/.ssh/authorized_keys, because turning password authentication off takes effect on the next login.

Open a second SSH session in another terminal to confirm you can still log in before you close the first one. This is a habit worth keeping for any change to sshd.

Minute 7 to 9: phone alerts

Detection without notification is just an expensive log file. Telegram is the path of least friction. Talk to@BotFatheron Telegram, create a bot, copy the token. Send a message to your bot and grab your chat id fromhttps://api.telegram.org/bot<TOKEN>/getUpdates.

The wizard asks for both, saves them and sends a test message:

sudo innerwarden config telegram

Test it again any time withsudo innerwarden notify test --channel telegram. Telegram pages you only for an intrusion in progress that nothing has contained. Brute force and port scans wait on the dashboard and in the daily briefing. Read why false positives are a feature problem for the reasoning.

Minute 9 to 10: decide when to block

The install starts in monitor mode: it detects and tells you, and blocks nothing. Once you have watched what it would block for a while, turn on automatic IP blocking:

sudo innerwarden enable block-ip

From then on a confident detection, such as an SSH brute-force source, gets its IP blocked at the firewall, and the block is recorded with its evidence.

What you have now

A box with key-only SSH, a sane firewall, hardened sysctl, eBPF-level visibility into syscalls, network connections, and the process tree, and Telegram alerts on your phone. An AI provider for incident triage is optional and can be added later.

Re-run the hardening report and the score should climb. The findings that remain are usually workload-specific: TLS certs, application user segmentation, log shipping, things only you know about.

What this does not cover

Honest list of things still on you. InnerWarden does not patch your OS, you still needunattended-upgradesor equivalent. It does not handle application-level authentication, your web app still needs proper auth and rate limits. It does not back up your data. It does not replace TLS. It does not stop a zero-day in your kernel from happening, only helps you notice the aftermath. And it will not stop you shipping a vulnerable code path, or save you from a leaked deploy token: it is a host security layer, not a shield around everything you run.

For deeper context on what hardening actually buys you, see the Linux hardening checklist.

When to walk away

You have the host stack running, a dashboard on127.0.0.1:8787you can reach through an SSH tunnel when curious, and Telegram will tap you on the shoulder when something matters. That is the point. The whole exercise should fade into the background within an hour and stay there.

Read more: Telegram server security alerts · SSH brute-force detection