Veritas NetBackup™ Appliance Security Guide
- About the NetBackup appliance Security Guide
- User authentication
- About user authentication on the NetBackup appliance
- About configuring user authentication
- About authenticating LDAP users
- About authenticating Active Directory users
- About authentication using smart cards and digital certificates
- About authenticating Kerberos-NIS users
- About the appliance login banner
- About user name and password specifications
- User authorization
- Intrusion prevention and intrusion detection systems
- About Symantec Data Center Security on the NetBackup appliance
- About the NetBackup appliance intrusion prevention system
- About the NetBackup appliance intrusion detection system
- Reviewing SDCS events on the NetBackup appliance
- Running SDCS in unmanaged mode on the NetBackup appliance
- Running SDCS in managed mode on the NetBackup appliance
- Log files
- Operating system security
- Data security
- Web security
- Network security
- Call Home security
- Remote Management Module (RMM) security
- STIG and FIPS conformance
- Appendix A. Security release content
- Index
KMS support
The NetBackup appliance supports encryption managed by NetBackup Key Management Service (KMS) which is integrated with NetBackup Enterprise Server 7.1. KMS is supported on primary and media server appliances. Regenerating the data encryption key is the only supported method of recovering KMS on an appliance primary server.
The following describes the KMS key features:
Does not require an additional license.
Is a primary server-based symmetric key management service.
Can be administered as a primary 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).
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 Primary 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 primary server, you must log in as a NetBackupCLI user,
Note:
If required, you can create a new NetBackupCLI user for configuring and enabling KMS. For more information about the NetBackupCLI user, See About the NetBackupCLI user role.
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 primary 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 primary server, you can enable KMS encryption for MSDP on all of the media servers that are associated with the primary server.
Note:
If required, you can create a new NetBackupCLI user for configuring and enabling KMS. For more information about the NetBackupCLI user, See About the NetBackupCLI user role.
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@myappliance:~> pdcfg --write=/msdp/data/dp1/pdvol/etc/puredisk/contentrouter.cfg --section=KMSOptions --option=KMSType --value=0
nbcli@myappliance:~> pdcfg --write=/msdp/data/dp1/pdvol/etc/puredisk/contentrouter.cfg --section=KMSOptions --option=KMSServerName --value=<primary server hostname>
nbcli@myappliance:~> pdcfg --write=/msdp/data/dp1/pdvol/etc/puredisk/contentrouter.cfg --section=KMSOptions --option=KMSKeyGroupName --value=msdp
nbcli@myappliance:~> pdcfg --write=/msdp/data/dp1/pdvol/etc/puredisk/contentrouter.cfg --section=KMSOptions --option=KeyName --value=<KMS KeyName>
nbcli@myappliance:~> 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 primary server
- Identify yourself to the system by logging on to the NetBackup web application. Run the following command:
bpnbat -login -loginType WEB
Authentication Broker: ApplianceHostname
Authentication Port: 0
Authentication Type: unixpwd
LoginName: Username
Password: Password
- Ensure that the KMS is registered with NetBackup web service.
nbkmscmd -discoverNbkms
- 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