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 133: 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) |
| 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. |
The certificate infrastructure in One Identity Safeguard for Privileged Passwords consists of the following.
Replaceable certificates
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 signing certificate used to validate that archived audit logs were created by and came from Safeguard for Privileged Passwords.
User-supplied certificates
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
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 (SPP) cluster.
Define an audit log signing certificate
You can have only one audit log signing certificate defined, which is used by all Safeguard for Privileged Passwords Appliances in the same cluster. A default audit log signing certificate is supplied, however it is recommends that you load your own. If you do not upload a certificate, the default is used.
Generate a Certificate Signing Request (CSR)
Once the audit log signing certificate is defined, it is recommended you generate the Certificate Signing Request (CSR) using Create Certificate Signing Request (CSR) . The administrator will have a copy of the public key which will be used to verify the validity of the archived audit logs.
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.
How to use the signing certificate
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.
The certificate's public key and the certificate's issuer, must be available to validate the signed audit log.
- Get the audit log public certificate. See the following:
- If you are using your own PKI, the public certificate should be available
- Get the public certificate in Base64 format from the SPP API at:
GET /AuditLog/Retention/SigningCertificate
- If the public certificate is obtained from the API, save the Base64 data to cert.pem
- Use openssl to convert the pem file to a public key file.
- openssl x509 -pubkey -in cert.pem -noout > cert.pub
- Use openssl to verify that the audit log file has been signed and the contents are valid.
- openssl dgst -sha256 -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 -signature <signature-file>.sig -verify cert.pub <audit-log-file>
Managing audit log signing certificates
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 134: Audit Log Certificates: Properties
 Refresh |
Click Refresh to update the certificate displayed on the Audit Log Certificates pane. |
| Subject |
The name of the subject (such as user, program, computer, service or other entity) assigned to the certificate when it was requested. |
| Thumbprint |
A unique hash value that identifies the certificate. |
| Add 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)
|
| Use Default |
Click Use Default to reset the certificate back to the default. |
It is recommended that you not use the default certificate provided with Safeguard for Privileged Passwords. Instead, replace it with another certificate with a private key.
To replace the default certificate with your own, the certificate must have the following:
- Enhanced Key Usage extension with the Server Authentication (1.3.6.1.5.5.7.3.1) OID value.
- Digital Signature key Usage extension with the Server Authentication (2.5.29.37.3) OID value.
For uploading certificates with private keys, Safeguard for Privileged Passwords supports .pfx ( or .p12) files which follow the PKCS #12 standard.
To install an audit log signing certificate
- Navigate to Administrative Tools | Settings | Certificates | Audit Log Signing Certificate.
-
Click the Add Certificate button for the sessions certificate to be replaced. Select the appropriate option:
- Install Certificate generated from CSR
- Install Certificate with Private Key
- Browse to select the certificate file (.pfx file) and click OK.
- Once installed, this new certificate will replace the default certificate listed on the Audit Log Signing Certificates pane.
