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. 01reconUFW installed? already active?
2. 02reconwhich ports are listening (so as not to cut them off)?
3. 03actInstall UFWverify
4. 04actAllow SSH BEFORE anythingverify
5. 05actDeny incoming by defaultdestructiveverify
6. 06actEnable the firewalldestructiveverify

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. 01verifyInstall UFWVerified bycommand -v ufw
2. 02verifyAllow SSH BEFORE anythingVerified byufw status | grep -ci ssh
3. 03verifyDeny incoming by defaultVerified bytrue
4. 04verifyEnable the firewallVerified byufw status | head -1

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. 01Harden SSHDisables root and password login, keeps keys. Destructive: verify your key access first.
2. 02fail2banfail2ban with the SSH jail, active and verified.
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.