We’re pleased to announce that a new beta version of Imunify360, version 5.4, is now available. The following features are new in the v.5.4 beta release:

• Nginx support for “no panel” installations
  Imunify360 now supports Nginx + ModSecurity v3 setup on a server without a panel.
• Gradual removal of "Delete" and "Quarantine" actions
  Version 5.4 introduces the first step of “Delete” and “Quarantine” default action removal in the Malware Scanner UI. All stages were announced and explained in our blog earlier.
• Malware Database Scanner (MDS) improvements
  Earlier this year, we announced the CLI tool to find malicious injections in the database and clean-up them automatically. We continue improving the scanning engine. Another update allows the admin to detect and clean-up injections with various malicious and blacklisted URLs, which are stored in a separate URL database and regularly updated along with Malware Scanner databases. 

Let’s review the changes in version 5.4.

Nginx support for “no panel” installations

If you are managing a server powered by Nginx with a custom panel installed or without a panel, it’s the best time to install Imunify360 on it and protect your server proactively from all known threats, including all sorts of L7 attacks, malware, and web spam. 

Imunify360 could be easily configured with a few steps on a “panel-less” setup, so you will start to benefit from the security suite almost instantly.

Detailed documentation on how to configure Imunify360 with Nginx and ModSecurity v3 is available here.

Gradual removal of "Delete" and "Quarantine" Default Actions

During the last few years, Imunify products utilized several ways of handling malicious files in the Malware Scanner, giving users an option to choose a way that fits them best (Delete permanently, Quarantine file, Cleanup, or Just display in the dashboard). It’s been a while since we introduced the options, and some of them are obsolete and outdated (basically, they can cause issues). It was explained in detail in our blog post some time ago.

Ultimately, the Cleanup option includes everything needed to make the malware removal process safe and effective, and the websites remain operational afterward, unlike the quarantining and entire deletion of malicious files. None of the obsolete actions (Delete, Quarantine) can deal with injections, which are roughly half of all malicious entries found on infected websites, but the clean-up can.

Version 5.4 introduces the first step of “Delete” and “Quarantine” Default Action removal in the Malware Scanner UI. The options will still be available via the configuration file and the CLI, but they will be removed from the Settings’ drop-down list. If you have it selected, we recommend changing the Default Action to “Cleanup” (otherwise, it will not be changed upon the Imunify360 upgrade automatically; thus, you will continue using some of the obsolete Default Actions). There will be no issue with that, but we will remove them completely in v5.8 (in 3-4 months). All new installations will have “Cleanup” as Default Action.

Restore from the Quarantine is available until the “Quarantine” Default Action is completely removed from the product. You could still manage files in quarantine if they have been quarantined earlier. 

Malware Database Scanner (MDS) improvements for WordPress

We continue improving the database scanning engine. Another update allows admin to detect and clean-up injections with various malicious and blacklisted URLs in the WordPress database. Imunify will automatically update the URL blacklists and detect all known malicious injections of <IFRAME> and <SCRIPT> that can harm your website’s reputation. 

Check our instructions on how to run the Malware Database Scanner from the command-line. 

If you have not yet got a chance to test our CLI version of Malware Database Scanner, check it out now and let us know how we could improve it. Please, read a comprehensive guide on the tool in our blog first.

Additional information

Imunify360 v5.4 includes 102 tasks and 33 bug fixes.

Internal records

yum update imunify360-firewall --enablerepo=imunify360-testing

echo 'deb https://repo.imunify360.cloudlinux.com/imunify360/ubuntu-testing/16.04/ xenial main'  > /etc/apt/sources.list.d/imunify360-testing.list
apt-get update
apt-get install --only-upgrade imunify360-firewall

echo 'deb https://repo.imunify360.cloudlinux.com/imunify360/ubuntu-testing/18.04/ bionic main'  > /etc/apt/sources.list.d/imunify360-testing.list
apt-get update
apt-get install --only-upgrade imunify360-firewall