Veritas NetBackup™ 8.0 Security and Encryption Guide
- Increasing NetBackup security
- About NetBackup security and encryption
- NetBackup security implementation levels
- World-level security
- Enterprise-level security
- Datacenter-level security overview
- NetBackup Access Control (NBAC)
- Combined world, enterprise, and data center levels
- NetBackup security implementation types
- Operating system security
- NetBackup security vulnerabilities
- Standard NetBackup security
- Media Server Encryption Option (MSEO) security
- Client side encryption security
- NBAC on master, media server, and graphical user interface security
- NBAC complete security
- All NetBackup security
- Security deployment models
- Workgroups
- Single datacenters
- Multi-datacenters
- Workgroup with NetBackup
- Single datacenter with standard NetBackup
- Single datacenter with Media Server Encryption Option (MSEO)
- Single datacenter with client side encryption
- Single datacenter with NBAC on master and media servers
- Single datacenter with NBAC complete
- Single datacenter with all security implemented
- Multi-datacenter with standard NetBackup
- Multi-datacenter with Media Server Encryption Option (MSEO)
- Multi-datacenter with client side encryption
- Multi-datacenter with NBAC on master and media servers
- Multi-datacenter with NBAC complete
- Multi-datacenter with all NetBackup security
- Port security
- About NetBackup TCP/IP ports
- About NetBackup daemons, ports, and communication
- Standard NetBackup ports
- NetBackup master server outgoing ports
- NetBackup media server outgoing ports
- NetBackup enterprise media management (EMM) server outgoing ports
- Client outgoing ports
- Windows administration console and Java server outgoing ports
- Java console outgoing ports
- About MSDP port usage
- About Cloud port usage
- Additional port information for products that interoperate with NetBackup
- About communication and firewall considerations
- Ports required to communicate with backup products
- Web browser to NetBackup Web GUI connection
- About NetBackup user interface and NetBackup server software communication
- About NetBackup server to NetBackup master server (NBSL) communication
- About SNMP traps
- About communication between NetBackup and Sybase database communication
- About email communication in NetBackup
- About configuring ports
- Enabling or disabling random port assignments
- Specifying firewall connection options on a NetBackup server or client
- Specifying firewall connection options for destination computers from a source computer
- Editing port information in configuration files
- Updating client connection options
- Updating port settings for the Media Manager in the vm.conf file
- Port requirements for NDMP backups
- Known firewall problems encountered when using NetBackup with third-party robotic products
- Auditing NetBackup operations
- About NetBackup auditing
- Viewing the current audit settings
- Configuring auditing on a NetBackup master server
- User identity in the audit report
- About Enhanced Auditing
- Enabling Enhanced Auditing
- Configuring Enhanced Auditing
- Disabling Enhanced Auditing
- Auditing host property changes
- Retaining and backing up audit trail records
- Viewing the audit report
- Using the command line -reason or -r option
- nbaudit log behavior
- Audit alert notification for audit failures
- Access control security
- NetBackup Access Control Security (NBAC)
- About using NetBackup Access Control (NBAC)
- NetBackup access management administration
- About NetBackup Access Control (NBAC) configuration
- Configuring NetBackup Access Control (NBAC)
- NBAC configuration overview
- Configuring NetBackup Access Control (NBAC) on standalone master servers
- Installing the NetBackup master server highly available on a cluster
- Configuring NetBackup Access Control (NBAC) on a clustered master server
- Configuring NetBackup Access Control (NBAC) on media servers
- Installing and configuring NetBackup Access Control (NBAC) on clients
- Establishing a trust relationship between the broker and the Windows remote console
- About including authentication and authorization databases in the NetBackup hot catalog backups
- NBAC configure commands summary
- Unifying NetBackup Management infrastructures with the setuptrust command
- Using the setuptrust command
- Configuring Access Control host properties for the master and media server
- Access Control host properties dialog for the client
- Troubleshooting Access Management
- Troubleshooting NBAC issues
- Configuration and troubleshooting topics for NetBackup Authentication and Authorization
- 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 the nbac_cron utility
- Using the nbac_cron utility
- Using the Access Management utility
- About determining who can access NetBackup
- Viewing specific user permissions for NetBackup user groups
- Granting permissions
- Authorization objects
- Media authorization object permissions
- Policy authorization object permissions
- Drive authorization object permissions
- Report authorization object permissions
- NBU_Catalog authorization object permissions
- Robot authorization object permissions
- Storage unit authorization object permissions
- DiskPool authorization object permissions
- BUAndRest authorization object permissions
- Job authorization object permissions
- Service authorization object permissions
- HostProperties authorization object permissions
- License authorization object permissions
- Volume group authorization object permissions
- VolumePool authorization object permissions
- DevHost authorization object permissions
- Security authorization object permissions
- Fat server authorization object permissions
- Fat client authorization object permissions
- Vault authorization object permissions
- Server group authorization object permissions
- Key management system (kms) group authorization object permissions
- Upgrading NetBackup Access Control (NBAC)
- Upgrading NetBackup when an older version of NetBackup is using a root broker installed on a remote machine
- Security certificates in NetBackup
- Overview of security certificates in NetBackup
- About the Security Management utilities
- About host name-based certificates
- About host ID-based certificates
- Web login requirements for nbcertcmd command options
- Using the Certificate Management utility to issue and deploy host ID-based certificates
- About certificate deployment security levels
- Automatic host ID-based certificate deployment
- Deploying host ID-based certificates
- Implication of clock skew on certificate validity
- Setting up trust with the master server (Certificate Authority)
- Deploying certificates from multiple masters
- Forcing or overwriting certificate deployment
- Retaining host ID-based certificates when reinstalling NetBackup on non-master hosts
- Deploying certificates on a client that has no connectivity with the master server
- About host ID-based certificate expiration and renewal
- Cleaning host ID-based certificate information from a host before cloning a virtual machine
- About reissuing host ID-based certificates
- About Token Management for host ID-based certificates
- 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
- Deploying a host ID-based certificates on inactive master server nodes
- Deploying a host ID-based certificate on a clustered NetBackup media server (upgrade only)
- Renewing a host ID-based certificate on a clustered NetBackup host
- About deploying a new host ID-based certificate
- Viewing certificate details for a clustered NetBackup setup
- Removing CA certificates from a clustered NetBackup setup
- Data at rest encryption security
- Data at rest encryption terminology
- Data at rest encryption considerations
- Encryption security questions to consider
- Comparison of encryption options
- About NetBackup client encryption
- Configuring standard encryption on clients
- Managing standard encryption configuration options
- Managing the NetBackup encryption key file
- About configuring standard encryption from the server
- Restoring an encrypted backup file to another client
- About configuring standard encryption directly on clients
- Setting standard encryption attribute in policies
- Changing the client encryption settings from the NetBackup server
- Configuring legacy encryption on clients
- About configuring legacy encryption from the client
- About configuring legacy encryption from the server
- Restoring a legacy encrypted backup created on another client
- About setting legacy encryption attribute in policies
- Changing client legacy encryption settings from the server
- Additional legacy key file security for UNIX clients
- Media server encryption
- Data at rest key management
- Federal Information Processing Standards (FIPS)
- About FIPS enabled KMS
- About the Key Management Service (KMS)
- Installing KMS
- Configuring KMS
- Creating the key database
- About key groups and key records
- Overview of key record states
- About backing up the KMS database files
- About recovering KMS by restoring all data files
- Recovering KMS by restoring only the KMS data file
- Recovering KMS by regenerating the data encryption key
- Problems backing up the KMS data files
- Solutions for backing up the KMS data files
- Creating a key record
- Listing keys from a key group
- Configuring NetBackup to work with KMS
- About using KMS for encryption
- KMS database constituents
- Command line interface (CLI) commands
- CLI usage help
- Create a new key group
- Create a new key
- Modify key group attributes
- Modify key attributes
- Get details of key groups
- Get details of keys
- Delete a key group
- Delete a key
- Recover a key
- About exporting and importing keys from the KMS database
- Modify host master key (HMK)
- Get host master key (HMK) ID
- Get key protection key (KPK) ID
- Modify key protection key (KPK)
- Get keystore statistics
- Quiesce KMS database
- Unquiesce KMS database
- Key creation options
- Troubleshooting KMS
Implication of clock skew on certificate validity
When a master server issues a certificate, it determines for how long the certificate will be valid for the host to use. The master server sets the validity of the certificate based on its own time, recording two timestamps: Not before and Not after. The certificate is valid only between these two timestamps.
The clock on the master server and the clock on the host that will receive the certificate should be in sync so that the certificate is valid for as long as is expected, given the timestamps.
The hosts can reside in different time zones, as long as the clock on each host is set to the correct time for that host's timezone. As a general practice, NetBackup recommends using a service such as Network Time Protocol (NTP) to automatically keep all clocks on all hosts in the NetBackup domain synchronized.
If the clocks are not in sync, the difference can result in the following consequences:
If the host clock is ahead of the master server, the validity period of the certificate will be less than expected on that particular host. If the difference is extreme and the clocks vary by more than the certificate's validity period, it is possible that if the master server issued a fresh certificate, it could be treated as expired.
If the host clock is behind the master server, a fresh certificate issued by the master server could be considered as unusable by the host because the host considers the certificate as not yet valid.
To determine whether the master server clock and the host clock are in sync
- Run the following command on the host to determine whether the host clock is in sync with the master server clock:
nbcertcmd -checkClockSkew -server master_server_name
- If the clock skew on the host is causing a problem with the certificate validity, take corrective actions as necessary.
The command returns one of the following results:
If both clocks are in sync, the following displays:
The current host clock is in sync with the master server.
If the current host is behind the master server, the command reports the difference in seconds:
The current host clock is behind the master server by 36 seconds(s).
If the current host is ahead of the master server, the command reports the difference in seconds:
The current host clock is ahead of the master server by 86363 second(s).
If the command is run on the master server, the command skips the check and displays the following:
Specified server is same as the current host. Clock skew check is skipped.