Web Server Defender
The Web Server Defender protects against DoS and account hacking using brute force.
Behind a reverse proxy in the own network, for example on the same computer or with a private address, the sessions are counted for the client address that the proxy appends to the X-Forwarded-For header. The header is not evaluated if the direct peer has a public address, because such a proxy can not be told apart from a client.
Note: If a CDN such as Cloudflare runs in front of the server, all requests arrive from the addresses of the CDN. In this case, disable the Web Server Defender by setting both session limits to 0 and the number of login errors without delay to a value less than 0, and rely on the protection of the CDN provider.
The following options are available:
Maximum sessions per address
Defines the maximum number of session an attacker can create within 30 minutes, before the address is being blocked. The HTTP status code 429 will be sent, once the address was blocked.
For IPv6, all addresses of a /64 network count as one address, because a client can use any address of its /64 network.
Each session - defined by a session cookie - consumes some memory on the server side, usually only a few kilobytes per session. An attacker could easily create an out of memory situation, paralyzing the server, without having a session limit set.
The session counter is reset after a server restart or saving the value 0.
Note: The check can be disabled by setting the value to 0.
-
Default value: 1000
Maximum sessions per network
Defines the maximum number of sessions that can be created within 30 minutes from one network, before the network is being blocked. A network is a /24 range for IPv4 addresses and a /48 range for IPv6 addresses. The HTTP status code 429 will be sent, once the network was blocked.
The limit protects against attacks from botnets that send only a few requests from each of many addresses and therefore never reach the limit per address. Choose the value according to the expected visitors: a network can contain many legitimate clients, e.g., the computers of a company or the customers of a mobile network provider.
Note: The check can be disabled by setting the value to 0.
-
Default value: 1000
Number of login errors without delay
Defines the number of login errors before a delay will be used to stop brute force attacks to find out a users password. The delay in seconds can be calculated using the following formula:
delayInSeconds = max(0, (X - N)²) # X = number of failed login # N = configured number of erroneous logins before delay
Note: A value that is less than 0 disables the delay behaviour
-
Default value: 10
