The reward for reporting software piracy to the BSA is "up to $1 Million". How much does the person reporting the piracy receive? Not the full amount. Not much at all. Is the person reporting a company for piracy really protected by whistle blower law? Not always. One employee was fired for reporting a security breach.

The BSA is only one of the 26 enforcement agencies in the United States. There are over 100 in the world. 2008 is off to a good start. It's only February and the BSA has announced collecting the following settlements: $72,053, $80,000, $92,500, $175,000, $135,750, $112,000. Remember, the actual costs involved in a settlement run three to six times the settlement figures shown.

Unfortunately, "...the great majority of businesses out here in the "real world" still haven't recognized the massive threat represented by the software piracy and copyright enforcement industry players." --Alan Plastow

Of particular interest on the updated Business Technology Consumer Network (BTCN) website is a video presentation that all your management must watch. This compelling, eye-opening video gives you the flavor of the only online course on software pirate audit offense that also leads to 25% software savings. There are facts and figures you won't forget. Take a few moments to watch Software Piracy Prevention Training Overviews. Share it with your management. It doesn't get more convenient, cost effective and time efficient than this!

The BTCN also offers some nice Project Management courses. Take a look!

One thing I would like to see happen, now that software consumers are getting more proactive and aware, is somehow to find a way to encourage software publishers to set a standard as far as software headers go to aid in license compliance.

It seems it is very difficult for publishers of software asset management software to get everything right when they scan for software as the headers are all unique to the publisher.

Not only that, but they can be unique to each product, and version of the product, by the publisher.

If it is so difficult for the publishers of software asset management software, how hard is it for us to deal with the complexities of managing software licensing?

I would like to see the publishers take it upon themselves to standarize the headers in their packages, but I don't think that will happen. I really believe it will be organizations such as the Software Managers Resource and other consumer organizations who will need to address this issue and present it to the software publishers.

Now, how can we, as very informed and involved consumers, and I.T. Asset mangers, go about addressing this issue? I have ideas, but the logistics of doing it are enormous. I'd be interested in knowing what others think of this proposal.