NetBackup™ Security and Encryption Guide
- Read this first for secure communications in NetBackup
- Communication failure scenarios
- Increasing NetBackup security
- Security deployment models
- Auditing NetBackup operations
- About audit events
- Section I. Identity and access management
- About identity and access management
- AD and LDAP domains
- Access keys
- API keys
- Auth.conf file
- Role-based access control
- Default RBAC roles
- Smart card or digital certificate
- Single Sign-On (SSO)
- Enhanced Auditing
- NetBackup Access Control Security (NBAC)
- Configuring NetBackup Access Control (NBAC)
- Configuring Access Control host properties for the primary 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 primary server
- Verification points in a mixed environment with a Windows primary server
- About determining who can access NetBackup
- Viewing specific user permissions for NetBackup user groups
- Section II. Encryption of data-in-transit
- NetBackup CA and NetBackup certificates
- About the Security Management utilities
- 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 NetBackup certificate deployment security levels
- Setting up trust with the primary 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
- Host ID-based certificate deployment in a clustered setup
- About deployment of a host ID-based certificate on a clustered NetBackup host
- Migrating NetBackup CA
- Configuring data-in-transit encryption (DTE)
- Configure the DTE mode on a client
- Modify the DTE mode on a backup image
- How DTE configuration settings work in various NetBackup operations
- External CA and external certificates
- About external CA support in NetBackup
- Configuration options for external CA-signed certificates
- ECA_CERT_PATH for NetBackup servers and clients
- About certificate revocation lists for external CA
- About certificate enrollment
- Configuring an external certificate for the NetBackup web server
- About external certificate configuration for a clustered primary server
- Regenerating keys and certificates
- NetBackup CA and NetBackup certificates
- Section III. Encryption of data at rest
- 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
- NetBackup key management service
- About FIPS enabled 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
- External key management service
- Configuring KMS credentials
- Configuring KMS
- Creating keys in an external KMS
- Working with multiple KMS servers
- Data at rest encryption security
- Ciphers used in NetBackup for secure communication
- FIPS compliance in NetBackup
- Disable FIPS mode for NetBackup
- NetBackup web services account
- Running NetBackup services with non-privileged user (service user) account
- Running NetBackup commands with non-privileged user account
- Immutability and indelibility of data in NetBackup
- Backup anomaly detection
- Section IV. Malware scanning
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 primary server. The levels are Medium, High, and Very High. By default, the security level is High.
A host ID-based certificate is automatically deployed on the primary server during upgrade or installation.
Host ID-based certificates are deployed on hosts after confirming the fingerprint. Whether an authorization token is required or not depends on the security level.
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. Select the certificate deployment level according to the security requirements of your NetBackup environment.
See About NetBackup 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 primary server administrator creates a token to be used on the non-primary host: | The host administrator of the non-primary server host must obtain an authorization token from the primary server administrator and use it to deploy the host ID-based certificate. |
Certificate deployment level setting at High (default) |
Maybe. Certificates are deployed without tokens on hosts that are known to the primary server. The following topic explains what it means to be known to the primary server: See About NetBackup certificate deployment security levels. If the host is not known to the primary server, the certificate must be deployed using an authorization token. The primary server administrator creates a token to be used on the non-primary server host. | If a host ID-based certificate is deployed, no further action is required. If a token is required, the host administrator of the non-primary server host must to obtain one from the primary server administrator and use it to deploy the host ID-based certificate. |
Certificate deployment level setting at Medium | No. Certificates may be deployed on all hosts that request one. See Automatic host ID-based certificate deployment. Note: A certificate may not be deployed if the primary server cannot verify that the requested host name matches the IP from which the certificate request originated. | If a host ID-based certificate is deployed, no further action is required. If the primary server cannot verify the host name, a host ID-based certificate must be deployed using a token. |
Certificate reissue | Yes. A certificate reissue requires a reissue token in most cases. | |
Hosts that cannot communicate with the primary server directly (an example of this is NetBackup hosts in a demilitarized zone (DMZ)). | Yes. NetBackup can automatically detect whether a host has connectivity with the primary server or not. If there is no connectivity, NetBackup attempts to use the built-in HTTP tunnel on a media server to route the certificate request to the primary server. | See Deploying certificates on a client that has no connectivity with the primary server. |
Certificate deployment and generation for NAT clients | Yes. During NetBackup certificate deployment on a NAT client, you must provide an authorization token is must, irrespective of the certificate deployment security level that is set on the primary server. This is because, the primary server cannot resolve the host name to the IP address from which the request is sent. | For more information about the support for NAT clients in NetBackup, refer to the NetBackup Administrator's Guide, Volume I. |