Virtual TapeServer 6.04.03 Operations and Administration Guide

Using SecureVTS

SecureVTS is an optional Virtual TapeServer (VTS) software module that enables VTS to

encrypt data that is stored on virtual tape. SecureVTS encrypts data when storing it on a

virtual tape. Here is how SecureVTS affects tape operations:

• When an encrypted tape is mounted, the data that is written to the tape is encrypted. You

can also instruct SecureVTS to encrypt data that is already stored on a virtual tape if the

tape is not encrypted.

• When SecureVTS exports an encrypted virtual tape to a physical tape, it decrypts the

data before it is exported.

• When data is imported (restored) from a physical tape, the data is encrypted if the target

virtual tape is encrypted.

• When SecureVTS migrates an encrypted virtual tape to a physical tape (through a backup

management application), the data remains encrypted as it is migrated.

This chapter provides an overview of SecureVTS, including tape operation, upgrade, and

cluster implications. It also provides instructions for configuring SecureVTS and using the

feature to encrypt and decrypt data.

Note SecureVTS protects data at rest. It does not protect or secure the VTS server.

Overview of SecureVTS

When SecureVTS is enabled on a VTS server, the embedded key server can be configured to

generate keys for encrypting virtual tapes. SecureVTS uses symmetric key encryption to

secure data written to tape. This encryption is based on the Advanced Encryption Standard

(AES) and uses 256-bit keys provided by a random number generator. When a key is

generated, its key ID is stored with the encrypted virtual tape. The key is stored in a key

database on the server that generated it, and each key is encrypted multiple times before

being stored. When data on a virtual tape must be decrypted, VTS uses the key ID to retrieve

the key from the key database. Storing the key ID with the tape and the key in the database

ensures that the key will not be compromised and that it resides in a central, secure location

with all other keys.

The key database is backed up on the key server and on at least one other server to ensure

that a backup of the keys is always available in case the key server is damaged or destroyed.

The backup must complete successfully on the localhost and backup host before the keys are

available for use by SecureVTS. This ensures that keys are backed up before data is

encrypted.