Capítulo 2 Una mirada a las vanguardias en América Latina
2.1.1 Modernismo: El caso de José Juan Tablada, (1900 1945)
Key management tasks include: • Creating a key
• Activating a key
• Deactivating a key
• Managing an encryption key file
10.1.1 Creating a Key
When you go to the [Home] > [Database Encryption] page, either the Activate Encryption Key or Deac- tivate Encryption Key link is available — the available choice is in blue and has an arrow pointing to it. If Activate Encryption Key is available, then either your instance has no encryption key or its key has not been activated (that is, loaded into memory from disk).
To create a key:
1. Click on Create Encryption Key. This displays the Create Encryption Key page ([Home] > [Database Encryption] > [Create Encryption Key]).
2. On the Create Encryption Key page, enter values in the following fields:
• Encryption Key Path and File Name — The name of the file where the encryption key is stored, along with administrator information for the key; this can be an absolute or relative path name.
If you enter an absolute file name, the key file is placed in the specified directory on the specified drive; if you enter a relative file name, the key file is placed in the specified file in the mgr directory below the Caché installation directory
(<cache-install-dir>/mgr/<specified-name>). Also, no file suffix is appended to the file name, so that the file MyKey is saved simply with that file name. You can also use the Browse button to the right of this field to choose a directory and file name for the key file.
WARNING!
Any key stored in <cache-install-dir>/Mgr/Temp is deleted when Caché next reboots — never store a key in <cache-install-dir>/Mgr/Temp.• Administrator Name — The name of an administrator who can activate the key (make it available for use). There must be at least one administrator.
Because the database encryption functionality exists independent of Caché Advanced Security, this name need not match any user names that are part of Caché Advanced Security. By default, the initial administrator name value is the current username.
130 Caché Security Administration Guide Database Encryption
• Password — A password for this user. Because the database encryption functionality exists independent of Caché Advanced Security, this password need not match the password that a user has for Caché Advanced Security. Note that this password is not stored anywhere on disk; it is the responsibility of the administrator to ensure that this information is not lost. InterSystems suggests that this password follow the administrator password strength guidelines. • Confirm Password — The password for this user entered again to confirm its value.
Click the Save button to save the key file to disk. This creates a key file where each copy of the database-encryption key is encrypted using an administrator’s key-encryption key (KEK). Once you save the key file, you can move it anywhere you choose — this is why Caché cannot track the locations of key file.
Note: Saving a new key file to disk also activates it.
3. Follow the instructions in the section “Protection from Accidental Loss of Access to Encrypted Data” to create and store a backup copy of the key file.
4. Refer to the section “Protection from Unauthorized Access to Encrypted Data” for details about measures to prevent currently or formerly privileged users from gaining unsanctioned access to encrypted data.
WARNING!
Each time you create a database-encryption key, it is a unique key that cannot be re-created. Using the same administrator and password for a new key still results in the creation of a different and unique key. If an unactivated key is lost and cannot be recovered, the encrypted database that it protected will be unreadable and its data will be permanently lost.Caché database encryption uses 128-bit keys by default. If you so choose, the size of keys for a Caché instance can be changed to other valid values. Contact the InterSystems Worldwide Response Center
if you want to use one of these alternate, valid key lengths.
10.1.2 Activating a Key
When you create a key, this process also activates it. However, if you have deactivated a key, then you need to activate it prior to performing any operations related to encrypted databases. The procedure is:
1. On the System Management Portal’s [Home] > [Database Encryption] page, select Activate Encryption Key. This displays the Activate Encryption Key page ([Home] > [Database Encryption] > [Activate Encryption Key]). (If the Activate Encryption Key choice is not available, this is because the instance’s key is already activated.)
2. On this page, enter values for the following fields:
• Encryption Key Path and File Name — The name of the file where the encryption key is stored. If you enter an absolute file name, Caché looks for the key file in the specified directory on the specified drive; if you enter a relative file name, Caché looks for the key file in the mgr
directory below the Caché installation directory (<cache-install-dir>/mgr/<specified-name>). • Administrator Name — The name of an administrator for this key, specified either when the
key was created or edited.
• Encryption Password — The password specified for the named administrator.
Then click the Activate button.
If Deactivate Encryption Key link is now active, then the key has been activated.
10.1.3 Deactivating a Key
To do this:
1. On the System Management Portal’s [Home] > [Database Encryption] page, select Deactivate Encryption Key. This displays the Deactivate Encryption confirmation page.
2. To deactivate the key, click the Perform Action Now button. When the [Home] > [Database Encryption] page appears again, the Deactivate Encryption Key link should no longer be available.
Caché does not allow you deactivate a key under the following circumstances: • There is a currently-mounted encrypted database.
• The CACHETEMP database is encrypted. • Encrypted journal files are in use.
The error message may include information that encrypted databases are mounted or that keys are being activated at startup. To deactivate the key, each condition requires a different action:
• For any encrypted database except CACHETEMP, dismount the database; you can then deactivate the key.
• For CACHETEMP, specify that the CACHETEMP database is not to be encrypted and then restart Caché.
This is part of the Encryption Settings page ([Home] > [Database Encryption] > [Encryption Settings]). You can either choose to not activate a database encryption key at startup (in which case the option to encrypt CACHETEMP is not available) or you can choose interactive or unattended database encryption key activation at startup (in which cases the choice whether or not to encrypt CACHETEMP becomes available — choose “No” ).
• For encrypted journal files, ensure that no encrypted journal file is required for recovery. This is described in the section “Encrypted Journal Files and Configuring Startup without Key Activation.”
132 Caché Security Administration Guide Database Encryption
10.1.4 Managing an Encryption Key File
This section describes two activities related to database-encryption key files: • Adding and removing administrators
• Managing key files with multinode technologies
10.1.4.1 Adding and Removing Administrators
Two of the principal key management tasks are adding administrators to or removing administrators from a key file. The procedure for these is:
1. Go to the System Management Portal’s [Home] > [Database Encryption] page. 2. Make sure there is an activated key — you cannot edit a key unless one is activated.
3. Select Manage Key File. This displays the Manage Key File page ([Home] > [Database Encryption] > [Manage Key File]).
4. On this page, in the Encryption Key Path and File Name field, enter the location of the key file to edit and click Save immediately below the field where you entered the name. You can also use the Browse button to look for the key on disk. Selecting a key causes a table of administrators to appear in the lower part of the page, with a label that reads “Administrators Defined in Key File [<key-file-name>].” Administrator names are listed in all capital letters, regardless of how they were defined.
5. In the table of administrators, either click the Add button to add a new administrator or click the Delete link next to an administrator to remove that administrator for the key.
Clicking Delete displays a confirmation page for the action.
Clicking Add displays a page that accepts an administrator name, a password, and a password confirmation. Because the database encryption functionality exists independent of Caché Advanced Security, the administrator name need not match any user names that are part of Caché Advanced Security; similarly, the password need not match the password that a user has for Caché Advanced Security.
InterSystems suggests that this password follow the administrator password strength guidelines.
Information regarding each new administrator for a key is added to the key file. Once this is done, you may wish to copy the key, making sure that each copy is in a secure location. However, if copies of the key are made and later on, as an administrative function, a new administrator is added, only the currently loaded key will then be up to date. All other copies will need to be replaced with this key as they will be out of sync with the current key. Further, InterSystems strongly recommends that you create multiple administrators for each key, one of which has the name and password written down and stored in a secure location, such as in a fireproof safe.
Note: When you add a new administrator to a key file, the encryption password is permanently associated with the entry for the administrator name created in the file. Once assigned, passwords cannot be changed. If you wish to assign a new password, delete the entry in the key file for that administrator name and then create a new entry with the same name and a new password.
10.1.4.2 Managing Keys and Key Files with Multinode Technologies
If you are using encrypted databases or journal files with any Caché multinode technology (such as clusters), then all nodes must share a single database-encryption key.
There are two ways to do this:
• All the nodes share a single key file, which is located on one node.
In this case, changes to the single copy of the key file are then visible to all nodes. However, if the node holding the key file becomes unavailable to the other nodes, then any attempt to read the key from the key file fails; this can prevent instances of Caché from restarting properly.
• Each node has its own copy of the key file.
Here, you propagate copies of the key file (containing the same key) to all the other nodes. This increases the burden of administering the key file (which is typically small), but ensures that each instance of Caché always has a key available at startup.
Important: Whether there are single or multiple key files, the database-encryption key itself is the same for all instances.
Using a Single Key File
1. Create a database-encryption key on one node. For more information on this procedure, see the section “Creating a Key.”
2. Secure this key according to the instructions in the section “Protection from Accidental Loss of Access to Encrypted Data.”
CAUTION: Failure to take these precautions can result in a situation where the encrypted database will be unreadable and permanently lost.
3. Configure each instance of Caché for unattended startup and provide Caché with the path to the key file. For more information on this procedure, see the section “Configuring Startup with Unattended Key Activation.”
Since all the Caché instances use the same key, they are able to read data encrypted by each other. Any changes to the key file are visible to all instances.
134 Caché Security Administration Guide Database Encryption
Important: Refer to the section “Protection from Unauthorized Access to Encrypted Data” for details about measures to prevent currently or formerly privileged users from gaining unsanctioned access to encrypted data.
Using Multiple Key Files
If you choose to use multiple copies of the key file:
1. Create a database-encryption key on one node. For more information on this procedure, see the section “Creating a Key.”
2. Secure this key according to the instructions in the section “Protection from Accidental Loss of Access to Encrypted Data.”
CAUTION: Failure to take these precautions can result in a situation where the encrypted database will be unreadable and permanently lost.
3. Make a copy of the key file for each node. 4. On each node:
a. Get a copy of the key and put it in a secure and stable location on that machine.
b. Configure each instance of Caché for unattended startup. For more information on this proce- dure, see the section “Configuring Startup with Unattended Key Activation.”
Since each key file contains a copy of the same key, all the Caché instances are able to read data encrypted by each other. Since each Caché instance has a key file on its machine, the key file should always be available for a Caché re-start. If there are any changes to the key file (such as adding or removing administrators), you must propagate new copies of the key file to each machine and recon- figure each instance of Caché for unattended startup using the new copy of the key file (even if that file is in the same location as the old file).
Important: Refer to the section “Protection from Unauthorized Access to Encrypted Data” for details about measures to prevent currently or formerly privileged users from gaining unsanctioned access to encrypted data.