ModSecurity is a powerful firewall for Apache web servers which is used to prevent attacks against web applications. It tracks the HTTP traffic to a certain Internet site in real time and prevents any intrusion attempts the moment it identifies them. The firewall relies on a set of rules to do this - as an illustration, trying to log in to a script admin area without success several times activates one rule, sending a request to execute a particular file which may result in getting access to the Internet site triggers a different rule, and so on. ModSecurity is amongst the best firewalls on the market and it'll protect even scripts that are not updated on a regular basis as it can prevent attackers from employing known exploits and security holes. Very thorough information about every single intrusion attempt is recorded and the logs the firewall keeps are a lot more specific than the regular logs provided by the Apache server, so you could later analyze them and determine whether you need to take additional measures so as to boost the safety of your script-driven Internet sites.

ModSecurity in Shared Web Hosting

ModSecurity comes standard with all shared web hosting solutions which we offer and it shall be turned on automatically for any domain or subdomain that you add/create inside your Hepsia hosting Control Panel. The firewall has 3 different modes, so you can activate and deactivate it with only a click or set it to detection mode, so it shall keep a log of all attacks, but it shall not do anything to stop them. The log for any of your websites will include elaborate information including the nature of the attack, where it originated from, what action was taken by ModSecurity, and so forth. The firewall rules that we use are constantly updated and include both commercial ones that we get from a third-party security firm and custom ones which our system administrators include in case that they detect a new type of attacks. This way, the websites that you host here shall be far more protected with no action expected on your end.

ModSecurity in Semi-dedicated Servers

Any web program you install inside your new semi-dedicated server account shall be protected by ModSecurity as the firewall is provided with all our hosting packages and is activated by default for any domain and subdomain you add or create via your Hepsia hosting Control Panel. You'll be able to manage ModSecurity via a dedicated section in Hepsia where not simply can you activate or deactivate it fully, but you could also switch on a passive mode, so the firewall won't block anything, but it shall still keep an archive of possible attacks. This requires only a mouse click and you'll be able to look at the logs no matter if ModSecurity is in active or passive mode through the same section - what the attack was and where it came from, how it was dealt with, and so on. The firewall uses 2 sets of rules on our web servers - a commercial one which we get from a third-party web security provider and a custom one that our administrators update manually as to respond to newly discovered threats as quickly as possible.

ModSecurity in Dedicated Servers

ModSecurity is offered by default with all dedicated servers which are set up with the Hepsia Control Panel and is set to “Active” automatically for any domain that you host or subdomain which you create on the web server. Just in case that a web app does not function adequately, you can either turn off the firewall or set it to operate in passive mode. The second means that ModSecurity shall keep a log of any possible attack that might happen, but shall not take any action to stop it. The logs created in passive or active mode shall give you more details about the exact file that was attacked, the form of the attack and the IP address it originated from, etc. This information will allow you to decide what steps you can take to increase the safety of your Internet sites, such as blocking IPs or performing script and plugin updates. The ModSecurity rules which we use are updated frequently with a commercial bundle from a third-party security firm we work with, but occasionally our admins add their own rules also when they identify a new potential threat.