If you’re using Microsoft Forefront Threat Management Gateway, there is a bug in the logging that causes Bytes Sent and Bytes Received to be logged in reverse. This seems to only affect the Web Proxy logs – both SQL and W3c . We noticed in a few web reports, that people were generally uploading a lot more than they were downloading. So we checked the logs and verified the buggy behavior: (more…)
Archive for the ‘WebSpy’ Category
Video: How to use WebSpy Vantage to report on IronPort log files
Friday, June 18th, 2010
I’ve produced a video on how to use WebSpy Vantage to report on IronPort’s Web Security Appliance’s access log files. It is quite a detailed look at the key tasks involved in setting up and using WebSpy Vantage with IronPort WSA access logs, and is therefore divided into several parts. The videos take you through the following activities:
- How to import your log files and explore the information recorded by IronPort using the Summaries screen
- How to open the customized IronPort Report Templates and Aliases
- How to generate reports
- How to import your organizational structure and report on departments
- How to setup the Web Module and publish reports
(more…)
Accessing Microsoft Forefront TMG’s Log Files (SQL Express)
Friday, June 11th, 2010
If you need to analyze and report on Microsoft Forefront Threat Management Gateway log files, the most common stumbling block is enabling access to the default SQL Express databases that contains the firewall and web proxy log files.
The log databases are stored in an SQL Express instance named MSFW. By default these databases cannot be accessed by a remote computer. I’d first like to say that we recommend changing TMG’s logging to W3C text files, as these logs are about 5-6 times faster to import, and you don’t need to worry about the steps below.
But if you need to stick with the SQL Express logging, here are the basic steps to enable access to the logs from a remote computer: (more…)
How to report on bandwidth utilization using Cisco devices
Thursday, May 27th, 2010
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. In theory, this sounds like a fair plan. Unfortunately, the Cisco Firewall logs many different types of messages. Some to do with denied packets, some to do with authentication, some for vpn and so on. The information contained within each message changes. Some events include the size information that is required for any type of bandwidth assessment and some don’t. Correlating the required events to get any sort of accurate ‘bandwidth’ representation is a bit of a nightmare.
Fortunately, there’s a simpler method. (more…)
How WebSpy Vantage uses your CPUs
Friday, May 21st, 2010
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. (more…)


