ModSecurity in Shared Hosting
ModSecurity comes standard with all shared hosting packages that we supply and it will be activated automatically for any domain or subdomain that you add/create within your Hepsia hosting CP. The firewall has three different modes, so you'll be able to switch on and disable it with a click or set it to detection mode, so it'll keep a log of all attacks, but it'll not do anything to stop them. The log for each of your Internet sites shall contain in-depth info which includes the nature of the attack, where it came from, what action was taken by ModSecurity, and so forth. The firewall rules which we use are constantly updated and consist of both commercial ones we get from a third-party security business and custom ones our system admins add in the event that they detect a new type of attacks. This way, the websites that you host here shall be far more secure without any action required on your end.
ModSecurity in Semi-dedicated Hosting
Any web application which you set up in your new semi-dedicated hosting account will be protected by ModSecurity since the firewall is included with all our hosting solutions and is switched on by default for any domain and subdomain you include or create through your Hepsia hosting CP. You will be able to manage ModSecurity via a dedicated area in Hepsia where not only could you activate or deactivate it fully, but you can also activate a passive mode, so the firewall won't stop anything, but it'll still maintain a record of possible attacks. This normally requires simply a click and you'll be able to look at the logs regardless of if ModSecurity is in passive or active mode through the same section - what the attack was and where it came from, how it was addressed, etcetera. The firewall uses two sets of rules on our machines - a commercial one that we get from a third-party web security provider and a custom one that our admins update manually as to respond to newly discovered risks at the earliest opportunity.
ModSecurity in VPS Hosting
Protection is of the utmost importance to us, so we install ModSecurity on all virtual private servers which are provided with the Hepsia Control Panel as a standard. The firewall could be managed through a dedicated section within Hepsia and is turned on automatically when you include a new domain or create a subdomain, so you'll not need to do anything by hand. You will also be able to disable it or activate the so-called detection mode, so it shall keep a log of potential attacks which you can later examine, but shall not prevent them. The logs in both passive and active modes include information regarding the kind of the attack and how it was prevented, what IP address it originated from and other useful info that could help you to tighten the security of your sites by updating them or blocking IPs, for instance. In addition to the commercial rules we get for ModSecurity from a third-party security enterprise, we also implement our own rules as from time to time we find specific attacks which are not yet present in the commercial package. That way, we can easily enhance the security of your Virtual private server right away instead of awaiting an official update.
ModSecurity in Dedicated Web Hosting
ModSecurity is provided by default with all dedicated servers which are set up with the Hepsia Control Panel and is set to “Active” automatically for any domain you host or subdomain which you create on the hosting server. In the event that a web application does not operate properly, you could either switch off the firewall or set it to work in passive mode. The second means that ModSecurity will maintain a log of any possible attack that could take place, but shall not take any action to prevent it. The logs created in active or passive mode will offer you additional details about the exact file which was attacked, the form of the attack and the IP address it originated from, etc. This info will allow you to determine what steps you can take to enhance the security of your sites, such as blocking IPs or carrying out script and plugin updates. The ModSecurity rules we use are updated constantly with a commercial package from a third-party security enterprise we work with, but oftentimes our admins add their own rules too when they identify a new potential threat.