This is encryption that takes place at the server machine as opposed to the client machine, as in NEP. With server-side encryption, the encryption drivers only need to reside on the server machine where the database process resides. Encryptionizer for SQL Server and for SQL Express is a server-side encryption tool.
Transparent database encryption and column encryption are actually two completely different methods of providing data encryption. Each has its advantages and limitations. For more information, please follow this link: Differences between transparent database and column encryption.
It seems counter-intuitive. Why would performance when working with a wholly encrypted database be better than performance when working with just a few columns? That is because NetLib’s patented Transparent Database Encryption processing actually takes place between the SQL Server and file system layers. Since Transparent Database Encryption works at such a low level, it… Read More
Most encryption security tools are not designed to work with SQL Server or SQL Express. The few that do require a large amount of ongoing administration. Some are considerably more expensive. Generic encryption tools, such as those that encrypt an entire directory or drive, are usually suitable for small standalone systems and require the user… Read More
In many cases, yes. This is often important to developers distributing an MSSQL Server or SQL Express-based application. They want to ensure that the end user can only access the database through the supplied application, not through SQL Management Studio or a query window. Just changing the SA password is not enough! The end user… Read More
Only the person who originally encrypts the database needs to know the key(s). This is usually the DBA or an administrator of some kind. Our “Split Knowledge Protocol” allows you to split a key among two or more people so that no single person knows the entire key. One optional feature allows you to ask… Read More
Data keys are stored with a variety of methods, and we are constantly adding new methods. The primary methods are: Keys can be stored in a strongly encrypted file (called a profile) on the local drive. Keys can be stored in a profile on a floppy disk, CD, or USB key. The authorized user must… Read More
We work on all editions of SQL from SQL Express to Enterprise, and SQL Server Versions: SQL Server 2000 (SP4) SQL 2005 (SP4) SQL 2008 (SP4) SQL 2008 R2 (SP3) SQL 2012 (SP2) SQL Server 2014 (SP1) Encryptionizer is tested with major released service packs for SQL Server. It is not specifically tested with Hotfixes… Read More
Yes! Encryptionizer for SQL Server works with clustered servers, both active/active and active/passive on Windows 2003 and up. Encryptionizer must be installed independently on each server. The User Guide includes detailed instructions for installation on a cluster.
Encryptionizer has a feature whereby two different people to are able to enter a portion of the key without allowing each to see the other portion.