ModSecurity in Cloud Hosting
ModSecurity is available on all cloud hosting web servers, so if you decide to host your sites with our company, they will be protected against a wide array of attacks. The firewall is enabled as standard for all domains and subdomains, so there shall be nothing you shall have to do on your end. You shall be able to stop ModSecurity for any website if needed, or to enable a detection mode, so that all activity shall be recorded, but the firewall won't take any real action. You shall be able to view detailed logs using your Hepsia CP including the IP where the attack came from, what the attacker wished to do and how ModSecurity dealt with the threat. As we take the safety of our clients' sites seriously, we employ a selection of commercial rules that we get from one of the leading companies that maintain such rules. Our admins also include custom rules to ensure that your websites will be shielded from as many risks as possible.
ModSecurity in Semi-dedicated Hosting
Any web program you install inside your new semi-dedicated hosting account will be protected by ModSecurity as the firewall comes with all our hosting packages and is turned on by default for any domain and subdomain you add or create using your Hepsia hosting CP. You will be able to manage ModSecurity via a dedicated area inside Hepsia where not simply can you activate or deactivate it entirely, but you can also switch on a passive mode, so the firewall shall not stop anything, but it'll still maintain a record of potential attacks. This requires simply a click and you will be able to see the logs no matter if ModSecurity is in passive or active mode through the same section - what the attack was and where it originated from, how it was addressed, etcetera. The firewall uses 2 sets of rules on our machines - a commercial one which we get from a third-party web security provider and a custom one which our administrators update personally in order to respond to newly discovered threats as fast as possible.
ModSecurity in VPS Hosting
Protection is essential to us, so we install ModSecurity on all virtual private servers which are set up with the Hepsia Control Panel as a standard. The firewall can be managed via a dedicated section in Hepsia and is activated automatically when you add a new domain or create a subdomain, so you won't have to do anything personally. You will also be able to deactivate it or activate the so-called detection mode, so it shall keep a log of potential attacks which you can later study, but won't stop them. The logs in both passive and active modes offer details regarding the kind of the attack and how it was stopped, what IP it originated from and other important data which may help you to tighten the security of your websites by updating them or blocking IPs, for instance. On top of the commercial rules which we get for ModSecurity from a third-party security firm, we also use our own rules as once in a while we detect specific attacks that are not yet present inside the commercial package. This way, we can easily increase the security of your Virtual private server in a timely manner instead of waiting for an official update.
ModSecurity in Dedicated Web Hosting
ModSecurity is offered by default 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 you create on the server. In case that a web app does not operate adequately, you could either switch off the firewall or set it to work in passive mode. The latter means that ModSecurity will keep a log of any potential attack that could take place, but shall not take any action to stop it. The logs produced in active or passive 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, etcetera. This info will enable you to determine what actions you can take to increase the protection of your Internet sites, including blocking IPs or performing script and plugin updates. The ModSecurity rules that we use are updated regularly with a commercial bundle from a third-party security provider we work with, but sometimes our admins add their own rules also in the event that they identify a new potential threat.