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
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 malware tool must be installed and configured.
The scan host must have a share type configured, that is, an NFS or SMB client.
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.
OpenSSH must be configured on windows scan host.
Note the following:
For Windows 2016, get OpenSSH from GIT hub repository and for Windows 2019, enable OpenSSH server feature. For more details, refer to Microsoft documentation.
Microsoft Visual C/C++ Redistributable is an additional dependency if media server is updated to 10.1.1.
Visual C/C++ run-time library DLL is required to execute nbmalwareutil utility on windows scan host. The runtime DLL can be obtained from Microsoft Visual C++ Redistributable latest supported downloads.
The minimum required configuration for the scan host is 8 CPU and 32-GB RAM.
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.
For the supported operating systems of the scan host, refer Software Compatibility List.
For NetBackup malware detection utility to execute on scan host, install
libnsl.so.1library on scan host. If the latest version oflibnsllibrary file is present (for example,/usr/lib64/libnsl.so.2), then create a softlink file/usr/lib64/libnsl.so.1which points to/usr/lib64/libnsl.so.2file.Example for creating softlink file:
# cd /usr/lib64 # ln -sf libnsl.so.2 libnsl.so.1
Note:
For assistance on installing
libnsl* library file, contact operating system administrator.
For non-root user on Linux:
Allow
sshconnection using non-root user.For example: Add the Allow Users root scanuser entry in the
/etc/ssh/sshd_configfile.Note:
Scanuser is a non-root user created in the system.
Provide user permission to mount and umount. Add user permission entry in
sodoersfile.For example: In the
/etc/sudoersfile add one of the following:scanuser ALL=(ALL) NOPASSWD:ALL
scanuser ALL=(ALL) NOPASSWD:/bin/umount, /bin/mount
Configure malware tool using non-root user on the scan host.
Note:
If scanning is done using root user, then change the permission of the
/tmp/malwarefolder to provide write permissions to the non-root user.Note:
For example: chmod a+rwx /tmp/malware