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
Adding a replication operation to SLP at the production primary server
To configure the reverse connections
- On the left, click Storage > Disk storage.
- Click the Storage servers tab.
- Click on the MSDP storage server that you want to configure.
- Under Isolated Recovery Environment, click Modify SLP on the remote primary server.
- On the Modify SLP on the remote primary server page, provide the production primary server name.
- Select the existing login credentials or add new credentials and click Next.
Select existing credentials: Select the existing credentials.
Add a new credential: Add a new credential for the production primary server. Under Credential type, select Username Password authentication or Use API key.
Note:
The user of the production primary server needs privileges in the default IRE SLP Administrator role.
- Click Connect.
- Select the SLP that you want to add a replication operation to the IRE MSDP storage server and click Next.
- Select an operation that you want to replicate to IRE MSDP storage server after the operation and click Next.
- Select an SLP of the IRE domain for image import after replication completed.
- On the Window tab, configure SLP window for the replication operation. Create a new SLP window or select an existing SLP window.
When you adjust the SLP window, ensure that the SLP window is covered by IRE schedule. If a replication is triggered outside the IRE schedule, reverse connection does not happen, and the replication job fails.
The Synchronize with the reverse connection schedule helps to replace the current SLP window with the IRE Schedule. You can adjust the SLP window based on the IRE Schedule.
The date and time that is shown on the page are based on the time zone of IRE primary server. If the production primary server and the IRE primary server are in different time zones, the time difference is calculated and the SLP window for the production primary server is converted automatically.
Click Finish.
- Click Save.
All the configurations including MSDP storage server replication target, SLP window, and replication operation in the SLP are applied to the production primary server.