Advanced Security Analytics Module (ASAM), is one of the most significant Add-Ons for any enterprise class network looking to utilize flow based monitoring technology. Without any additional hardware or export configurations, this simple Add-On to NetFlow Analyzer can act as your network Intrusion Detection System leveraging on the prevailing flow data collection in place.

Compelling reasons to choose a flow based security analytics system over complex and expensive signature based threat detection systems is ease of deployment and cost effectiveness. ASAM does not require any base lining period and manual intervention for it to detect network anomalies. ASAM starts reporting on anomaly events immediately after the installation of the module.

Below are the salient features of the ASAM Add-On for NetFlow Analyzer:

1. Real time threat detection

      ASAM, built using the state-of-the-art "Continuous Stream Miner" technology, helps identify numerous threats in your network in real time. The underlying engine is optimized for scalability with very less memory and CPU footprints.

2. Security Snapshot Report

      Security snapshot gives you a quick understanding of different types of intrusion activities over a configurable time period.

                
                

3. Highly Customizable 

      Discarding and White listing based on 

                  * Security Events
                  * IP addresses
                  * Flows matching specific criteria

      ASAM, giving more power to the you, helps see threats based on your specific requirements also. Ensures near zero false positives occur by filtering known good data. 

      Additionally ASAM does not require signature or pattern definition updates to detect security threats, instead the analytics engine is capable of identifying threats by correlating transactions using a robust "date time span offset" clustering algorithm, delimited based on active and inactive time outs and threshold violations for various flow fields.
 
To know more about ASAM and the anomaly types detected by ASAM, check the link here.

Try the 30 day fully featured trial of NetFlow Analyzer with ASAM Add-On. Feel free to talk to the support team for any questions on NetFlow Analyzer and ASAM.


Thanks

Configuring Cisco ASA NetFlow via ASDM

Jul 22 2010 06:20:40 AM Posted By : Praveen Kumar V

All of you must have already heard about Cisco ASA now supporting NetFlow export through a flow format called NetFlow Secure Event Logging (NSEL ). This now provides users the ability to do almost real time traffic analysis and bandwidth monitoring on their firewall devices too. NetFlow support from ASA received very excellent responses from users because of which we at NetFlow Analyzer started support for not just plain ASA NetFlow reports but also for NATed information available in the ASA NetFlow packets.

With NetFlow support, I am sure a number of users out there will like to know the best and easiest way to configure ASA for NetFlow export. Check out the steps below to configure NetFlow export on ASA via ASDM:

Configuring Flow Collector:

In ASDM, under Configuration go to Device Management > Logging > NetFlow


Here, you can set the NetFlow Analyzer server IP address, the ASA interface through which NetFlow packets are to be exported and the NetFlow listener port (By default it is 9996). When you choose the interface, select the interface which connects to the server where NetFlow Analyzer is installed. You can also set the template packet send frequency and disable syslogs that are redundant after the NetFlow information extraction.

Set the template time out rate as 1 minute and delay transmission of flow creation events for short-lived flows to be 60 seconds.


Then click on Apply to write the commands on ASA.

Configuring NetFlow information extraction:

To enable the ASA to start sending information to the NetFlow Analyzer defined above you need to go to Firewall > Service Policy Rules.


Then you need to create a new service policy that needs to be applied GLOBALLY.


And then define the collector that statistics for this traffic will be sent to (was defined initially).

Once the service policy is created click on Apply to write the commands on ASA.


To configure Cisco ASA through CLI click here .

Once the configuration is complete, NetFlow data will be exported and you will start seeing results in NetFlow Analyzer.

Demo | Download 30-day Trial Twitter  | Customers

Regards,
Praveen Kumar

Hope you have seen the last blog regarding the reporting enhancements we made in NetFlow Analyzer Version 8 . In continuation of the last blog, some of the other reporting enhancements.

1. New averages for Traffic Report (5 and 15 Minute)

2. Global Search Function

3. Enhanced CBQoS Reporting.

Traffic Reports:

In earlier versions of the product, traffic reports generated for less than 24 hour period were shown in 1 minute granularity. As the time period increased, the granularity also increased. But we had demands for other granular reporting like 5 minutes which would enable users to compare their NetFlow statistics with SNMP statistics because the difference between 1 minute average and 5 minute average was much higher than required and also called for the user to do a manual comparison.

