Re: Statistical Anomaly Analysis? (was: a bunch of things)
From: John S Flowers (jflowers@well.com)Date: 03/18/02
- Previous message: John S Flowers: "Re: Snot/state [WAS: Re: Signature and Traffic generation]"
- In reply to: Josh Gray: "Re: Statistical Anomaly Analysis? "Was [more specific] Signaturevs. Protocol Analysis ""
- Next in thread: Andrew Plato: "Re: Statistical Anomaly Analysis? (was: a bunch of things)"
- Next in thread: Xiaoyong Wu: "Re: Statistical Anomaly Analysis? "Was [more specific] Signaturevs. Protocol Analysis ""
- Reply: Andrew Plato: "Re: Statistical Anomaly Analysis? (was: a bunch of things)"
- Reply: John S Flowers: "Re: Statistical Anomaly Analysis? (was: a bunch of things)"
- Reply: Josh Gray: "Re: Statistical Anomaly Analysis? (was: a bunch of things)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sun, 17 Mar 2002 20:37:51 -0800 To: Josh Gray <grayjr@cerias.purdue.edu> From: John S Flowers <jflowers@well.com>
You said, " Basically my point is that your IDS is what you make of it.
If you're tired of seeing the same alerts every day then disable them."
The stated purpose of an Intrusion Detection System is to detect an
intrusion on your network environment. If any IDS cannot do this - the
task it was specifically designed to perform - I would say it is both
incorrectly named and also totally useless.
The notion of disabling attacks just because they annoy someone is
completely ridiculous. It's like poking your head in the sand and saying
"no one can see me, since I can't see them!" If someone actually cares
about the network they're protecting, this kind of approach to security
should be unconscionable.
Unfortunately, I see this attitude manifest itself every day when a
network administrator gets a page, looks at the pager, then cradles it in
the holster again and looks up, saying, "Just our IDS going off again..."
And then said, "If you know your network really well then you can tune
your IDS to look for things that shouldn't be happening."
This, on the other hand, I completely agree with. You should be familiar
enough with your network to tune your IDS to alert on anything that
violates your network policy. This might be a port scan or or access to a
sensitive server or someone using hotmail or an actual attack. In any case,
detecting _everything_ that could be considered an intrusion is exactly
the point of an intrusion detection system.
This does not, however, mean "log all traffic on my network." If logging
all traffic is important to someone's environment, there are far better
tools for this than IDS technology, which has trouble even keeping up with
the wire.
// apologies for the soapbox comments in advance.
// i'm listening to Nine Inch Nails live album,
// which always makes me a little edgy. ;)
On Saturday, March 16, 2002, at 05:29 PM, Josh Gray wrote:
> comments inline...
>
> Xiaoyong Wu wrote:
>
> > I would consider a system with the false alarm rate tunable. I can
> > understand that everyone likes zero false alarm rate but different
> people
> > may have different endurance for receiving those false alarms. I am more
> > than agree that an Intrusion Detection System is no more than a burglar
> > system. But, Let's take a look at the commercial products for burglar
> > systems. We will notice that the false alarm rate for those systems is
> way
> > below current that for IDS'es. Yeah, there's still a long way for IDS!
>
> What do you consider a false alarm? I don't see a lot of false alarms
> personally. I see a lot of unsuccessful attacks that get alerted on,
> such as
> code red attempts to apache servers. The code red alerts fire because
> there was
> an attempt to infect a machine with code red, or to check if it has
> already been
> infected. This alert fires all the time. If you are overwhelmed by it
> then
> simply disable the signature. The reason people get overwhelmed with
> alerts is
> because they don't take the time to go through and eliminate the
> signatures that
> they don't want or need. If you don't have any web servers then disable
> all of
> the web related signatures. Most IDSs come with a large signature set by
> default because they have no idea what their deployment environment is
> like.
> It's up to the operators of the system to tune it. IDS vendors could
> simply not
> include a default signature set and that would eliminate the alerts you
> have to
> deal with. If they did that though everyone would start complaining that
> their
> IDS didn't detect anything.
>
> Basically my point is that your IDS is what you make of it. If you're
> tired of
> seeing the same alerts every day then disable them. If you want to catch
> new
> attacks play around with the signature set to detect more generic things.
> If
> you know your network really well then you can tune your IDS to look for
> things
> that shouldn't be happening.
>
> >
> > I am not sure how those home security systems are build but I would
> > believe they are taking more events into consideration. At one time I
> know
> > that cats trigger them pretty often:).
> >
>
> Actually, they are looking for less events. They are looking for a small
> set of
> very specific events, such as someone breaking your window or kicking
> your door
> down. If a home alarm system alerted every time someone knocked on your
> door or
> called and hung up you would probably be overwhelmed (or at least annoyed)
> with
> alarms by this system too. I know some police/fire departments will stop
> responding to these alarms if they go off to often.
>
>
> Josh
>
- Previous message: John S Flowers: "Re: Snot/state [WAS: Re: Signature and Traffic generation]"
- In reply to: Josh Gray: "Re: Statistical Anomaly Analysis? "Was [more specific] Signaturevs. Protocol Analysis ""
- Next in thread: Andrew Plato: "Re: Statistical Anomaly Analysis? (was: a bunch of things)"
- Next in thread: Xiaoyong Wu: "Re: Statistical Anomaly Analysis? "Was [more specific] Signaturevs. Protocol Analysis ""
- Reply: Andrew Plato: "Re: Statistical Anomaly Analysis? (was: a bunch of things)"
- Reply: John S Flowers: "Re: Statistical Anomaly Analysis? (was: a bunch of things)"
- Reply: Josh Gray: "Re: Statistical Anomaly Analysis? (was: a bunch of things)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|