Overview   Technical   FAQ   APIs

Encryptionizer encryption software delivers client-side file encryption and field encryption or Win32 applications and desktop databases. It is an additional layer of security on top of Windows security and your application's security. It can secure data on servers, desktops, laptops, backup media, CDs, DVDs, and in transit.  Encryptionizer works with most Win32 platforms including Visual Basic (VB), Visual FoxPro (VFP), Access, Delphi, IBM VisualAge and C/C++, just to name a few. It is easy to include with your application. (PDF data sheet)

Encryptionizer encryption software delivers two types of protection: Automatic Whole File Encryption, and optional field encryption APIs.

As any developer or administrator knows, stopping someone from running an application is only part of the story. If someone can get access to the files or databases, they can see anything they want. Most desktop databases and files, no matter how complicated they seem, can be opened with a variety of tools like Excel, Access, or even a simple text editor. For example, if you have an application that uses DBFs, try opening one of them with Notepad and you'll be amazed how much someone can see. 

Whole File Encryption has one simple purpose - to make databases, files, backups, etc., unusable if they are stolen, copied, downloaded, lost, or accessed outside of the application. It provides completely transparent, on-the-fly file encryption making it perfect for use with desktop databases or applications that distribute digital content. Whole file encryption is a two-step process:

• Encrypt the desired databases and/of files with the included utility or APIs.

• Secure your application with Encryptionizer or with the optional APIs.

Once that is done, no one will be able to use the encrypted databases or files except via your application. If you have  encrypted backups, no one will be able to restore the encrypted backups anywhere else.

Whole File Encryption is extremely easy to use, is almost maintenance-free, requires no user intervention, and can usually be deployed in a couple of hours, using the included utilities. You can encrypt almost any kind of file including DBF, MDB, DOC, TXT, etc. In many cases, you will not need to change the source code which makes it perfect for protecting existing applications where the source code is not available.

If you are a Visual FoxPro or MS Access developer, you can even use Encryptionizer to protect your source code! 

The APIs can be used in combination with (or depending on your requirements, instead of) whole file encryption. They allow programatical access to the "Encryptionizer engine." They allow a greater level of flexibility and "granularity" than whole database encryption. 

The main purpose of the APIs is to protect certain columns, fields, and/or records from authorized users who must have access to other columns in a table. For example, you might want to give only  certain users the ability to see a column containing credit card numbers. You can even use them to encrypt SQL Server columns.

Besides column encryption, there are various APIs for encrypting and decrypting files. These are useful if you are planning to distribute encrypted databases, files, or other digital content to workstations, laptops, or other servers (e.g., connected by LAN, over the internet, or via CD.).

Overview   Technical   FAQ   APIs