| |
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
Crypto-Runtime |
|
|
|
| |
|
|
|
|
| |
Warranted secure clients for DB systems
If clients are protected by our crypto Edition, so they need the crypto runtime to the protected database accesses to. The crypto runtime is installed centrally from the server will be up and running in the background. The data access takes place via the ODBC/JDBC interface. Because the master with information of each client and if necessary with a key that is stored on a chip card is encrypted, only the crypto runtime provides access to an even unencrypted DB system. Both the password and the chip card must be read only once each system restart.
The crypto runtime has no effect on structure and relationships to your relational database already in use. |
|
The crypto runtime is mainly used for:
-
against data theft of exposed clients
- Personal access control, z.B. Casino
|
|
|
|
| |
|
|
| |
| |
| |
|
|
