We are pleased to announce that the new Imunify360 version 4.4 is now scheduled for gradual roll-out from our production repository and will be available for all customers in about two weeks or less.
If you want to upgrade to the new Imunify360 version 4.4 right now, you can run the following commands:
wget https://repo.imunify360.cloudlinux.com/defence360/imunify-force-update.shbash imunify-force-update.sh
Version: 4.4.4-2
Rolled out to: 1%
Last updated: December 18, 2019 11 am EST
We’ve introduced an effective way to prevent brute-force attacks against FTP/SSH. It considers both the username and IP address used in an attack, so it’s possible to distinguish between legitimate user logins and brute-force attacks against the account. It works in a more effective way with fewer false positives. It is enabled in the GUI via Settings->General->PAM.
It can also be enabled via the CLI with the following command:
imunify360-agent config update '{"PAM": {"enabled": true}}'
The KernelCare extension for Imunify360 allows the tracing of malicious invocations to detect privilege escalation attempts. We use KernelCare’s Honeypot to hook into those calls to catch vulnerability exploitation attempts, notifying administrators when something bad is happening on the server. In version 4.4, we list attempts on the Incident tab (as part of the OSSEC log). The incident can be seen by filtering events with the “EDF” label.
This is how you activate it:
It can also be enabled via the CLI with the following command:
imunify360-agent config update '{"KERNELCARE": {"edf": true}}'
Malicious binary executables (ELF files) are often placed within user home directories. So, there is a new option that also scans these directories for malware. To prevent too many false positives, it’s disabled in version 4.4 by default.
As this is an experimental feature, please share your experiences of it via feedback@imunify360.com, so we can improve it in future versions.
In previous versions, CDN support was considered experimental. It is now proven, so we have enabled it by default for all new installations. It lets Imunify360 manage traffic coming through, and detects attackers behind CDNs and proxies.
For existing installations, you can turn it on in the UI with:
Settings->General->WebShield
or via the CLI:
imunify360-agent config update '{"WEBSHIELD": {"known_proxies_support": true}}'
In previous versions, the DOS plugin was also considered experimental, but it too has proved its worth so now it’s time to enable it by default for all new installations.
For existing installations, you can turn it on in the UI using:
Settings->General->DoS Protection
It can be enabled via the CLI with:
imunify360-agent config update '{"DOS": {"enabled": true}}'
We’ve implemented a series of improvements to make Imunify360 perform better on low-RAM VPS servers. We call it “Low Resource Usage” mode. It is enabled by default for the installations with low RAM.
In the “Low Resource Usage” mode, Imunify360 disables WebShield component (and GreyListing as a dependent) and switches to the minimized ModSec ruleset to dramatically reduce RAM usage, yet stay defensive and effective.
You can easily switch back to the normal mode just by enabling WebShield or unchecking “Minimized ModSec Ruleset” in Settings.
ImunifyAV now has the same domain reputation features already enjoyed by Imunify360 customers.
Imunify360 can block almost all brute-force server attacks within 2 minutes of them starting.
Under some conditions, the results of scans were not consistent in the UI (the number of detected threats might vary). This has been fixed.
The installation process of Imunify360 for Plesk became more visible and informative:
It has got a log window:
If you have any comments and suggestions regarding the release, or any feature requests, you can reach out to the product team via feedback@imunify360.com.
And, don’t forget the support team, who are always happy to help with any issues or questions on product installation and usage. To contact them, submit a ticket via ZenDesk.
To install the new Imunify360 version 4.4, please follow the instructions in the documentation.
yum update imunify360-firewall
apt-get update
apt-get install --only-upgrade imunify360-firewall