ModSecurity is an effective firewall for Apache web servers that is employed to stop attacks toward web applications. It monitors the HTTP traffic to a particular website in real time and blocks any intrusion attempts the instant it discovers them. The firewall relies on a set of rules to do this - as an illustration, attempting to log in to a script administrator area without success a few times triggers one rule, sending a request to execute a particular file that could result in gaining access to the site triggers another rule, and so forth. ModSecurity is among the best firewalls available on the market and it'll protect even scripts that aren't updated regularly as it can prevent attackers from using known exploits and security holes. Quite comprehensive data about each intrusion attempt is recorded and the logs the firewall keeps are much more comprehensive than the conventional logs generated by the Apache server, so you could later examine them and determine whether you need to take extra measures so as to increase the safety of your script-driven websites.
ModSecurity in Cloud Hosting
We provide ModSecurity with all cloud hosting
packages, so your web apps shall be shielded from harmful attacks. The firewall is switched on by default for all domains and subdomains, but if you would like, you will be able to stop it via the respective area of your Hepsia CP. You could also switch on a detection mode, so ModSecurity will keep a log as intended, but won't take any action. The logs that you will discover in Hepsia are very detailed and include data about the nature of any attack, when it happened and from what IP, the firewall rule that was triggered, and so forth. We use a range of commercial rules which are regularly updated, but sometimes our admins add custom rules as well in order to efficiently protect the sites hosted on our machines.
ModSecurity in Semi-dedicated Hosting
Any web app you set up in your new semi-dedicated hosting
account will be protected by ModSecurity as the firewall comes with all our hosting solutions and is turned on by default for any domain and subdomain which you add or create through your Hepsia hosting CP. You will be able to manage ModSecurity via a dedicated section within Hepsia where not only can you activate or deactivate it entirely, but you can also activate a passive mode, so the firewall shall not stop anything, but it'll still maintain an archive of potential attacks. This requires simply a click and you shall be able to look at the logs regardless 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 forth. The firewall employs 2 sets of rules on our machines - a commercial one that we get from a third-party web security company and a custom one which our administrators update personally in order to respond to recently discovered risks as soon as possible.
ModSecurity in VPS Web Hosting
All virtual private servers
that are provided with the Hepsia CP include ModSecurity. The firewall is installed and switched on by default for all domains that are hosted on the web server, so there won't be anything special which you'll need to do to protect your sites. It will take you a mouse click to stop ModSecurity if required or to activate its passive mode so that it records what occurs without taking any actions to stop intrusions. You will be able to look at the logs created in passive or active mode via the corresponding section of Hepsia and learn more about the type of the attack, where it came from, what rule the firewall used to deal with it, etcetera. We employ a combination of commercial and custom rules so as to make certain that ModSecurity shall block as many threats as possible, hence increasing the security of your web applications as much as possible.
ModSecurity in Dedicated Servers Hosting
ModSecurity is included with all dedicated servers
that are integrated with our Hepsia Control Panel and you'll not have to do anything specific on your end to employ it as it's activated by default each time you include a new domain or subdomain on your web server. If it disrupts some of your programs, you will be able to stop it via the respective section of Hepsia, or you could leave it in passive mode, so it'll identify attacks and shall still maintain a log for them, but shall not stop them. You'll be able to analyze the logs later to find out what you can do to enhance the security of your sites as you'll find info such as where an intrusion attempt came from, what website was attacked and based upon what rule ModSecurity reacted, etc. The rules we employ are commercial, thus they are constantly updated by a security provider, but to be on the safe side, our administrators also include custom rules every now and then as to respond to any new threats they have found.