ModSecurity in Cloud Hosting
ModSecurity is supplied with all cloud hosting machines, so if you decide to host your websites with our business, they'll be resistant to a wide range of attacks. The firewall is turned on as standard for all domains and subdomains, so there'll be nothing you will have to do on your end. You will be able to stop ModSecurity for any Internet site if needed, or to enable a detection mode, so all activity will be recorded, but the firewall won't take any real action. You'll be able to view comprehensive logs using your Hepsia Control Panel including the IP where the attack originated from, what the attacker wanted to do and how ModSecurity handled the threat. Since we take the protection of our clients' Internet sites seriously, we employ a group of commercial rules that we get from one of the top companies that maintain this sort of rules. Our administrators also add custom rules to make certain that your sites will be protected against as many risks as possible.
ModSecurity in Semi-dedicated Hosting
Any web program which you set up inside your new semi-dedicated hosting account shall be protected by ModSecurity since the firewall comes with all our hosting solutions and is activated by default for any domain and subdomain you add or create using your Hepsia hosting CP. You shall be able to manage ModSecurity via a dedicated section in Hepsia where not simply can you activate or deactivate it entirely, but you can also activate a passive mode, so the firewall won't block anything, but it'll still keep a record of potential attacks. This takes just a mouse click and you'll be able to view 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 dealt with, etc. The firewall uses two sets of rules on our web servers - a commercial one that we get from a third-party web security provider and a custom one which our admins update personally as to respond to newly discovered risks as fast as possible.
ModSecurity in VPS
Protection is of the utmost importance to us, so we set up ModSecurity on all virtual private servers which are made available with the Hepsia Control Panel by default. The firewall can be managed via a dedicated section within Hepsia and is switched on automatically when you add a new domain or generate a subdomain, so you will not need to do anything personally. You will also be able to deactivate it or activate the so-called detection mode, so it'll keep a log of possible attacks which you can later study, but won't stop them. The logs in both passive and active modes contain details about the form of the attack and how it was stopped, what IP address it originated from and other important data which might help you to tighten the security of your sites by updating them or blocking IPs, for instance. Beyond the commercial rules which we get for ModSecurity from a third-party security company, we also use our own rules as every now and then we identify specific attacks which are not yet present inside the commercial group. This way, we could increase the security of your VPS immediately rather than awaiting an official update.
ModSecurity in Dedicated 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 which you host or subdomain that you create on the server. In the event that a web application does not operate correctly, you can either disable the firewall or set it to operate in passive mode. The latter means that ModSecurity will keep a log of any possible attack which could occur, but shall not take any action to prevent it. The logs generated in passive or active mode will provide you with more details about the exact file which was attacked, the nature of the attack and the IP address it originated from, and so forth. This information will allow you to choose what measures you can take to enhance the security of your Internet sites, including blocking IPs or performing script and plugin updates. The ModSecurity rules which we use are updated often with a commercial package from a third-party security provider we work with, but from time to time our staff include their own rules also when they find a new potential threat.