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
- Smart card or digital certificate
- Single Sign-On (SSO)
- Enhanced Auditing
- 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
- 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
- Configuring 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
- Command line interface (CLI) commands
- 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
- Backup anomaly detection
- Section IV. Malware scanning
Anomaly configuration to enable automatic scanning
The anomaly detection process can trigger malware scan for those anomalies that have high severity. Use the configuration file on the primary server to do the required settings.
See Prerequisites for a scan host.
To enable automatic malware scan for the images on which an anomaly was detected
- Create the anomaly_config.conf configuration file on the primary server on the given location:
On Windows : Install_Path\NetBackup\var\global\anomaly_detection
On UNIX : /usr/openv/var/global/anomaly_detection
- Add the following contents in the anomaly_config.conf configuration file:
#Use this setting to start malware scan on anomaly detected image automatically.
[AUTOMATED_MALWARE_SCAN_SETTINGS]
ENABLE_AUTOMATED_SCAN=1
# Enable all clients. In this case pool mentioned SCAN_HOST_POOL_NAME will be used for clients not mentioned
# under batch
ENABLE_ALL_CLIENTS=1
SCAN_HOST_POOL_NAME=<scan_host_pool_name> # Default pool name
#Use specific pool for mentioned clients
NUM_CLIENTS_BATCH_SPECIFIED=2
ENABLE_SCAN_ON_SPECIFIC_CLIENT_1=client1,client2
SCAN_HOST_POOL_NAME_1=<scan_host_pool_for_batch_1>
ENABLE_SCAN_ON_SPECIFIC_CLIENT_2=client3,client4
SCAN_HOST_POOL_NAME_2=<scan_host_pool_for_batch_2>
- Note that SCAN_HOST_POOL_NAME is a mandatory field.
For the ENABLE_SCAN_ON_SPECIFIC_CLIENT_n option, you should specify complete client names.
- Ensure that all settings are under [AUTOMATED_MALWARE_SCAN_SETTINGS]. Review the following descriptions of the settings:
ENABLE_AUTOMATED_SCAN=1
Starts malware scan on anomalies with high score.
ENABLE_ALL_CLIENTS=1
Enable all clients for scan. If this value is 0, scanning happens only on the clients that are mentioned for the following option:
ENABLE_SCAN_ON_SPECIFIC_CLIENT_<Batch_Number>
NUM_CLIENTS_BATCH_SPECIFIED=<batches> - This option specifies the number of batches for different scan host pool. For example, if you want to use a specific scan host pool for a set of clients, use this setting.
- Do the following to automatically trigger malware scan for various severity levels of anomalies:
For low severity anomaly, set the TRIGGER_SCAN_FOR_LOW_SEVERITY option as follows:
TRIGGER_SCAN_FOR_LOW_SEVERITY=1
For medium severity anomaly, set the TRIGGER_SCAN_FOR_MEDIUM_SEVERITY option as follows:
TRIGGER_SCAN_FOR_MEDIUM_SEVERITY=1
To automatically trigger malware scan for the anomaly score that is greater than or equal to the given value, set the TRIGGER_SCAN_FOR_SCORE_GREATER_THAN option to a positive value.
For example:
TRIGGER_SCAN_FOR_SCORE_GREATER_THAN=2.5