To configure the appliance backup retention settings
Once Safeguard for Privileged Passwords saves the maximum number of backup files, next time it performs a backup, it deletes the backup file with the oldest date.
Use the Certificate settings to manage the certificates used to secure One Identity Safeguard for Privileged Passwords. The panes on this page display default certificates that can be replaced or user-supplied certificates that have been added to Safeguard for Privileged Passwords.
Navigate to Administrative Tools | Settings | Certificates.
Where you manage the audit log signing certificate used to validate audit logs stored on an archive server.
|Certificate Signing Request||Where you can view and manage certificate signing requests (CSRs)|
|Sessions Certificates||Where you manage session certificates, including installing session certificates or creating CSRs to enroll a sessions certificate. If a Safeguard Sessions Appliance is joined to Safeguard for Privileged Passwords, assigning the certificate is handled via Safeguard for Privileged Sessions.|
|SSL Certificates||Where you manage SSL certificates, including installing SSL certificates or creating CSRs to enroll a public SSL certificate.|
|Trusted Certificates||Where you add and manage certificates trusted by Safeguard for Privileged Passwords, for example your company's root Certificate Authority (CA) certificate.|
One Identity Safeguard for Privileged Passwords ships with the following default certificates which are meant to be replaced:
A self-signed SSL certificate for HTTPS.
The name of the SSL certificate matches the hostname of the Safeguard for Privileged Passwords Appliance and uses the appliance's default IP addresses as the Subject Alternative Name (SAN).
A self-signed Certificate Authority (CA) certificate used by the embedded sessions module that generates server SSL certificates on-the-fly to secure RDP connections when an RDP session is initiated using Safeguard for Privileged Passwords. The "requester" must accept the certificate in order to launch a remote desktop session.
Safeguard for Privileged Passwords allows you to specify the security certificates to be used. When replacing or adding certificates, keep the following considerations in mind:
For imports, Safeguard for Privileged Passwords must access the relevant network resources to validate the CRL end points specified in the signed CSR.
For uploading certificates with private keys, Safeguard for Privileged Passwords supports .pfx ( or .p12) files which follow the PKCS #12 standard.
The Audit Log Signing Certificate pane on the Certificates setting page displays details about the certificate used to sign the audit log files saved to an archive server. The audit log signing certificate proves that the audit logs were created by and came from a particular Safeguard for Privileged Passwords cluster.
This signing certificate is used by administrators who want to verify that the exported Audit Log History originated from their Safeguard for Privileged Passwords cluster. This certificate's public key, in addition to the certificate's issuer, must be available if you wish to validate the signed audit log.
A common signature format is used. Each audit log archive is hashed using the SHA256 hash algorithm. The hash value is signed with the audit log signing certificate private key using RSA signing with PSS signature padding. The signature file is created using the same file name as the archive file but with the .sig file extension.
It is recommended to generate the CSR from within the Safeguard for Privileged Passwords user interface using the Add Certificate | Create Certificate Signing Request (CSR) option. For more information, see Creating a Certificate Signing Request for audit logs.
While Safeguard for Privileged Passwords ships a default audit log signing certificate, One Identity recommends that you load your own.
If you replace the default certificate with your own, the certificate must have the following:
You can have only one audit log signing certificate defined, which is used by all Safeguard for Privileged Passwords Appliances in the same cluster. That is, Safeguard for Privileged Passwords uses the default certificate or a certificate you uploaded to replace the default certificate.
Navigate to Administrative Tools | Settings | Certificates | Audit Log Signing Certificate. The following properties and controls are available to manage your audit log signing certificate.
Click Refresh to update the certificate displayed on the Audit Log Certificates pane.
The name of the subject (such as user, program, computer, service or other entity) assigned to the certificate when it was requested.
A unique hash value that identifies the certificate.
Click Add Certificate and select one of the following options to replace the default certificate with a new certificate:
Click Use Default to reset the certificate back to the default.