Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: Cisco IDS 4250 vs Sourcefire IS3000 + RNA Sensor |
|---|---|
| Date: | Fri, 14 Oct 2005 22:17:16 -0500 |
On Thu, 2005-10-13 at 12:31 +0100, Tim Holman wrote:
Wouldn't you rather block bad traffic, rather than detect it?
Absolutely. That's why IDS interfacing with firewalls have merit.
Most companies are moving away from IDS as a protection mechanism, because: 1) It only detects, and doesn't effectively block intrusions
Many IDSes can do that, and could for years. It's just that the industry is promoting the "Intrusion Prevention Systems" much louder, and confuse people by presenting it to be holy savior of networks.
2) Problems with false positives, as by using pattern matching signatures, there is always a chance that these patterns also appear in valid traffic
Same problem applies to signature based IPSes. (Or do I detect a bias towards rate-based IPS?)
3) Management overheads. An IDS can only be a reasonably effective prevention method if there is someone on hand 24/7 to monitor logs and take immediate action on intrusions.
Sure. IDS and IPS are only tools, not the end-all-be-all solutions. Someone needs to operate these tools. MSSPs can certainly help out if companies can not muster the resource effort themselves.
4) There is absolutely no protection for rate-based attacks (SYN, TCP, UDP floods)
I'm starting to see a pattern now...
5) Without maintaining a L3/4 connection/state table, there is no way an IDS can be truly stateful.
Network and Transport layer states are so yesterday. You really need to keep state on at least the session layer. :)
I would recommend looking at IPS products instead, so something that you can postion inline and get immediate value from.
(Any particular vendor in mind?)
A true IPS will focus on defining what is GOOD traffic, and assuming all else is BAD (and dropping it). By doing this, zero-day attacks can be virtually be eliminated, as they all ultimately rely on abuse of a valid protocol in the hope of slipping past your protection mechanisms and onto your network.
And how about the the valid protocols that are abused to cause denial of service attacks?
Replacing like for like (IDS for IDS) is not going to give you much value, and even the market analysts are recommending against it. IDS isn't dead. Far off it, but use it for what it's good for - DETECTION and FORENSICS, and not as a device that can insure your network against rate-based and zero-day attacks.
Thank you. That paragraph I can agree with. And just a reminder, we came from a thread about spyware, not about rate-based DoS. For protection, I believe the good old firewall is *still* under utilized. How many networks do you know of that don't restrict outbound access for example? There are people that complain about P2P software, yet have "Internal->Internet-any-allow" type firewall policies. Why throw new products on the market when the existing products aren't used correctly yet? People need to realize that _Intrusion_Prevention_ is not a product, but a state of mind. It's something you do, not something you have/buy. This whole market is going crazy with the IPS term. The sad fact is that it clouds the expectancies and distracts from the real issues by offering solution to mitigate problems, not by offering solutions to eliminate problems. But I guess if that were the case, a whole market niche would solve itself out of existence.... </rant> -Frank
signature.asc
Description: This is a digitally signed message part
| Previous by Date: | Re: Cisco IDS 4250 vs Sourcefire IS3000 + RNA Sensor, byte_jump |
|---|---|
| Next by Date: | RE: IDS and Spywares, Frank Knobbe |
| Previous by Thread: | Re: Cisco IDS 4250 vs Sourcefire IS3000 + RNA Sensor, byte_jump |
| Next by Thread: | Re: Cisco IDS 4250 vs Sourcefire IS3000 + RNA Sensor, Jason |
| Indexes: | [Date] [Thread] [Top] [All Lists] |