Not necessarily. I’d prefer to leave that decision to the system administrator.
There are environments where CrowdSec provides clear value and should definitely be installed, but there are also scenarios where administrators may consider it unnecessary, redundant with existing protections, or simply not worth the additional complexity.
Ummm … I hate to ask this question, because it seems dumb, but if a node with crowdsec has a reverse proxy setup in http routes, is crowdsec inspecting and as necessary blocking the traffic before it’s sent to the proxy target on another node or cluster?
I would say no because what is looking for crowdsec is bad authentication and this answer will be done by the final destination host, so the reverse proxy is just adressing the route to the host and no more.
CrowdSec primarily analyzes logs available in the local node journal and makes decisions based on those logs. Traefik on the front-end node may still record requests and backend responses, including 401 errors, whether the application is hosted locally or on a remote server. However, CrowdSec’s ability to act on those events depends on the parsers and detection scenarios that are enabled.
Results can vary between applications because some generate logs and response patterns that match CrowdSec’s detection rules, while others do not. Testing different setups and sharing feedback can help determine how effectively CrowdSec supports these configurations in practice.