NetBackup™ Security and Encryption Guide
- Read this first for secure communications in NetBackup
- Communication failure scenarios
- Increasing NetBackup security
- Security deployment models
- Auditing NetBackup operations
- About audit events
- Section I. Identity and access management
- About identity and access management
- AD and LDAP domains
- Access keys
- API keys
- Auth.conf file
- Role-based access control
- Default RBAC roles
- NetBackup interface access for OS Administrators
- Smart card or digital certificate
- Single Sign-On (SSO)
- NetBackup Access Control Security (NBAC)
- Configuring NetBackup Access Control (NBAC)
- Configuring Access Control host properties for the primary and media server
- Access Control host properties dialog for the client
- Troubleshooting Access Management
- Windows verification points
- UNIX verification points
- Verification points in a mixed environment with a UNIX primary server
- Verification points in a mixed environment with a Windows primary server
- About determining who can access NetBackup
- Viewing specific user permissions for NetBackup user groups
- Minimizing security configuration risk
- Configuring multifactor authentication
- Configuring multi-person authorization
- Section II. Encryption of data-in-transit
- NetBackup CA and NetBackup certificates
- About the Security Management utilities
- About host management
- Adding shared or cluster mappings
- Allowing or disallowing automatic certificate reissue
- About global security settings
- About host name-based certificates
- About host ID-based certificates
- Using the Certificate Management utility to issue and deploy host ID-based certificates
- About NetBackup certificate deployment security levels
- Setting up trust with the primary server (Certificate Authority)
- About reissuing host ID-based certificates
- About Token Management for host ID-based certificates
- About the host ID-based certificate revocation list
- About revoking host ID-based certificates
- Host ID-based certificate deployment in a clustered setup
- About deployment of a host ID-based certificate on a clustered NetBackup host
- Migrating NetBackup CA
- Configuring data-in-transit encryption (DTE)
- Configure the DTE mode on a client
- Modify the DTE mode on a backup image
- How DTE configuration settings work in various NetBackup operations
- External CA and external certificates
- About external CA support in NetBackup
- Configuration options for external CA-signed certificates
- ECA_CERT_PATH for NetBackup servers and clients
- About certificate revocation lists for external CA
- About certificate enrollment
- Configure an external certificate for the NetBackup web server
- About external certificate configuration for a clustered primary server
- Regenerating keys and certificates
- NetBackup CA and NetBackup certificates
- Section III. Encryption of data at rest
- Data at rest encryption security
- About NetBackup client encryption
- Configuring standard encryption on clients
- About configuring standard encryption from the server
- Configuring legacy encryption on clients
- About configuring legacy encryption from the client
- About configuring legacy encryption from the server
- Additional legacy key file security for UNIX clients
- NetBackup key management service
- About FIPS enabled KMS
- Installing KMS
- Configuring KMS
- About key groups and key records
- Overview of key record states
- Configuring NetBackup to work with KMS
- About using KMS for encryption
- KMS database constituents
- KMS operations using command-line interface (CLI)
- About exporting and importing keys from the KMS database
- Troubleshooting KMS
- External key management service
- Configuring KMS credentials
- Configuring KMS
- Creating keys in an external KMS
- Working with multiple KMS servers
- Data at rest encryption security
- Ciphers used in NetBackup for secure communication
- FIPS compliance in NetBackup
- Disable FIPS mode for NetBackup
- NetBackup web services account
- Running NetBackup services with non-privileged user (service user) account
- Running NetBackup commands with non-privileged user account
- Immutability and indelibility of data in NetBackup
- Anomaly detection
- Section IV. Malware scanning
- Introduction
- How to setup Malware scanning
- Instant Access configurations
- Malware tools configurations
- Scan host configurations
- Prerequisites for a scan host
- Configuring scan host
- Configuring a scan host pool
- Managing a scan host
- Performing malware scan
- Managing scan tasks
- Malware scan configuration parameters
- Troubleshooting
Prerequisites for Linux scan host
In addition to the prerequisites listed in Prerequisites for a scan host, ensure that you meet the following requirements for Linux platform:
For a Linux scan host the default login shell must be bash.
For RHEL 9 (and above) scan host, ensure that the SCP Linux command is not disabled.
Install the following:
For NFS share type:
nfs-utils
For SMB share type:
cifs-utils
For NetBackup malware detection utility to run on scan host, install
libnsl.so.1
library on scan host. If the latest version oflibnsl
library file is present (for example,/usr/lib64/libnsl.so.2
), then create a soft link file/usr/lib64/libnsl.so.1
which points to/usr/lib64/libnsl.so.2
file.Example to create a soft link file:
# cd /usr/lib64 # ln -sf libnsl.so.2 libnsl.so.1
Note:
For assistance on installing the
libnsl
* library file, contact operating system administrator.(Optional) A new variable entry (
$TMPDIR
) having a value equal to the desired location can be added for malware scan temp directory in the scan user's bashrc file.For example,
$TMPDIR=/mytempdirectory/malware
to overwrite the default/tmp/malware
temporary location. If user specifies$TMPDIR=/home/scanuser
as the temporary directory, then/home/scanuser/tmp/malware
directory would be used as the temporary directory for all the malware related files.Note:
Ensure that the scanuser has the required permissions to
$TMPDIR
folder for performing the malware scan successfully.For a non-root user on Linux:
Allow the
ssh
connection with a non-root user.For example: Add the Allow Users root scanuser entry in the
/etc/ssh/sshd_config
file.Note:
A scan user is a non-root user that is created in the system.
Provide user permission to mount and umount. Add the user permission entry in
sudoers
file.For example: In the
/etc/sudoers
file add one of the following:scanuser ALL=(ALL) NOPASSWD:ALL
scanuser ALL=(ALL) NOPASSWD:/bin/umount, /bin/mount
Configure the malware tool with a non-root user on the scan host.
Note:
If scanning is done using the root user, then change the permission of the
/tmp/malware
folder to provide write permissions to the non-root user.For example: chmod a+rwx /tmp/malware
Note:
For VMware and Cloud workload policy scanning, UID and GID mapping must be set to 0.
(If scan host is created in Azure or AWS from marketplace images) Enable root access for scan host as follows:
Change the root password using the following command:
- sudo -i passwd
Change
/etc/ssh/sshd_config
file to provide the permit for root login as follows:"PermitRootLogin yes" "PasswordAuthentication yes"
Restart the service with the following command:
- service sshd reload
Change
/etc/cloud/cloud.cfg
file as follows to enable root user:disable_root 0