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. 01reconRDP already on (fDeny 0)? NLA (1 = required)? custom port?
  2. 02reconstate of the "Remote Desktop" rules (language-independent group)
  3. 03reconTermService service present and startable?
  4. 04actRequire NLAverify
  5. 05actEnable RDPdestructiveverify
  6. 06actAllow through the firewalldestructiveverify
  7. 07actRestrict access (only if an allowed IP is provided)verify
  8. 08actCheck it is listeningverify

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. 01Require NLAVerified by(Get-ItemProperty 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp').UserAuthentication
  2. 02Enable RDPVerified by(Get-ItemProperty 'HKLM:\System\CurrentControlSet\Control\Terminal Server').fDenyTSConnections
  3. 03Allow through the firewallVerified by(Get-NetFirewallRule -Group '@FirewallAPI.dll,-28752' | Where-Object Enabled -eq 'True' | Measure-Object).Count
  4. 04Restrict access (only if an allowed IP is provided)Verified byGet-NetFirewallRule -Group '@FirewallAPI.dll,-28752' | Get-NetFirewallAddressFilter | Select-Object -ExpandProperty RemoteAddress -Unique
  5. 05Check it is listeningVerified by(Test-NetConnection -ComputerName localhost -Port 3389 -WarningAction SilentlyContinue).TcpTestSucceeded

SEC.03

Guardrails

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

RDP exposed to the Internet is an attack target: NLA always required, restricting to an IP/VPN strongly recommended. Do not change the listening port. Do not cut current sessions.

SEC.04

Variables

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

NameMeaning
${allowed_ip}Allowed IP/range (optional)

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.

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

Deploy on Servor button

Maintain Remote Desktop (RDP) 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/enable-rdp)

SEC.07

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.