Do you mean the type of unknown traffic that cannot be identified is
consuming your bandwith. Most in-line IDS products do not consume
bandwidth, in other words, whne you place an inline IDS within a
particular network, you may introduce some latency when an IP packet
is being analyzed and then if the packet is forwarded or dropped. If
there is a complaint from your network team, you may want to invest
some time in troubleshooting the type of traffic that is being
observed on the various nodes of your network before pointing fingers
at each other. NFR used to have a nice flowchart diagram that
illustrated Network Intrusion Detection process..
/m
At 11:46 PM 7/4/2005, bhaskar.gupta@tcs.com wrote:
Dear frendz
I am working as an IDS operator in my company. Due to big size of
the organisation, different IDS nodes are monitoring different
centers through a central master node. Since there are lot of
incidents ( including false positives ) generated across the
organsation, there is a complaint from our networking team that IDS
is consuming lot of bandwidth over networking
I am really not able to figure out how much IDS can eat up network bandwidth.
Please throw some light on this.
cheers, Bhaskar
--------------------------------------------------------------------------
Test Your IDS
Is your IDS deployed correctly?
Find out quickly and easily by testing it with real-world attacks from
CORE IMPACT.
Go to http://www.securityfocus.com/sponsor/CoreSecurity_focus-ids_040708
to learn more.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Test Your IDS
Is your IDS deployed correctly?
Find out quickly and easily by testing it with real-world attacks from
CORE IMPACT.
Go to http://www.securityfocus.com/sponsor/CoreSecurity_focus-ids_040708
to learn more.
--------------------------------------------------------------------------
