DBDefence uses AES-128 encryption to completely encrypt your database and log files. As standard, It uses highly optimized AES encryption routines. If your environment requires a FIPS 140-2 validated encryption module please contact us.

You can encrypt a database by using the DBDefence GUI or the command line tool. Both will produce the same result, however the GUI version runs several simple tests to ensure the database integrity and protection after encryption.

After encryption DBDefence will deny any attempted access to the database until the correct password is supplied. An encrypted database contains a symmetric key called dbdx. You will need to open that key with an SQL Server statement:

OPEN SYMMETRIC KEY dbdx DECRYPTION BY PASSWORD='<password>'.

If you drop that key from the string you will not be able to access the database. However, you do also have the option to decrypt the database and re-encrypt it. To decrypt the database you must know the password and have the corresponding key files. Read more about accessing a protected database.

Any backups created from a protected database are also encrypted. There are several things you need to know about the backup and restore process. Please read the Backup section for more information.

For each encrypted file DBDefence creates a key file with extension .dbd_key If you copy the database to another server you must copy corresponding key files too. Without those files it will be impossible to attach them to an SQL Server. If your distribute the database you need to distribute all key files as well. Read more about distribution

Free Version can be used in commercial projects freely. However, the Free Version has a limited database size of up to 77Mb. Read more about obtaining the full version.