The renewal form lands in your inbox, and halfway down there are questions about patching, multi-factor authentication, backups and who has access to what. Some of them are really questions about your website. Client security reviews work the same way. If nobody on your team can answer them with confidence, this guide is for you.
One note before we start. Forms differ between insurers and clients, and this is not insurance or legal advice. Your broker should confirm what your policy requires. What follows is how common control questions apply to a WordPress site.
What underwriters tend to ask
The State of Indiana's cyber insurance toolkit lists 18 categories of controls that underwriters ask about, with sample questions. Most are about the whole organization, such as endpoints, email and staff training. Several land directly on your website and the people who run it.
What each question means for WordPress
| The question | What it means for WordPress | What to have ready |
|---|---|---|
| Routine patching | WordPress core, plugins and themes updated promptly. The toolkit's sample question asks about critical and high-severity patches within 30 days. | Update history and who applies updates |
| Current software | No end-of-life software: supported PHP version, no abandoned plugins or themes | A version list and a record of what was replaced |
| Multi-factor authentication | MFA on WordPress admin accounts, and on the hosting, domain registrar and email accounts behind them | Which accounts have MFA turned on |
| Access management | Only the access each person needs. Former staff, agencies and freelancers removed. | A user list with roles and an offboarding step |
| Backups | Backups kept off the web server, with a restore that has actually been tested | Backup schedule and the date of the last restore test |
| Monitoring and logging | Uptime monitoring, vulnerability alerts and an activity log | Who gets alerts and how long logs are kept |
| Response planning | A written plan for a hack or outage: who to call, how to restore, who tells customers | The plan and a contact list |
| Vendor management | Knowing which outside parties can touch the site: host, agency, freelancer, plugin vendors | A vendor list showing what access each has |
The questions most WordPress sites cannot answer
The technical controls are usually the easy part. The questions that stall people are ownership questions: who is responsible for updates, when was the last time anyone tested a restore, and who has admin access today. When nobody owns the site, the answers are guesses. We wrote about that gap in the WordPress accountability gap and why your site needs someone accountable.
What a managed provider can cover
A provider that runs your site can take on most of the website rows in that table. At CriticalWP, the $99 per month maintenance plan includes tested updates, the Patchstack firewall, uptime monitoring and backups. Managed Stability at $249 per month adds security hardening and posture monitoring. Vulnerability protection blocks exploit attempts against known plugin and theme flaws while updates are tested.
Whichever provider you use, ask what records they keep. A form asks you to prove things, so you want a provider who can show you the update history, the backup schedule and the access list.
A short prep list
- Write down who is responsible for WordPress updates, by name.
- List every user with admin access and remove the ones who do not need it.
- Turn on MFA for admin accounts, hosting, your domain registrar and email.
- Confirm backups run, live off the server, and restore a copy somewhere to prove it.
- Check your PHP version and look for plugins that have not been updated in a long time.
- Write a one-page plan: who to call, how to restore, who tells customers.
What this will not cover
Your website is one part of the questionnaire. Laptops, email, staff training and payment procedures all get asked about too, and none of that lives in WordPress. Answer every question truthfully. A clean answer you can back up beats a confident one you cannot.