|
|
| How PrivateServer HSM Works
Any application that requires a cryptographic-based process will access PrivateServer through the network using the PrivateServer client. All data transferred across the network is encrypted. The process then takes place in the server, which accesses relevant keys provided the connecting user has the necessary permissions to do so. The entire operation is performed by PrivateServer, which then replies back to the client application to enable the transaction. |
|
|
|
- Microsoft CA (Win 2000, 2003 Server, 2008 Server)
- Microsoft Certificate Lifecycle Management (CLM)
- Entrust PKI
- Baltimore UniCERT
|  |
| |
- FIPS 140-2 Level 3
- FCC Subpart B Class B
- EN 55022 Class B for AC mains and Ethernet lines
| |
| | |
- PKCS#11
- Microsoft-Cryptographic API (CAPI)
- Java (JCA or extended)
| |
|
- W 48.3cm; D 44.7cm; H 17.8cm
- 6U Rack mountable
- Weight 15KG
| |
|
- Smart Card (Windows only)
- USB Token (Windows only)
- Software Key (Windows, Linux, HP, AIX and Solaris)
| |
|
- 1350 RSA Signatures per second (1024 bit)
- 8000 Symmetric Transactions per second
| |
|
- SHA-1, SHA-256, SHA-512
- ISO-Hashing
- ARDFP
- MD5
| |
| |
- Microsoft Windows 2000, XP, 2003 Server, Vista
- Sun/ Solaris (32 and 64 bit)
- HP-UX
- AIX (32 and 64 bit)
- OS/2
- Linux
- STRATUS/VOS
- Tandem
- MVSOS390
- OpenVMS
| |
|
|  |  | Interessieren Sie sich für weitere Informationen? | |
|  |
|
|
|
|
Asymmetric Encryption Algorithm