Microsoft Forefront Threat Management Gateway (TMG) popularity is starting to pick up. WebSpy added support for analyzing and reporting on TMG logs even before the public release and have been improving our compatibility ever since. […]
I’m actually not trying to compare WebSpy Vantage with Google Analytics (GA), it’s like comparing apples and oranges. Both solutions provide powerful ways of tracking how visitors find your site and how they navigate through it, ideally giving you rich insights into your website traffic and marketing effectiveness. However, GA is a pure web analytics [...]
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.
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.
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.
One feature on our roadmap is the ability to re-brand the WebSpy Vantage Web Module, so that when your users hit the web module to view reports, they’re greeted with your own company logo and branding. In the mean time, I thought I’d share a way to re-brand the main elements in the Web Module by editing a few files and replacing a few images.
Google Alerts have become an invaluable tool to keep track of WebSpy’s online presence and mentions. I’m also alerted on keywords related to other players in the Internet Security Industry. The last couple of weeks I have noticed quite a steep increase in alerts on a well-known internet blocking and filtering vendor. Majority of these [...]
If you follow @WebSpy on Twitter, you would have received a very strange Direct Message (DM) from us yesterday. Something along the lines of "rofl this you?" or "you're on this vid!" or "I found you on here!" Unfortunately, the WebSpy Twitter account fell victim to a phishing scam, and as a result sent phishing spam to all our Twitter followers. We are embarrassed by the incident and we apologize to all of our followers, especially the ones that clicked the link in the DM and were caught by the phishing scam themselves. Here's a rundown of the event in the hope that it will help others know what to look out for.
In the log file analysis world, we're always dealing with large volumes of data. By default, WebSpy Vantage stores its data, including the storages that you import log files into, somewhere on your c: drive. Changing this location to somewhere with more disk space is therefore one of the first steps that customers like to perform, so I thought I'd write a quick blog to explain the locations you should be aware of and how to change them.