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
Catalog backup and recovery
Media server should be of the same NetBackup version as the primary server for catalog backup and recovery workflow.
Review the following points:
DTE mode for catalog backup jobs is similar to the file system workflow and DTE decision is similar to the backup workflow described above.
DTE mode in catalog backup jobs:
Parent catalog backup job does not have DTE mode set.
Database staging child job does not have DTE mode set.
Other two child jobs have DTE mode set as per the configured DTE settings.
DTE mode in catalog recovery jobs:
First 2 jobs have the DTE mode set as per the following tables depending on the image DTE mode.
The first two jobs replace the global DTE setting and primary server's bp.conf values, so the 3rd job DTE mode is set as per the recovered global DTE setting and primary server's bp.conf values.
Table: When the image DTE mode is Off and the media server DTE setting is On
Global DTE mode | NetBackup Primary server 9.1 and later with DTE mode | ||
|---|---|---|---|
On | Off | Automatic | |
Preferred Off | Data is encrypted | Data is not encrypted | Data is not encrypted |
Preferred On | Data is encrypted | Data is not encrypted | Data is encrypted |
Enforced | Data is encrypted | Data is encrypted | Data is encrypted |
Note:
When the global DTE setting is set to ENFORCED and the DTE_CLIENT_MODE is Off, DTE is preferred over failure in case of catalog recovery.
Table: When the image DTE mode is Off and the media server DTE setting is Off
Global DTE mode | NetBackup Primary server 9.1 and later with DTE mode | ||
|---|---|---|---|
On | Off | Automatic | |
Preferred Off | Data is encrypted * | Data is not encrypted | Data is not encrypted |
Preferred On | Data is encrypted * | Data is not encrypted | Data is not encrypted |
Enforced | Data is encrypted * | Data is encrypted * | Data is encrypted * |
* signifies that DTE is preferred over failure during catalog recovery. It ignores the DTE setting on the media server, that is Off unless the client DTE mode is set to Automatic.
Table: When the image DTE mode is On and the media server DTE setting is On
Global DTE mode | Host | Value of the DTE_IGNORE_IMAGE_MODE configuration option | ||
|---|---|---|---|---|
NEVER (default) | WHERE_UNSUPPORTED | ALWAYS | ||
Preferred Off | Primary server with DTE_CLIENT_MODE as ON | Data is encrypted | Data is encrypted | Data is encrypted |
Primary server with DTE_CLIENT_MODE as OFF | Data is encrypted | Data is encrypted | Data is not encrypted | |
Primary server with DTE_CLIENT_MODE as AUTOMATIC | Data is encrypted | Data is encrypted | Data is not encrypted | |
Preferred On | Primary server with DTE_CLIENT_MODE as ON | Data is encrypted | Data is encrypted | Data is encrypted |
Primary server with DTE_CLIENT_MODE as OFF | Data is encrypted | Data is encrypted | Data is not encrypted | |
Primary server with DTE_CLIENT_MODE as AUTOMATIC | Data is encrypted | Data is encrypted | Data is encrypted | |
Enforced | Primary server with DTE_CLIENT_MODE as ON | Data is encrypted | Data is encrypted | Data is encrypted |
Primary server with DTE_CLIENT_MODE as OFF | Data is encrypted | Data is encrypted | Data is encrypted | |
Primary server with DTE_CLIENT_MODE as AUTOMATIC | Data is encrypted | Data is encrypted | Data is encrypted | |
Note:
If DTE_IGNORE_IMAGE_MODE is set to ALWAYS, the DTE decision is as per the table - Table: When the image DTE mode is Off and the media server DTE setting is On.
Table: When the image DTE mode is On and the media server DTE setting is Off
Global DTE mode | Host | Value of the DTE_IGNORE_IMAGE_MODE configuration option | ||
|---|---|---|---|---|
NEVER (default) | WHERE_UNSUPPORTED | ALWAYS | ||
Preferred Off | Primary server with DTE_CLIENT_MODE as ON | Data is encrypted * | Data is encrypted * | Data is encrypted * |
Primary server with DTE_CLIENT_MODE as OFF | Data is encrypted * | Data is encrypted * | Data is not encrypted | |
Primary server with DTE_CLIENT_MODE as AUTOMATIC | Data is encrypted * | Data is encrypted * | Data is not encrypted | |
Preferred On | Primary server with DTE_CLIENT_MODE as ON | Data is encrypted * | Data is encrypted * | Data is encrypted * |
Primary server with DTE_CLIENT_MODE as OFF | Data is encrypted * | Data is encrypted * | Data is not encrypted | |
Primary server with DTE_CLIENT_MODE as AUTOMATIC | Data is encrypted * | Data is encrypted * | Data is not encrypted | |
Enforced | Primary server with DTE_CLIENT_MODE as ON | Data is encrypted * | Data is encrypted * | Data is encrypted * |
Primary server with DTE_CLIENT_MODE as OFF | Data is encrypted * | Data is encrypted * | Data is encrypted | |
Primary server with DTE_CLIENT_MODE as AUTOMATIC | Data is encrypted * | Data is encrypted * | Data is encrypted * | |
* signifies that DTE is preferred over failure during catalog recovery. It ignores the DTE setting on the media server, that is Off unless the client DTE mode is set to Automatic.