Skip to content

Imunify360 vs ImunifyAV vs AV+: which one fits your cPanel

Compare Imunify360 vs ImunifyAV and ImunifyAV+ on a cPanel server and pick the tier that matches who uploads code to it. You will also see how to move between tiers safely and keep them from clashing with CSF or other firewalls.

Pick Imunify360 if people you don’t control can put PHP on your cPanel server, and pick ImunifyAV or ImunifyAV+ if the only code on it is code your own team deploys. Shared hosting, reseller accounts and WordPress fleets where clients install their own plugins all fall in the first group. ImunifyAV, CloudLinux’s free malware scanner, finds infected files after they land on disk. ImunifyAV+ adds automatic cleanup and blocklist monitoring to that same scanner, so it suits a team that already reads scan results but loses hours removing what it finds. Imunify360 is the only tier that can stop an attack earlier, at the firewall, in the request or while PHP runs.

What you’ll accomplish

  • Know exactly what each tier can and cannot do, from one table built on CloudLinux’s own documentation.
  • Match a tier to your server based on who runs code on it and who reviews the findings.
  • Move from ImunifyAV to ImunifyAV+ or Imunify360, or back down, with the commands CloudLinux documents.
  • Avoid the common clashes when Imunify360 meets CSF (ConfigServer Security & Firewall), fail2ban or a second ModSecurity rule set.

Where each tier acts during an attack

Most compromises of a cPanel account follow the same path. A request arrives, it reaches a PHP script, the script writes a file, and the file sits on disk until someone finds it. Each tier gets its first chance to act at a different point on that path.

Attack path from request to cleanup, showing Imunify360 covering the firewall, WAF, PHP execution, file scan and cleanup steps, while ImunifyAV and AV+ only act once a file is on disk

ImunifyAV and ImunifyAV+ start at the file on disk. By then the attacker’s code has already run at least once. Imunify360 adds three earlier layers. Its firewall drops traffic from IP addresses with a bad reputation and blocks brute-force logins. Its WAF (web application firewall, a filter that inspects each HTTP request for attack patterns) runs as a rule set inside ModSecurity. That is the open-source request filter cPanel offers as an EasyApache 4 module. Proactive Defense is a PHP module that watches what scripts do while they run and can block patterns such as command injection or malicious code planting.

The three tiers compared

What you needImunifyAVImunifyAV+Imunify360
Malware scanning on demandYesYesYes
Scheduled background scansMonthly onlyDaily, weekly or monthlyDaily, weekly or monthly
Automatic cleanup of infected filesNo, it detects and listsYes, originals kept 14 days by defaultYes, originals kept 14 days by default
Real-time scanning of changed files in user accountsNoNoYes
Scanning of files uploaded over HTTP and FTPNoNoYes, needs ModSecurity (HTTP) and Pure-FTPd (FTP)
WAF rules in ModSecurityNoNoYes, as the imunify360-full-apache or imunify360-full-litespeed vendor
Firewall with IP reputation lists and a bot challenge pageNoNoYes
Brute-force protection for SSH, FTP and mail loginsNoNoYes
Proactive Defense for PHPNoNoYes, requires Hardened PHP (CloudLinux’s alt-php builds)
Hardened PHP and KernelCareNoNoInstallable from Settings; KernelCare is included on Imunify360 servers
Reputation monitoring (Google Safe Browsing, Spamhaus and others)NoYesYes
cPanel and WHM integrationWHM plugin; end-user view off by defaultWHM plugin; end-user view off by defaultWHM plugin and an end-user interface
Licensing modelFree, no key neededPaid licence, by key or by server IPPaid licence, by key or by server IP

Three rows deserve a closer look. Real-time scanning means the agent checks a file as soon as it changes, instead of waiting for the next scheduled pass. KernelCare applies kernel security patches without a reboot, and CloudLinux’s documentation says it is included on servers running Imunify360. Brute-force protection uses Imunify360’s own intrusion detection plus a PAM module, the Linux login layer that SSH and FTP pass through.

Some protections sit outside all three tiers. None of them updates your clients’ WordPress plugins, takes backups or isolates one cPanel account from another. Account isolation on cPanel comes from CloudLinux OS features such as CageFS, a per-user virtual file system.

Who should pick which

ImunifyAV fits a server where your own team writes and deploys all the code. Think of an agency’s staging box or a small set of business sites that change through your own release process. A monthly scan plus someone who reads the results is a fair baseline there. If you want a scan more often than monthly, that is a reason to upgrade.

ImunifyAV+ fits a server where you maintain client sites and findings already get reviewed, but cleanup eats your week. You keep the same scanner and gain one-click and automatic cleanup, daily or weekly schedules and an alert when a hosted domain lands on a public blocklist. It still cannot block a request, so it suits sites where break-ins are rare and get patched quickly.

