Quote from igsi:
dottom,
your post did not contain solution section, so, here it is:
Solution:
-Download and install IIS patches
As you can see, BID has not been used to solve this problem.
What happens between the time an exploit is discovered and when Microsoft announces patch,
and the user installs it.
The point is that BID, as an IDS, will
prevent malicious activity that a firewall will let through. For example, you run a web server, your firewall allows
all traffic on HTTP and SSL port. If there is an exploit with your web server or SSL then you have absolutely no defense until patch is available and installed. BID can detect maligned, unicode, ISAPI buffer overflow, etc. exploits even if that specific exploit is not in its database.
BID, like any other IDS, is not designed to be the solution. Obviously the solution is to patch the vulnerable service. What an IDS does is buys you
time and protects you against the known and the most common exploits.
I really don't know why there's so much damn discussion... IDS and firewall are
two different things.
Use both!.
P.S. And go to Google and search on one of the mentioned Usenet groups to get reams upon reams of discussion. Keep the discussion here to trading!