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
Media device selection (MDS) and resource allocation
Based on the global DTE mode, client DTE mode, media server DTE mode, and image DTE mode, the resources are allocated.
For dynamic storage units, like MSDP or Storage Unit Group, a media server with the DTE mode On is preferred if that is a requirement for the job.
Note:
For Snapshot Manager backup and recovery work flows, if DTE is required to be On, you need to ensure that DTE is configured to be On for each media server that is configured for the respective storage unit.
If the job demands a media server with the DTE mode On, but such a media server is not available, NetBackup falls back on the original resource allocation decisions.
In such cases, it is possible that the job goes ahead and sees a failure later on during job execution (in nbjm or bprd or other such daemons and CLIs), where NetBackup the DTE is required by media server.
The following process describes how the media device selection and DTE validations take place:
- In case of a backup operation, directly go to step 2. For any other operations such as restore, duplication, replication, import, verify, the source image DTE mode is taken into consideration:
If the DTE mode of an image is ON, the media server DTE media server is ON, irrespective of any other DTE configuration.
If DTE mode of an image is OFF, check for global, client and media server DTE modes.
- If the global DTE setting is ENFORCED, then a DTE enabled media server is preferred.
- If the global DTE setting is PREFERRED ON or PREFERRED OFF, a client DTE mode is taken into consideration.
If the client DTE mode is ON - DTE enabled media server is preferred.
If the client DTE mode is OFF - any available media server can be selected.
If the client DTE mode is Automatic - the decision is made based on the global DTE setting. It means if the global DTE setting is set to PREFERRED OFF, select any available media server, else select the DTE enabled media server.
During resource allocation, many parameters play an important role. Following are the special conditions:
If the client name is blank, it signifies a secondary operation such as duplication, replication, import, verify and so on. The image DTE mode or global DTE mode are honored.
If the client name is not blank, however it is not present in the host database as the client is earlier than 8.0, the client does not support DTE. Hence, any media server can be selected.
After the global and client DTE settings, media server's version and its DTE setting are checked:
NetBackup 9.1 and later media servers are by default DTE capable and DTE enabled.
DTE_IGNORE_IMAGE_MODE setting (for any secondary operations based on an image)
If the image DTE mode is ON, and if the DTE_IGNORE_IMAGE_MODE option is applied, the global, client, and media server settings are used for the media server selection.