Veritas NetBackup™ 8.0 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 certificates in NetBackup
- Overview of security certificates in NetBackup
- About the Security Management utilities
- 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 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
- About deploying a new host ID-based certificate
- 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
About host ID-based certificates
Each host in a NetBackup domain is assigned a unique identity, which is referred to as the host ID. The master server is the Certificate Authority (CA), and stores the host information in the nbdb database. The CA maintains a list of all of the host IDs that have been issued certificates or have had their certificates revoked. The host ID is used in many certificate management operations to identify the host.
For the troubleshooting issues that are related to host-ID based certificates and their resolutions, refer to the Troubleshooting technical article at the following location:
http://www.veritas.com/docs/DOC5332
The following topic provides a table that lists the operations that require a host ID-based certificate.
See Overview of security certificates in NetBackup.
Only a NetBackup administrator can control the settings that are related to certificate deployment and revocation.
If the host certificate is lost due to a communication error during the initial deployment phase, through data loss at a later stage, or even if NetBackup is uninstalled on the host--the master server continues to consider the certificate as a valid certificate.
The host ID remains the same, even when the host name changes. When NetBackup is reinstalled, the host can either retain the same identity or get a new host ID from the master server.
If a host obtains certificates from multiple NetBackup domains, it has multiple host IDs that correspond to each NetBackup domain.
When the master server is configured as part of a cluster, each node in the cluster receives a unique host ID. An additional host ID is assigned for the cluster name. For example, if the master server cluster is comprised of N nodes, the number of host IDs that are allocated for the master server cluster is N + 1.