Explore our new Cybersecurity Terms Glossary, explained by our experts.

Low and slow DDoS attacks aim to bring down a web service by overwhelming it with extremely slow HTTP or TCP traffic. In this type of attack, the goal is to exhaust the resources of an application or server. The attack, which is delivered in small and very slow increments, actually requires very few connections. This makes it harder to distinguish from normal traffic. Even though large-scale DDoS attacks may be detected quickly, if a low-and-slow attack goes unnoticed for a long period of time, the victim server can be taken offline.
In this type of attack, applications called Slowloris or Rudy are generally used. In this attack technique, each thread is tied to slow requests and the aim is to prevent timeout. Imagine you are stuck in a single cash lane on an eight-lane motorway exit. The slower things go at the cash booth, the more drivers get stuck at the toll gate, and traffic keeps piling up. It is an incredibly effective and challenging attack.
The attacker generally sends HTTP headers; the server keeps this request open, and to prevent it from timing out, the headers are sent in partial sections. When detecting traditional DDoS attacks, speed and similar countermeasures are applied, but this attack technique will not be detected.
The best way to detect this type of attack is through behavioural analysis. Server resource usage should be continuously monitored and logged, and alerts should be generated for slow connections. Normal traffic and user behaviour during regular times can be compared with attack-time behaviour to perform behavioural analysis.
If your servers are running extremely slowly or crashing, you may be affected by a low and slow DDoS attack. Monitoring the response times of form fields or other activities on your web page can also help with detection.
To stop this type of attack, a reverse proxy can generally be used. At the same time, the more simultaneous connections your server can handle, the more resilient it will be against these attacks. Detection is of course crucial — otherwise the attacker will try to push server capacity to its limits.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.