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 Windows scan host
In addition to the prerequisites listed in Prerequisites for a scan host, ensure that you meet the following requirements for Windows platform:
For a non-administrator user on Windows: A non-administrator user of a Windows scan host must be added to the administrators group.
For supporting non-English characters on the Windows scan host, enable multibyte characters support.
For more information on enabling multibyte characters support in Microsoft Windows Server 2019, refer to the article Retrieve Data in UTF-8 on Windows.
For supporting long paths on the Windows scan host, enable long path support. For more information on enabling maximum path length support, refer to Maximum Path Length Limitation.
OpenSSH must be configured on windows scan host. Create the firewall rule for OpenSSH so that scan host is accessible from the media server.
Note the following:
For Windows 2016, get OpenSSH from the GIT hub repository and for Windows 2019, enable the OpenSSH server feature. For more details, refer to the Microsoft documentation.
Microsoft Visual C/C++ Redistributable is an additional dependency if the media server is updated to 10.1.1 or later.
The Visual C/C++ run-time library DLL is required to run the nbmalwareutil utility on a windows scan host. The run-time DLL can be obtained from the Microsoft Visual C++ Redistributable latest supported downloads.
Note:
Run the scan host credential validation again from the Web UI if changes are done to ID mapping.
For VMware and Cloud workload policy scanning, UID and GID mapping must be set to 0. This requires a separate scan host pool having separate scan host.
Perform the following
- Enable local
passwd
file mapping using PowerShell:C:\Users\Administrator> Set-NfsMappingStore -EnableUNMLookup $True -UNMServer localhost C:\Users\Administrator> nfsadmin mapping The following are the settings on localhost Mapping Server Lookup : Enabled Mapping Server : localhost AD Lookup : Disabled AD Domain :
- Install NFS client by running the following command on PowerShell:
Install-WindowsFeature -Name NFS-Client
- The entry must be as follows in the respective files (in file type format):
Note:
Ensure that the scanuser and scangroup are created. The scanuser must be part of the scangroup and Administrators group.
In
C:\Windows\System32\drivers\etc\passwd
file:scanuser:x:1001:1001:Description:C:\Users\scanuser
In
C:\Windows\System32\drivers\etc\group
file:scangroup:x:1001:1001
- Restart
nfsadmin
client as follows:nfsadmin client stop
nfsadmin client start
- Verify the ID (UID/GID) mapping for user by running the following command using PowerShell:
Get-NfsMappedIdentity -AccountName scanuser -AccountType User UserIdentifier : 1001 GroupIdentifier : 1001 UserName : scanuser PrimaryGroup : SupplementaryGroups :