NetBackup™ Web UI Administrator's Guide
- Introducing the NetBackup web user interface
- Section I. Managing security
- Monitoring and notifications
- Managing role-based access control
- Configuring RBAC
- Role permissions
- Global > NetBackup management
- Global > Security
- Global > Storage
- Global > NetBackup management
- Manage access
- Configure an external certificate for the NetBackup web server
- Security events and audit logs
- Managing security certificates
- Managing user sessions
- Managing master server security settings
- About trusted master servers
- Creating and using API keys
- Configuring authentication options
- Managing hosts
- Troubleshooting the web UI
- Section II. Managing storage and backups
- Configuring storage
- Managing protection plans
- Managing protection plans for Microsoft SQL Server
- Usage reporting and capacity licensing
- Configuring storage
- Section III. Veritas Resiliency Platform
- Section IV. Managing credentials
About NetBackup certificate deployment security levels
Security levels for certificate deployment are specific to NetBackup CA-signed certificates. If the NetBackup web server is not configured to use NetBackup certificates for secure communication, the security levels cannot be accessed.
The NetBackup certificate deployment level determines the checks that are performed before the NetBackup CA issues a certificate to a NetBackup host. It also determines how frequently the NetBackup Certificate Revocation List (CRL) is refreshed on the host.
NetBackup certificates are deployed on hosts during installation (after the host administrator confirms the master server fingerprint) or with the nbcertcmd command. Choose a deployment level that corresponds to the security requirements of your NetBackup environment.
Table: Description of NetBackup certificate deployment security levels
Security level | Description | CRL refresh |
---|---|---|
Very High |
An authorization token is required for every new NetBackup certificate request. | The CRL that is present on the host is refreshed every hour. |
High (default) |
No authorization token is required if the host is known to the master server. A host is considered to be known to the master server if the host can be found in the following entities:
| The CRL that is present on the host is refreshed every 4 hours. |
Medium | The certificates are issued without an authorization token if the master server can resolve the host name to the IP address from which the request was originated. | The CRL that is present on the host is refreshed every 8 hours. |