Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ENHANCEMENTS] Fail2ban features #22

Open
burjuyz opened this issue Jun 15, 2023 · 8 comments
Open

[ENHANCEMENTS] Fail2ban features #22

burjuyz opened this issue Jun 15, 2023 · 8 comments
Labels
enhancement New feature or request

Comments

@burjuyz
Copy link

burjuyz commented Jun 15, 2023

Please consider to add fail2ban for security reasons.
As for example you could check SWAG solution

@burjuyz burjuyz added the enhancement New feature or request label Jun 15, 2023
@ahmedabokandil
Copy link

yes totally agreed we need to integrate with fail2ban

@tobychui
Copy link
Owner

tobychui commented Sep 3, 2023

Hi @ahmedabokandil, I am just wondering, why you need fail2ban in the first place?
It doesn't seems like it can stop DDOS, or improve security in web serving.
If you need further security features regarding access to the management panel (e.g. 2FA or password-less login), you should be using another business grade reverse proxy before Zoraxy for managing authentication to the management panel.

@ahmedabokandil
Copy link

Hi @tobychui , thanks for your reply , but i will tell you why this important
when we enable basic authentication to protect an backend servers , if someone tried brute force attack to get password
we can block it using fail2ban , what do you think ?

@tobychui
Copy link
Owner

tobychui commented Sep 3, 2023

@ahmedabokandil thanks for your explanation.
Fail2ban is an existing project that would alter the firewall rules of the host OS, which is way out of the scope of Zoraxy (as a reverse proxy server). Integrating another huge project into Zoraxy just doesn't make sense on its own.

But if what you mean is something like a maximum retry per preset time period (and the IP get banned if over that retry counts) in the basic auth mechanism, I think it is a valid enhancement request.

@ahmedabokandil
Copy link

@tobychui
thanks for reply , totally agree , its very great idea to get dynamic ip banned if over retry counts

But if what you mean is something like a maximum retry per preset time period (and the IP get banned if over that retry counts) in the basic auth mechanism, I think it is a valid enhancement request

@LaurenceJJones
Copy link

Hey, we @crowdsecurity also would like to add log parser / scenario support. The remediation, however, would purely up to you if you would like to implement we do have golang libraries if not user can use the firewall remediation but would not be effective if they use something like CF.

@barto95100
Copy link

YEs great feature is implemented Crowdsec ;)

@Aerics84
Copy link

Aerics84 commented May 5, 2024

Support for crowdsec would be nice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants