Hi @cruiseshipholiday , thanks for your message.
Are you already using a bouncer (nginx or others) so that we can compare the WordPress plugin to it ?
Or is your question more about the general benefits of using a bouncer?
Thanks again
Yes, there is a bouncer on the server.
As CrowdSec is already on the server, I’m unclear how a WP plug-in provides additional security. This, of course, is assuming the CrowdSec WordPress List on the active blocklists.
The WordPress bouncer is a good bouncer in its own right, as it has AppSec and Remediation Metrics capabilities, and it can (as all bouncers) also be used standalone to block IPs from subscribed lists. It’s a good bouncer to have if you can’t install a bouncer linked to your NGINX, OpenResty or Traefik bouncer (soon HAProxy will also have AppSec capabilities). We do recommend those latter bouncers as they will run more efficiently. The WordPress bouncer has the advantage of being in the hands of the user via the setting, which in some cases could be an advantage (for hosters, MSP…).
Also note that if you have an exposed SSH on the server it’s important to also have the firewall bouncer (for you iptables/nftables)
The WP, NGINX,.. bouncers cover HTTP traffic only and are good to have for their AppSec capability in tandem with the firewall bouncer in that case.
Some links:
Thanks
