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 multi-factor authentication on NetBackup primary and media server instance
On Flex appliance, you can log in to the NetBackup instance through SSH. You can configure multi-factor authentication (MFA) on NetBackup primary and media server instance.
You can perform the following tasks to configure multi-factor authentication:
Enroll the multi-factor authentication.
After you enroll multi-factor authentication, user is required to provide six-digit token additionally to username and password to be able to log in. The authentication application generates the token on the mobile phone every 30 seconds.
Enforce the multi-factor authentication.
By default, multi-factor authentication is optional for the users. However, appadmin user can enforce it for all SSH login users in the application instance.
Reset the multi-factor authentication.
If the user's mobile phone is lost or factory-reset, the user is no longer able to log in with a token. The appadmin user can help the user to reset and re-enroll the multi-factor authentication.
If appadmin user is locked, he cannot reset multi-factor authentication for himself. To avoid this situation, we recommend that two or multiple users scan the same QR code of appadmin user with their mobile phones. If one user loses access to the MFA token, another can help him to enroll MFA again.
To configure the multi-factor authentication for SSH login
- Run the following command to enroll the multi-factor authentication:
/usr/openv/netbackup/bin/goodies/nbmfacfg -enroll
The command generates secret key randomly and displays it as the QR code.
- Scan the QR code using an authentication application on your mobile phone. For example, Google Authenticator or Microsoft Authenticator.
- If you want to manage multiple applications using the same secret key, you can get the secret key string from one MFA-enrolled application. Use the same key to configure multi-factor authentication on another instance.
To show the secret key and QR code, run the following command:
/usr/openv/netbackup/bin/goodies/nbmfacfg -show
To enroll MFA using a specific secret key, run the following command:
/usr/openv/netbackup/bin/goodies/nbmfacfg -enroll -secret <secret key>
Note:
The token validation is based on the server time. Ensure that the clock of the Flex Appliance and the mobile phone are correct.
- Run the following command to enforce multi-factor authentication for all SSH login users in the application instance. You must be appadmin user to perform this task.
/usr/openv/netbackup/bin/goodies/nbmfacfg -setenforce <1/0> [-grace-period <days>]
For example,
/usr/openv/netbackup/bin/goodies/nbmfacfg -setenforce 1 -grace-period 90
-setenforce: Sets the multi-factor authentication enforcement.
The value "1" enforces the multi-factor authentication. The value "0" disables the multi-factor authentication enforcement.
-grace-period: The grace period in days for SSH login without multi-factor authentication. After specified grace period is over, SSH login is denied if the user still does not enroll multi-factor authentication.
- To reset the multi-factor authentication for the user, run the following command. You must be appadmin user to perform this task.
/usr/openv/netbackup/bin/goodies/nbmfacfg -reset -user <user name>