Find out how having ModSecurity allowed inside your web hosting account will help silently with your web site protection.
ModSecurity is an effective firewall for Apache web servers that is used to stop attacks towards web apps. It keeps track of the HTTP traffic to a specific Internet site in real time and stops any intrusion attempts as soon as it discovers them. The firewall relies on a set of rules to accomplish that - as an example, attempting to log in to a script administrator area without success a few times triggers one rule, sending a request to execute a specific file that may result in gaining access to the site triggers a different rule, and so on. ModSecurity is one of the best firewalls out there and it'll secure even scripts that aren't updated regularly because it can prevent attackers from employing known exploits and security holes. Very comprehensive information about each intrusion attempt is recorded and the logs the firewall maintains are a lot more comprehensive than the conventional logs generated by the Apache server, so you may later analyze them and determine whether you need to take more measures in order to boost the protection of your script-driven sites.
ModSecurity in Shared Website Hosting
ModSecurity is provided with all shared website hosting
machines, so if you choose to host your websites with our company, they will be protected against an array of attacks. The firewall is enabled as standard for all domains and subdomains, so there will be nothing you shall have to do on your end. You shall be able to stop ModSecurity for any site if necessary, or to enable a detection mode, so all activity shall be recorded, but the firewall won't take any real action. You'll be able to view specific logs through your Hepsia Control Panel including the IP where the attack originated from, what the attacker wished to do and how ModSecurity handled the threat. As we take the protection of our customers' Internet sites very seriously, we use a selection of commercial rules that we get from one of the best firms that maintain this type of rules. Our administrators also include custom rules to ensure that your websites will be shielded from as many risks as possible.
ModSecurity in Semi-dedicated Hosting
We have incorporated ModSecurity by default in all semi-dedicated hosting
packages, so your web apps shall be protected the instant you set them up under any domain or subdomain. The Hepsia Control Panel that comes with the semi-dedicated accounts shall allow you to switch on or turn off the firewall for any Internet site with a mouse click. You will also be able to activate a passive detection mode through which ModSecurity shall keep a log of possible attacks without really preventing them. The detailed logs include things like the nature of the attack and what ModSecurity response that attack triggered, where it originated from, etc. The list of rules that we use is frequently updated as to match any new threats which could appear on the Internet and it comes with both commercial rules that we get from a security firm and custom-written ones that our admins include in the event that they find a threat that's not present within the commercial list yet.
ModSecurity in Dedicated Hosting
All of our dedicated servers
that are installed with the Hepsia hosting CP include ModSecurity, so any application you upload or set up will be properly secured from the very beginning and you will not need to stress about common attacks or vulnerabilities. An individual section in Hepsia will allow you to start or stop the firewall for each and every domain or subdomain, or turn on a detection mode so that it records details about intrusions, but does not take actions to prevent them. What you will see in the logs shall enable you to to secure your websites better - the IP address an attack originated from, what website was attacked as well as how, what ModSecurity rule was triggered, etc. With this information, you'll be able to see if a site needs an update, whether you need to block IPs from accessing your hosting server, etcetera. In addition to the third-party commercial security rules for ModSecurity that we use, our administrators include custom ones as well every time they discover a new threat that's not yet a part of the commercial bundle.