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 or reconfiguring multifactor authentication
Flex Appliance supports multifactor authentication for local, Active Directory (AD), and LDAP users in the Flex Appliance Console and the hostadmin user in the Flex Appliance Shell.
The following authenticator apps are supported:
Microsoft Authenticator version 6.5.12 and later
Google Authenticator
Okta Verify
Note that when you scan the QR code with this app, the authentication process could take up to a minute.
Symantec VIP Access 4.3.3 and later
Note:
Multifactor authentication may affect integrations like APIs, automation, and third-party Privileged Access Management (PAM) solutions.
Before you can configure multifactor authentication for a user in the Flex Appliance Console, the following prerequisites must be met:
The appliance date and time must be set with NTP.
At least one user must have the security administrator role. If you are the user with the security administrator role, at least one additional user must also have the security administrator role.
You must have a supported authenticator app installed on your mobile device.
To configure or reconfigure multifactor authentication for the Flex Appliance Console
- From the Flex Appliance Console, click your user icon in the top-right corner and click Configure multifactor authentication.
- On the Configure multifactor authentication page, click Configure or Reconfigure.
Note:
The Reconfigure option is only available if multifactor authentication is enforced, and the start date has passed. For other scenarios, click Disable and then click Configure.
- Follow the prompts to add your Flex Appliance account to the authenticator app.
If you have already configured multifactor authentication for another appliance and want to use the same authenticator account to sign in to this appliance, select the option Use a custom key. Enter the key from the appliance that is already configured.
You can also create and enter your own key with the custom key option. If you create your own key, note that some authenticator apps may not support pad characters. Confirm compatibility with your app if you want to use them.
Before you can configure multifactor authentication for the hostadmin user in the Flex Appliance Shell, the following prerequisites must be met:
The appliance date and time must be set with NTP.
You must have a supported authenticator app installed on your mobile device.
To configure or reconfigure multifactor authentication for the Flex Appliance Shell
- From the Flex Appliance Shell, run the following command:
set user mfa
- Follow the prompts to add the hostadmin account to your authenticator app.
If you have already configured multifactor authentication for another appliance and want to use the same authenticator account to sign in to this appliance, respond yes to the question Do you want to specify an existing key? Enter the key from the appliance that is already configured. You can view the key on the other appliance with the show user mfa key command.
You can also create and enter your own key with the existing key option. If you create your own key, note that some authenticator apps may not support pad characters. Confirm compatibility with your app if you want to use them.
- Share the QR code or the key with anyone else who requires access to the Flex Appliance Shell so that they can also add the hostadmin account to their authenticator app. You can view the QR code and the key at any time with the following command:
show user mfa key
- If you have a multi-node appliance, repeat these steps on the other node.