Veritas NetBackup™ Security and Encryption Guide
- Read this first for secure communications in NetBackup
- Communication failure scenarios
- Increasing NetBackup security
- Security deployment models
- Auditing NetBackup operations
- About audit events
- Section I. Identity and access management
- About identity and access management
- AD and LDAP domains
- API keys
- Auth.conf file
- Role-based access control (RBAC)
- Smart card or digital certificate
- Single Sign-On (SSO)
- Enhanced Auditing
- NetBackup Access Control Security (NBAC)
- Configuring NetBackup Access Control (NBAC)
- Configuring Access Control host properties for the master and media server
- Access Control host properties dialog for the client
- Troubleshooting Access Management
- Windows verification points
- UNIX verification points
- Verification points in a mixed environment with a UNIX master server
- Verification points in a mixed environment with a Windows master server
- About determining who can access NetBackup
- Viewing specific user permissions for NetBackup user groups
- Section II. Encryption of data in transit
- NetBackup CA and NetBackup certificates
- About the Security Management utilities
- About host management
- Adding shared or cluster mappings
- Allowing or disallowing automatic certificate reissue
- About global security settings
- About host name-based certificates
- About host ID-based certificates
- Using the Certificate Management utility to issue and deploy host ID-based certificates
- About NetBackup certificate deployment security levels
- Setting up trust with the master server (Certificate Authority)
- About reissuing host ID-based certificates
- About Token Management for host ID-based certificates
- About the host ID-based certificate revocation list
- About revoking host ID-based certificates
- Host ID-based certificate deployment in a clustered setup
- About deployment of a host ID-based certificate on a clustered NetBackup host
- Migrating NetBackup CA
- External CA and external certificates
- About external CA support in NetBackup
- Configuration options for external CA-signed certificates
- ECA_CERT_PATH for NetBackup servers and clients
- About certificate revocation lists for external CA
- About certificate enrollment
- Configuring an external certificate for the NetBackup web server
- About external certificate configuration for a clustered master server
- Regenerating keys and certificates
- NetBackup CA and NetBackup certificates
- Section III. Encryption of data at rest
- Data at rest encryption security
- About NetBackup client encryption
- Configuring standard encryption on clients
- About configuring standard encryption from the server
- Configuring legacy encryption on clients
- About configuring legacy encryption from the client
- About configuring legacy encryption from the server
- Additional legacy key file security for UNIX clients
- NetBackup key management service
- About FIPS enabled KMS
- About the Key Management Service (KMS)
- Installing KMS
- Configuring KMS
- About key groups and key records
- Overview of key record states
- Configuring NetBackup to work with KMS
- About using KMS for encryption
- KMS database constituents
- Command line interface (CLI) commands
- About exporting and importing keys from the KMS database
- Troubleshooting KMS
- External key management service
- Configuring KMS credentials
- Configuring KMS
- Creating keys in an external KMS
- Working with multiple KMS servers
- Data at rest encryption security
- NetBackup web services account
- Immutability and indelibility of data in NetBackup
Configuring keys in an external KMS for NetBackup consumption
NetBackup can use the keys that are already created in an external KMS or you can create keys in an external KMS using NetBackup, for which the NetBackup master server needs to be authorized to create keys.
NetBackup can discover the keys that are created in an external KMS for the NetBackup use. Specify custom attributes x-application and x-keygroup while generating keys or associate these attributes to the existing keys, so NetBackup can determine the keys to be used. NetBackup uses any key that has these attributes for encryption purpose.
Key group name for tape volume pool must have ENCR_ as a prefix.
Consider the following example: You have configured a tape volume pool with name ENCR_P1. The volume pool name suggests that the backup images in this volume pool are encrypted.
x-keygroup is case-sensitive and it should exactly match the volume pool name.
To configure keys
- Create a key in an external KMS with the custom attribute x-keygroup and its value as ENCR_P1.
- Set the custom attribute x-application with its value as NetBackup to indicate that this key belongs to NetBackup.
- For the keys that are already created and are to be used for encryption for this volume pool, you can create the custom attributes.
- To set these attributes, you can use the user interface that the respective KMS vendor has specified.
If the user interface of the KMS vendor does not support adding and setting custom attributes, you can use the nbkmiputil command to set the attributes for the keys.
nbkmiputil -kmsServer kms_server_name -port 5696 -certPath cert_path -privateKeyPath private_key_path -trustStorePath caCertificatePath -setAttribute -attributeName attributeName -attributeValue attributeVal
See the NetBackup Commands Reference Guide for more information on the command.