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
- 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 authorization tokens
If the security setting is Very High, all certificate requests require a token. Perform the procedure that is described in this topic.
If the security setting is High, certificates are automatically deployed to hosts that are known to the master server. If the host is not known to the master server, the certificate must be deployed using an authorization token. In that case, perform the procedure that is described in this topic.
To understand what it means to be known to the master server, see the following topic:
If the security setting is Medium, this procedure may be less likely because certificates are automatically deployed to all hosts that request one. However, the master server must be able to cross verify the IP and host name of the host that is requesting a certificate.
A token is required to request a certificate on behalf of a host that has no connectivity with the master server.
Do not use this procedure to create an authorization token for a NetBackup host whose current certificate is not in a valid state because it is lost, corrupt, or expired. In these cases, a reissue token must be used.
The NetBackup administrator of the master server can use the NetBackup Administration Console or the command line to create the token.
To create a token using the NetBackup Administration Console
- In the NetBackup Administration Console, expand Security Management > Certificate Management > Token Management.
- On the Actions menu, select New Token.
The Create Token dialog box is displayed.
- Enter a unique and meaningful name for the token. The field cannot be left blank.
For example, to create a token to request certificates for multiple hosts that belong to master_server_1, name the token Token1_MS1. A good practice is to write a useful description in the Reason field for the token.
- Enter a number for the Maximum Uses Allowed option for the number of times the token can be used. The default is 1, which indicates that one host can use the token one time.
To use the same token for multiple hosts, enter any value between 1 and 99999. For example, to use the token for 8 hosts, enter 8. The ninth host that attempts to use the token will not succeed.
- Use the Valid for option to indicate how long the token can be used before it is invalid and cannot be used. After the Valid for date, the master server must generate another token.
Select a period between 1 and 999 hours or days.
- Optionally, enter the reason for creating the token. The reason appears in the audit logs, along with the other entries in the dialog.
- Select Create.
- The new 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 uses the token to obtain a host ID-based certificate from the Certificate Authority. See the following procedure for instructions:
To create a token using the nbcertcmd command
- Run the following command on the host:
nbcertcmd -createToken -name token_name
nbcertcmd -createToken -name testtoken
Token FCBVYUTDUIELUDOE created successfully.
Additional parameters can be used to indicate maximum uses, validity duration, and the reason for creation.
For information about the nbcertcmd command, see the NetBackup Commands Reference Guide.