Add or Edit a Container Key File

Home > selected Organization > menu or right-click > Settings > Container Key Files > New Key File | Edit
Project > Settings drop-down > Organization Settings > Container Key Files > New Key File | Edit

Requires Organization - Container Key Files - Add/Edit Permissions

Users with the appropriate permissions can use Container Key files at the Organization-level settings to add two types of Container Key Files:

  • Lotus Notes ID files (.id) — These ID files enable processing of password-protected Lotus Notes NSF files or the encrypted items from unprotected NSF files.
  • Microsoft BitLocker Key files (.txt) — These Key files (text files with a 48-digit key) enable processing of Microsoft BitLocker-encrypted disk partitions.

In general, add Container Key files before import to help avoid reprocessing scenarios.

Adding the Container Key files after import means that you must rely on a reprocessing scenario, which begins by checking the Warning and Errors section of the Data Set Scan Report for Protected, Encrypted, or Partitions Encrypted entries.

How to Manage Container Key Files provides details about Lotus Notes ID files and MS BitLocker Key files and summarizes the steps involved in a reprocessing scenario.

A Lotus Notes ID file typically has an associated password that enables access to a password-protected NSF file. (Not all Lotus Notes ID files may require passwords.) Each Lotus Notes ID file and its password (if applicable) are validated when you add the file to the files list. Note that the ID file for a protected NSF file applies to all of its children. You can also add a Lotus Notes ID file to accommodate the situation in which the NSF file itself is unprotected but has items that are encrypted/protected. In this case, the ID file must apply to all children of a given NSF file.

An MS BitLocker Key file is a text file with a 48-digit key and a partition ID. When multiple partitions are BitLocker-encrypted, each partition will have its own Key file and password. You can open a BitLocker-encrypted partition using the Key file, and/or you can upload a password file with the password for the partition for the Known Passwords form of password-cracking during reprocessing. Password-cracking options are available from the Project settings, under Password Cracking).

Note: If you supply both the BitLocker Key file for an encrypted disk partition and its password (as part of password-cracking), the Digital Reef software uses whichever it finds first. If you want to supply the password for a BitLocker-encrypted partition as part of password-cracking, the Known Passwords mode is recommended instead of the more intensive modes. For some BitLocker files, you may have to perform a second reprocessing pass.

Container Key File Options

All of the following options apply when adding a Container Key file.

Note: When editing a key file, you can change only the Name.

! " # $ % & * + . / : ; < = > ? @ [ \ ] ^ { | } ~ “ ”

  • Type (required)Select the Key type, either Lotus Notes (.id) for a Lotus Notes ID file (the default) or MS BitLocker (.txt) for a BitLocker Key file.
  • Key File(required) – Click Browse to open a popup that enables you to browse and select the appropriate Key File based on your selected Key File type: either browse and select a Lotus Notes ID file (.id file format) or an MS BitLocker file (.txt file format).
  • Password (required for Lotus Notes ID files only)For a Lotus Notes ID file only, specify the password for the Container key file that you are uploading to the system. This field does not apply to an MS BitLocker Key file.
  • OK – As long as you have addressed all required fields, this option saves the new or modified Container Key file information. For a Lotus Notes ID file only, the password is validated. An error appears if the password is not valid.
  • Cancel – Cancel the addition or modification of a Container Key file.