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
Prerequisites for a scan host
A scan host is a host machine that has the required malware tool configured. Once it is integrated with NetBackup, NetBackup initiates scanning on the scan host.
Ensure that you meet the following prerequisites:
The minimum required configuration for the scan host is 8 CPU and 32-GB RAM.
The malware tool must be installed and configured.
For the supported operating systems of the scan host, refer to the Software Compatibility List.
The scan host must have a share type configured, that is, an NFS or an SMB client.
If the scan host connectivity type is
:NetBackup footprint is not required on the scan host. The existing systems with the NetBackup client or media server can be used as scan host, too.
The scan host must be reachable from the media server over SSH.
Note:
SSH connection to scan host from the media server must be successful and this can be verified by running the following command from media server:
ssh scanuser@scanhost
If the scan host connectivity type is
:NetBackup footprint is required on the scan host.
The NetBackup primary server and the media server providing the Instant Access mounts must be reachable from the NetBackup client.
By default, the NetBackup client scan host would be in deactivate state. After adding NetBackup client scan host to scan host pool you must activate the scan host.
The malware tool uses the temporary location to store files created during malware scan. The path of temporary location is configured in Web UI under the Malware global settings. Ensure that the user has write permissions to this path.
For archive scanning purposes, it is recommended to have the free disk space of 10 GB on the scan host.
Note:
(Applicable for NetBackup version 10.0 and later) Any other malware scanner tools that are installed on the scan host with on-access/real time protection enabled can interfere with backup scanning. Disable or add NFS/SMB mounts on the scan host to the exclusion list of the scanner.
For example, on a Windows scan host, the user must disable the
option of the Windows Defender while the malware scan is in progress.Depending on the platform, ensure that the following additional prerequisites are met:
Windows:
Linux:
Note:
It is recommended to keep only the required ports open for malware scanning.
Allow NFS/SMB read from NetBackup storage server. Refer to NetBackup Network Ports Reference Guide.
Allow SSH From NetBackup media server (used for connecting to scan host).
Allow Malware signature updates. This depends on malware scanner used. For NetBackup Malware Scanner, update happens over HTTPS (https://oem.avira-update.com/update).