The ongoing debate around virtualization shows no signs of getting old. Virtualization has always created a ‘conflict of interests’ between those who worry about the technology (the software vendors) and those who enjoy the benefits it offers (the end customers of the aforementioned vendors).
There was a temporary sigh of relief in the world of automated license enforcement when new methods and techniques became available to bind software licenses in a more secure and reliable manner to a virtual machine . Almost overnight, all the concerns and fears of license duplication and misuse (albeit accidental or intentional) went away. The ultimate goal of eliminating the requirements for ISV’s to make a ‘VM/no VM’ decision at the time of deploying or activating their software was finally achieved. End customers could deploy applications where they liked, the vendors no longer had to care, and the world was a happy place.
Or so it seemed….
The notion of keeping valuable information, such as licensing and trade secrets, hidden while operating in a fully transparent environment poses various challenges. How do I encrypt or decrypt content without directly revealing any portion of the key or the data? How do I perform strong encryption knowing that hackers can observe and/or alter the code during execution?
White box cryptography is an alternative approach to traditional security models. As opposed to implementations where the attacker only had access to a Black box, i.e. access to inputs and outputs and possibly knowledge of the cryptographic algorithm under attack and assumed zero visibility into internal workings, white box allows full visibility of the attacker but still keeps security intact.
This is a multi-part blog where we’ll look at the business case around a license enforcement system from many different angles. This article will begin the discussion surrounding the initial business case for initiating a license enforcement project. Follow-on blogs will focus on measuring the return on the investment of a licensing system after implementation.
Here is a term that has made it into our vocabulary a bit too much lately – “wobbly”. Suddenly everything is wobbly – our economy, stock market, jobs market. The obvious connotation is “uncertainty” but wobbly has also become a cop-out term for not knowing where something is headed. It is a sign of times we are in – or so it feels. Uncertainty in economy leads to uncertainty everywhere else.
My advice – something I try to follow rigorously at work and and personally – when you are surrounded by uncertainty, do the opposite – be decisive. This is especially true for high tech companies.
Part 3 of 3 from the series “Take on Licensing: What High-Tech Manufacturers Need to Know”
Recently, I shared the five phases that high-tech manufacturers move through in the transition from hardware-based to software-based solutions. Now that we’ve reviewed the phases and the challenges, let’s discuss best practices.
Part 2 of 3 from the series “Take on Licensing: What High-Tech Manufacturers Need to Know”
Shifting from an equipment manufacturer business model to that of a software company does not happen overnight, and typically occurs in phases. These are the common phases that take place during the transition from equipment manufacturer to software vendor:
Part 1 of 3 from the series “Take on Licensing: What High-Tech Manufacturers Need to Know”
If you’re an equipment manufacturer in the high-tech sector, you are probably already deeply involved in the evolution from a pure hardware manufacturer to a software vendor. Whether you are in the business of selling software-driven equipment for the automotive industry, medical imaging and diagnostics, digital printing, sophisticated surveillance systems, coin-operated gaming and casino gambling, the change to software licensing is impacting your business.
Each year, SD Times creates a list of the top 100 leaders and influencers in the software industry –The SD Times 100. For the third year in a row, SafeNet has made the list in the Software Security category, as well as, Quality Assurance.
While your current security infrastructure is robust, you need to ensure that you effectively keep your implementation protected in order to increase your product’s longevity and significantly increase your company’s revenue.
Some recent articles I found online got me thinking about a post I made a little under a year ago – One Man’s License is another Man’s Poison. When I looked at it again – it took me a minute to figure out the chart.
Charts that take more than a few seconds to figure out are not very good charts.
So I decided to re-do it.