Let's enable the Full transparent proxy mode in the WAF module.
From version 2.29.5 if the BitNinja agent was installed via the one-liner installation command, then the Transparent proxy mode is enabled in the WAF module by default. In this case, you just need to enable the WAF module. Please...
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 up the X-Forwarded-For header in your web server.
Instructions
We need to set this up in the WAF 2.0 mod...
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 this only if it has the SSL certificates of the domains at its disposal. BitNinja has such a cert miner by default ...
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 be exploited to push an arbitrary IP address to the backend webserver behind our WAF module, thus bypassing the afor...
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 rule that has been false positively triggered or allow the IP address of the customer.
Find which rule was tr...
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 WAF module is enabled and working on the domains, you wish to protect with this feature.
You can set a limit for the...
