Database Encryption
Another important security feature of Domino is the capability to encrypt an entire database. As you may know, encryption is the process of using complex mathematical algorithms called keys to scramble data so that is it unintelligible to anyone who does not have the appropriate key. You can encrypt any local database to which you have Manager access by using the public key in your Notes ID.
There are three increasingly secure levels of encryption that you can apply to a local database:
Simple encryption— Simple encryption, in the words of Lotus, “provides protection against casual snooping.” It provides the fastest access to the database and enables the database to be compressed by disk compression utilities.
Medium encryption— Medium encryption strikes a balance between performance and security. Lotus recommends this option for most users.
Databases using Medium encryption cannot be compressed by disk compression utilities.
Strong encryption— Strong encryption should be used for the most sensitive information. Although this is the most secure level, it also exacts the most severe performance penalties. Databases encrypted with this option cannot be compressed by disk compression utilities.
 | Although it may sometimes make sense to encrypt highly confidential databases when they are stored on a mobile or shared computer, there are several downsides to doing so. First, you suffer a performance penalty when using encrypted databases. Second, because the private key needed to decrypt the database is stored in your Notes ID, you are the only person who can open it. Do not lose your ID! |
To encrypt a database, follow these steps:
1. | Select the database you want to encrypt and choose File, Database, Properties. |
2. | On the Basics tab, click the Encryption Settings button, which opens the Encryption dialog shown in Figure 10.6. |
3. | Choose an encryption option in the Locally Encrypt This Database Using field. |
4. | Optionally, click the For button to change the user ID used to encrypt the database. By default the current user's ID is used. Note that if you change the user ID, only the specified user can access the database. |
To remove encryption, follow these steps:
1. | Select the database and choose File, Database, Properties. |
2. | On the Basics tab, click the Encryption Settings button. |
3. | Click the Do Not Locally Encrypt this Database radio button. |
 | Database encryption can be removed only by the ID that originally encrypted the database. |