sidebar hamburger menu

Installation Guide


Supported operating systems

  • CentOS/RHEL 6,7,8,9
  • CloudLinux OS 6,7,8,9
  • Ubuntu 16.04 (LTS only), 18.04, 20.04 (LTS), and 22 (Plesk, DirectAdmin, and standalone)
  • Debian 9 (up to Imunify v6.11 (including)), 10 (requires buster-backports), and 11 (Plesk, DirectAdmin, and standalone)
  • AlmaLinux 8,9
  • Rocky Linux 8,9 (cPanel, Plesk, and standalone)


OpenVZ - works for Virtuozzo 7 with kernel 3.10.0-1160.80.1.vz7.191.4 or newer.


  • RAM: 1GB
  • HDD: 20GB available disk space
  • CPU: 64bit version on x86_64 processors only

Supported hosting panels

Required browsers

  • Safari version 10 or later
  • Chrome version 39 or later
  • Firefox version 28 or later
  • Edge version 17 or later

Supported Web-servers

  • Apache
  • LiteSpeed
  • Nginx (fully supported in the Standalone mode; for supported control panels – with ModSec 3 only for now)

Installation Instructions

No hosting panel installation note:

This instruction is intended for supported panels such as cPanel, Plesk, DirectAdmin, etc. from the list above. If you are currently using a non-supported control panel, please proceed with the Stand-Alone documentation section.

  1. Get your license key at You can purchase it or get a trial key from a received email.

  2. Log in with root privileges to the server where Imunify360 should be installed.

  3. Go to your home directory and run the commands:

wget -O
bash --key YOUR_KEY

where YOUR_KEY is your license key. Replace YOUR_KEY with the actual key - trial or purchased at

To install Imunify360 beta version add argument --beta . For example:

bash --key YOUR_KEY --beta

If you have an IP-based license, run the same script with no arguments:


To view available options for installation script run:

bash -h


In a case of registration key is passed later, then you can register an activation key via the Imunify360-agent command:

imunify360-agent register YOUR_KEY

Where YOUR_KEY is your activation key.

If you have IP-based license, you can use the following command:

imunify360-agent register IPL

SELinux support

If SELinux (Security-Enhanced Linux) is enabled on your server, you should install the Imunify360 SELinux policy module. You can check SELinux status by sestatus command. Policy is shipped with Imunify360 package and is located in the /opt/imunify360/venv/share/imunify360/imunify360.te

To apply it, run the following commands:

checkmodule -M -m -o /var/imunify360/imunify360.mod /opt/imunify360/venv/share/imunify360/imunify360.te
semodule_package -o /var/imunify360/imunify360.pp -m /var/imunify360/imunify360.mod
semodule -i /var/imunify360/imunify360.pp

After that, restart imunify360 and imunify360-webshield services. For CentOS6/CloudLinux6:

service imunify360 restart
service imunify360-webshield restart

For other systems:

systemctl restart imunify360
systemctl restart imunify360-webshield

If checkmodule command is not found, please, install it: For CentOS8/CloudLinux 8:

yum install policycoreutils-python-utils


On DirectAdmin, Imunify UI requires the proc_open PHP function to be enabled. If you are unable to open the Imunify UI, you might see a related message in the web server error log. If so, please remove it from the disable_functions list in php.ini.



IDS nameComment
LiteSpeedIntegrates with version 5.1 or higher.
EasyApache3Works only in cPanel.
EasyApache4Works only in cPanel.
CSFIntegrated with CSF, more details here.
CWAF AgentNo problems detected.
PatchmanNo problems detected.
SuhosinWe are ignoring alerts by Suhosin.
CloudflareImunify360 supports graylisting IP addresses behind Cloudflare. More details here.
CXSSpecial actions required to use Imunify360 with CXS installed.
cPHulkImunify360 disables cPHulk during installation. However in case of enabling it back, Imunify360 integrates with it and shows cPHulk events in the incident screen.
OpenVZWorks for Virtuozzo 7 with kernel 3.10.0-1160.80.1.vz7.191.4 or later.
UptimeRobotNo problems detected.


IDS nameComment
ASL (Atomicorp Secured Linux)ASL is not compatible with Imunify360, and cannot be run with Imunify360 on the same server.
fail2banImunify360 disables fail2ban: the latter resets chains of iptables rules which causes inconsistency with Imunify360