SafeNet today announced an enhanced version of the Sentinel Envelope file-wrapper technology within its software protection, licensing, and entitlement management system, Sentinel License Development Kit (LDK).
With the new AppOnChip functionality, software developers bind protected software to hardware keys, requiring the physical presence of the key to not only validate usage authorization but to execute the code itself, further strengthening the protection, said a press release.
AppOnChip is a fully automated process for binding a Sentinel hardware key to protected software by forcing selected pieces of code to execute on the key. In the absence of the key, the application fails to execute. All this is done without storing any of the application code on the key itself, the release added.
AppOnChip strengthens Sentinel LDK’s intellectual property protection, adding to Sentinel Envelope’s file encryption, code obfuscation, and anti-debugging features. AppOnChip evolves software security to prevent the illegal use of commercial software by unauthorized users.
Michael Zunke, CTO of SafeNet’s software monetization division, said, “Many ISVs have avoided implementing software security to the level provided by AppOnChip because it was a cumbersome, manual process.”
“Now, SafeNet customers can implement token-based software execution technology at the touch of a button. We believe that the additional security that AppOnChip delivers makes Sentinel LDK the most secure software licensing implementation available in the market,” added Zunke.
Benefits of SafeNet’s AppOnChip software protection technology include:
* Stronger security – As AppOnChip forces a small piece of code to run on the token, and the results are necessary for the application to fully execute, the application will fail to execute without the hardware key. Software vendors can choose which specific code blocks should be protected via an easy-to-use graphical interface.
* Easy implementation – The process of binding the software to the hardware key, analyzing which code can be executed on the token, and converting code into token-executable form is fully automated- no engineering effort is required.
* Nothing is stored on the token – Unlike competitive solutions, all of the code resides on the hard drive of the machine running the protected application. Only at run time, a small piece of code is executed on the token. User memory on the key is not impacted.
* Internal processes are unaffected – Protected applications do not require version tracking at the software vendor’s end, and key updates in the field are not required for new versions of the protected software.