NetBackup and Veritas Appliances Hardening Guide
- Top recommendations to improve your NetBackup and Veritas appliances security posture
- Steps to protect Flex Appliance
- Managing multifactor authentication
- Managing multifactor authentication on a primary or a media server instance
- Managing multifactor authentication on a WORM storage server
- Managing single sign-on (SSO)
- About lockdown mode
- Configuring an isolated recovery environment using the web UI
- Steps to protect NetBackup Appliance
- About single sign-on (SSO) authentication and authorization
- About authentication using smart cards and digital certificates
- About data encryption
- About forwarding logs to an external server
- Steps to protect NetBackup
- 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
- Workflow for external KMS configuration
- 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 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
- About protecting the MSDP catalog
- How to set up malware scanning
- About backup anomaly detection
- Steps to protect NetBackup Flex Scale
- STIG overview for NetBackup Flex Scale
- FIPS overview for NetBackup Flex Scale
- Support for immutability in NetBackup Flex Scale
- Deploying external certificates on NetBackup Flex Scale
- About multifactor authentication
- About single sign-on (SSO) configuration
- Steps to protect Access Appliance
- FIPS 140-2 conformance for Access Appliance
- Managing the login banner using the UI
- Managing the password policy using the UI
- Support for immutability in Access Appliance
- About system certificates on Access Appliance
- About single sign-on (SSO) configuration
- Configuring user authentication using digital certificates or smart cards
- About multifactor authentication
- Configuring an isolated recovery environment using the command line
- Forwarding logs to an external server
Managing the banner from the command-line interface
You can create a customized text banner that appears when you sign in to Access Appliance UI or the system console. You can use the login banner to communicate various kinds of messages to users. Typical uses for the login banner include legal notices, warning messages, and company policy information.
If the Security Technical Implementation Guide (STIG) mode is enabled for the cluster, the login banner cannot be modified.
To display the banner:
- Log on to the Access command-line interface by opening an SSH session to the management console IP as an administrator.
- In the Access command-line interface, run the following command:
system banner get
access-clus> system banner get No login banner is currently set for the appliance.
Note:
No banner is set by default.
To set the banner:
- Log on to the Access command-line interface by opening an SSH session to the management console IP as an administrator.
- In the Access command-line interface run the following command:
system banner get
# access-clus> system banner set Enter Header (Type <enter> and <Ctrl + d> to complete the body. Max 250 characters) This is header Enter Body (Type <enter> and <Ctrl + d> to complete the body. Max 4000 characters) This is body text line 1. This is body text line 2.
The banner is made up of two parts, the header and the body. The header is the heading for the banner and the body is the banner content. The header can be a maximum of 250 characters and body can be a maximum of 4000 characters.
After the banner is set, you can view the banner using the system banner get command:
access-clus> system banner get **************** This is header **************** This is body text line 1. This is body text line 2.
Note:
If STIG is enabled on the system, you cannot change the default STIG banner.
accessclus> system banner set ACCESS Banner ERROR V-493-10-0 The banner cannot be set as STIG is enabled on the cluster.