full-disclosure - Re: how to detect DDoS attack through HTTP response analysis(throuput)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1b9e7018d4f5b3324e1f5a73885c4fbb@rhynn.net>
Date: Mon, 27 Jun 2011 07:01:06 +0400
From: Kai <kai@...nn.net>
To: 김무성 <kimms@...osec.co.kr>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: how to detect DDoS attack through HTTP
 response analysis(throuput)

 Hi,

 its kinda <s>stupid</s> incorrect way of detecting ddos by reading http 
 responce.
 if server says error 408, it could be just a script which takes long to 
 complete. if there is some caching server, e.g. nginx, before actual web 
 server, e.g. apache httpd, then error 502 could be a result of any 
 apache death, not a ddos attack.
 but if you still want to monitor sites in such "unusual" way, and if 
 you have access to web-servers' serverstatus, you'd could parse them to 
 find out: amount of simultaneous requests; similar requests by IP; 
 similar requests by Requested Page; etc.

-- 
 Cheers,

 Kai

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/