NetLib Encryptionizer

NetLib Encryptionizer for MSDE

NetLib Encryptionizer DE (Desktop Engine)

Automatic Whole Database Encryption
The purpose of whole database encryption is to make a database unusable if it is stolen, copied, down­loaded, lost, or otherwise improperly accessed. It is fast, unobtrusive, requires no programming, no administration, and can usually be deployed in a couple of hours or less. Whole database encryption uses completely on-the-fly, dynamic encryption and decryption. Data is never decrypted on disk, only in memory as requested by SQL Server. In addition, data is automatically encrypted before being written back to disk.

Column Encryption APIs
Also available are optional column encryption APIs. Their main purpose is to protect specific columns from users/groups who normally need access to the underlying table. A typical example is allowing all users to browse the customer table, but only certain users to decrypt the credit card column. Column encryption APIs are extremely easy to use in SQL 2000. They can be used anywhere built-in SQL functions can be used, including views, triggers, procedures, user defined functions, jobs, in-line SQL commands, etc. (In SQL 7, APIs can be used in triggers, procedures and jobs, but not in views or in-line SQL commands.)

In addition to column encryption, there are APIs for encrypting and decrypting simple files. For example, a log file can be encrypted before it is attached and sent with xp_sendmail.

Scalability
Encryptionizer is available for databases at various levels (SQL Server at the server level, MSDE and other desktop databases at the workstation level). All versions of Encryptionizer are interoperable. This allows you to secure data all the way from the primary server down to the desktop/laptop. For example, a mobile sales-force might have portions of a database replicated on a laptop that is later synchronized with a database on the server. Databases can even be securely distributed on CD/DVD or the Internet. Encryptionizer can easily be bundled into an application. Developers can protect their own intellectual property (in many cases you can even protect against the sysadmin), while enterprise users can create their own customized installation scripts for easy, enterprise-wide deployment