ModSecurity is a plugin for Apache web servers that acts as a web app layer firewall. It's employed to prevent attacks toward script-driven Internet sites by employing security rules which contain particular expressions. In this way, the firewall can stop hacking and spamming attempts and preserve even sites that are not updated often. For example, numerous failed login attempts to a script administrator area or attempts to execute a certain file with the intention to get access to the script will trigger certain rules, so ModSecurity will stop these activities the minute it identifies them. The firewall is incredibly efficient as it monitors the whole HTTP traffic to a site in real time without slowing it down, so it could prevent an attack before any harm is done. It also keeps an exceptionally comprehensive log of all attack attempts that features more info than conventional Apache logs, so you can later analyze the data and take additional measures to enhance the security of your Internet sites if required.

ModSecurity in Cloud Hosting

ModSecurity is available with every cloud hosting plan which we offer and it's activated by default for every domain or subdomain that you include via your Hepsia Control Panel. In the event that it interferes with any of your applications or you'd like to disable it for whatever reason, you'll be able to accomplish that through the ModSecurity section of Hepsia with only a mouse click. You may also use a passive mode, so the firewall will discover potential attacks and keep a log, but shall not take any action. You could view extensive logs in the exact same section, including the IP address where the attack came from, what exactly the attacker tried to do and at what time, what ModSecurity did, etc. For optimum security of our customers we use a set of commercial firewall rules combined with custom ones which are added by our system administrators.

ModSecurity in Semi-dedicated Servers

ModSecurity is a part of our semi-dedicated server plans and if you opt to host your sites with us, there won't be anything special you'll need to do since the firewall is activated by default for all domains and subdomains which you add via your hosting CP. If necessary, you can disable ModSecurity for a given site or activate the so-called detection mode in which case the firewall will still work and record info, but shall not do anything to stop possible attacks on your sites. Comprehensive logs will be readily available within your Control Panel and you shall be able to see which kind of attacks took place, what security rules were triggered and how the firewall addressed the threats, what IP addresses the attacks came from, and so forth. We employ 2 sorts of rules on our servers - commercial ones from a business that operates in the field of web security, and customized ones which our admins often include to respond to newly identified threats in a timely manner.

ModSecurity in VPS Servers

ModSecurity is pre-installed on all VPS servers which are offered with the Hepsia hosting CP, so your web applications will be protected from the instant your server is ready. The firewall is turned on by default for any domain or subdomain on the Virtual Private Server, but if needed, you can deactivate it with a click through the corresponding section of Hepsia. You can also set it to function in detection mode, so it will maintain an extensive log of any potential attacks without taking any action to prevent them. The logs can be found in the very same section and include information about the nature of the attack, what IP address it originated from and what ModSecurity rule was triggered to stop it. For optimum security, we employ not only commercial rules from a company working in the field of web security, but also custom ones that our admins include manually so as to react to new risks which are still not addressed in the commercial rules.

ModSecurity in Dedicated Servers

ModSecurity is offered by default with all dedicated servers that are set up with the Hepsia CP and is set to “Active” automatically for any domain you host or subdomain that you create on the server. Just in case that a web app doesn't work correctly, you could either switch off the firewall or set it to work in passive mode. The second means that ModSecurity shall maintain a log of any potential attack which may take place, but won't take any action to stop it. The logs produced in active or passive mode shall present you with additional details about the exact file that was attacked, the nature of the attack and the IP address it came from, and so on. This info shall allow you to choose what measures you can take to enhance the protection of your Internet sites, for instance blocking IPs or performing script and plugin updates. The ModSecurity rules that we employ are updated regularly with a commercial bundle from a third-party security company we work with, but sometimes our staff add their own rules too when they find a new potential threat.