Veritas NetBackup™ Security and Encryption Guide
- Increasing NetBackup security
- Security deployment models
- Port security
- About NetBackup daemons, ports, and communication
- Additional port information for products that interoperate with NetBackup
- About configuring ports
- Auditing NetBackup operations
- Configuring Enhanced Auditing
- Access control security
- 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
- Configuring user groups
- About defining a user group and users
- Viewing specific user permissions for NetBackup user groups
- Security management in NetBackup
- About the Security Management utilities
- About audit events
- About host management
- Adding shared or cluster mappings
- 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 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
- Security certificate deployment in a clustered NetBackup setup
- About deployment of a host ID-based certificate on a clustered NetBackup host
- 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
- Data at rest key management
- 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
- Regenerating keys and certificates
- NetBackup web services account
Unifying NetBackup Management infrastructures with the setuptrust command
This is done automatically when the OpsCenter server name is provided during install time. If not, there is a command that adds OpsCenter server name to the NetBackup master server. That establishes the trust from the NetBackup side.
The Veritas products management servers need to communicate so that an administrator for one product has permission to administer another product. This communication ensures that application processes in one management server work with another server. One way of ensuring that communication is to use a common independent security server called a root broker. If all of the management servers point to a common root broker, the permission for each server is based on a common certificate. Another way of ensuring communication is to use the setuptrust command. This command is used to establish trust between the two management servers. The command is issued from the management server that needs to trust another management server. The security information is transferred from that host to the one requesting the trust establishment. A one-way trust is established. Setting up two way (mutual) trust is performed by issuing the setuptrust command from each of the two servers involved. For example, a NetBackup configuration may consist of one OpsCenter server (OPS) and three master servers (A, B, and C). Each of the master servers has connected to them the NBAC policies and management for the clients and the media servers.
The first step is to have the OpsCenter server (OPS) setup trust with each of the master servers (A, B, and C). This trust ensures that the Veritas OpsCenter server receives secure communications from each of the master servers, the clients and the media servers connected to each of the master servers. A sequence of these events is as follows:
The OPS sets up trust with master server A.
The OPS sets up trust with master server B.
The OPS sets up trust with master server C.
If Veritas OpsCenter is set up to perform actions on the individual master servers, a trust relationship needs to be set up from each of the master servers to the OpsCenter server (OPS). A sequence of these events is as follows. In this case, the setuptrust command is run six times.
The master server A sets up trust with Veritas OpsCenter server (OPS).
The master server B sets up trust with Veritas OpsCenter server (OPS).
The master server C sets up trust with Veritas OpsCenter server (OPS).
The Veritas OpsCenter server OPS sets up trust with master server A.
The Veritas OpsCenter server OPS sets up trust with master server B.
The Veritas OpsCenter server OPS sets up trust with master server C.
NetBackup and OpsCenter establish trust automatically. You may need to do these setuptrust operations manually with older NetBackup master servers. At the end of the NetBackup master server installation, there is a question on the OpsCenter host name. With that, the master server can initiate a two-way trust setup.