Dell PowerVault TL4000 Dell PowerVault ML6000 Encryption Key Manager User's - Page 113

Appendix C. Frequently Asked Questions

Can some combination of application-based key management and

library-managed encryption be used?

No. When application-managed encryption is used, the encryption is

transparent at the library layers. Likewise, when library-managed encryption is

used, the process is transparent at the other layers. Each method of encryption

management is exclusive of the others. For library-managed encryption, the

applications need not be changed in any way.

Must the Encryption Key Manager be installed and running on every system

that might generate a request to encrypt or decrypt a tape?

With library-managed encryption, the system from which the tape drive write

request originates need NOT be the system on which the Encryption Key

Manager is running. Furthermore, an instance of Encryption Key Manager

need NOT be running on every system from which an encrypting tape drive is

accessed.

If I include the

″

drive.acceptUnknownDrives = True

″

parameter, should I still

include the

″

config.drivetable.file.url = FILE:/filename

″

parameter in the

configuration file?

config.drivetable.file.url

must always be specified. It is where the drive

information will be. If you set

drive.acceptUnknownDrives = True

you also

should specify the

drive.default.alias1

and

drive.default.alias2

variables

to the correct certificate alias/key label.

Is FILE:/filename the correct syntax for the

config.drivetable.file.url

property? FILE:///filename appears in the sample file, and FILE:../ in the

description.

The examples are correct. This is a URL specification and is not what people

normally expect for a directory structure specification

Must I use forward or backward slashes when specifying fully-qualified paths

in the KeyManagerConfig.properties file for an instance of Encryption Key

Manager running on Windows?

Because KeyManagerConfig.properties is a Java properties file, only forward

slashes are recognized in pathnames, even in Windows. If you use back slashes

in the KeyManagerConfig.properties file, errors will occur.

Does the Encryption Key Manager perform any Certificate Revocation List (CRL)

checking?

No, the Encryption Key Manager does not perform any CRL checking

What happens when the certificate being used to encrypt the tapes expires? Will

the Encryption Key Manager read previously encrypted tapes?

It does not matter to Encryption Key Manager if the certificate has expired. It

will continue to honor these certificates and read previously encrypted tapes.

However the expired certificate must remain in the keystore in order for

previously encrypted tapes to be read or appended.

Will the Encryption Key Manager require that a certificate be renamed on

renewal?

The Encryption Key Manager is configured by default to honor new key

requests with expired certificates. When the Encryption Key Manager is

configured this way certificate renewal is not required. If this function is

disabled and this private key/certificate pair must still be used for new key

C-1

Section	Page
Contents	3
Figures	5
Tables	7
Preface	9
About this Book	9
Who Should Read this Book	9
Conventions and Terminology Used in this Book	9
Attention Notice	9
Related Publications	10
Linux Information	10
Red Hat Information	10
SuSE Information	10
Microsoft Windows Information	10
Online Support	10
Read this First	11
Contacting Dell	11
Chapter 1. Tape Encryption Overview	13
Components	13
Managing Encryption	14
Application-Managed Tape Encryption	16
Library-Managed Tape Encryption	17
About Encryption Keys	17
Chapter 2. Planning Your Encryption Key Manager Environment	21
Encryption Setup Tasks at a Glance	21
Encryption Key Manager Setup Tasks	21
Planning for Library-Managed Tape Encryption	21
Hardware and Software Requirements	22
Linux Solution Components	22
Windows Solution Components	23
Keystore Considerations	23
The JCEKS Keystore	23
Encryption Keys and the LTO 4 and LTO 5 Tape Drives	24
Backing up Keystore Data	25
Multiple Key Managers for Redundancy	27
Encryption Key Manager Server Configurations	27
Single-Server Configuration	27
Two-Server Configurations	28
Disaster Recovery Site Considerations	29
Considerations for Sharing Encrypted Tapes Offsite	29
Federal Information Processing Standard 140-2 Considerations	30
Chapter 3. Installing the Encryption Key Manager and Keystores	31
Downloading the Latest Version Key Manager ISO Image	31
Installing the Encryption Key Manager on Linux	31
Installing the Encryption Key Manager on Windows	32
Using the GUI to Create a Configuration File, Keystore, and Certificates	35
Generating Keys and Aliases for Encryption on LTO 4 and LTO 5	39
Creating and Managing Key Groups	44
Chapter 4. Configuring the Encryption Key Manager	51
Using the GUI to Configure the Encryption Key Manager	51
Configuration Strategies	51
Automatically Update Tape Drive Table	51
Synchronizing Data Between Two Key Manager Servers	52
Configuration Basics	53
Chapter 5. Administering the Encryption Key Manager	57
Starting, Refreshing, and Stopping the Key Manager Server	57
The Command Line Interface Client	61
CLI Commands	63
Chapter 6. Problem Determination	71
Check These Important Files for Encryption Key Manager Server Problems	71
Debugging Communication Problems Between the CLI Client and the EKM Server	72
Debugging Key Manager Server Problems	72
Encryption Key Manager-Reported Errors	75
Messages	79
Config File not Specified	79
Failed to Add Drive	80
Failed to Archive the Log File	80
Failed to Delete the Configuration	80
Failed to Delete the Drive Entry	81
Failed to Import	81
Failed to Modify the Configuration	81
File Name Cannot be Null	81
File Size Limit Cannot be a Negative Number	82
No Data to be Synchronized	82
Invalid Input	82
Invalid SSL Port Number in Configuration File	83
Invalid TCP Port Number in Configuration File	83
Must Specify SSL Port Number in Configuration File	83
Must Specify TCP Port Number in Configuration File	84
Server Failed to Start	84
Sync Failed	84
The Specified Audit Log File is Read Only	85
Unable to Load the Admin Keystore	85
Unable to load the keystore	86
Unable to Load the Transport Keystore	86
Unsupported Action	86
Chapter 7. Audit Records	89
Audit Overview	89
Audit Configuration Parameters	89
Audit.event.types	89
Audit.event.outcome	90
Audit.eventQueue.max	90
Audit.handler.file.directory	90
Audit.handler.file.size	91
Audit.handler.file.name	91
Audit.handler.file.multithreads	92
Audit.handler.file.threadlifespan	92
Audit Record Format	92
Audit Points in the Encryption Key Manager	93
Audit Record Attributes	93
Audited Events	95
Chapter 8. Using Metadata	97
Appendix A. Sample Files	101
Sample startup daemon script	101
Linux Platforms	101
Sample Configuration Files	101
Appendix B. Encryption Key Manager Configuration Properties Files	103
Encryption Key Manager Server Configuration Properties File	103
CLI Client Configuration Properties File	111
Appendix C. Frequently Asked Questions	113
Notices	115
Trademarks	115
Glossary	117
Index	119
A	119
C	119
D	119
E	119
F	119
G	119
H	119
I	119
J	119
K	119
L	119
M	119
N	119
P	119
R	120
S	120
T	120
W	120

Dell PowerVault TL4000 Dell PowerVault ML6000 Encryption Key Manager User's - Page 113

Appendix C. Frequently Asked Questions

Page 113 highlights