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. 01reconWindows edition and build (ProductType 1 = workstation, 2 = DC, 3 = server), RAM
  2. 02reconIIS already installed? (Get-WindowsFeature on servers, optional feature on workstations)
  3. 03reconports 80/443 already taken? (PID 4 = http.sys: IIS or another HTTP.sys app)
  4. 04reconexisting IIS sites (leave them untouched)
  5. 05actInstall IISverify
  6. 06actStart the serviceverify
  7. 07actCheck the HTTP responseverify

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. 01Install IISVerified by(Get-WindowsFeature Web-Server).InstallState
  2. 02Start the serviceVerified by(Get-Service W3SVC).Status
  3. 03Check the HTTP responseVerified by(Invoke-WebRequest -UseBasicParsing -Uri http://localhost/ -TimeoutSec 10).StatusCode

SEC.03

Guardrails

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

Never overwrite or remove an existing site or binding. If port 80 is held by another process, stop and report it. Do not open any extra firewall rule: the install already enables "World Wide Web Services (HTTP Traffic-In)".

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.

recipe — fail2ban_setup150+ in catalogue
security4 steps · low risk · idempotentrun
reconsshd present? ufw active? existing jails?✓
actinstall fail2ban · write default jails✓
actenable service · restart sshd (safe)✓
verifytest ban 60s · jails active · sshd alive✓

search by intent — type “firewall”, get ufw

  • 01Read-only reconnaissance before any change
  • 02Every command signed by your browser, approved by you
  • 03Each step verified before the run moves on, every run kept in the history

SEC.05

Deploy on Servor button

Maintain IIS (web server) 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.

Deploy on ServorDark background
Deploy on ServorLight background
[![Deploy on Servor](https://servor.app/badges/deploy-on-servor.svg)](https://servor.app/deploy/install-iis)

SEC.06

Verified recipe

Run this recipe on your server

Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.