NetBackup and Veritas Appliances Hardening Guide
- Top recommendations to improve your NetBackup and Veritas appliances security posture
- Introduction
- Keeping all systems and software updated
- Enabling multifactor authentication
- Enabling multiperson authorization
- Increasing the security level
- Implementing an immutable data vault
- Securing credentials
- Reducing network exposure
- Enabling encryption
- Enabling catalog protection
- Enabling malware scanning and anomaly detection
- Enabling security observability
- Restricting user access
- Configuring a sign-in banner
- Steps to protect Flex Appliance
- About Flex Appliance hardening
- Managing multifactor authentication
- Configuring the multi-factor authentication on NetBackup primary and media server instance
- Configuring the multi-factor authentication on NetBackup WORM storage server instance
- Managing single sign-on (SSO)
- Managing user authentication with smart cards or digital certificates
- About lockdown mode
- Using network access control
- Using an external certificate
- Forwarding logs
- Creating a NetBackup WORM storage server instance
- Configuring an isolated recovery environment using the web UI
- Protecting the NetBackup catalog on a WORM storage server
- Using a sign-in banner
- Steps to protect NetBackup Appliance
- About NetBackup Appliance hardening
- About multifactor authentication
- About single sign-on (SSO) authentication and authorization
- About authentication using smart cards and digital certificates
- Disable user access to the NetBackup appliance operating system
- About Network Access Control
- About data encryption
- FIPS 140-2 conformance for NetBackup Appliance
- About implementing external certificates
- About antimalware protection
- About forwarding logs to an external server
- Creating the appliance login banner
- Steps to protect NetBackup
- About NetBackup hardening
- About multifactor authentication
- Configure NetBackup for single sign-on (SSO)
- Configure user authentication with smart cards or digital certificates
- Workflow to configure multi-person authorization for NetBackup operations
- Access codes
- Workflow to configure immutable and indelible data
- Add a configuration for an external CMS server
- Configuring an isolated recovery environment on a NetBackup BYO media server
- About FIPS support in NetBackup
- Installing KMS
- Workflow for external KMS configuration
- Validating KMS credentials
- Configuring KMS credentials
- Configuring KMS
- Creating keys in an external KMS
- Workflow to configure data-in-transit encryption
- Workflow to use external certificates for NetBackup host communication
- About certificate revocation lists for external CA
- Configure an external certificate for the NetBackup web server
- Configuring the primary server to use an external CA-signed certificate
- Configuring an external certificate for a clustered primary server
- Configuring a NetBackup host (media server, client, or cluster node) to use an external CA-signed certificate after installation
- Configuration options for external CA-signed certificates
- ECA_CERT_PATH for NetBackup servers and clients
- ECA_TRUST_STORE_PATH for NetBackup servers and clients
- ECA_PRIVATE_KEY_PATH for NetBackup servers and clients
- ECA_KEY_PASSPHRASEFILE for NetBackup servers and clients
- ECA_CRL_CHECK for NetBackup servers and clients
- ECA_CRL_PATH for NetBackup servers and clients
- ECA_CRL_PATH_SYNC_HOURS for NetBackup servers and clients
- ECA_CRL_REFRESH_HOURS for NetBackup servers and clients
- ECA_DISABLE_AUTO_ENROLLMENT for NetBackup servers and clients
- ECA_DR_BKUP_WIN_CERT_STORE for NetBackup servers and clients
- MANAGE_WIN_CERT_STORE_PRIVATE_KEY option for NetBackup primary servers
- Guidelines for managing the primary server NetBackup catalog
- About protecting the MSDP catalog
- How to set up malware scanning
- About backup anomaly detection
- Send audit events to system logs
- Send audit events to log forwarding endpoints
- Display a banner to users when they sign in
Configuring the primary server to use an external CA-signed certificate
A NetBackup host ID-based certificate is deployed on the primary server during installation or upgrade. You can configure the primary server to use an external CA-signed certificate after installation. It includes:
Defining the external certificate configuration options
See Configuration options for external CA-signed certificates.
Enrolling the external certificate for the primary server host
The enrolled certificate is used for communication between the host and the primary server domain that is listed in the SERVER configuration option on the host.
See Configuring an external certificate for a clustered primary server.
Ensure that the NetBackup domain is enabled to use external CA-signed certificates by configuring the NetBackup web server.
See Configure an external certificate for the NetBackup web server.
External certificates for the NetBackup web server and the primary server must be issued by the same root certificate authority.
If the two certificate authorities do not match, communication between the NetBackup Administration Console and the NetBackup Web Management Console service (nbwmc service) fails.
Ensure that the certificate revocation lists (CRLs) for the external CA are stored at the required location.
If CRL distribution point (CDP) is used, ensure that the URLs that are specified in the CDP are accessible.
When NetBackup primary server is configured to use the service user (non-privileged user on UNIX and Local Service on Windows) to start most of the daemons or services, you must ensure that the following ECA paths are accessible to the service user:
ECA_CERT_PATH
ECA_PRIVATE_KEY_PATH
ECA_TRUST_STORE_PATH
ECA_KEY_PASSPHRASEFILE (optional)
ECA_CRL_PATH (optional)
To grant access to the service user, do the following:
On Unix, use the chmod or the chown command.
On Windows run the following command:
install_path\NetBackup\bin\goodies\nbserviceusercmd.exe -addAcl ECA path -reason reason
To configure the primary server to use an external certificate
- Update the NetBackup configuration file (
bp.conffile on UNIX or Windows registry) on the primary server with the external certificate-specific parameters.See Configuration options for external CA-signed certificates.
For Windows certificate store
Use the nbsetconfig command to configure the following parameters:
ECA_CERT_PATH
ECA_CRL_CHECK (optional)
ECA_CRL_PATH (optional)
ECA_CRL_PATH_SYNC_HOURS (optional)
ECA_CRL_REFRESH_HOURS (optional)
ECA_DR_BKUP_WIN_CERT_STORE (optional)
For file-based certificates
Use the nbsetconfig command to configure the following parameters:
ECA_CERT_PATH
ECA_PRIVATE_KEY_PATH
ECA_TRUST_STORE_PATH
ECA_KEY_PASSPHRASEFILE (optional)
ECA_CRL_CHECK (optional)
ECA_CRL_PATH (optional)
ECA_CRL_PATH_SYNC_HOURS (optional)
ECA_CRL_REFRESH_HOURS (optional)
Note:
If you have a Flex Appliance application instance, the certificate files must be stored in the following directories on the instance:
ECA_CERT_PATH, ECA_PRIVATE_KEY PATH, and ECA_TRUST_STORE_PATH:
/mnt/nbdata/hostcert/ECA_CRL_PATH:
/mnt/nbdata/hostcert/crl - Run the following command on the primary server to enroll an external certificate with the primary server domain that is defined in the SERVER option:
nbcertcmd -enrollCertificate
For more details on the command, refer to the NetBackup Commands Reference Guide.