white papers

Encryptionizer Vs. Whole Disk Encryption

Encryptionizer allows the separation of roles of the Data Owner, Application Owner and Computer Owner. Often with Whole Disk Encryption, Encryption keys are in the hands of the computer owner or Computer Admin. Encryptionizer allows the protection of application data from the Computer admin, allowing the Application or Data owner to maintain control of the data – all while providing Transparent access only via the allowed applications.

  • You cannot bundle and deploy Whole Disk Encryption with your application as it requires end user setup.
  • With Whole Disk Encryption, the end user will need to know the encryption key in order to run your application, and in that case they can just decrypt the files.
  • Encryptionizer lets you use different keys for different purposes (e.g., databases encrypted with one key, backups encrypted with another).
  • Encryptionizer has an API set.
  • Whole Disk Encryption leaves data decrypted in System Cache, whereas with Encryptionizer, data in System Cache is encrypted.
  • There is no support for freeware Whole Disk Encryption. We have support plus a 24/7 hotline for off-hours production emergencies.
  • Whole Disk Encryption is generally suitable only for desktops/laptops. Encryptionizer is also for servers and is optimized for multi-processors/cores.
  • Encryptionizer can encrypt databases on CDs/DVDs, Flash drives, backups on tape, USB keys, etc.
  • Keys can expire with Encryptionizer so that encrypted files are no longer accessible after a specific date or number of days. (This can be appealing to Developers with distributable applications who which to create expiring versions for demos or time limited licenses.)