2 ms·
Thanks for the response. I didn't know F5 had such an offering, I will certainly check it out. ">For simple flood attacks, connection rate-limiting per source
by bogomipz 10y ago
Thanks for the response. I didn't know F5 had such an offering, I will certainly check it out.
">For simple flood attacks, connection rate-limiting per source IP is very effective."
But if a each of the 8 million bots in a hypothetical botnet sends exactly one syn packet then you can't really rate limit per source IP. Or the case of DNS a single UDP datagram which might be indistinguishable from a "legitimate" DNS query datagram.
Also rate limiting is different that what I would think of as "scrubbing" unless I am thinking about scrubbing wrong. Back to my example of the botnet where the command and control tells each node to send a single packet or a small handful of packets towards a destination, theres very limit match a rate limit filter on in that case no?
- gbuk2013 10y agoI think "rate limiting" is used as an indicator of malicious intent rather than in the QoS sense. If we classify traffic as malicious we drop it. The single SYN will fail the 3WHS test, so we would drop it. For DNS we can usually fingerprint the attacker and block traffic. Because we are a full proxy we can do packet inspection as well. ;) There's a fair amount of intelligence already built into our products which we of course make use of (BIG-IP LTM/AFM/ASM, "IP Intelligence"). Eventually it may well come down to the SOC monitoring and adjusting the filters in real time as required - that's life.