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
Smart card authentication for NetBackup Appliance Shell Menu
This topic provides the following information to configure smart card authentication for the NetBackup Appliance Shell Menu (shell menu):
Order of steps
Smart card SSH menu commands
Order of steps
Enable smart card authentication for SSH. You must first enable the feature before you can add the public key (step 3).
Configure the mapping attribute to determine which field in the remote database is used to search for the public key.
Add the public key for a local user. You can use either a public key file or a certificate file method.
(Optional) Choose to enable or disable password authentication for SSH login.
Table: Smart card SSH menu commands
Command | Description |
|---|---|
Configure MappingAttribute CN/UPN Configure PublicKey Add filetype <username> Configure PublicKey Remove <username> | The Configure command configures the appliance smart card authentication and is used to configure the following parameters: MappingAttribute is for either CN (Common Name) or UPN (User Principle Name). This attribute determines which of those fields in the remote database is used to search for the public key. Configure PublicKey Add filetype <username> adds a public key for a local user. Here, filetype is either Note: Before you can add a public key, you must first enable SSH smart card authentication with the Enable command described further below. Configure PublicKey Remove <username> removes a public key for a local user. |
Disable | Disables smart card authentication for SSH user. |
Enable | Enables smart card authentication for SSH users. If all the prerequisites for DNS and smart card configuration commands have been performed successfully, authentication with smart cards is enabled. Note: Before you can add a public key, you must first run this command to enable SSH smart card authentication. |
PWauth | Enables or disables password authentication for SSH login. |
Show | Shows the values of the mapping attribute and status of the smart card authentication. |