| File Level Encryption Architecture Options |
|
|
|
|
|
|||||||||||||
![]() | Transparent & Customary:Transparency and customary usage are essential for acceptance of use within a enterprise. Benefits of transparent and accustomed use must apply to all those involved in the enterprise: users, IT administrators, and security administrators. Tricryption meets these requirements for: | |
Users:
| ||
![]() | Networked & Autonomous (Disconnected) Operation: Tricryption file level encryption clients typically operate with a network connected Key Server. With authorization, the client may activate it’s own internal Key Server (Remote Engine) and temporarily operate independently of the network. On the next network reattachment, key management and logging functions are resynchronized and network client-server operations are resumed. | |
![]() | Architecture Efficiencies: With file encryption clients distributed among the enterprise architecture, the overall processing cost of encryption is decentralized across all of the nodes. Key servers can be scaled and allocated to various client encryption groups (Communities of Interest/CoI) as encryption operational loading dictates |
Security Components & Infrastructure Integration
![]() | ![]() |
| Encryption Algorithms AES 256 (NSA Suite B) AES 192 AES 128 3DES Proprietary (Client) Concurrent Use Capable | Crypto Modules Open SSL 0.99L Safenet Luna HSM nCipher nShield |
![]() | ![]() |
| Authentication Active Directory LDAP NIS (*nix) Token PKI Native (SRP Protocol) SAML (Development) | Authorization
|

File Encryption









