fbpx
FAQ

Can I use Encryptionizer to protect a database from the DBA?

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

Who needs to know the encryption key(s)?

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

Where are the data keys stored?

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

What editions of SQL Server do you support?

We work on all editions of SQL server from SQL Express to Enterprise. Encryptionizer is tested with major released service packs for SQL Server. It is not specifically tested with Hotfixes or Cumulative Updates. If you must apply a Hotfix or Cumulative Update, we recommend as Microsoft does to test in a test or development… Read More

Does Encryptionizer work on clustered servers?

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.

Can I split keys for added security?

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.

What documentation is included?

All documentation is included in electronic form. A Tutorial Guide will give you a quick overview to getting Encryptionizer up and running quickly with the most common scenarios. A more detailed User Guide is provided with detailed explanations of all features available. The Developer Version for Application Developers, ISVs and OEMs distributing Encryptionizer bundled with… Read More

What encryption algorithms and key lengths do you use?

Encryptionizer is standardized on the AES algorithm. Depending on use, we have several formulations of the AES algorithm for special purposes.  Each has been validated by NIST for the FIPS 140-2 standard. Key Lengths: 128 bit (16 bytes) 256 bit (32 bytes) Modes: CBC: For performance reasons, recommended for structured files, such as SQL Server… Read More

Can I bundle Encryptionizer with my application?

Yes! With the distribution license you can include transparent data encryption and/or column encryption in your distributed application. Use it to protect your own intellectual property, or enable your users to protect the data they enter into your application. We include instructions on how to build the installation scripts. Even if you are distributing Encryptionizer throughout… Read More

Can I use Encryptionizer to become compliant with HIPAA, PCIDSS, etc?

While using Encryptionizer alone will not make you immediately compliant, Encryptionizer can be used as your compliance strategy. NetLib clients use Encryptionizer as part of the overall plan for HIPAA compliance, PCIDSS, FIPS 140-2

Top