Select Language US Language
German Language
breadcrumb.home / Documentation / API Implementation

API Implementation

API Overview

Hardware-based protection requires your protected applications and/or data files to have a corresponding CRYPTO-BOX attached to the computer (or a computer in the network) in order to function normally. The protected software checks wether the CRYPTO-BOX is present. If the CRYPTO-BOX is not found, the program can switch to demo mode or even refuse to work (in whole or in part, depending on your protection settings).

When the CRYPTO-BOX is connected, the program communicates with it and carries out a detailed check of the information stored in the CRYPTO-BOX, such as:

  • Verification of serial number (BoxName) or Developer ID
     
  • Use the hardware-based encryption engine to decrypt information while the application is running
     
  • Querying license information from the internal memory of the CRYPTO-BOX during application run-time

These and many other unique CRYPTO-BOX functions can be used to create a reliable protection strategy. Data files can be encrypted with the CRYPTO-BOX internal on-board encryption.

This approach guarantees an extremely reliable protection model:
Encrypted data files can be viewed only if a corresponding CRYPTO-BOX is connected to the end user's computer.

Further limitations can be added, e.g., expiration dates:
The end user can only use the software until a defined date has been reached.

MARX offers you a convenient option to update such expiration dates remotely (see RUMS Application Notes for more details).

Implementation with API means that all of the above functions can be added directly into the application's source code using predefined API calls (details can be found here).