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
- Hardware Security Module (HSM) support in NetBackup
- Data at rest encryption security
- Ciphers used in NetBackup for secure communication
- FIPS compliance in NetBackup
- Disable FIPS mode for NetBackup
- Post-Quantum Cryptography (PQC) support in 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
Configuring NetBackup client as the scan host
NetBackup malware scanning feature requires configuration of an additional host (a scan-host).
Before configuring scan host ensure that the following prerequisites are met:
See Prerequisites for a scan host.
Configuring NetBackup client as the scan host
- Install NFS client by running the following command on PowerShell:
Install-WindowsFeature -Name NFS-Client
- Enable UID mapping by running the following commands on PowerShell to enable NFS user mapping:
PS C:\Users\Administrator> Set-NfsMappingStore -EnableUNMLookup $True -UNMServer localhost PS C:\Users\Administrator> nfsadmin mapping The following are the settings on localhost Mapping Server Lookup : Enabled Mapping Server : localhost AD Lookup : Disabled AD Domain
- Run the configuration script as follows:
For Linux: /usr/openv/netbackup/bin/goodies/nbscanhostconfigcmd -validate
For Windows: C:\Program Files\Veritas\NetBackup\bin\goodies\nbscanhostconfigcmd.exe" -validate
- Restart NFS client:
After updating
passwd
/group
files, restart NFS client service using the following commands: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 :
- Configure the Malware scanner tool (Microsoft Defender Antivirus).
If required user can use the PBX port communication feature for the communication between the primary server and the scan host.
Following are the steps required to set up PBX communication:
:
Using the following command stop the mqbroker service (or stop all services):
For Linux: /usr/openv/mqbroker/bin/nbmqbroker terminate
For Windows: C:\Program Files\Veritas\NetBackup\mqbroker\bin\nbmqbroker.exe -stop
Configure mqbroker using the following respective command:
For Linux: /usr/openv/mqbroker/bin/install/configureMQ -defaultPorts
For Windows: C:\Program Files\Veritas\NetBackup\mqbroker\bin\install\configureMQ.bat -defaultPorts
In the above commands,
-defaultPorts
sets the default port values for external and internal ports as follows:Default external port: 13781
Default internal ports: 13780, 13779, 13778
To set the port values other than the default values, see the options by running the following command:
For Linux: /usr/openv/mqbroker/bin/install/configureMQ --help
For Windows: C:\Program Files\Veritas\NetBackup\mqbroker\bin\install\configureMQ --help
Add the above configured external port to the configuration file.
Default: 13781
NB_MQBROKER_PORT = 13781
For Linux, add the entry in
bp.conf
file.For Windows, add DWORD entry in registry editor.
Using the following command start the mqbroker service (or start all services):
For Linux: /usr/openv/mqbroker/bin/nbmqbroker start
For Windows: C:\Program Files\Veritas\NetBackup\mqbroker\bin>nbmqbroker.exe -start
:
Stop all the services.
To use PBX port, add the entry in
bp.conf
file:SCAN_HOST_VIA_PBX = 1
For Linux, add the entry in
bp.conf
file.For Windows, add DWORD entry in registry editor.
Start all the services.
In case you happened to run the configure MQ command twice, the fix the issue using the following steps:
Delete the
/usr/openv/var/global/mqbroker/mqhome/.erlang.cookie
file.Configure the PBX connection again using the above mentioned steps.