What Security Plugin Should I Use Alongside WP Ghost?
This tutorial has moved to the new WP Ghost Knowledge Base where each feature is presented in detail.
For prevention you don’t need a second plugin: WP Ghost hides the WordPress paths and blocks attacks, and Cloudflare in front of the site filters traffic at the edge. Add a malware scanner (your host’s, or a scan-based security plugin) only for detection and cleanup, which WP Ghost doesn’t do.
When does WP Ghost need another security tool?
WP Ghost is a prevention tool. It reduces your attack surface by changing WordPress paths, filtering malicious requests with the 2026 Ghost Firewall, protecting logins with 2FA and brute force limits, and sending security headers. Bots can’t attack paths they can’t find.
Prevention doesn’t cover detection: scanning files for malware, watching file changes and cleaning an infected site. WP Ghost doesn’t scan for malware, so that part comes from your host or from a scan-based security plugin.
What to pair with WP Ghost
The setup we recommend is WP Ghost on the site and Cloudflare in front of it. Cloudflare filters traffic at the network edge, and WP Ghost hides the WordPress structure and blocks what reaches your server. For malware scanning, use the scanner your host provides, or a scan-based security plugin with its overlapping features switched off.
What if my hosting already provides security?
If your hosting company offers malware scanning, file cleaning, and server-level protection (common on managed WordPress hosts like WP Engine, Kinsta, SiteGround, and Cloudways), you may not need a second security plugin at all. WP Ghost handles the prevention layer. Your hosting handles the detection and response layer. That’s already a complete stack.
Add a separate scanning plugin only if your hosting doesn’t include malware scanning or if you want more detailed monitoring than your host provides.
How do I avoid conflicts between security plugins?
The key rule: don’t switch on the same feature in two plugins. Scan-based security plugins often have their own custom login URL, 2FA, country blocking, IP blocking and login attempt limits. Pick one plugin for each feature and turn it off in the other. For example, let WP Ghost handle path security, 2FA with passkeys and brute force protection, and keep only the malware scanner on in the other plugin. Avoid two firewalls or two login limiters running at once.
For the full list of tested compatible plugins, see the compatibility plugins list.
Frequently asked questions
Can WP Ghost replace a scan-based security plugin?
WP Ghost covers prevention: path security, firewall, brute force protection, 2FA and security headers. It doesn’t scan for malware or monitor file integrity. If you need those and your host doesn’t provide them, keep a scanner next to WP Ghost. If your host handles malware detection, WP Ghost alone may be enough.
Do I need a paid security plugin or will free versions work?
Free tools are enough for most sites: WP Ghost Free on the site, Cloudflare’s free plan in front of it, and your host’s malware scanning. If your host doesn’t scan for malware, a free scan-based plugin fills that gap. Paid plans add things like priority support and longer log storage.
Does WP Ghost modify WordPress core files?
No. WP Ghost uses server rewrite rules and WordPress filters to change paths and block threats at runtime. No core files, theme files or plugin files are modified, so file-integrity scanners have no changed core files to flag. Deactivating WP Ghost restores all defaults instantly.