Hardware-based software protection systems have emerged as a compelling solution for software developers that want to protect themselves against theft of their intellectual property.
That`s the word from Ernest Cockcroft, MD of DexSecurity Solutions, a company in the Dex IT Group that distributes hardware-based software security systems from Aladdin Knowledge Systems.
Cockcroft says that the term "software protection" describes all methods that a vendor can implement to ensure that users can run only copies of its software that are paid for. The aim of software protection is to make the effort of running a program illegally more expensive than a license to run the program. Cockcroft cites research from US-based International Data Corp to illustrate the impact of software piracy on just one segment of the IT market.
Says Cockcroft: "Around 26% of CAD/CAM sites have only one software seat; another 26% have just two or three. However, the average number of seats per site is 12, due to the minority of sites that have a very large number of seats-only 4% have over 50.
"According to these figures, engineering software vendors could increase revenues from software in use by up to 36% by proactively combating software piracy."
Apart from legal mechanisms such as copyright, software vendors have a range of technology-based solutions at their disposal to prevent unauthorised use of their software. Unlike legal mechanisms, technological solutions cannot simply be ignored and are often cheaper to implement, says Cockcroft.
A good software protection solution will allow software vendors to increase their revenues, as well to gain remote control over their software and its distribution and reseller channels. Such a solution should also empower vendors to capitalise on innovative sales models without the worry of licence violations, says Cockcroft.
Technological mechanisms use encryption or other protective measures to protect the software, and can be split into hardware- and software-based approaches. Common protection technologies include copy-resistant distribution disks, access locks, hard-coded numbers in computer memory, software resident inside a ROM chip and copy protection security devices (`dongles`).
Cockcroft argues that hardware-based copy protection systems offer the superior solution because they are more secure than software solutions and place a minimum burden on the software user. There are two major types of hardware-based solutions: EEPROMs and the much stronger ASIC-based solutions.
Electrical Erasable Programmable Read-Only Memory (EEPROM) is a standard memory chip that can be bought off the shelf. Dongle vendors that use these chips will often mask them to conceal their identity and the known technology.
EEPROM contents are almost always readable via software and often contain plain data that make it possible to emulate the process with a software patch.
EEPROM-based copy-protection keys are "dumb" devices that allow users to store data. This is because validating the presence of the device to determine whether the user is authorised is a simple operation of reading what is stored on the EEPROM and comparing it to an expected value.
The second and stronger solution, Application Specific Integrated Circuit (ASIC), is a chip designed for a special application and cannot be bought from a regular computer or electronics shop. An ASIC can be pre-manufactured for a special application or it can be custom manufactured for a customer`s application. Because only the company that designed and manufactured it knows the technology, it is extremely secure. Microcontrollers also fall into this category.
ASIC-based and microcontroller-based keys are referred to as "intelligent" devices because they can deploy encryption. ASICs have an on-chip encryption engine designed within their logic, while microcontrollers activate an encryption algorithm that is burned into an internal EEPROM.
Says Cockcroft: "One of the most compelling arguments in favour of hardware-based software protection is that it allows vendors to implement a range of compelling business models.
"These include allowing end-users to activate the software a limited amount of times for evaluation purposes; the supply of `lite` demo version of the software with a limited amount of features activated; subscription and pay-per-use models; and concurrent user licencing models."
Editorial contacts

