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
Using the Certificate Management utility to issue and deploy host ID-based certificates
The process for host ID-based certificate deployment varies based on the certificate deployment security level configured on the master server. The levels are Medium, High, and Very High. By default, the security level is High. A host ID-based certificate is deployed on the master server automatically upon upgrade or new installation.
These levels determine the nature of the Certificate Authority (CA) checks that are performed when the CA receives a certificate request from a NetBackup host. The levels determine which checks are performed before a certificate is issued. Select the certificate deployment level according to the security requirements of your NetBackup environment.
See About certificate deployment security levels.
In some scenarios, certificate deployment requires the use of authorization tokens that are managed by a NetBackup administrator. The NetBackup administrator creates and shares these tokens with the administrators of individual hosts for certificate deployment on their local hosts. Certificate deployment can happen easily, allowing for scalable deployment across multiple NetBackup hosts without requiring NetBackup administrator intervention.
Table: Deployment requirements at each certificate deployment level or scenario
Certificate deployment level or scenario | Is an authorization token required? | Deploy host ID-based certificate? |
---|---|---|
Certificate deployment level setting at Very High | Yes. All certificate requests require an authorization token. The master server administrator creates a token to be used on the non-master host: | After receiving the token, the non-master administrator uses it to deploy a host ID-based certificate: |
Certificate deployment level setting at High (default) | Maybe. Certificates are automatically deployed to hosts that are known to the master server. The following topic explains what it means to be known to the master server: See About certificate deployment security levels. If the host is unknown to the master server, the certificate must be deployed using an authorization token. The master server administrator creates a token to be used on the non-master host: | After receiving the token, the non-master administrator uses it to deploy a host ID-based certificate: |
Certificate deployment level setting at Medium | No. Certificates may be automatically deployed to all hosts that request one. See Automatic host ID-based certificate deployment. Note: A certificate may not be automatically deployed if the master server cannot verify that the requested host name matches the IP from which the certificate request originated. | If a host ID-based certificate was deployed automatically, no further action is required. If the master server could not verify the host name, a host ID-based certificate must be deployed: |
Certificate reissue | ||
Hosts that cannot communicate with the master server directly | If a host has no connectivity with the master server, another NetBackup host that can communicate with the master server is used as a proxy for the client. The proxy host requires a token to get a signed certificate from the master server on behalf of the host. | See Deploying certificates on a client that has no connectivity with the master server. |