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
Smart card authentication for NetBackup Appliance Web UI
Ensure that you perform the following three steps before you perform authentication for the Appliance Web UI.
Note:
You can perform the steps in any order.
Configure LDAP authentication with the directory type as OpenLDAP or ActiveDirectory.
Settings > Security > Authentication > LDAP
Add and grant roles to LDAP users who will be authenticated by the appliance.
Settings > Security > Authentication > LDAP > Users Add
Settings > Security > Authorization > Grant
Add all the certificates in the CA chain to the appliance. Intermediate certificates on the card do not have to be added.
Settings > Security > Certificates > AddCACertificate
The smart card command menu allows you to configure and display parameters related to the Appliance Web UI smart card authentication. You can also enable or disable this feature.
Settings > Security > Authentication > SmartCard
Table: Smart card menu commands
Command | Description |
|---|---|
Configure MappingAttribute | The Configure command configures the appliance smart card authentication. It has one required and one optional configuration parameter. The MappingAttribute parameter specifies if the Common Name (CN) or the User Principal Name (UPN) of the certificate on the smart card is used to authenticate a user and determine that user's role. Enter CN or UPN. It is a required parameter. CN can be used if the CN in the certificates matches the CN field of the user records in the remote databases, OpenLDAP or ActiveDirectory. UPN can be used if the UPN in the certificates matches the UPN field of the user records in OpenLDAP or ActiveDirectory. When LDAP is, configured the directoryType is specified as OpenLDAP or ActiveDirectory. |
Configure OCSPURI | The OCSPURI parameter (Online Certificate Status Protocol) determines if the certificate on the smart card has been revoked. It is an optional parameter. If present, this parameter overrides the OCSP URI present in the certificate. The URI is an FQDN or IPv4 address. An IPv6 address is not supported for the OCSP URI. Note: If authentication with smart card fails even after all the necessary steps have been performed, use the command and verify that the parameters, including the OCSP URI, if present, are correct. Verify that a name server which can resolve the OCSP URI is configured in the Network menu by navigating to |
Disable | Disables smart card authentication. |
Enable | Enables smart card authentication. You can enable smart card authentication only if LDAP has been configured, CA certificates have been added and smart card authentication has been configured. |
Show | Displays a table which shows if smart card authentication is enabled, the selected mapping attribute, and the OCSP URI, if one was entered. |