On a shared cPanel host running mostly WordPress, enable ConfigServer as your rule vendor for ModSecurity, the web application firewall inside Apache. This comparison is for cPanel administrators weighing the three rule sets that WHM (Web Host Manager) can install, which decide what the firewall blocks. They are the OWASP (Open Web Application Security Project) Core Rule Set, Comodo CWAF (Comodo Web Application Firewall) and ConfigServer ModSecurity Control. Pick OWASP CRS when a compliance requirement names it, and Comodo CWAF when a single-application box needs aggressive bot blocking. Keep only one enabled, because two active vendors double your false positives and roughly double the rule-parse time per request.
What’s happening
ModSecurity is a rules engine; the rule set is what tells it what to block. cPanel exposes the active rule set in WHM > ModSecurity Vendors. Adding a vendor downloads its rule pack and enables it; removing one disables it. The default WordPress-host-grade vendor (in our experience) is ConfigServer because it has the smallest false-positive surface on cPanel workloads, but CRS is the safe choice when compliance asks “are you running OWASP” and Comodo is acceptable when you want the broadest catch-all and have budget for ticket triage.
How to verify
See which vendor(s) are active:
whmapi1 modsec_get_vendors
ls /usr/local/cpanel/modsec_vendor_configs/
grep -r "SecRule\|Include" /etc/apache2/conf.d/modsec_vendor_configs/*/ | wc -l
modsec2-clearcache 2>/dev/null
If whmapi1 modsec_get_vendors returns more than one enabled=1, you are running two rule sets concurrently and inheriting both vendors’ false positives.
The fix
- Decide which vendor matches the workload. WordPress-heavy shared host with mixed plugins: ConfigServer. Compliance-driven hosting with explicit “OWASP CRS” line item: OWASP CRS. Aggressive bot-blocking required on a single-application host: Comodo CWAF.
- WHM > ModSecurity Vendors > disable the vendors you do not want. The toggle is per-vendor; disabling does not uninstall.
- If only one vendor was active and you are switching: install the new vendor first (it downloads in the background), confirm it is enabled, then disable the old. There is no atomic swap; you accept a few minutes of both being on or both being off depending on which order you choose.
- Run
modsec2-clearcacheif available, thenapachectl -t && apachectl graceful. ModSecurity reloads rules with Apache. - Watch the audit log for a few hours:
tail -f /etc/apache2/logs/modsec_audit.log(path varies; check WHM > ModSecurity Tools > Audit Log). False positives surface quickly — typically a customer reporting “I cannot post to my contact form.” - For false positives that are legitimate, disable the specific rule per account rather than disabling the whole rule. See the dedicated article on
SecRuleRemoveByIdpatterns.
For environments where ModSecurity policy is part of compliance posture, Stack Harbor picks the vendor against the workload and tracks false-positive disables under cPanel server administration.