It is the responsibility of the Appliance Administrator to configure the maximum number of backup files you want Safeguard for Privileged Passwords to store on the appliance.
To configure the appliance backup retention settings
- Navigate to Administrative Tools | Settings | Backup and Retention | Safeguard for Privileged Passwords Backup Retention.
- Select the Enable Backup Retention check box.
- Enter the maximum number of backup files you want to store on the appliance.
- Click OK.
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.
It is the responsibility of the Appliance Administrator to manage the certificates used by Safeguard for Privileged Passwords.
Navigate to Administrative Tools | Settings | Certificates.
Table 131: Certificates settings
Audit Log Signing Certificate
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)|
||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. |
||Where you manage SSL certificates, including installing SSL certificates or creating CSRs to enroll a public SSL certificate. |
||Where you add and manage certificates trusted by Safeguard for Privileged Passwords, for example your company's root Certificate Authority (CA) certificate.|
The certificate infrastructure in One Identity Safeguard for Privileged Passwords consists of the following.
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.
- A signing certificate used to validate that archived audit logs were created by and came from Safeguard for Privileged Passwords.
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:
- Safeguard for Privileged Passwords supports Certificate Signing Requests (CSRs) to enroll any type of certificate. CSRs use the Public-Key Cryptography Standard (PKCS) #10 format.
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 that follow the PKCS #12 standard.
- For SSL certificates, Safeguard for Privileged Passwords allows you to upload or use a CSR to enroll multiple certificates that can then be applied to different appliances.
- Safeguard for Privileged Passwords provides an SSL certificate store that allows you to assign any uploaded or enrolled SSL certificate to any appliance.
- Prior to adding an asset that uses SSL server certificate validation, you must add the server's signing authority certificate to the Trusted Certificates store in Safeguard for Privileged Passwords
- For embedded sessions certificates, uploading a new certificate or using a CSR to enroll a new certificate will replace the default certificate supplied with Safeguard for Privileged Passwords.
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:
- Enhanced Key Usage extension with the Server Authentication (18.104.22.168.22.214.171.124.1) OID value.
- Digital Signature key Usage extension with the Server Authentication (126.96.36.199.3) OID value.
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.
Table 132: Audit Log Certificates: Properties
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:
- Install Certificate generated from CSR
- Install Certificate with Private Key
- Create Certificate Signing Request (CSR)
Click Use Default to reset the certificate back to the default.