We have now introduced new reporting granularity to the traffic reports where data can be shown in 1 minute, 5 minute or 15 minute averages. Users can now get a better picture for capacity planning based on different averages and can also compare the NetFlow statistics with SNMP based statistics avoiding manual calculation. Users can also also generate conversation reports for all these averages helping users find the cause for change in traffic pattern visibility reports.




Global Search Report :

Users looking for an IP Address, port, protocol or for that matter, any information, had to select an interface and then use a troubleshoot report to search for their requirement. A global search option was one of the most requested feature form customers and evaluators alike. Just as most of our features are defined by users, we introduced the ''Global Search' function in Version 8.

This report helps users to generate reports for IP address, Port, network, nodes, Application, DSCP..., etc by entering their criteria in the 'Global Search' box available in the top right corner of the UI from every page. When you enter a criteria here and search, the results are generated for the specific value after searching all the interfaces being monitored with NetFlow Analyzer .



Enahanced CBQoS Reporting:

Quality of Service refers to the ability to provide better treatment for some applications over other services in the network. The primary goal of implementing QoS in business critical networks includes priority routing for critical applications through dedicated bandwidth, controlling jitter and latency. Configuring QoS can also limit the bandwidth used by non critical network traffic and so makes network performance more predictable and bandwidth utilization much more effective.

We have discussed a lot about deploying CBQoS policies for improved network performance. You can find CBQoS blog series in this link. Until last version, CBQoS reorts will show only the parent policies with its pre and post policy and drop metrics . From Version 8, we list all the child policies created under the parent policy along with the pre and post policy, drop metrics for each child policy and even match statement based statistics. All the reports for CBQoS can also be exported to PDF and scheduled from this version which takes bandwidth management to a more easier level.



Do drop your suggestions for each of these features and let us know what else you would like to see in the future releases of the product.

Demo | Download 30-day Trial Twitter  | Customers

Regards,
Praveen Kumar

World cup referees and network administrators!

Jun 23 2010 04:14:13 AM Posted By : Joseph

Hope you all are enjoying the world cup 2010. I know I am! After 10 days in to the game, I came to a conclusion that there are two kinds of referees, one who blows the whistle every time a player as much as just touches another player. This is followed by a game stoppage, even for a few seconds, which ruins the game for the players, spectators and everyone else involved.

And then there are the other kind of referees, they are experienced bit. They know exactly when a serious offense has been committed and if it is worth to stop the game. This might be followed by a yellow card or even a red card.




Now to the Network and network administrators, they are the referees in the ground called "network" and the players called "users". There are two kinds of network administrators. Those who stop the whole network trying to troubleshoot a network-slowdown issue caused by a single person, this ruins every users' experience in the network. The other kind of network administrator is the ones who have the experience and the right tools to know exactly with whom and where the fault lies. They identify the exact cause (maybe a person, application etc.) of the problem and deal only with the problem without causing unnecessary havoc in the whole network.

Which kind are you?! Get the right tool !


The "game" must go on!

cheers
Joe

At Manage Engine NetFlow Analyzer , we have always concentrated on having a simple, easy to understand GUI which can give the results you are searching for within minimal number of clicks and less than a minute. If you have used NetFlow Analyzer you certainly must have seen all the reporting options . If you have not, check our Online Demo to know how easy things are.

NetFlow Analyzer Version 8 brought in many features like VoIP monitoring, SNMP V3 and Cisco ASA support, Flexible NetFlow based NBAR, Geo Locations and so on. But along with these vertical enhancements, we have also topped up the reporting capabilities to help users get more from the product. I will explain some of the enhancements we made in Version 8 through this blog.

Consolidated Device Reports:

Until the last version, Consolidated report was available for Interfaces and IP groups. This single page report lists the traffic graph for a selected interface or IP group with the top 10 Applications, Source and Destination for IN and OUT directions. Same as consolidated report for Interface or IP group, NetFlow Analyzer 8 provides an option to generate a consolidated report for a device itself.

Consolidated Report for a device lists traffic graph with Top Interfaces based on Utilization and Speed, Top Application, Protocol, Source, Destination, Conversation, DSCP etc. This report can be generated for last hour and up to last 24 hours. With this report, NetFlow Analyzer provides a view of traffic at the device level giving you an idea on the high usage devices. The report should help get a more detailed visibility on device traffic, narrow down on the performance of device in relation to traffic passing and helps understand the traffic pattern on the devices.

This Report can be generated by clicking on Device Name or IP address from the Interface View or Dashboard.



Enhanced Schedule of Reports.

