Short answer
Check security alerts every day and apply security fixes the same day, do routine updates weekly on staging, and audit plugins, users, and the PHP and database versions monthly. On IIS, the tasks stay the same but the tools change: NTFS permissions instead of chmod , web.config instead of .htaccess , IIS logs, Task Scheduler instead of cron, and PHP updates I install myself.
I maintain a law firm's WordPress site that runs on Windows Server and IIS. This post is the routine I've set up for it and follow from now on: what I check, how often, and which steps from the usual Linux-based guides work differently on IIS. The full 49-task checklist is at the end as a PDF.
Why I check more often now
Four things changed in 2026, and together they moved security work from my weekly list to my daily one.
Patches race attackers. Patchstack counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 91% of them in plugins. 46% had no fix from the developer when they were made public.…