SEC.01

The playbook

The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.

1. 01reconthe current SSH config
2. 02recondo any authorized keys exist? (otherwise DO NOT disable passwords)
3. 03reconis the SSH config valid before touching it?
4. 04actBack up sshd_configverify
5. 05actDisable root + passworddestructiveverify
6. 06actReload sshddestructiveverify

SEC.02

What it verifies

Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.

1. 01verifyBack up sshd_configVerified byls /etc/ssh/sshd_config.bak.*
2. 02verifyDisable root + passwordVerified bysshd -t 2>&1 && echo ok
3. 03verifyReload sshdVerified bysystemctl is-active ssh || systemctl is-active sshd

SEC.03

Variables

What you choose before launching — the recipe fills in the rest.

SEC.04

How a recipe runs in Servor

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.

SEC.05

More security recipes

1. 01fail2banfail2ban with the SSH jail, active and verified.
2. 02UFW firewallUFW: deny incoming by default, allow SSH + chosen ports. Destructive: keeps SSH open.
3. 03Automatic security updatesEnables automatic security updates (unattended-upgrades).
4. 04CrowdSecCrowdSec collaborative IPS + firewall bouncer.
5. 05ClamAVClamAV antivirus with an up-to-date signature database.