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
About external certificate configuration for a clustered primary server
You can now use X.509 certificates that your trusted certificate authority (CA) has issued, for a clustered primary server.
You should first enable your NetBackup domain to use external CA-signed certificates by configuring the NetBackup web server.
You can then configure the NetBackup clustered primary server to use external CA-signed certificates for secure host communication.
See Workflow to use external certificates for a clustered primary server.
Review the following notes before you configure NetBackup to use external certificates:
NetBackup certificate or host ID-based certificate is deployed on the primary server during NetBackup installation. You need to manually configure an external certificate on the clustered primary server after installation.
In a clustered primary server setup, you require to configure one external certificate for each cluster node, which resides on the local disk of each node. Additionally, you need to configure one certificate for the virtual name, which resides on the shared disk of the cluster.
The NetBackup configuration options (for example, CLUSTER_ECA_CERT_PATH) that are required for external certificate enrollment for the virtual name are stored in the
nbcl.conf
file. This file resides on the shared disk and external certificate configuration options for each cluster node are stored in thebp.conf
file or Windows registry.Windows certificate store is not supported as an external certificate source for virtual name. It can be used as a source for certificates for cluster nodes.
There is no separate CRL configuration option for the virtual name. Based on the ECA_CRL_CHECK configuration option on the node, certificate revocation lists (CRLs) - ECA_CRL_PATH or CDP - of the cluster nodes are used to verify the revocation status of the peer host's certificate during communication. Therefore, the CRL configuration options should be set before using an external certificate for the primary server virtual name.