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. 02reconauditd already present?
3. 03reconservice active?
4. 04reconenabled 2 = immutable rules (cannot load without a reboot)
5. 05reconrules already in place (do not duplicate or overwrite them)
6. 06reconfree disk for /var/log/audit
7. 07actInstall auditdverify
8. 08actEnableverify
9. 09actAdd baseline rules (accounts, sudo, SSH)verify
10. 10actLoad the rulesverify

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 auditdVerified byauditctl -v
2. 02verifyEnableVerified bysystemctl is-active auditd
3. 03verifyAdd baseline rules (accounts, sudo, SSH)Verified bytest -s /etc/audit/rules.d/50-servor.rules && echo ok
4. 04verifyLoad the rulesVerified byauditctl -l | grep -c identity

SEC.03

Guardrails

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

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

Deploy on Servor button

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

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. 05CrowdSecCrowdSec collaborative IPS, SSH collections and firewall bouncer.