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 distribution: apt (Debian/Ubuntu) or dnf (RHEL/Fedora/Rocky/Alma)
2. 02reconCrowdSec already installed? version (allowlists ≥ 1.6.8)
3. 03reconengine and bouncer active?
4. 04reconports 8080 (LAPI) and 6060 (metrics) already taken by something other than crowdsec → change listen_uri
5. 05reconCrowdSec repository already configured?
6. 06reconfirewall backend (nftables or iptables bouncer); fail2ban can coexist
7. 07reconopen SSH sessions and the admin IP that must never be blocked
8. 08actAdd the CrowdSec repositoryverify
9. 09actInstall CrowdSecverify
10. 10actMove the LAPI (only if port 8080 was already taken)verify
11. 11actCheck the Linux + SSH collectionsverify
12. 12actProtect the admin IP (only if an IP is provided)verify
13. 13actInstall the firewall bouncerverify

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. 01verifyAdd the CrowdSec repositoryVerified byls /etc/apt/sources.list.d/ /etc/yum.repos.d/ 2>/dev/null | grep -ci crowdsec
2. 02verifyInstall CrowdSecVerified bycscli version && systemctl is-active crowdsec
3. 03verifyMove the LAPI (only if port 8080 was already taken)Verified bycscli lapi status
4. 04verifyCheck the Linux + SSH collectionsVerified bycscli collections list -o raw | grep -c 'crowdsecurity/sshd'
5. 05verifyProtect the admin IP (only if an IP is provided)Verified bycscli allowlists inspect servor-admin
6. 06verifyInstall the firewall bouncerVerified bysystemctl is-active crowdsec-firewall-bouncer && cscli bouncers list

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

SEC.04

Variables

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

SEC.05

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.06

Deploy on Servor button

Maintain CrowdSec or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.

SEC.07

More security recipes

1. 01Harden SSHTurns off password login and root password login, keeps keys. Destructive: verify your key access first.
2. 02fail2banfail2ban with the SSH jail on the right port, active and verified.
3. 03UFW firewallUFW: denies incoming by default, allows the real SSH port + chosen ports, with a safety net. Destructive: keeps SSH open.
4. 04Automatic security updatesEnables automatic security updates: unattended-upgrades (Debian/Ubuntu) or dnf-automatic (RHEL/Fedora).
5. 05ClamAVClamAV antivirus with signatures kept up to date, optional daemon.