Intrusion Prevention vs. Intrusion Detection

topic posted Mon, November 7, 2005 - 2:06 PM by  Jimbo
I wanted to know your feelings on prevention vs detection. It seems like both have there strengths and weaknesses what offers the best trade off?
posted by:
Jimbo
Seattle
  • Re: Intrusion Prevention vs. Intrusion Detection

    Tue, November 8, 2005 - 2:58 AM
    It's gartner bulshit. :)

    There is no PREVENTION. Call it Intrusion REACTION to be more precise...

    This is actually dangerous... because it can lead to denial of service attacks. Do something that triggers the intrusion reaction system and it decides to shut down the network... :)

    Gilles.
    • Re: Intrusion Prevention vs. Intrusion Detection

      Tue, November 22, 2005 - 10:17 PM
      I think it depends - I hope nobody's using intrusion reaction, if you will, as a replacement for keeping systems patched and other good security patches, but there isn't a technical fix in the world right now that can keep every single [laptop] user from bringing malware into your network.

      So call it EXtrusion reaction. Ideally it'd clamp down on the switch port of any system that's spewing nasties onto the network.
  • Re: Intrusion Prevention vs. Intrusion Detection

    Sun, November 20, 2005 - 1:03 PM
    I run a small network (about 50 nodes) with an open-source based IDS/IPS just inside of the NAT/Firewall. Mainly I use it for detecting malware that people have brought into the network on their laptops. I hate laptops. The only prevention it does is to cut off connections on overtly and obvious dangerous stuff like in backdoors.rules.
    • Re: Intrusion Prevention vs. Intrusion Detection

      Mon, November 21, 2005 - 12:39 AM
      Hi Alex which one you use snort?
      • Re: Intrusion Prevention vs. Intrusion Detection

        Tue, November 22, 2005 - 10:12 PM
        Yeah, just vanilla snort on an openbsd box.
        • Re: Intrusion Prevention vs. Intrusion Detection

          Wed, November 23, 2005 - 11:52 PM
          any of you have experience with ACL's on a cisco router?
          I need to disable all netbios traffic but to/from one host.(The only one allow)
          Thanks.
          • X
            X
            offline 21

            Re: Intrusion Prevention vs. Intrusion Detection

            Sat, November 26, 2005 - 12:11 PM
            Warning: the last time I worked with router ACLs was back when they were made of bronze and used a waterwheel for power. That said...

            Wouldn't the normal way to do that be to allow all netbios traffic to the one server, allow all netbios traffic from the one server, and then to deny all netbios traffic? I'm incredibly rusty and just taking a guess here, but most routers will go down their rules list and obey the first thing that matches, and if nothing matches it falls through to the default (DENY ALL in this case).
            • Re: Intrusion Prevention vs. Intrusion Detection

              Sun, November 27, 2005 - 10:46 AM
              yes I remember that, just looking for input on the topic see if someone comes with simpler way.. Thanks.
              • Re: Intrusion Prevention vs. Intrusion Detection

                Wed, February 1, 2006 - 8:30 PM
                Yes, I'm familiar with Cisco ACL's (it's a large part of what I do at work, in fact). The previous reply was correct - ACL's are processed top down and stop at the first match, so you have to put more specific rules before more general rules. Also, there's an implicit "deny any any" at the end of all ACL's, so you don't need to put your own deny at the end if you don't want to (though some people like to for a variety of reasons).

                Back to the main topic of the thread, I always thought the name "Intrusion Prevention" was a little odd anyway, since that's what I always though firewalls were supposed to do. I'm generally not the biggest fan of IPS/IDS boxes, but see more value in well placed and monitored IDS than I do in IPS. Just my $.02.

                HTH

Recent topics in "Network Security"