ModSecurity in Cloud Website Hosting
We provide ModSecurity with all cloud website hosting solutions, so your web applications shall be resistant to destructive attacks. The firewall is turned on as standard for all domains and subdomains, but if you would like, you will be able to stop it using the respective section of your Hepsia CP. You'll be able to also activate a detection mode, so ModSecurity shall keep a log as intended, but shall not take any action. The logs which you'll find in Hepsia are extremely detailed and offer info about the nature of any attack, when it took place and from what IP address, the firewall rule which was triggered, etc. We employ a range of commercial rules that are regularly updated, but sometimes our administrators add custom rules as well so as to efficiently protect the websites hosted on our servers.
ModSecurity in Semi-dedicated Hosting
All semi-dedicated hosting solutions that we offer come with ModSecurity and given that the firewall is switched on by default, any website which you set up under a domain or a subdomain will be secured right from the start. An independent section within the Hepsia Control Panel that comes with the semi-dedicated accounts is devoted to ModSecurity and it shall permit you to start and stop the firewall for any website or enable a detection mode. With the last option, ModSecurity won't take any action, but it will still detect possible attacks and shall keep all info within a log as if it were fully active. The logs could be found within the same section of the CP and they include info about the IP where an attack originated from, what its nature was, what rule ModSecurity applies to recognize and stop it, and so forth. The security rules which we use on our web servers are a mix of commercial ones from a security business and custom ones made by our system administrators. Therefore, we provide greater security for your web apps as we can defend them from attacks even before security businesses release updates for brand new threats.
ModSecurity in VPS Web Hosting
Safety is of the utmost importance to us, so we set up ModSecurity on all virtual private servers which are provided with the Hepsia CP by default. The firewall could be managed through a dedicated section within Hepsia and is turned on automatically when you add a new domain or create a subdomain, so you will not have to do anything by hand. You shall also be able to deactivate it or turn on the so-called detection mode, so it shall keep a log of potential attacks you can later examine, but shall not block them. The logs in both passive and active modes contain information about the form of the attack and how it was prevented, what IP it came from and other useful information that could help you to tighten the security of your sites by updating them or blocking IPs, for example. On top of the commercial rules that we get for ModSecurity from a third-party security company, we also use our own rules because every now and then we detect specific attacks that are not yet present in the commercial pack. That way, we can easily improve the security of your Virtual private server right away as opposed to waiting for a certified update.
ModSecurity in Dedicated Servers Hosting
ModSecurity is offered as standard with all dedicated servers that are set up with the Hepsia CP and is set to “Active” automatically for any domain that you host or subdomain that you create on the web server. In the event that a web app doesn't operate properly, you can 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 which might take place, but will not take any action to stop it. The logs produced in passive or active mode will present you with additional details about the exact file that was attacked, the form of the attack and the IP it originated from, etcetera. This data shall allow you to choose what measures you can take to improve the security of your sites, including blocking IPs or carrying out script and plugin updates. The ModSecurity rules we employ are updated constantly with a commercial package from a third-party security provider we work with, but occasionally our administrators include their own rules too if they find a new potential threat.