ModSecurity in Cloud Website Hosting
We provide ModSecurity with all cloud website hosting plans, so your Internet applications will be protected against harmful attacks. The firewall is activated by default for all domains and subdomains, but if you would like, you'll be able to stop it using the respective section of your Hepsia CP. You could also switch on a detection mode, so ModSecurity will keep a log as intended, but will not take any action. The logs that you shall discover within Hepsia are extremely detailed and offer data about the nature of any attack, when it occurred and from what IP address, the firewall rule that was triggered, and so on. We use a set of commercial rules which are constantly updated, but sometimes our administrators include custom rules as well in order to better protect the Internet sites hosted on our machines.
ModSecurity in Semi-dedicated Hosting
All semi-dedicated hosting plans that we offer come with ModSecurity and given that the firewall is enabled by default, any website which you create under a domain or a subdomain shall be secured immediately. An individual section in the Hepsia Control Panel that comes with the semi-dedicated accounts is devoted to ModSecurity and it'll enable you to start and stop the firewall for any website or activate a detection mode. With the last option, ModSecurity will not take any action, but it shall still detect possible attacks and shall keep all data in a log as if it were completely active. The logs could be found inside the same section of the Control Panel and they include info about the IP where an attack came from, what its nature was, what rule ModSecurity applies to identify and stop it, and so forth. The security rules we employ on our servers are a mix between commercial ones from a security company and custom ones developed by our system administrators. For that reason, we provide increased security for your web applications as we can defend them from attacks even before security businesses release updates for completely new threats.
ModSecurity in VPS Hosting
Protection is vital to us, so we set up ModSecurity on all virtual private servers which are set up with the Hepsia CP as a standard. The firewall could be managed through a dedicated section within Hepsia and is activated automatically when you include a new domain or generate a subdomain, so you will not have to do anything manually. You shall also be able to disable it or switch on the so-called detection mode, so it will keep a log of possible attacks that you can later examine, but won't prevent them. The logs in both passive and active modes contain details about the type of the attack and how it was prevented, what IP address it originated from and other valuable information which could help you to tighten the security of your websites by updating them or blocking IPs, as an example. On top of the commercial rules which we get for ModSecurity from a third-party security enterprise, we also employ our own rules because every now and then we find specific attacks that are not yet present inside the commercial group. That way, we can improve the protection of your VPS instantly instead of awaiting an official update.
ModSecurity in Dedicated Web Hosting
ModSecurity is available as standard with all dedicated servers that are set up with the Hepsia Control Panel and is set to “Active” automatically for any domain which you host or subdomain which you create on the server. Just in case that a web app doesn't operate correctly, you may either disable the firewall or set it to function in passive mode. The latter means that ModSecurity will keep a log of any possible attack which may happen, but will not take any action to prevent it. The logs generated in active or passive mode shall present you with more 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 permit you to decide what actions you can take to increase the security of your websites, including blocking IPs or performing script and plugin updates. The ModSecurity rules which we employ are updated often with a commercial bundle from a third-party security firm we work with, but oftentimes our administrators include their own rules too in case they come across a new potential threat.