Security Suite & Firewall
A firewall inside the site for requests to public pages: allow and block lists of addresses and ranges, country and scanner rules, named rules for probes, a rate limit, temporary blocks that grow, a log and alerts.
Not open yet No card
Description
A firewall inside the site for requests to public pages: allow and block lists of addresses and ranges, country and scanner rules, named rules for probes, a rate limit, temporary blocks that grow, a log and alerts.
What it does
- Web app firewall for public pages: named, switchable rules for probes (WordPress addresses, hidden files, server tools, folder climbing, database commands and script in the address), with a watch-only mode
- Blocklist and IP rules: allow and block lists of addresses and ranges (IPv4 and IPv6), country blocking where the country can be trusted, and programs that call themselves scanners
- Rate limiting per address, by the minute and by ten seconds, counted exactly under simultaneous requests
- Temporary blocks that start after repeated refusals or a flood of missing pages and last twice as long each time
- Security alerts: an email to administrators when many requests are refused, at most one an hour, and a dashboard line
- A security log with search, a CSV download, and the address kept in full, shortened or as a code
- A box to try an address, program name and request against the rules before relying on them
- Malware scanner: there are no plugin or theme files on the server to scan. Modules and themes arrive as checked packs, and content is stored as blocks, not files. Not built yet.
- File-change detection: for the same reason there is no file system to watch. The pack's fingerprint is checked when it is installed. Not built yet.
- Protecting the admin area and the API: a module is asked only about public pages. Core would need to ask modules before those too, for instance a filter `core.request.guard` called for every path with `{ url, method, clientAddress, headers, area: 'admin' | 'api' | 'public' }` that may answer with a refusal. Until then Core's own sign-in limits and token checks guard them. Not built yet.
- Login security: sign-in history, lockouts and two-factor are the Login Security module's. Not built yet.
- Real-time threat feeds: lists of known-bad addresses fetched from a service. They need an outside service and a key; none is built in. Not built yet.
- CAPTCHA challenges in place of a refusal: a refused request gets a plain page with a reference. Forms can ask for Cloudflare Turnstile through the Spam Protection module. Not built yet.
Stands in for
Wordfence Security.
These are other companies' products, named only to say what job this module does. WebHD is not affiliated with them.
What comes across
What this module brings over from the plugin a site used before, and what it leaves behind. Each import ends with a report that names anything it could not carry.
- From Wordfence Security
- Comes across: The addresses and ranges it was told to block, and its allowlisted addresses, copied into a small JSON file.
- Does not: Its firewall rules and learning data, wildcard and from–to ranges (add those as CIDR ranges), country blocking, scan results, and its login and two-factor settings.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Solid Security (iThemes Security)
- Comes across: Banned hosts as the block list and authorised hosts as the allow list, from its settings export.
- Does not: Banned user agents (listed in the report to add by hand), lockout thresholds, file change detection, password and database rules, and two-factor settings.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From All In One Security (AIOS)
- Comes across: Its blocked addresses and its firewall allow list, from the one option it keeps its settings in; a list that was switched off there is left out.
- Does not: Wildcard and from–to ranges (add them as CIDR ranges), banned user agents (counted in the report), the sign-in allow list, login lockout and 404 lockout numbers, the permanent block table, file scans and .htaccess rules.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Jetpack Protect
- Comes across: The firewall's allow list and block list; a list that was switched off there is left out.
- Does not: Jetpack's automatic firewall rules and vulnerability scans (they come from Jetpack's service), brute-force protection, and wildcard or from–to ranges.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Patchstack
- Comes across: Its blocked addresses.
- Does not: Its sign-in allow list (counted in the report), wildcard and from–to ranges, and everything kept in Patchstack's own service: virtual patches, firewall rules and vulnerability reports.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From WP Ghost (Hide My WP Ghost)
- Comes across: Its allowed addresses as the allow list and its banned addresses as the block list.
- Does not: Hidden and renamed WordPress paths (there are none here to hide), banned user agents, host names and referrers (counted in the report), country blocking (named in the report), brute-force and two-factor settings.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- In place of Sucuri Security
- Its firewall is Sucuri's own cloud service in front of the site, and the plugin keeps only alert choices and a service key. There are no address lists or rules on the site to bring over: set the rules on the Security screen.
- In place of Anti-Malware Security and Brute-Force Firewall (GOTMLS)
- It scans plugin and theme files for malware and keeps definitions and a quarantine. This site has no plugin files to scan (modules arrive as checked packs), so nothing it stores applies; its firewall's job is the Security screen.
- In place of MalCare
- Its scans and settings live in MalCare's service; the plugin keeps a connection key. There is nothing on the site to bring over: set the firewall rules on the Security screen.
- In place of Block Bad Queries (BBQ)
- The free plugin has no settings: it refuses requests that match fixed patterns. The Security screen's rules for probes, folder climbing, database commands and script in the address do that job.
- In place of NinjaFirewall
- Its rules are built in and its address lists are a paid feature kept in files outside WordPress's settings. Nothing the free plugin stores can be read here: set the rules and lists on the Security screen.
Using a plugin that is not named here? It is built for your site On The Fly. How that works
Changelog
1.1.1 November 19, 2026
Security Suite & Firewall 1.1.1: on Cloudflare, searching the log for long text (a long address that was asked for, or a long program name) gave an error page. It now narrows the log.
1.0.0 November 18, 2026
Security Suite & Firewall: a firewall for public pages with block and allow lists (addresses and ranges), rules for common probes, per-address rate limits, temporary blocks that grow, a watch-only mode and a security log. A signed-in administrator is never blocked. Imports blocked addresses from Wordfence and Solid Security.
1.1.0 November 17, 2026
Security Suite & Firewall 1.1.0: imports blocked and allowed addresses from All In One Security (AIOS), Jetpack Protect, Patchstack and WP Ghost, each address once, leaving out lists that were switched off on the old site. Wildcards, from–to ranges, banned programs, sign-in allow lists and country blocking are named in the report for adding by hand. Sucuri, Anti-Malware (GOTMLS), MalCare, Block Bad Queries and NinjaFirewall keep nothing on the site that applies here, so they are listed as replaced.
Get Security Suite & Firewall when WebHD opens
One form on the home page: your WordPress address, then your email.
No card Takes a minute No fake scan