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.

Sign up for GitHub

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

Jump to bottom

Investigate whether or how to use fail2ban #451

Open

birkland opened this issue Nov 19, 2021 · 1 comment

Labels

LAG Security recommendations vendor

birkland commented Nov 19, 2021 •

edited by htpvu

Loading

From security audit:

As mentioned above, utilize Fail2ban to monitor activity. This can be an invaluable resource and is difficult to express all the benefits of limiting resources to potentially malicious actors.

Full security audit recommendation is here https://docs.google.com/document/d/1gNMnJqZsq7WDDPLMtfW44bzxWEPHTBf8k-kh76zpH7c/edit#bookmark=id.b93db0rilcgk

htpvu added the Security recommendations label

htpvu added the vendor label

htpvu commented Mar 3, 2022

@bbranan I think There's a call to make here on whether this needs to be implemented prior to the hand-off to LAG

htpvu added the LAG label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment