Veritas 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
- API keys
- Auth.conf file
- Role-based access control (RBAC)
- 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 master 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 master server
- Verification points in a mixed environment with a Windows master 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 master 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
- 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 master 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
- About the Key Management Service (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
- NetBackup web services account
- Immutability and indelibility of data in NetBackup
Adding AD or LDAP domains in NetBackup
NetBackup supports Active Directory (AD) or Lightweight Directory Access Protocol (LDAP) domain users.
If an AD domain or an LDAP domain is added in NetBackup, the respective domain users can logon to a NetBackup master server and Security Administrator can assign role-based access control (RBAC) roles to these domain users.
See About role-based access control (RBAC) in NetBackup.
For more information about RBAC, see the NetBackup Web UI Administrator's Guide.
The following procedure describes how to add an existing AD or LDAP domain in NetBackup and authenticate the domain users to access NetBackup.
To add an AD domain or an LDAP domain in NetBackup
- Run the following command to add an AD domain or an LDAP domain in the NetBackup master server:
vssat addldapdomain -d DomainName -s server_URL -u user_base_DN -g group_base_DN [-f trusted_CA_file_name] [-t rfc2307 | msad | {-c user_object_class -a user_attribute -q user_GID_attribute -un user_display_name_attribute -ui user_ID_attribute[:value_type] -ud user_description_attribute -x group_object_class -y group_attribute -z group_GID_attribute -gn group_display_name_attribute -gi group_ID_attribute[:value_type] -gd group_description_attribute [-k DN | UID]]} [-b FLAT | BOB] -m admin_user_DN [-w admin_user_password] [-p SUB | ONE | BASE]
Note:
Ensure that the user name that is specified in the -m option has the required rights to query the AD or the LDAP server.
In case of LDAPS, if the Authentication Service (nbatd) does not trust the certificate authority (CA) that has signed the server's certificate, use the -f option to add the CA certificate in the nbatd trust store.
See Certificate authorities trusted by the NetBackup Authentication Service.
For more information about the vssat command, see the NetBackup Commands Reference Guide.
Contact your AD administrator for the correct values for these command-line options. The values may vary based on how your AD is setup.
An example to add an AD domain:
vssat addldapdomain -d domain1 -s ldap://domain1.veritas.com -u "CN=Users,DC=domain1,DC=veritas,DC=com" -g "CN=Users,DC=domain1,DC=veritas,DC=com" -t msad -m "CN=user1,CN=Users,DC=domain1,DC=veritas,DC=com" -b BOB
- Run the vssat validateprpl command on the master server to verify whether the specified AD or LDAP domain is successfully added or not.
validateprpl -p username -d ldap:domain_name -b localhost:1556:nbatd
An example to validate an AD or LDAP domain:
vssat validateprpl -p user1 -d ldap:domain1 -b localhost:1556:nbatd
The domain name must match the one that is used in the addldapdomain command option.
For more information about the vssat command, see the NetBackup Commands Reference Guide.
If the AD or LDAP domain is added and the vssat validateprpl or vssat validategroup command fails, you need to carry out certain troubleshooting steps to resolve the issue.
See Troubleshooting AD or LDAP domain configuration issues .