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. 02reconClamAV already present? which version / signature date?
3. 03reconfreshclam and daemon already active?
4. 04reconRAM (clamd uses ~1.5 GB once loaded) and free disk (~400 MB of signatures)
5. 05reconsignature database already present?
6. 06actEnable EPEL (RHEL/Rocky/Alma only)verify
7. 07actInstall ClamAVverify
8. 08actUnblock freshclam.conf (RHEL/Fedora, only if an Example line exists)verify
9. 09actUpdate the signaturesverify
10. 10actEnable clamd (only if daemon = true)verify
11. 11actTest detection (EICAR file)verify

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. 01verifyEnable EPEL (RHEL/Rocky/Alma only)Verified bydnf repolist enabled | grep -ci epel
2. 02verifyInstall ClamAVVerified byclamscan --version
3. 03verifyUnblock freshclam.conf (RHEL/Fedora, only if an Example line exists)Verified bygrep -c '^Example' /etc/freshclam.conf
4. 04verifyUpdate the signaturesVerified byls /var/lib/clamav/ | grep -cE '^(main|daily)\.c[vl]d$'
5. 05verifyEnable clamd (only if daemon = true)Verified bysystemctl is-active clamav-daemon clamd@scan 2>/dev/null
6. 06verifyTest detection (EICAR file)Verified byclamscan --no-summary /tmp/eicar.com

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