WAF Module

Overview In some cases, enabling BitNinja WAF Pro may result in websites returning the following error: 400 Bad Request The plain HTTP request was sent to HTTPS port This issue ca…

Overview Starting with BitNinja 3.16.0 , the legacy web application firewall components have been removed and replaced by the new WAF Pro solution. WAF Pro is built on the Caddy w…

With the 2.29.0 version of BitNinja , we introduced the rate limiting feature. This is based on the WAF and SSLTerminating modules. In order to use this feature make sure that the…

The Close Direct Access option is enabled by default. The setting can be modified from the Dashboard by navigating to the Configuration menu -> Advanced Modules -> IP Reputation -…

Info This is necessary only if you are using Enhance version below v12.0.0 Introduction: When configuring BitNinja on servers using the Enhance control panel, several key adjustme…

Customer IP got blocked when he/she was editing his/her site. This is most likely because of a false positively triggered BitNinja WAF rule. In short terms, we need to disable the…

Description Suppose an IP-based access control solution is implemented in your web server (back-end server). In that case, the Haproxy used by BitNinja's SslTerminating module can…

Why do we need an SSL certificate miner? The WAF module can only listen on HTTP but it needs the SSL Terminating module to be able to listen on HTTPS as well. This module can do t…

Enabling the Transparent proxy mode in the WAF 2.0 module allows you to see the real IP addresses behind the WAF module instead of the server’s own IP address(es) without setting…

If you have enabled the WAF 2.0 module after the pre-requirements are met, you can test whether WAF 2.0 module is running okay. Check whether the WAF module can be triggered on on…

Apache Open your Apache configuration file with your favourite text editor. Insert the following lines at the end of the httpd.conf or apache2.conf file. On Debian you can find th…

Some applications miss behave behind a proxy. This is why we need to force a redirection to remain https most of the time. Solution This behavior can be changed: You just need to…

Warning By default mapping the certs to the domains is not necessary , BitNinja does this automatically, however in case the automatism that should gather the certs fail or get th…

By default, WAF 2.0 will only create port redirections for public IPs. However, it can be set to observe on the private interface. It can happen, that your server does not have a…

Info If you see an error on your screen with a 5xx error, the issue might be solved differently based on your configuration or setup. First, we need to check what kind of error co…

How to set up DNAT redirection mode for the WAF 2.0 module: Info As of BitNinja version 2.29.5, the default redirection mode in the WAF module is the Transparent mode. So if you w…

Info This configuration is only required if you’re using DNAT redirection mode for the WAF module. If you are using cPanel/WHM please make sure to open/allow the 60418 port on TCP…

Info This configuration is only required if you're using DNAT redirection mode for the WAF module. In Plesk, the X-Forwarded-For header is already included with all IP addresses o…

Info Pre-Requirements In the WAF module’s case, there are pre-requirements that need to be met. Please check if the required settings are done. You can check these settings in thi…

The WAF module blocks web-based attacks before they reach the server. If a well-aimed web-based attack, like a PHP code injection, reaches the server, it will cause serious issues…