ModSecurity in Shared Web Hosting
ModSecurity is supplied with all shared web hosting servers, so if you opt to host your sites with our business, they shall be shielded from a wide range of attacks. The firewall is enabled by default for all domains and subdomains, so there will be nothing you will need to do on your end. You shall be able to stop ModSecurity for any Internet site if needed, or to activate a detection mode, so all activity shall be recorded, but the firewall will not take any real action. You will be able to view comprehensive logs via your Hepsia CP including the IP where the attack came from, what the attacker planned to do and how ModSecurity addressed the threat. As we take the safety of our clients' websites very seriously, we employ a collection of commercial rules that we take from one of the best companies that maintain this type of rules. Our admins also add custom rules to make sure that your sites shall be shielded from as many threats as possible.
ModSecurity in Semi-dedicated Hosting
All semi-dedicated hosting plans which we offer come with ModSecurity and because the firewall is enabled by default, any site which you create under a domain or a subdomain shall be protected right away. A separate section in the Hepsia Control Panel which comes with the semi-dedicated accounts is dedicated to ModSecurity and it shall enable you to start and stop the firewall for any site or switch on a detection mode. With the last mentioned, ModSecurity will not take any action, but it shall still identify possible attacks and shall keep all data within a log as if it were 100% active. The logs can be found inside the same section of the CP and they include information about the IP where an attack came from, what its nature was, what rule ModSecurity applies to recognize and stop it, etcetera. The security rules which we use on our servers are a mix of commercial ones from a security business and custom ones created by our system admins. Consequently, we offer greater security for your web programs as we can shield them from attacks even before security corporations release updates for brand new threats.
ModSecurity in VPS
Safety is essential to us, so we set up ModSecurity on all virtual private servers that are set up with the Hepsia Control Panel by default. The firewall could be managed via a dedicated section within Hepsia and is turned on automatically when you add a new domain or create a subdomain, so you won't need to do anything by hand. You will also be able to disable it or turn on the so-called detection mode, so it'll keep a log of possible attacks which you can later examine, but shall not block them. The logs in both passive and active modes contain information about the kind of the attack and how it was eliminated, what IP it came from and other useful information that might help you to tighten the security of your websites by updating them or blocking IPs, for instance. Beyond the commercial rules which we get for ModSecurity from a third-party security enterprise, we also use our own rules as every now and then we find specific attacks which aren't yet present inside the commercial package. This way, we can easily boost the protection of your Virtual private server promptly as opposed to awaiting a certified update.
ModSecurity in Dedicated Hosting
ModSecurity is offered 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 that you create on the hosting server. Just in case that a web application doesn't operate adequately, you can either turn off the firewall or set it to work in passive mode. The second means that ModSecurity shall keep a log of any potential attack that might happen, but will not take any action to stop it. The logs created in passive or active mode shall give you additional details about the exact file that was attacked, the form of the attack and the IP it came from, etcetera. This data will permit you to determine what measures you can take to boost the security of your websites, for instance blocking IPs or performing script and plugin updates. The ModSecurity rules we use are updated frequently with a commercial package from a third-party security firm we work with, but occasionally our staff add their own rules too in case they identify a new potential threat.