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
- Configuring user groups
- About defining a user group and users
- 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
Creating a reissue token
A host ID-based certificate can be reissued if the non-master host is already registered with the master server but its host ID-based certificate is no longer valid. For example, a certificate is not valid when it has expired, is revoked, or is lost.
A reissue token is a type of token that can be used to reissue a certificate. It is a special type of token because it retains the same host ID as the original certificate. Since a reissue token is bound to a specific host, the token cannot be used to request certificates for additional hosts.
To create a reissue a token using the NetBackup Administration Console
- In the NetBackup Administration Console, expand Security Management.
- Select the Certificate Management or Host Management node.
- In the right pane, select the host that requires a reissue token.
- From the Actions menu, select Generate Reissue Token.
- In the Create Reissue Token dialog, enter a name for the token.
- Select a date for token validity from the Valid until option.
- In the Reason field, enter a reason for the reissue token. The reason appears in the log as an audit event.
- Click Create.
- The reissue token appears in a dialog. Select Copy to save the token value to the clipboard.
- Convey the token value to the administrator of the non-master host. How the token is conveyed depends on various security factors in the environment. The token may be transmitted by email, by file, or verbally.
The administrator of the non-master host deploys the token to obtain another host ID-based certificate. See the following topic for instructions:
To create a reissue a token using the nbcertcmd command
- The master server administrator must be logged in to the NetBackup Web Management Service to perform this task. Use the following command to login:
bpnbat -login -logintype WEB
- Run one of the following commands on the master server:
Use the host name for which the certificate needs to be reissued:
nbcertcmd -createToken -name token_name -reissue -host host_name
You must provide the primary name of the host for which you want to reissue the certificate. If you provide any of the host ID-to-host name mappings that are added for the host, the certificate cannot be reissued.
Use the host ID for which the certificate needs to be reissued:
nbcertcmd -createToken -name token_name -reissue -hostId host_id
Additional parameters can be used to indicate validity duration and the reason for creation.
In addition to reissuing a token, the following steps are required to request a certificate for a renamed NetBackup host.
To request a certificate for a host after a host name change
- The NetBackup administrator of the master server generates a reissue token for the renamed NetBackup host.
- Add the new host name as one of the approved host ID-to-host name mappings by using NetBackup Administration Console.
Alternatively, you can use the nbhostmgmt -add command-line interface option.
For more information about the nbhostmgmt command, see the NetBackup Commands Reference Guide.
- The NetBackup administrator must revoke the host ID-based certificate for the renamed host.
After the certificate is revoked, the host is unable to communicate with the NetBackup Web Management Console service (nbwmc). When the host obtains a new certificate using the reissue token, the host can communicate with nbwmc again.
- After the certificate is revoked, the administrator of the non-master host must use the reissue token to get a certificate for the renamed host.