Schedule reporting option lets users create reports about the information they need and have it automatically emailed to them on a daily, weekly or monthly basis. The reports can be send to multiple email addresses defined by the users and the reports are also saved within the product for later access. Until the last version, only two types of reports were possible, Consolidated Report and Custom Report, both of which could be scheduled for Interfaces and IP groups.

Version 8 introduced the "One Click" Schedule option. This allows users to create schedules for any report they see on the screen. Say, you are looking at a Application report for an interface and you would like to have it emailed to you, use the 'Once Click' schedule.

The reports (for Traffic, Application, Source, Destination, Conversation, QoS, NBAR, CBQoS, etc) can be scheduled for Interfaces and IP groups using the one click option. You now don't have to go into Schedule Settings, create schedule and etc. This one click schedule is keeping in tandem with our aim for fewer clicks and faster reporting.



This is not it. We do have other enhancements in reporting like 'Global Search', '5, 10 and 15 minute averages' and will walk you through them in our next blog.

Demo | Download 30-day Trial Twitter  | Customers

Regards,
Praveen Kumar

Accountability in an Enterprise!

Jun 15 2010 02:51:43 AM Posted By : Joseph
Large enterprises which span across various countries face a challenge when it comes to monitoring bandwidth usage across various branches.  Harder still is the accountability, who is using what application or who is using a non-business-critical application which is clogging the bandwidth and suffocating a much needed business critical application.

At times, depending on the department in an enterprise, the critical applications will vary. In such a case it is important for network managers to account department wise bandwidth usage. For enterprises dealing with client projects, it is critical to keep track of bandwidth used by the enterprise team, for chargeback, allocated for that project.

NetFlow Analyzer Enterprise Edition has a distinct two-tier architecture which allows high scalability. Enterprise edition allows large enterprises to monitor branch offices spread across different geographic locations.

Billing for Enterprise Edition

NetFlow Analyzer allows the creation of IP groups, which can be used to segregate departments. For example, groups such as R&D or Finance or HR can be created by grouping the associated IP addresses. It is possible to monitor the traffic behavior for these groups and which applications are used. If need be, alert profiles can be set for these groups separately.



Billing in netflow analyzer

In case of enterprises dealing with client projects, the network manager can create group consisting of employees working for that project. Traffic reports consisting of applications and other details for that particular group can be monitored. In addition to that, this group can be associated with a user configured bill plan. The flexible bill plans allows creation of customized bill plans as per the needs of the enterprise. This can be used to chargeback / accounting. Enterprises can also use this to crosscheck the bills received from ISP’s.

Every penny saved is a penny gained!

Download  | Online Demo  | Enterprise Edition overview [video] | Twitter


Related Read:



cheers
Joe

The last blog gave an outlook on what NBAR reporting is and how NetFlow Analyzer can report on NBAR stats via both SNMP and Flexible NetFlow giving users the edge to get NBAR reports from old and new Cisco network devices. Lets now move on to configuring your devices for Flexible NetFlow export with NBAR information.

Flexible NetFlow (FNF) requires the creation of a flow exporter, flow record and flow monitor. The flow exporter defines the export aspects of the flow data like export destination, UDP port for NetFlow export, export interface and so on. The flow record defines the key and non key fields to be included in the flows. Both the exporter and record are then associated with a flow monitor which again has to be associated with every L3 interface of the monitored router. Doing this exports NetFlow data from the device to the IP Address specified.

First, let us create the flow exporter.

FLOW EXPORTER:

cisco_281(config)#flow exporter FNFnbarEXP                        - Name of the flow exporter
cisco_281(config-flow-exporter)#destination 192.168.116.80    - IP Address of the NetFlow Analyzer server
cisco_281(config-flow-exporter)#source fastEthernet 0/0         - Can be any interface like Loopback
cisco_281(config-flow-exporter)#transport udp 9996                - UDP for exporting NetFlow packets
cisco_281(config-flow-exporter)#version 9

Now, to creating a flow record with the statement which will enable the inclusion of NBAR records with the NetFlow data.

FLOW RECORD:

cisco_281(config)#flow record FNFnbarREC
cisco_281(config-flow-record)#match ipv4 source address
cisco_281(config-flow-record)#match ipv4 destination address
cisco_281(config-flow-record)#match transport source-port
cisco_281(config-flow-record)#match transport destination-port
cisco_281(config-flow-record)#match interface input
cisco_281(config-flow-record)#match ipv4 protocol
cisco_281(config-flow-record)#match ipv4 tos
cisco_281(config-flow-record)#match ipv4 dscp
cisco_281(config-flow-record)#match application name        - This statement allows the inclusion of NBAR data in NetFlow records.

