WAAS is able to enforce rate limit on IPs or sessions to protect against high-rate and "low and slow" application layer DoS attacks.
DoS protection Overview
WAAS is able to limit the rate of requests to the protected endpoints within each app based on two configurable request rates:
- Burst Rate- Average rate of requests per second calculated over a 5 seconds period
- Avarage Rate- Average rate of requests per second calculated over a 120 seconds period
Users are able to specify match conditions for qualifying requests to be included in the count. Match conditions are based on HTTP methods, File Extensions and HTTP response codes.
Users are also able to specify Network lists to be excluded from the DoS protection rate accounting.
If no match conditions are specified - all requests to the protected endpoints would be included in the rate accounting.
Enabling DoS protection
- EnterDoS Protectiontab and set the DoS Protection toggle to On
- Set the effect with the action to apply once a threshold is reached.A message at the top of the page indicates the entity by which the ban will be applied (IP or Prisma Session ID).To enable ban by Prisma Session ID, Prisma Session Cookies has to be enabled in the Advanced Settings tab. for more information please refer to the Advanced Settings help page.
- Apply rate limitation thresholds (requests per second) for Burst rate (calculated over 5 seconds) and for Average rate (calculated over 120 seconds)
- To apply the rate limitation on a subset of requests click on button.Conditions can be specified as a combination (AND) of the following:
- HTTP Methods
- HTTP Response Codes- specify either a single response code, a range or a combination of them (e.g. 302, 400-410, 500-599).
- Multiple match conditions are allowed (ORrelation between them).In the above example the following request would be counted against the rate limitation thresholds:
- Specify Network lists of IP addresses to be excluded from the rate accounting.
Requests that exceed the rate limitation thresholds are subject to one of the following actions:
- Alert- The request is passed to the protected application and an audit is generated for visibility.
- Ban- Can be applied on either IP or Prisma Session. All requests originating from the same IP/Prisma Session to the protected application are denied for the configured time period (default is 5 minutes) following the last detected attack.
A message at the top of the page indicates the entity by which the ban will be applied (IP or Prisma Session ID). When the X-Forwarded-For HTTP header is included in the request headers, ban will apply based on the first IP listed in the header value (true client IP).
For more information on enabling Prisma Sessions and configuring ban definitions please refer to the Advanced Settings help page.
WAAS implements state, which is required for banning user sessions by IP address or Prisma Sessions. Because Defenders do not share state, any application that is replicated across multiple nodes must enable IP stickiness on the load balancer.