Today I was speaking to a customer that had the following reporting request. "I would like to know how much of my bandwidth is being eaten by each protocol. I will then use this information to determine if circuit may need to be increased due to increased traffic". This customer was collecting syslog messages from a Cisco Firewall, then using WebSpy Vantage to generate reports. There's a simpler method.
I’m frequently asked how WebSpy Vantage utilizes a systems CPU resources. Sometimes you may notice Vantage utilizing 100% of your machine's CPU power, and other times it will be hardly touched. So here is an overview of how the software works internally so you can understand when your CPUs will and won’t be pushed.
We've just released an auto update for WebSpy Vantage (Premium, Giga and Ultimate) as well as the Web Module. This is a great update for Vantage Ultimate users as we've introduced a new feature/tab into the Web Module called 'Dynamic Reports'. Here's the full list of changes since the last auto update (184.108.40.206 on the 14th April 2010).
We have just issued an automatic update for the Vantage range of products, including Vantage Ultimate and the Web Module. Unfortunately there are two issues with the Web Module auto update process. Everyone on a 64 bit operating system machines will encounter issue #1 (Unable to locate installation location), and some of you may encounter issue #2 (System.IO.FileLoadException).
It’s been a crazy few weeks but we’ve finally managed to get the first release of WebSpy Soho out the door. It is our intention to keep our Alpha testers up to date with our ongoing development. Right now, I’d like to inform you about some issues experienced by a handful of testers and how to go about resolving them.
We have just added support for the 'Group' field in IronPort's access logs. You can add this field to your logs by adding %g in the 'Custom Fields' edit box. We have also added support for the custom fields Body Request Size and Body Response Size.
Our support for Microsoft Forefront Threat Management Gateway is quite new and we’ve just fixed a couple of issues that we haven’t yet released as a public update yet. In particular, this update fixes the "specified cast invalid error" that occurs when importing the Web Proxy database logs.
I've been having a look through the reporting functionality included in Microsoft Forefront Threat Management Gateway to find that not much has changed from ISA Server 2006. There is some new information regarding the newly implemented URL categorization and threat management technology, but there is very little flexibility or customization for those with reporting requirements beyond general overviews cluttered with irrelevant information. Here is what I consider to be the 8 main limitations of Microsoft Forefront TMG's reporting functionality.
Most of our customers using Microsoft ISA server are probably aware by now that Microsoft have released the new version of ISA server, which is now re-branded as Microsoft Forefront Threat Management Gateway (TMG). In addition to this, Microsoft has also re-branded its Internet Access Gateway (IAG) to Unified Access Gateway (UAG). […]
Today I was asked how to transfer one report in the web module to a different user. The obvious reason for this is when someone leaves your company, the reports they had access to need to be transfered to the new person taking over their role. Unfortunately there’s not an easy way to do this via the user interface yet, but it is a planned feature. In the mean time, you can do it by editing an XML file manually.