cisco_281(config-flow-record)#collect routing source as
cisco_281(config-flow-record)#collect routing destination as
cisco_281(config-flow-record)#collect routing next-hop address ipv4
cisco_281(config-flow-record)#collect transport tcp flags
cisco_281(config-flow-record)#collect counter bytes
cisco_281(config-flow-record)#collect counter packets
cisco_281(config-flow-record)#collect timestamp sys-uptime first
cisco_281(config-flow-record)#collect timestamp sys-uptime last
cisco_281(config-flow-record)#collect interface output
cisco_281(config-flow-record)#collect flow direction
cisco_281(config-flow-record)#collect ipv4 id
cisco_281(config-flow-record)#collect ipv4 source mask
cisco_281(config-flow-record)#collect ipv4 destination mask

The flow record and exporter now has to be associated with a flow monitor.

FLOW MONITOR:

cisco_281(config)#flow monitor FNFnbarMON
cisco_281(config-flow-monitor)#exporter FNFnbarEXP
cisco_281(config-flow-monitor)#record FNFnbarREC
cisco_281(config-flow-monitor)#cache timeout active 1
cisco_281(config-flow-monitor)#cache timeout inactive 15

The flow monitor then has to be associated with each and every L3 interface of the router. The 'input' variable sets the flow collection for ingress traffic.

ASSOCIATING TO INTERFACE:

cisco_281(config)#int FastEthernet 0/0
cisco_281(config-if)#ip flow monitor FNFnbarMON input

cisco_281(config)#int FastEthernet 0/1
cisco_281(config-if)#ip flow monitor FNFnbarMON input

Once the configuration is done and saved, flows will be exported to the server where NetFlow Analyzer is installed. NetFlow Analyzer is based on automatic discovery and so the NetFlow exporting devices are automatically discovered and reports are generated within seconds of receiving the flows.

Lets now see how the NBAR reports look like.

Traditional NBAR, based on SNMP polling, allowed only the capture of the application name and its usage in the network. This did not have the capability to include the hosts involved with the application traffic.

SNMP based NBAR

Though this information is useful for defining CBQoS polices, the lack of visibility was always there. This is where FNF NBAR report really makes the difference. FNF NBAR can show the traffic conversations for the applications identified by NBAR thus helping network administrators find out who really used an application.

Flexible NetFlow based NBAR
For SNMP based NBAR collection, your router should support the CISCO-NBAR-PROTOCOL-DISCOVERY-MIB. This will enable reporting softwares like NetFlow Analyzer to collect NBAR stats via SNMP polling. In case your router has the latest IOS with FNF support, you can use the FNF based NBAR collection which can be done by simply configuring the router as mentioned before.

Use NetFlow Analyzer to get NBAR reporting the way you would like to have it.

Download | Interactive Demo | Product overview video | Twitter | Customers

Regards,
Don Thomas Jacob
ManageEngine NetFlow Analyzer was one of the first tools to add NBAR reporting along with NetFlow reporting to the product. Network Based Application Recognition, a classification engine in Cisco IOS, has the ability to detect a wide variety of applications via deep packet inspection using PDLMs (Packet Description Language Module - The PDLMs contain the rules used by NBAR to recognize an application.).

NBAR is a more of an intelligent classification and has the ability to identify web based and client-server applications that uses dynamic ports as well as those using well known port numbers (like Bit Torrent). This helps the network administrator identify what really is going on in the network and then define QoS policies to ensure that the bandwidth is used for its original purpose - run business applications.

NBAR data, until now, has to be collected through SNMP polling of the NBAR MIB (CISCO-NBAR-PROTOCOL-DISCOVERY MIB) in the router. The NBAR reporting tool queried this MIB and gave outputs about the usage. Though NBAR gave users the ability to discover applications that used well know ports or visibility on applications that used dynamic ports, well visible was the limitation too. SNMP NBAR did not have the ability to report on the hosts involved with the identified application. So, NBAR allowed the network admin to define QoS policies which limited or blocked the application bandwidth, but he was unable to find out which user was involved with the traffic. Identifying the user will give more powers: identify hosts on which Peer to Peer applications are installed, ensure that the application was used by the intended user, warn the user if he was using a business critical application or define network management policies.

