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
- NetBackup interface access for OS Administrators
- Smart card or digital certificate
- Single Sign-On (SSO)
- 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
- Minimizing security configuration risk
- Configuring multifactor authentication
- Configuring multi-person authorization
- 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
- Configure 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
- KMS operations using command-line interface (CLI)
- 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
- Hardware Security Module (HSM) support in NetBackup
- Data at rest encryption security
- Ciphers used in NetBackup for secure communication
- FIPS compliance in NetBackup
- Disable FIPS mode for NetBackup
- Post-Quantum Cryptography (PQC) support in 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
- Anomaly detection
- Section IV. Malware scanning
- Introduction
- How to setup Malware scanning
- Instant Access configurations
- Malware tools configurations
- Scan host configurations
- Prerequisites for a scan host
- Configuring scan host
- Configuring a scan host pool
- Managing a scan host
- Performing malware scan
- Managing scan tasks
- Malware scan configuration parameters
- Troubleshooting
Decommission a client
This operation is applicable only for NetBackup clients.
To decommission a host with special roles like media server, remote primary server, or Flex WORM storage server, you should first downgrade its role and then decommission the host.
When you decommission a client, NetBackup removes the client from the domain by revoking its identity. It resets the host's communication status and other attributes like Operating System version, NetBackup machine type and so on for that client. Primary servers and media servers from the same domain cannot communicate with the decommissioned client.
Review the following notes before decommissioning a client host:
If the specified client is configured with NetBackup certificate, the associated certificates are revoked.
If the specified client is configured with external certificate, its enrollment is removed.
You should remove the client that needs to be decommissioned from the policies and protection plan, and expire the associated images of that client.
Alternatively, you can use the -force option to decommission the client irrespective of the associated policies or images. With the -force option, you do not need to delete the data.
A user with the following RBAC roles can decommission a host:
NetBackup Administrator
Default Security Administrator
A custom role with the 'Decommission host' permission
To decommission a client using the NetBackup web UI
- On the left, select Security > Host mappings.
- Locate the host and click Actions > Decommission client.
- Enter the reason to decommission the client.
To decommission a client, use the following API: POST - /config/hosts/{hostId}/decommission
To list decommissioned clients, use the following API: GET - /config/hosts
Use the filter 'decommissionedDateTime'
To decommission a client using command-line interface
- Run the following command:
nbhostmgmt {{-dh | -decommissionhost} {{-i | -hostid} <hostid> | {-n | -host} <host>} {{-r | -reason} "<reason>"} [-f | -force] [{-j | -json} | { -jc | -json_compact}]
If you want to recommission a previously decommissioned client with host ID-based (NBCA) certificate, provision a new certificate on that client host.
To recommission a client with NetBackup certificate
- Run the following command on the client:
Install_Path/bin/nbcertcmd -getCertificate -reissue -token value -force
To recommission a client with external certificate
- Run the following command on the client:
Install_Path/bin/nbcertcmd -enrollCertificate -force
After a client is recommissioned, restart the NetBackup services on the client host or run the following command:
Install_Path/bin/nbhostdbcmd -update -force