Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 28 subscribers
  • Views 1132 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

how to beat brute force attacks on Linux server

GernotMeyer

Hi,

is there any concept to avoid brute force attacks?

There is no concept for XG WAF, right?

When installing fail2ban the linux server always gets the sophos address (when inside out traffic is normally NATed.

Any possibility to go around this and block brute force?

Thanks for hints.



This thread was automatically locked due to age.
Parents
  • 0

    Hi  

    When a client establishes a connection and accesses the web server, the web server does not obtain the client’s real IP address. The server obtains the address of the interface used by the web application firewall (WAF) because the connection is made through the WAF. The client’s real IP address is available in the HTTP header.

    So if you can do the rate limit settings on your Linux server based on X-Forwarded-For addresses for each request then this may help you to prevent brute force attack on server.

Reply
  • 0

    Hi  

    When a client establishes a connection and accesses the web server, the web server does not obtain the client’s real IP address. The server obtains the address of the interface used by the web application firewall (WAF) because the connection is made through the WAF. The client’s real IP address is available in the HTTP header.

    So if you can do the rate limit settings on your Linux server based on X-Forwarded-For addresses for each request then this may help you to prevent brute force attack on server.

Children
No Data