Imunify360 fits any server where strangers upload code. That covers shared hosting, reseller plans and WordPress fleets with client-installed plugins. On those servers the useful question is how many attacks you can stop before a file exists. Imunify360 can also replace a self-managed firewall stack if you want one product to run, though it can coexist with CSF.

Before you pay for Imunify360’s WAF, check what ModSecurity is already doing on the server. The Fail2ban vs CSF vs Imunify360 comparison covers where each of those layers draws its line.

How to move between them

Run every command below as root over SSH. First copy the Imunify configuration directory, which both products use, so you can compare settings after the switch.

cp -a /etc/sysconfig/imunify360 /root/imunify360-config-backup

No output means the copy worked.

1. Check what is installed today. Package names are the reliable way to tell the tiers apart on an inherited server.

rpm -q imunify-antivirus imunify360-firewall

Example output on a server running ImunifyAV or ImunifyAV+:

imunify-antivirus-8.4.1-2.el9.x86_64
package imunify360-firewall is not installed

On a cPanel server running Ubuntu, dpkg -l imunify-antivirus imunify360-firewall gives the same answer. If imunify360-firewall is installed instead, the server runs Imunify360. ImunifyAV and ImunifyAV+ share the imunify-antivirus package, so only the licence tells them apart. Open the ImunifyAV plugin in WHM under Plugins. A Reputation Management item in its menu means ImunifyAV+, since that feature exists only in the paid tier. No such item means the free ImunifyAV.

2. Upgrade ImunifyAV to ImunifyAV+. No reinstall is needed. Register the key you bought, or use IPL if your licence is tied to the server’s IP address.

imunify-antivirus register YOUR_KEY
imunify-antivirus rstatus

Expected output is OK from rstatus, which means the licence is registered and valid. An error message instead means the key was not accepted, so check it for typos. You can also activate the key from the Upgrade page of the ImunifyAV plugin in WHM. Then raise the scan schedule, since daily scans are one of the things you paid for:

imunify-antivirus config update '{"MALWARE_SCAN_SCHEDULE": {"interval": "DAY", "hour": 3}}'

To confirm, open the plugin’s background scanning settings. Run scanning should read Daily, with 3 as the hour. On the free tier the agent resets a daily or weekly schedule back to monthly, which is a quick way to spot a licence that did not apply.

3. Upgrade ImunifyAV or ImunifyAV+ to Imunify360. CloudLinux’s guidance is to uninstall ImunifyAV first and then install Imunify360. Buying the licence alone does not switch the product. Before you start, list your ModSecurity vendors, the rule sets that cPanel’s ModSecurity engine loads:

whmapi1 modsec_get_vendors | grep -E '^ +(enabled|name):'

Example output on a server with only the OWASP rules installed:

      enabled: 1
      name: OWASP ModSecurity Core Rule Set V3.0

Each vendor prints one enabled line and one name line, and enabled: 1 means its rules are active. If another vendor such as OWASP CRS or Comodo is enabled, the Imunify360 installer adds only a minimal rule set. Turn other vendors off in WHM » Security Center » ModSecurity® Vendors before installing if you want the full Imunify360 rules. Then swap the products:

wget https://repo.imunify360.cloudlinux.com/defence360/imav-deploy.sh -O imav-deploy.sh
bash imav-deploy.sh --uninstall
wget https://repo.imunify360.cloudlinux.com/defence360/i360deploy.sh -O i360deploy.sh
bash i360deploy.sh --key YOUR_KEY

The uninstall step keeps ImunifyAV’s state data and configuration. When the installer finishes, confirm that the service runs and the licence is valid:

systemctl is-active imunify360
imunify360-agent rstatus

Expected output is active, then OK. If the service shows inactive or failed, read the end of the installer’s output for the error before going further.

4. Check the safe defaults before production traffic hits it. Proactive Defense ships in log-only mode, which records suspicious PHP behaviour without blocking it. Confirm that, and check ModSecurity’s global settings:

imunify360-agent config show --json -v | grep -A6 PROACTIVE_DEFENCE
imunify360-agent check modsec directives

Expected output includes "mode": "LOG". The second command prints a WARNING line for each ModSecurity directive that differs from Imunify360’s recommendation. imunify360-agent fix modsec directives applies the recommended values. Keep Proactive Defense in LOG mode for the first weeks, as the first 30 days of Imunify360 tuning describes, before you switch it to KILL.

5. Prove the WAF rules are live. CloudLinux provides a harmless test request that triggers a marker rule. Replace example.com with a domain hosted on the server.

curl -s -o /dev/null "http://example.com/?i360test=88ff0adf94a190b9d1311c8b50fe2891c85af732"
grep 'IM360 WAF: Testing the IM360 ModSecurity ruleset' /var/log/imunify360/console.log

Expected output is at least one log line containing that text. No match means the Imunify360 vendor isn’t loaded (see Troubleshooting).

6. Downgrade from Imunify360 to ImunifyAV or ImunifyAV+. If you plan to reuse the Imunify360 licence on another server, unregister it first. Then uninstall and install ImunifyAV, with your key if you bought ImunifyAV+.

imunify360-agent unregister
wget https://repo.imunify360.cloudlinux.com/defence360/i360deploy.sh -O i360deploy.sh
bash i360deploy.sh --uninstall
wget https://repo.imunify360.cloudlinux.com/defence360/imav-deploy.sh -O imav-deploy.sh
bash imav-deploy.sh --key YOUR_KEY
imunify-antivirus rstatus

Expected output from the last command is OK. Leave out --key YOUR_KEY to go back to the free tier. On CloudLinux OS, also run cagefsctl --force-update and cagefsctl --remount-all afterwards, as CloudLinux’s uninstall notes describe. Imunify360 turns off cPHulk (cPanel’s built-in login blocker) and fail2ban (a tool that bans IPs after repeated failed logins) when it installs. Check WHM » Security Center » cPHulk Brute Force Protection afterwards, because without Imunify360’s firewall nothing may be blocking brute-force logins.

Troubleshooting

The Imunify360 installer stops with a message about uninstalling ImunifyAV. The error reads “You’ve got a license for the advanced security product Imunify360. Please, uninstall ImunifyAV and replace it with the Imunify360”. It appears when you install over ImunifyAV, including from WHM’s store. Run bash imav-deploy.sh --uninstall, then rerun i360deploy.sh.

CSF and Imunify360 both seem to manage the firewall. Imunify360 detects CSF automatically and turns off its own Blocked Ports, DoS Protection and SMTP Traffic Manager features. IPs you allow in CSF stay managed in CSF, and Imunify360 won’t block them. CloudLinux recommends setting LF_MODSEC = "0" in /etc/csf/csf.conf. Otherwise CSF blocks IPs on every ModSecurity event, which produces many false positives. To see what Imunify360 thinks is competing with it:

imunify360-agent 3rdparty list

Example output on a server that still runs fail2ban:

fail2ban

No output means Imunify360 found no competing intrusion detection tool.

fail2ban or firewalld stopped working after the install. That is expected. Imunify360 disables fail2ban because fail2ban resets iptables chains that Imunify360 relies on. firewalld can run alongside it, but rules may need to be set in both places, so CloudLinux recommends either Imunify360’s firewall alone or Imunify360 with CSF. Atomicorp Secured Linux (ASL) cannot share a server with Imunify360 at all.

Every page returns a 500 error after installing on LiteSpeed. CloudLinux documents a conflict between the OWASP rule set and Imunify360’s rules on LiteSpeed Web Server. Turn OWASP off in ModSecurity® Vendors, reload the web server and test again.

The WAF test finds nothing, or uploads are not scanned. cPanel does not install ModSecurity as part of Imunify360. Without it, you get neither the WAF nor scanning of files uploaded over HTTP. Install ModSecurity through EasyApache 4 (WHM » Software » EasyApache 4), then add the rules and turn on their automatic updates:

imunify360-agent install-vendors
/usr/local/cpanel/scripts/modsec_vendor enable-updates imunify360-full-apache

On LiteSpeed, use imunify360-full-litespeed in the second command. Then repeat the WAF test from step 5. The log line should now appear, and if it still does not, check that ModSecurity shows as installed in EasyApache 4. If ConfigServer eXploit Scanner (CXS) is also installed, disable its cxswatch service and its ModSecurity vendor, or the two scanners will compete for the same files.

When this is the wrong approach

No tier fixes a compromise that is happening right now. If a site is serving malware today, contain it, restore from a clean backup and close the way in first. The ImunifyAV quarantine and cleanup workflow helps with the triage. Cleanup removes the infected file, but an unpatched plugin or a leaked FTP password will let the same attacker back in.

Imunify360 is also the wrong buy when nobody will look after it. Its firewall and WAF can block real customers, and someone has to read the incidents and adjust rules. If no one owns that, ImunifyAV+ is the calmer choice because its worst failure is a scan result nobody read.

Finally, none of these tiers replaces routine hygiene. Keep WordPress core and plugins current, use SSH keys, keep code directories non-writable where you can and test restores. A server with all of that and no untrusted tenants is often well served by ImunifyAV alone. CloudLinux’s Imunify documentation covers all three products, and cPanel’s documentation covers the ModSecurity side.

If this is the kind of work you’d rather never own again, it’s the daily job of Managed Cloud Ops — book an infrastructure review.