Veritas NetBackup™ Security and Encryption Guide
- Increasing NetBackup security
- Security deployment models
- Port security
- About NetBackup daemons, ports, and communication
- Additional port information for products that interoperate with NetBackup
- About configuring ports
- Auditing NetBackup operations
- Configuring Enhanced Auditing
- Access control security
- 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
- Security management in NetBackup
- About the Security Management utilities
- About audit events
- 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 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
- Security certificate deployment in a clustered NetBackup setup
- About deployment of a host ID-based certificate on a clustered NetBackup host
- 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
- Data at rest key management
- 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
- Regenerating keys and certificates
- NetBackup web services account
Configuration requirements if using Change Server with NBAC or Enhanced Auditing
Additional configuration is required to perform the Change Server operation if NetBackup Access Control or Enhanced Auditing is used.
The following steps assume that NBAC or Enhanced Auditing is already configured.
Add fromServer to the host properties Additional Servers list on toServer.
If fromServer and toServer are from different NetBackup domains (media servers of different master servers):
Use the vssat command to set up trust between the master servers of fromServer and toServer. (See Changing a server across NetBackup domains. Refer to step 2 in the procedure.)
Add the master server of fromServer to the host properties Additional Servers list on toServer.
If fromServer or toServer are media servers:
Use the bpnbaz - ProvisionCert command to deploy the security (Machine) certificate if needed. ( See Connecting to a media server with Enhanced Auditing.)
Add the USER entry to the auth.conf file on each server.
If NBAC is enabled, run the nbsetconfig on each server to add the entry: USE_AUTH_CONF_NBAC = YES
To use the Remote Administration Console:
Set up trust with each master server by using either the vssat command or explicitly log on to each server at least once. (See Changing a server across NetBackup domains. Refer to step 2 in the procedure.)
To troubleshoot the configuration after setup, use nslookup and bptestnetconn -a -s to check server communications.