A web application firewall (or WAF) filters, monitors and blocks HTTP traffic to and from a web application. The difference between a WAF and a regular firewall lies in a WAF's ability to filter the content of specific web applications while regular firewalls serve as a safety gate between servers. By inspecting HTTP traffic, it can prevent attacks stemming from web application security flaws, such as SQL-injections, cross-site scripting (XSS), file inclusion and security misconfigurations.
ModSecurity, sometimes called Modsec, is an open-source web application firewall (WAF). Originally designed as a module for the Apache HTTP Server, it has evolved to provide an array of Hypertext Transfer Protocol request and response filtering capabilities along with other security features across a number of different platforms including Apache HTTP Server, Microsoft IIS and NGINX. It is a free software released under the Apache license 2.0.
The platform provides a rule configuration language known as SecRules for real-time monitoring, logging and filtering of HTTP communications based on user-defined rules.
ModSecurity is most commonly deployed to provide protections against generic classes of vulnerabilities using the OWASP ModSecurity Core Rule Set (CRS). This is an open-source set of rules written in ModSecurity's SecRules language. The project is part of OWASP, the Open Web Application Security Project. Several other rule sets are also available.
To detect threats, the ModSecurity engine is deployed embedded within the web server or as a proxy server in front of a web application. This allows the engine to scan incoming and outgoing HTTP communications to the endpoint. Dependent on the rule configuration the engine will decide how communications should be handled which includes the capability to pass, drop, redirect, return a given status code, execute a user script and more.
Roxy-WI allows installing, configuring and managing WAF for HAProxy. You're able to integrate WAF with your HAProxy service in a click.
You can start/stop/restart WAF service and select WAF mode Tick the Metrics checkbox to collect WAF connections metrics.
Roxy-WI pre-installs OWASP-CRS rules with default settings. If you want to change any parameters you should edit them. All parameters are stored in the following directory: /etc/haproxy/waf/rules/
Roxy-WI pre-installs the following rules by default:
Tick the Enabled checkbox tp disable or enable rules. Do not forget to restart the WAF afterward.
You can view the details of each rule by pressing the View button. Rules look the way it's shown below:
Roxy-WI allows installing, configuring and managing WAF for NGINX as well. You're able to integrate WAF with your NGINX service in a click.
You can start/stop/restart WAF service.
Roxy-WI pre-installs OWASP-CRS rules with default settings. If you want to change any parameters you should edit them. All parameters are stored in the following directory: /etc/nginx/waf/rules/
Roxy-WI adds configuration data into the nginx.conf file and enables ModSecurity globally, but keeps it in "off" state by default. If you would like to enable it, just press the start button on the WAF page.
If you want to enable it only for a few domains, you have to add the following settings to a config file (e.g. conf.d/example.com.conf):
Roxy-WI pre-installs the following rules by default:
Tick the Enabled checkbox tp disable or enable rules. Do not forget to restart the WAF afterward.
You can view the details of each rule by pressing the View button. Rules look the way it's shown below: