2012-08-28 01:02 PM
We had a customer come to us asking to see if we could detect when an attacker tried to take a mirror of their webserver or detect when someone was running a web-based vulnerability scan against their webserver in the monitored environment. We don't publish native content for this because the solution requires customization for the customer environment. But it is pretty easy to do.
Or if it is against a cluster of webservers you can use the alias host. Ive even had one customer that used
and it works just fine.
In the query field you look for 'client'
In the where field you look for alert='site-crawl attempt'
The results will show you all of the normal bots and crawlers like google and yandex and yahoo in addition to targeted vulnerability scanning attempts. You can even chart this out in an Informer graph. Ive done exactly this many times in the field.
Another good use of this Investigator and Informer rule is to look for inbound web queries that have errors published in the error index. In this case, the Informer report would look for 'error'
In the where field you look for alert='site-crawl attempt' && error begins '4'
This will show you all of the 404 errors, which typically show up in a nessus scan or similar.
If you look for errors beginning '2' you will see successful queries that found an object.
2012-08-28 01:34 PM
The same concept can be used to detect abuse of SQL servers too. In that case it would be "sql count 50-u" to detect when someone retrieves masses of data from a database.