Websites are constantly threatened by automated bots, malware, compromised scripts, and other attacks. An attack does not necessarily have to be targeted at a specific website. A large portion runs fully automatically: bots scan servers and websites for known vulnerabilities, outdated plugins, insecure access credentials, or opportunities to inject malicious code.<\/p>\n\n\n\n
This is precisely where to start ImunifyAV and Imunify360<\/strong> Both security solutions are from CloudLinux and were developed specifically for Linux web servers and hosting environments. Although the names sound similar, the two solutions differ significantly in their range of functions.<\/p>\n\n\n\n Simply put, ImunifyAV a malware scanner<\/strong>. Imunify360 goes significantly further, forming a multi-layered security platform that detects and cleans malware, blocks attacks, analyzes suspicious behavior, and can protect websites even while an attack is underway.<\/p>\n\n\n\n ImunifyAV is a security solution for detecting malware on Linux web servers. The scanner examines files within a hosting environment while attempting to detect malicious or tampered code.<\/p>\n\n\n\n These can include smuggled PHP files, backdoors, webshells, or manipulated components of a website. Especially with content management systems like WordPress, attackers can modify existing files or place additional files in the web space after a successful compromise.<\/p>\n\n\n\n A typical example is a vulnerable WordPress plugin. If an attacker succeeds in injecting malicious code through this vulnerability, the malware scanner can detect the suspicious file.<\/p>\n\n\n\n The scanner scans files and analyzes them for known and suspicious structures. It doesn't just search for specific file names. Malware can hide in regular PHP files, manipulate existing code, or be heavily obfuscated.<\/p>\n\n\n\n Imunify therefore uses various detection mechanisms to track down malware, backdoors, webshells, and other manipulations.<\/p>\n\n\n\n This is an important component of server security. However, there is a fundamental difference between the Detecting an infection<\/strong> and the actively preventing an attack<\/strong>.<\/p>\n\n\n\n Right at this point, the significantly broader range of features of Imunify360 begins.<\/p>\n\n\n\n Imunify360 is a comprehensive security platform for Linux web servers. The malware scanner is just one of several layers of protection.<\/p>\n\n\n\n The system combines malware detection and automatic cleanup with a firewall, web application firewall, intrusion detection and prevention, proactive defense, brute-force protection, and mechanisms against malicious bots and automated attacks.<\/p>\n\n\n\n The crucial difference thus lies in the approach: A malware scanner searches for malicious software. Imunify360 additionally attempts to detect and stop many attacks before they result in a successful compromise of the website.<\/p>\n\n\n\n A particularly important function of Imunify360 is the Real-Time Malware Scan<\/strong>. This real-time monitoring is activated in CURIAWEB.<\/p>\n\n\n\n This means that protection does not exclusively wait for a scheduled malware scan. Imunify360 can monitor changes to files in a website's DocumentRoot and immediately check newly or newly modified files.<\/p>\n\n\n\n Even files uploaded via a website or HTTP\/HTTPS can be scanned in real time. The same applies to uploads via FTP, provided the server is configured accordingly.<\/p>\n\n\n\n This is relevant, for example, when a compromised web application attempts to place a malicious PHP file on the web space or when malware is to be introduced via an upload function. Imunify360 can detect such a file immediately and trigger appropriate protective measures instead of encountering it hours later during the next full scan.<\/p>\n\n\n\n This significantly reduces the time window between the appearance of a malicious file and its detection.<\/p>\n\n\n\n If Imunify360 finds malware, protection doesn't end with a simple warning. The platform can automatically clean infected files.<\/p>\n\n\n\n This is particularly important in hosting environments. A compromised website can damage more than just the actual operator. Injected code can be misused, for example, for sending spam, phishing, unwanted redirects, spying on login credentials, or launching further attacks.<\/p>\n\n\n\n The faster an infection is detected and eliminated, the smaller the risk of further problems developing from it.<\/p>\n\n\n\n A Web Application Firewall, WAF for short<\/strong>, analyzes web requests and attempts to detect malicious requests before the targeted application processes them.<\/p>\n\n\n\n This is particularly relevant for WordPress. A WordPress website often consists not only of WordPress itself, but also of numerous plugins and themes. If a security vulnerability is discovered in a popular extension, automated systems sometimes start scanning the internet for vulnerable installations within a short time.<\/p>\n\n\n\n The WAF can detect and block corresponding attack patterns. Imunify360 also supports so-called Virtual Patching<\/strong>. This makes it possible to protect known vulnerabilities in WordPress, plugins, and themes without having to modify the file in question.<\/p>\n\n\n\n This does not replace a necessary update. However, it can form an important additional layer of protection, especially in the period between a security vulnerability becoming known and the installation of the corresponding update.<\/p>\n\n\n\n We explain in more detail why regular updates remain important anyway in the article Why WordPress updates are necessary<\/a>.<\/p>\n\n\n\n Proactive Defense<\/strong> pursues yet another approach.<\/p>\n\n\n\n A classical malware scanner examines files and attempts to determine whether malicious code is present in them. Proactive Defense, on the other hand, analyzes the Behavior of PHP scripts during their execution<\/strong>.<\/p>\n\n\n\n This enables the system to detect suspicious actions, such as obfuscated command executions, the injection of malicious code, certain forms of SQL injection, or an attempt by a manipulated script to send spam.<\/p>\n\n\n\n This is particularly interesting in the case of new or yet unknown attack methods. Instead of exclusively searching for a known malware signature, consideration is also given to what a PHP script is actually trying to execute.<\/p>\n\n\n\n Upon proper detection, Imunify360 can stop the execution of the malicious process.<\/p>\n\n\n\n Not every attack consists of a malicious file. A classic example is automated login attempts.<\/p>\n\n\n\n Bots can try out large numbers of different combinations of usernames and passwords in a short time. Such brute-force attacks can affect various services on a server.<\/p>\n\n\n\n Imunify360 monitors suspicious activity and can automatically block conspicuous IP addresses or subject them to additional verification. This layer of protection thus operates independently of whether malware is already present on a website.<\/p>\n\n\n\n A significant portion of today's internet traffic is generated by automated systems. Among them are legitimate search engine crawlers, as well as scanners, scrapers, spam bots, and automated attack tools.<\/p>\n\n\n\n Imunify360 can detect suspicious automated traffic and intercept corresponding access requests. In doing so, legitimate visitors should remain as unaffected as possible.<\/p>\n\n\n\n This not only protects against certain attacks, but can also conserve server resources. A malicious bot whose request is already stopped at an upstream security layer cannot trigger resource-intensive processes within a website.<\/p>\n\n\n\n With WordPress, CURIAWEB goes a step further. The Imunify Security Plugin for WordPress is automatically installed<\/strong> and works together with the server-side Imunify360 protection.<\/p>\n\n\n\n Therefore, the customer does not need to search for, purchase, or manually install the security plugin themselves.<\/p>\n\n\n\n The plugin brings information from the server-side security platform directly into the WordPress administration area. Among other things, the current security status of the website can be viewed there. Detected or cleaned malware as well as the status of important protection functions can thus be made visible directly within WordPress.<\/p>\n\n\n\n At the same time, the plugin complements the server-side protection mechanisms with WordPress-specific functions. This includes, in particular, the Web Application Firewall with virtual patching for known vulnerabilities in WordPress core, plugins, and themes.<\/p>\n\n\n\n Another layer of protection involves automated bots. The protection can detect and limit aggressive crawlers, scrapers, and other automated access before WordPress even needs to be fully loaded.<\/p>\n\n\n\n With this, a WordPress website at CURIAWEB<\/a> multiple layers intertwined: server-side protection by Imunify360 and additional WordPress-specific protection directly within the CMS.<\/p>\n\n\n\n The most important difference is not that one of the products simply has a slightly better virus scanner.<\/p>\n\n\n\n ImunifyAV focuses primarily on malware detection.<\/strong> It primarily answers the question: Are there suspicious or malicious files on the server?<\/p>\n\n\n\n Imunify360, on the other hand, takes a multi-layered security approach.<\/strong> Malware detection is combined with automatic remediation, real-time monitoring, firewall mechanisms, attack detection, proactive defense, and further layers of protection.<\/p>\n\n\n\nWhat is ImunifyAV?<\/h2>\n\n\n\n
How does the malware scanner work?<\/h3>\n\n\n\n
What is Imunify360?<\/h2>\n\n\n\n
Real-time protection: Files are not just checked during the next scan<\/h2>\n\n\n\n
Detect malware and clean it automatically<\/h2>\n\n\n\n
What does the Web Application Firewall do?<\/h2>\n\n\n\n
Proactive Defense protects during execution<\/h2>\n\n\n\n
Intrusion Detection and Protection against Brute-Force Attacks<\/h2>\n\n\n\n
Protection against bots and automated attacks<\/h2>\n\n\n\n
Additional protection directly in WordPress<\/h2>\n\n\n\n
ImunifyAV or Imunify360 \u2013 what is the actual difference?<\/h2>\n\n\n\n