ADC

Guidelines for HTTP DoS protection deployment

August 20, 2024

Contributed by:

C C S

Citrix recommends you to deploy the HTTP DoS protection feature in a tested and planned manner and closely monitor its performance after the initial deployment. Use the following information to fine-tune the deployment of HTTP DoS Protection.

The maximum number of concurrent connections supported by your servers.
The average and normal values of the concurrent connections supported by your servers.
The maximum output rate (responses/sec) that your server can generate.
The average traffic that your server handles.
The typical bandwidth of your network.
The maximum bandwidth available upstream.
The limits affecting bandwidth (such as external links, a particular router, or other critical devices on the path that may suffer from a traffic surge).
Whether allowing a greater number of clients to connect is more important than protecting upstream network devices.

To determine the characteristics of a HTTP DoS attack, you should consider the following issues.

What is the rate of incoming fake requests that you have experienced in the past?
What types of requests have you received (complete posts, incomplete gets)?
Did previous attacks saturate your downstream links? If not, what was the bandwidth?
What types of source IP addresses and source ports did the HTTP requests have (e.g., IP addresses from one subnet, constant IP, ports increasing by one).
What types of attacks do you expect in future? What type have you seen in the past?
Any or all information that can help you tune DoS attack protection.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Guidelines for HTTP DoS protection deployment

August 20, 2024

Contributed by:

C C S

August 20, 2024

Contributed by:

C C S

Guidelines for HTTP DoS protection deployment

In this article