Flexible NetFlow - NBAR Integration (FNF - NBAR) :

With the introduction of Flexible NetFlow, things have changed. Flexible NetFlow, which requires NetFlow V9 exports, allows a user to define the key and non key fields in a flow record. This way, users define what they need to or need not see from NetFlow data and define what is classified as a single conversation. Flexible NetFlow configuration is different from the traditional NetFlow (called NetFlow v5) as this requires the creation of flow exporter, record and monitors. Read more on Flexible NetFlow configuration from our blogs here .

Match Application Name:

Flexible NetFlow allows defining the key and non key fields through match and collect statements, Our star match statement is the 'match application name' command which allows users to capture the NBAR application information to be included in NetFlow records. This helps identify, through a combination of NetFlow and NBAR reporting, the users involved with the 'unwanted' applications. Network admins who complained about not being able to see the users can leverage on the new reporting feature to see the hosts involved or the 'culprits' in case of undesired applications.

The support for this match statement is available with Cisco IOS 15.0 or above. So, any user running the latest IOS on their devices can use the new FNF - NBAR and get detailed visibility into their application usage.

The real 2 in 1:

Why limit your NBAR reporting to only the new devices or through IOS upgrades? Who will want to move the sturdy Cisco 2800 for a new device just for FNF NBAR report?
This is why NetFlow Analyzer has not dropped SNMP NBAR support even after the introduction of FNF - NBAR. There certainly are many users who have devices with the 12.x IOS trains which supports only SNMP NBAR and NetFlow Analyzer will not leave them in the lurch. So, users who have new devices with the mentioned IOS or have upgraded their IOS to the latest can opt for FNF - NBAR and users who have the earlier IOS versions can continue to use the SNMP NBAR. Now, that really is NBAR support.

Our next blog will walk you through the detailed configuration for Flexible NetFlow with NBAR support and show how NetFlow Analyzer does the reporting.

Download | Interactive Demo | Product overview video | Twitter | Customers

Regards,
Don Thomas Jacob

NetFlow Analyzer has various reports which helps users monitor bandwidth, do traffic analysis, drill down on network spikes, do trend analysis and make capacity planning decisions. With NetFlow Analyzer Version 8 , we have brought in Geo Location based report for IP Addresses.

What is Geo Location IP?

Geo Locations reports of IP Addresses provides businesses with a non-invasive way to determine region based information about the source and destination of traffic in real-time. This report can help determine to which country or region he was heading. Geo Locations reports of IP Addresses will help us in following:

1. Fraud Detection

2. Geo Marketing

3. Target Content

4. Spam fighting

5. Traffic Analytics

It helps ISP's and enterprises determine the location of their traffic and thus help in determining the routing and AS pairing for better performance and cost savings.

Geo Location IP in NetFlow Analyzer.

The Source and Destination Tab in NetFlow Analyzer gives traffic utilized by each IP addresses for the selected time period. Until the last version, these reports helped you to identify the IP Addresses contributing to the traffic on each interface either at the source or destination level. With the new feature, you can view the Region wise (Country) traffic distribution. The Geo Location reports for IP Addresses list top 10 IP addresses for each region on the Source and Destination Tab.

Configuring GeoLocations.

After upgrading to Version 8, clicking on the Source or Destination tab will give an option "Show Geo Locations". When you click on this, NetFlow Analyzer will prompt you to provide proxy settings to download the Geo location database and update NetFlow Analyzer database with these locations. In case you do not prefer to provide the proxy details in NetFlow Analyzer, you can download the "countrycode.zip" from the prompt window that appears and extract it under the NetFlow Analyzer installation directory (<NetFlow_Home>\).



Now, click on "Show Geo Locations" and NetFlow Analyzer will list the region wise report for the traffic. Much more visibility than ever before !

Regards,

Praveen Kumar

Demo | Download 30-day Trial Twitter  | Customers


Traffic spikes are unavoidable in most networks - The reasons can be many, ranging from increased network traffic due to a large online backup to a DDoS or a virus attack. To analyze such spikes which usually range from less than a minute to a few minutes, you need a tool capable of real time reporting with per minute visibility.

ManageEngine NetFlow Analyzer, with its capabilities for real time reports and sub minute visibility helps find the root cause of network spikes. This video will walk you through on how you can drill down to the root cause of a network spike almost as soon as it happens.

Watch the video and say adieu to unexpected downtime in your network !




Praveen Manohar
Technical Team
NetFlow Analyzer
Blogs | Forums | Twitter