Search the Knowledge Base, browse frequently asked questions, or submit a support request. Existing customers with a valid license receive direct access to our technical team.
Browse our full library of setup guides, how-to articles, configuration walkthroughs, and technical documentation.
Browse Knowledge Base →Find answers to the most common questions about Encryptionizer — deployment, encryption methods, compliance, key management, and more.
View FAQs Below ↓Can't find what you need? Submit a support request and our technical team will get back to you. Existing customers receive priority response.
Submit a Request ↓Organized by topic. Click any question to expand the answer.
Server-side encryption takes place at the server machine as opposed to the client machine. 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 SQL Express is a server-side encryption tool.
Transparent database encryption and column encryption are two completely different methods of providing data encryption. Each has its advantages and limitations. Transparent Database Encryption encrypts the entire database file, while Column Encryption encrypts specific columns within a database. Contact us for a detailed comparison.
NetLib’s patented Transparent Database Encryption processing takes place between the SQL Server and file system layers — a very low level that is extremely efficient. On a multi-processor machine, clients have noted virtually no impact on performance. Column encryption works within SQL Server itself, with a reported 5–6% performance impact per encrypted column. As a general rule, if more than 10% of the database needs to be encrypted, Transparent Database Encryption is recommended.
Most encryption tools are not designed to work with SQL Server or SQL Express. The few that do require significant ongoing administration and are considerably more expensive. Generic tools that encrypt entire directories require the user to enter a key anytime the directory is accessed. Encryptionizer is designed for high-volume, multi-processor servers and does not require the user to enter or even know the key.
In many cases, yes. This is important to developers distributing a SQL Server or SQL Express-based application. Without protection, end users can copy the database to a fresh install, restore a backup to a different instance, or overwrite the Master database. If your application uses a dedicated SQL instance, it is possible to lock out Sysadmins from accessing encrypted data. Contact us for more information.
Encryptionizer is transparent to any application or databases on the Windows platform – device, desktop, server or cloud. It works on every operating system from Windows Server 2008-R2 through 2025, Win 7 through Win 11. NetLib Security has a version specifically tuned to SQL Server, supporting every version and edition from 2005 through 2025, from Enterprise down to SQL Express and LocalDB. Encryptionizer can also protect other database management systems such as PostgreSQL, MySQL, MongoDB, MariaDB, Visual FoxPro and more. Although some encryption solutions focus only on database systems, Encryptionizer also supports protection of website data, and the transparent encryption of data types such as documents, images, and other files, including FileStreams and FileTables.
Start by using the included User Interface (or Command-Line Interface) to encrypt a database with a high-level algorithm, selected key length (up to 256-bit), and a passphrase. Then use another utility to secure your SQL Server, MySQL, or other application with the Encryptionizer engine. This allows only that instance to access your encrypted databases. Data is decrypted on-the-fly in the server’s RAM — never on disk. All new data is encrypted when written back to disk. It is completely transparent to your application. No code changes needed.
Transparent Database Encryption encrypts an entire database file or set of files. The encrypted database cannot be accessed unless the database engine, such as SQL Server or other application, is secured with the same key. This prevents anyone from stealing the database files and attaching elsewhere. It works with no new engineering, low maintenance and little to no impact on performance — the same way across SQL Server, MySQL, PostgreSQL, MongoDB and other Windows-based database systems.
Encryptionizer can automatically encrypt a database as a backup is being created — adding a layer of encryption that backup operators do not need to know the key for. If someone takes the backup media and tries to restore your database to a different machine or instance, it will appear as an unreadable backup. This prevents backup media theft from exposing your data.
The simplest method is through the Column Encryption Manager (Col-E Manager) point-and-click interface. First, create the server key by choosing a strong algorithm, key length up to 256-bit, and a passphrase. Then use the Col-E Manager to select which columns to encrypt. Alternatively, use the included APIs to perform encryption and decryption activities directly within your application.
When you select columns in the Col-E Manager, it encrypts the column data on disk and creates views controlling access to that data. INSTEAD OF triggers are created to ensure data is written back encrypted. You use the Manage Permissions function to determine which users have read access to the decrypted data. A transparent encryption feature allows the process to be transparent to existing applications in most cases.
Virtually every new privacy and data protection regulation requires an encryption component. Encryptionizer provides a simple solution to encrypt stored data transparently with no impact on end users and low total cost of ownership — directly addressing the most common regulatory encryption requirements.
Encryptionizer protects data at the Database and Application level. Volume or Disk level encryption is typically controlled by the computer administrator. Database and Application level encryption puts control in the hands of the data owner — a meaningful distinction for compliance and separation of duties.
NetLib Security’s Encryptionizer is built with intuitive interfaces which guide you through the process. It does not require training, and you can typically implement it in less than an hour. And there should be no impact whatsoever on end-users. It is important, however, to understand how the software works which is why we offer a Free Evaluation of our product, along with detailed documentation. We want our customers to see how easy the product is to use, and to make sure we are the right solution for them in their own environment.
Encryptionizer provides transparent, system-level encryption for Visual FoxPro databases, automatically encrypting files such as DBF, CDX, and FPT without requiring any changes to application code. In contrast, libraries like VFPEncrypt.ffl, _Cryptor, or _Crypt.vcx perform code-level encryption, meaning developers must explicitly encrypt and decrypt data within their programs, typically protecting only specific fields or strings rather than the entire database. As a result, Encryptionizer offers broader protection for database files at rest, prevents copied DBFs from being read outside the application, and simplifies security implementation compared to manual encryption libraries.
Fields marked with * are required. Existing customers with a valid license receive priority response within 1 business day.