Sentinel Hardware Keys Developer's Guide - Customer Connection ...

About Features, Templates, and Groups
Contents Glossary Index Troubleshooting
The more locks you add to your application, the more difficult it will be for
hackers to break your application’s protection.
When to Use API Features?
Compared to CodeCover, this method of protection is most commonly used
when:
You have access to the source code of the application.
You want to have control over the protection techniques used to
secure your application. For example, you can control the amount,
frequency, and location of the software locks4 within your application;
and the action taken if an unexpected response is received is left up to
you. Generally, the more locks you add to your application, the more
difficult it will be for hackers to break your application’s protection.
You have a little more time available to implement and test your
application protection. Typically, the API protection takes longer than
the CodeCover. Because, to implement the API protection, you must
understand the various functions and manually add them to your
code.
You want to take advantage of the state-of-the-art protection
techniques possible with Sentinel Keys—like AES-based encryption/
decryption, ECC-based signing/verification—in addition to the usual
data reading and writing methods. Using the API protection, you can
implement protection, both basic and advanced, that work best for
your application.
4. Refers to a decision point in your protected application. The purpose of a software
lock is to verify the presence of the correct Sentinel Key. For example, an application
might verify the validity of the signed data or send query data to the Sentinel Key
and require a specific response in order to continue execution. Other software locks
may simply read the data and compare it to the value known.
Sentinel Hardware Keys Developer’s Guide 59