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
- Increasing the appliance 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 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 on a WORM storage server
- Protecting the NetBackup catalog on a WORM storage server
- Using a sign-in banner
- Steps to protect NetBackup Appliance
- About NetBackup Appliance hardening
- 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 forwarding logs to an external server
- Creating the appliance login banner
- Steps to protect NetBackup
- About NetBackup hardening
- Configure NetBackup for single sign-on (SSO)
- Configure user authentication with smart cards or digital certificates
- 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
- Configuring 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
Enable FIPS mode on a NetBackup host after installation
This section provides steps to enable FIPS mode on a primary server, a media server, or a client in a NetBackup domain. You should do the following configurations on each host to enable FIPS.
If the host is a primary server, enable FIPS mode for the NetBackup Authentication Broker (AT) by updating the VRTSatlocal.conf configuration file on the primary server.
See Enable FIPS mode for the NetBackup Authentication Broker service.
To enable FIPS mode on a NetBackup host
- Enable the NB_FIPS_MODE flag in the NetBackup configuration file.
- Restart the NetBackup services.
To verify if a certain daemon or a command runs in FIPS mode, check the respective logs. The log lines are available only for the daemons and commands that use cryptography.
Example 1: To verify if the nbcertcmd command runs in FIPS mode
- Run the following command:
nbcertcmd -ping
Location of the command:
Windows: install_path\NetBackup\bin\nbcertcmd
UNIX: /usr/openv/netbackup/bin/nbcertcmd
- Check the nbcertcmd logs.
Location of the log directory:
Windows: install_path\NetBackup\logs\nbcert
UNIX: /usr/openv/netbackup/logs/nbcert
The following log lines should be present:
<2> nbcertcmd: ./nbcertcmd -ping ProcessContext: ProcessName:[nbcertcmd], FipsMode:[ENABLED], Username:[root], IsServiceAdmin:[0], UserID:[0], GroupID:[0]
Example 2: To verify if the NetBackup Web Management Console runs in FIPS mode
- By default, FIPS mode is disabled when the NetBackup Web Management Console (nbwmc) service runs. FIPS mode is enabled for the nbwmc service after you enable it for the NetBackup host.
Check the catalina log file on the NetBackup primary server host to verify if the nbwmc service runs in FIPS mode.
Location of the log file:
Windows: install_path\NetBackup\wmc\webserver\logs\catalina-date.log
UNIX: /usr/openv/wmc/webserver/logs/catalina-date.log
The following log lines should be present:
The nbwmc service is running in FIPS approved mode