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. 01reconnftables present?
2. 02recondo any rules already exist? do not break SSH access
3. 03reconcurrent SSH session to preserve
4. 04actInstall nftablesverify
5. 05actApply the baselinedestructiveverify
6. 06actEnableverify

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 nftablesVerified bynft --version
2. 02verifyApply the baselineVerified bynft list ruleset | grep -c "dport"
3. 03verifyEnableVerified bysystemctl is-active nftables

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. 03UFW firewallUFW: deny incoming by default, allow SSH + chosen ports. Destructive: keeps SSH open.
4. 04Automatic security updatesEnables automatic security updates (unattended-upgrades).
5. 05CrowdSecCrowdSec collaborative IPS + firewall bouncer.