Tag: desktop-management

Customizing ASAM module in NetFlow Analyzer

The previous blog was on ASAM will have given you an idea about the class “Scan and Probes” available with NetFlow Analyzer. Now that we know how the events are triggered we need to narrow it down, that the specific events or unwanted events can be ignored. When I say unwanted events, I mean the events that are deemed trusted or allowed network activities for certain resources and problems

Get the benefit of email alerts based on traffic volume through NetFlow Analyzer

Many organization s are concerned about volume of traffic in their network and NetFlow Analyzer makes it simpler to keep an eye on traffic volume. You could set up email alerts if the traffic goes beyond a particular level

More security to your network with NetFlow Analyzer’s ASAM

If you are looking for a tool to monitor your network bandwidth and keep a watch on the overall security snapshot of the network, then NetFlow Analyzer along with the Advanced Security Analytics Module is the perfect fit for you. With the release of the new version of ASAM, a number of new features have been added to it. This makes the ASAM the best fit to perform security analytics.

Performance based IT Shop Part 2

Not all IT problems come under the domain of the network engineer. In my previous Blog , I talked about IT shops having a hodge-podge set of tools. There are various reasons, but the real inefficiency is when these tools perform the same functions. There becomes a time and need to look at the IT problems from different perspectives. A few examples below: Kenn Nied, Senior Network Engineer at WA State Board for Community and Technical Colleges, illustrates this encounter. While looking at OpManager from a networking point of view, the operator sees alerts that a few switches and a firewall are unresponsive. Is it faulty equipment or an attack? Then turning to a Security mindset, he looks at ManageEngine Device Expert to see real time and historical configuration changes. In one case, it was identified that there was a Firewall rule change made and realized it was a misconfiguration that caused the switch unresponsive. Diagnostic time was minimal. Albert E.