CPGuard ​
CPGuard is a server security suite: antivirus, a web application firewall, and malware scanning for hosted sites. AdminBolt installs it from the Module Manager and shows its state on its own page.
Added in AdminBolt 1.7.0.
Overview ​
URL: /admin/cpguard, and /admin/cpguard-installer for the installation wizard.
The page appears in the Applications navigation group once CPGuard is installed. Until then, the module is offered in the Module Manager.
Note: CPGuard is a third-party product with its own licence. AdminBolt installs, connects and monitors it; the protection itself, and the reporting behind it, live in CPGuard's own app.
One security suite per server ​
CPGuard joins Imunify360 as a server security suite, and only one of the two is active on a server at a time. Decide which suite you want before installing: they both hook the same parts of the system, and running them together is not supported.
Installing ​
- Open the Module Manager and start the CPGuard installation.
- Enter your License Key.
- Run the installation and follow the log the wizard streams.
The installer refuses to start when the server is not in a state CPGuard can be installed on, and says why instead of failing halfway.
The status page ​
The page reports what the server itself says about CPGuard:
| Item | Meaning |
|---|---|
| Installed | The CPGuard package is present on the server |
| Running or Not running | The CPGuard service state |
| Connected or Not connected | Whether the server is registered with the CPGuard app |
| WAF rules | Which rule set is enforcing: CRS4 (AdminBolt) or CPGuard (CRS4 disabled) |
Open CPGuard Dashboard takes you to CPGuard's own app, where the scanning results, quarantine and policies live. Day-to-day security work happens there; this page is about the integration.
Switching the web application firewall ​
AdminBolt ships its own ModSecurity rule set, CRS4. CPGuard brings its own, and the two cannot enforce at the same time.
- Use CPGuard WAF (disable CRS4) turns off the shipped rules, enables the security engine, and hands the web application firewall to CPGuard. The web server is restarted as part of the switch.
- Restore CRS4 rules puts the shipped rule set back and returns the firewall to AdminBolt.
Warning: Both actions restart the web server. Check that the sites are still served afterwards, and expect a short interruption.
The action also switches CPGuard's own WAF on or off, so the two sides stay in step. Check the App Portal afterwards if the reporting there does not match what the panel says.
Under LiteSpeed, CPGuard's WAF blocks as expected, but its reporting stays empty: LiteSpeed writes its firewall events in a format CPGuard cannot read. The page says so where it applies.
Accounts and domains ​
Accounts and domains are kept in step with CPGuard as they are created, changed and removed, including after a web server switch. There is nothing to synchronize by hand.
Making it available to customers ​
Grant the CPGuard feature on a hosting plan to give those accounts the client CPGuard page.
Related pages ​
- Module Manager - where CPGuard is installed and removed.
- Imunify360 - the other security suite, and the alternative to this one.
- Apache Security Rules - the CRS4 rule set CPGuard's WAF replaces.
- Client CPGuard - what account owners see.