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
- 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
About certificate deployment security levels
NetBackup offers several levels that determine the nature of the CA checks that are performed when the CA receives a certificate request. The level determines the checks that are performed before the CA issues a certificate to a NetBackup host. It also determines how frequently the Certificate Revocation List (CRL) is refreshed on the host.
See About the host ID-based certificate revocation list.
Choose a certificate deployment level that corresponds with the security constraints and requirements of your NetBackup environment.
Table: Description of certificate deployment security levels lists and describes the three deployment levels.
Table: Description of certificate deployment security levels
Security Level | Description |
---|---|
Very High | Certificates are deployed on hosts during installation after confirming the master server fingerprint or through the nbcertcmd command. An authorization token is required for every new certificate request. See Creating authorization tokens. The Certificate Revocation List (CRL) that is present on the host is refreshed after every one hour. |
High (default) | Certificates are deployed on hosts during installation after confirming the master server fingerprint or through the nbcertcmd command. No authorization token is required if the host is known to the master server. A host is considered to be known to the master server if the host can be found in the following entities:
See Creating authorization tokens. The Certificate Revocation List (CRL) that is present on the host is refreshed after every four hours. |
Medium | Certificates are deployed on hosts during installation after confirming the master server fingerprint or through the nbcertcmd command. The certificates are issued without an authorization token if the master server can resolve the host name to the IP address from which the request was originated. The Certificate Revocation List (CRL) that is present on the host is refreshed after every eight hours. |