Comparison of Protection Key Attributes

This section compares Software (SL), Cloud (CL), and Hardware (HL) licensing methods, and describes the key attributes of each protection key type. It helps you choose the most suitable key based on your security, platform, and operational requirements.

Comparing Software (SL), Cloud (CL), and Hardware (HL) Licensing Methods

Sentinel LDK supports various licensing methods to suit your specific needs and requirements. Each method has its unique advantages for developers and end users. This section focuses on cloud licensing (CL) for its flexibility and ease of use.

The following table illustrates the various licensing methods that Sentinel LDK offers.

Aspect Software Licensing (SL) Cloud Licensing (CL) Hardware Licensing (HL)
Deployment Installed on the hard drive of the customer’s computer or server. Hosted on Thales cloud servers or Vendor-hosted server. Physical USB keys (dongles), connected to the customer’s computer or server.
Requires shipping to the customer No No Yes
Requires the user’s computer to have internet connection Optional (license fulfillment is simpler if connected)

Yes1

No
Action required from the customer / user Install a license file. Install an identity string or using user name and password. Connect the Sentinel HL key to the machine.
Use the license on any machine Possible through rehosting, where the user copies files to and from the source and recipient machines to transfer the license. Completely transparent. The user just needs to launch the application on any machine where the identity was previously installed or the user just needs to launch the application on any machine and enter the user name and password. Possible. Requires the key to be disconnected from one machine and connected to another.
For licenses with concurrency, users can detach a single license to their computer for continued offline use (commuter license) Yes Yes No
Suitability for VM and Docker environments Medium for servers/cloud. Low for local machines. High for all connected scenarios. Low for servers/cloud. High for local machines.

1Offline Detach can be used for air-gapped clients.

1A license can be detached to a server on the LAN that has internet connectivity, and the client without internet access can log in to that server to use the license.

Protection Key Attributes

The various types of Sentinel protection keys that are available provide different levels of security and flexibility, as described in the table that follows.

Type of Sentinel Protection Key Level of
Security
Supported
Operating
Systems (Local)
Supports
Time-based Licenses
Supports Concurrency and Detachable Licenses
SL AdminMode key (excluding Unlocked Products) + + + + 4 Windows Mac
Linux Intel/ARM
Uses V‑Clock Yes1
SL AdminMode key (Unlocked Products)

Windows:
+ + 4

Others:
+ 4

Windows Mac
Linux Intel/ARM
Uses V‑Clock No
SL UserMode key (excluding Unlocked Products) + + + + 4 Windows
Android
Linux Intel/ARM
Uses V‑Clock No
SL UserMode key(Unlocked Product) + 6 Windows
Linux Intel/ARM
Uses V‑Clock No
SL Legacy key + + + + 4 Windows Mac
Linux Intel
Uses V‑Clock Yes1
HL (HASP configuration) Basic key + + + + + Windows Mac
Linux Intel/ARM
No No
HL (Driverless configuration) Basic key + + + + + 5

Windows Mac
Linux Intel/ARM
Android

No No
HL (HASP configuration) Pro key + + + + + Windows Mac Linux Intel/ARM No No
HL (Driverless configuration) Pro key + + + + + 5 Windows Mac
Linux Intel/ARM
Android
Uses V‑Clock (Requires V‑Clock module in the Sentinel LDK Master license) Yes 1 2 3
(Detach not supported)
HL (HASP configuration) key (Max, Drive) + + + + + Windows Mac Linux Intel/ARM No No
HL (Driverless configuration) key (Max, Drive) + + + + + 5 Windows Mac
Linux Intel/ARM
Android
Uses V‑Clock Yes 1 2 3
(Detach not supported)
HL (HASP configuration) Time key + + + + + Windows Mac Linux Intel/ARM Uses real-time clock on the key No
HL (Driverless configuration) Time key + + + + +5 Windows Mac
Linux Intel/ARM
Android
Yes 1 2 3
(Detach not supported)
HL (HASP configuration) NetTime key + + + + + Windows Mac
Linux Intel/ARM
Yes
(Detach not supported)
HL (Driverless configuration) NetTime key + + + + + 5 Windows Mac
Linux Intel/ARM
HL (HASP configuration) Net key + + + + + Windows Mac
Linux Intel/ARM
No Yes
(Detach not supported)
HL (Driverless configuration) Net key + + + + + 5 Windows Mac Linux Intel/ARM Uses V‑Clock

Legend:

1 - Requires network seats from the Sentinel LDK Master license.

2 - Requires network seats from the Sentinel LDK Master license. Requires License Manager 7.3 or later on the machine where the protected application executes. The required version of License Manager is provided in Run-time Environment 6.65 or later.

3 - To support concurrency for Linux ARM, Run-time Environment 8.11 or later is required.

4 - For SL keys, support for virtual machine and for rehost is optional. Adding support for these should be avoided unless required because they implicitly reduce the security level.

5 - Security for all HL (Driverless configuration) keys can be further enhanced for Windows platforms using AppOnChip functionality.

6 - For SL keys, support for virtual machine is optional. Adding support for these should be avoided unless required because they implicitly reduce the security level. Rehosting does not apply to unlocked keys.

NOTE   The table above relates to the operating system on the machine to which the protection key is attached. However, for protection keys that support concurrency, the protected application can be located on a different machine. In this case, the protected application can be executing under any operating system listed in the table even when that operating system does not support the protection key.

For example: A protected application running on an Android machine can be licensed by an SL AdminMode protection key on a Linux Intel machine.

For information on V‑Clock (the virtual clock available on most Sentinel protection keys), see How Sentinel LDK Protects Time-based Licenses With V-Clock.

For full technical specifications of the available Sentinel HL keys, refer to the Sentinel HL Data Sheet.

For additional information, see Situations That Require Sentinel LDK Run-time Environment.