Best Practices in Network Behavior Analysis: Part 1 of 2

Posted in NetFlow on December 2nd, 2009 by mike@plixer.com
Best Practices in Network Behavior Analysis: Part 1 of 2

Many companies are primarily concerned with Internet security threats.  I feel that majority of security threats are derived internally. According to Forrester Research, the majority of security breaches involve internal employees, with some estimates as high as 85 percent.

What I want to point out today is that we should not only be concerned about internal threats but, we should go about dealing with them a bit differently than external threats.

Monitoring for the Scan
Monitoring for SYN, XMAS, RST/ACK, FIN, etc. scans on the internet will initially result in amazement.  The volume of these types of attacks on your internet connection are constant (i.e. hourly) and generally more of a nuisance than a real security threat.  Why would I reduce these Internet scans to merely calling them ‘annoying’?  Because trying to stop the constant barrage of these types of connections is impossible.  Chasing them down and stopping them is often impossible and for every one you stop, 6-10 more stack up.  Most companies deal with these scans simply by blocking them.

Monitoring for the above scans should most certainly be done internally.  Detecting a SYN scan internally for example, can often lead to a source that is infected with some nasty that was brought into the network either by a software download or via prior non internal use of the machine.  Perhaps the laptop went home, got infected and then came into the office (see internet threat video).  It happens all the time.

Compromised Internet Hosts
Other security practices involve monitoring who internal hosts are communicating with on the internet.  If they are exchanging traffic with a host listed on a “known bad guy list”, an event can be triggered to take action (e.g. block the conversation).  Because “the list” involves the Internet, checking for this type of traffic need only be done on Internet routers and not every NetFlow exporting or sFlow exporting piece of equipment.

What about False Positive Alarms
Due to the nature some business applications, false alarms will occur with all solutions however, a well designed security system will allow select routers, switches and end systems to be excluded from individual anomaly detection algorithms. A period of helping the system learn the different behaviors on the network allows the intelligence of the system to better recognize and alarm on unwanted traffic patterns.

Select routers and switches for each algorithm:

faExcludeRouters

Exclude specific hosts from selected algorithms:

faExcludeHosts

A partial list of the different traffic anomalies detected by Flow Analytics can be found in the manual on page 14.  In part 2 of this blog I will discuss conversations and flow behavior as well as alarming for specific behavior patterns.

Michael Patterson
Founder and CEO

For a free 30 day trial of Scrutinizer, Download Now!

Sign up for Advanced NetFlow Training™ coming to a city near you!

If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.
Tags: , ,

2 Responses to “Best Practices in Network Behavior Analysis: Part 1 of 2”

  1. Best Practices In Network Behavior Analysis: Part 2 of 2 - NetFlow & sFlow Network Monitoring - Systrax Says:

    [...] Here is part 1 of this blog. [...]

  2. NetFlow: Monitoring Network Behavior - NetFlow & sFlow Network Monitoring - Systrax Says:

    [...] That’s why in this blog, I would like to focus on one of the most important functions of Flow Analytics: NETWORK BEHAVIOR ANALYSIS: Flow Analytics is the network behavior analysis component of the [...]

Leave a Reply

You must be logged in to post a comment.