Veritas NetBackup™ Appliance Security Guide
- About the NetBackup appliance Security Guide
- User authentication
- User authorization
- Intrusion prevention and intrusion detection systems
- Log files
- Operating system security
- Data security
- Web security
- Network security
- Call Home security
- Remote Management Module (RMM) I security
- STIG and FIPS conformance
- Appendix A. Security release content
KMS support
The NetBackup appliance supports encryption managed by NetBackup Key Management Service (KMS) which is integrated with NetBackup Enterprise Server 7.1. With appliance versions 2.6 and later, KMS is supported on master and media server appliances. Regenerating the data encryption key is the only supported method of recovering KMS on an appliance master server.
The following describes the KMS key features:
Does not require an additional license.
Is a master server-based symmetric key management service.
Can be administered as a master server with tape devices connected to it or to another NetBackup appliance.
Manages symmetric cryptography keys for tape drives that conform to the T10 standard (such as LTO4 or LTO5).
Designed to use volume pool-based tape encryption.
Can be used with tape hardware that has built-in hardware encryption capability.
Can be managed by a NetBackup CLI administrator using the NetBackup Appliance Shell Menu or the KMS Command Line Interface (CLI).
Note:
In appliance versions earlier than 2.6, KMS is only supported when the appliance is configured as a media server. A non-appliance master server is required to administrate KMS with devices connected to an appliance.
The KMS generates keys from passcodes or auto-generates keys. Table: KMS files lists the associated KMS files that hold the information about the keys.
Table: KMS files
KMS files | Description | Location |
---|---|---|
Key file or key database | This file is critical for KMS, as it contains the data encryption keys. |
|
Host Master Key | This file contains the encryption key that encrypts and protects the |
|
Key Protection Key | This encryption key encrypts and protects individual records in the |
|
To configure KMS on an appliance master server, you must log in as a NetBackupCLI user. For information about this user, refer to the following topic:
See About the NetBackupCLI user role.
To create a NetBackupCLI user, see the NetBackup Appliance Commands Reference Guide.
The following describes how to configure and enable KMS on an appliance.
To configure and enable KMS on an appliance
- Log in to the appliance master server as a NetBackupCLI user.
- Create an empty database using the nbkms command, as follows:
[nbcli@myappliance~]# nbkms -createemptydb
- Start nbkms. For example:
[nbcli@myappliance~]# nbkms
- Create a Key group. For example:
[nbcli@myappliance~]# nbkmsutil -createkg -kgname KMSKeyGroupName
- Create an active key. For example:
[nbcli@myappliance~]# nbkmsutil -createkey -kgname KMSKeyGroupName -keyname KMS KeyName
After KMS has been configured and is running on the master server, you can enable KMS encryption for MSDP on all of the media servers that are associated with the master server.
To enable KMS encryption for MSDP on an appliance media server, you must log in as a NetBackupCLI user. For information about this user, refer to the following topic:
See About the NetBackupCLI user role.
To create a NetBackupCLI user, see the NetBackup Appliance Commands Reference Guide.
The following describes how to enable KMS encryption for MSDP on an appliance.
To enable KMS encryption for MSDP
- Log in to the appliance media server as a NetBackup CLI user.
- Change the following options in the order as shown:
nbcli@appesxdb03vm10:~> pdcfg --write=/msdp/data/dp1/pdvol/etc/puredisk/contentrouter.cfg --section=KMSOptions --option=KMSType --value=0
nbcli@appesxdb03vm10:~> pdcfg --write=/msdp/data/dp1/pdvol/etc/puredisk/contentrouter.cfg --section=KMSOptions --option=KMSServerName --value=<master server hostname>
nbcli@appesxdb03vm10:~> pdcfg --write=/msdp/data/dp1/pdvol/etc/puredisk/contentrouter.cfg --section=KMSOptions --option=KMSKeyGroupName --value=msdp
nbcli@appesxdb03vm10:~> pdcfg --write=/msdp/data/dp1/pdvol/etc/puredisk/contentrouter.cfg --section=KMSOptions --option=KeyName --value=<KMS KeyName>
nbcli@appesxdb03vm10:~> pdcfg --write=/msdp/data/dp1/pdvol/etc/puredisk/contentrouter.cfg --section=KMSOptions --option=KMSEnable --value=true
pdcfg --write= /msdp/data/dp1/pdvol/etc/puredisk/contentrouter.cfg --section=ContentRouter --option=ServerOptions --value=verify_so_references,fast,encrypt
Repeat this step on all media servers that are associated with the master server
- Stop and restart the NetBackup services with the following commands:
bp.kill_all
bp.start_all
- To verify that KMS encryption for MSDP is enabled on the media server, run a backup job on the server, then run the following command:
crcontrol --getmode