[This blogpost has been published as a guest diary on isc.sans.org]
HandlingÂ log files is not a new topic. For a long time, people should know that taking care of your logs is a must have. They are very valuable when you need to investigate an incident. But, if collecting events and storing them for later processing is one point, events must be properly generated to be able to investigate suspicious activities! Let’s take by example a firewall… Logging all the accepted traffic is one step but what’s really important is to log all the rejected traffic. Most of the modern security devices (IDS, firewalls, web application firewalls, …) can integrate dynamic blacklists maintained by external organizations. They are plenty of usefull blacklists on the internet with IP addresses, domain names, etc… It’s quite easy to add a rule on top of your security policy which says:
if (source_ip in blacklist): Â Â drop_traffic()
WithÂ the “blacklist” table beingÂ populated byÂ an external process. Usually, this rule is defined at the beginning of the security policy for performance reason. Very efficient, but is it the right place?
Let’s assume a web application firewall which has this kind of feature. It willÂ drop all connections from a (reported as) suspicious IP address from the beginning without more details. Let’s put the blacklist rule at the end of the policy of our WAF. We have now something like this:
if (detected_attack(pattern1)): Â Â drop_traffic() elif (detected_attack(pattern2)): Â Â drop_traffic() elif (detected_attack(pattern3)): Â drop_traffic() elif Â (source_ip in blacklist): Â drop_traffic()
If we block the malicious IP addresses at the beginning of the policy, we’ll never know which kind of attack has been tried. By blocking our malicious IP addresses at the end, we know that if one IP is blocked, our policy was not effective enough to block the attack! Maybe a new type of attack was tried and we need to add a new pattern. Blocking attackers is good but it’s more valuable to know why they were blocked…