The Safeguard for Privileged Passwords web client allows you to generate a backup on a hardware appliance which can then be uploaded and restored on a Safeguard virtual machine.
IMPORTANT: Due to the potential security risk with migrating from a hardware appliance to a virtual machine, the Appliance Administrator making the request is required to contact One Identity Support as part of this process before they will be able to complete enabling this feature. This approval is indicated by the Not Authorized/Authorized indicator at the top of the Authorize VM Compatible Backups page.
IMPORTANT: You cannot upload a backup to a hardware appliance which was previously downloaded from hardware as VM compatible. Such a backup can only be uploaded to a Safeguard virtual machine.
IMPORTANT: This feature is not available on a replica within a cluster.
To authorize generating a hardware appliance backup for use on a virtual machine
- Navigate to
Backup and Retention > Authorize VM Compatible Backups.
-
In the Challenge Request User Identifier field, enter the name of the user requesting permission for the backup to be generated.
-
Click Generate Request.
NOTE: Only one challenge request can be active at a time. If there is a pending challenge request already active, you can cancel the active request by selecting the Invalidate Existing Challenge Request check box before generating a new request.
-
A Challenge Request text box will appear. This text box contains the information needed by One Identity to confirm the VM compatible backup authorization request is valid. Use one of the following options to copy the information:
-
Contact One Identity Support regarding your request to authorize the download of VM compatible backups from a hardware appliance. When requested, send the copied or downloaded challenge request to One Identity Support.
-
Once One Identity Support has confirmed the request, a challenge response will be sent back. This text needs to be copy/pasted or uploaded (using the Browse button) to the Challenge Response text box.
-
Click Verify Response to confirm the request as been approved.
Once confirmed, an Authorized indicator will be displayed at the top of the Authorize VM Compatible Backups page. The Download VM Compatible option will now be available through the 
button on the Backup and Restore page on hardware appliances. In order to download a VM compatible backup it must have been created with password or GPG public key protection settings.
You can use the Remove Authorization button to disable this feature. To reenable a new Challenge Request must be sent to One Identity Support.
Use the Certificate settings to manage the certificates used to secure 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 Certificate Signing Requests (CSRs) used by Safeguard for Privileged Passwords.
Go to Certificates:
web client: Navigate to 
Certificates.
Table 23: Certificates settings
|
Audit Log Signing Certificate |
Where you manage the audit log signing certificate used to validate audit logs stored on an archive server. When the audit log is exported, the log is signed with this certificate to ensure that it is legitimate and has not been tampered with after export. |
| Certificate Signing Request |
Where you can view and manage certificate signing requests (CSRs) that have been issued by Safeguard for Privileged Passwords. CSRs that may be created in Safeguard for Privileged Passwords include: Audit Log Signing Certificate, SMTP Client Certificate, SSL Certificates, or Syslog Client Certificates. |
|
Hardware Security Module Certificates |
Where you manage client and server Hardware Security Module certificates. These certificates are used for connecting to Hardware Security Module devices. |
|
SMTP Certificate |
Where you manage SMTP client certificates. |
| SSL/TLS Certificates |
Where you manage SSL/TLS certificates, including installing certificates or creating CSRs to enroll a public SSL/TLS certificate. This certificate is used to secure all HTTP traffic. |
|
Syslog Client Certificate |
Where you manage the syslog client certificate used to secure traffic between Safeguard for Privileged Passwords and the syslog server. |
| Trusted CA Certificates |
Where you add and manage certificates trusted by Safeguard for Privileged Passwordsand used to verify the chain of trust on certificates for various usages. For example , a trusted certificate may be your company's root Certificate Authority (CA) certificate or an intermediate certificate . |
You can create a certificate signing request (CSR) in Safeguard for Privileged Passwords. The private key is kept securely on the Safeguard for Privileged Passwords Appliance and is not released. The public key and details are in an encoded text file. Here is the process:
- Create a CSR through Safeguard for Privileged Passwords. See:
- Submit the encoded text file to a Certificate Authority (CA) to create an appropriate X509 certificate that is trusted by other entities trusting the CA.
- Install the certificate generated by the CA on Safeguard for Privileged Passwords where it is associated with the private key. See:
- If necessary, add the CA certification to Trusted Certificates in Safeguard for Privileged Passwords. For more information, see Trusted CA Certificates.
The certificate infrastructure in Safeguard for Privileged Passwords consists of the following.
Replaceable certificates
Safeguard for Privileged Passwords ships with the following default certificates which are untrusted and are meant to be replaced:
User-supplied certificates
You can 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 installing certificates generated with a CSR, Safeguard for Privileged Passwords supports DER Encoded Files (.cer, .crt, or .der) and PEM Encoded Files (.pem).
- For SSL/TLS 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/TLS certificate store that allows you to assign any uploaded or enrolled a certificate to any appliance.
- Consider if the server's signing authority certificate must be added to the Trusted Certificates store in Safeguard for Privileged Passwords. For example, prior to adding an asset that uses SSL/TLS server certificate validation, you must add the signing authority certificate to the Trusted Certificates store. Or, if you uploaded a syslog certificate with a private key, you may upload the certificate's root CA to the list of trusted certificates. For more information, see Trusted CA Certificates.
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. For more information, see Installing an audit log certificate.
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) . For more information, see Creating an audit log Certificate Signing Request.
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 must be available to validate the signed audit log and, in the case of a certificate chain, the certificate's issuer.
IMPORTANT: Starting with the 6.6 version of the Safeguard-ps PowerShell cmdlets, a new cmdlet called Test-SafeguardAuditLogArchive has been added. This cmdlet will verify all of the audit log files in the archived zip file in one command and show the results for each file. When running the cmdlet you are validating the signature of each individual log file within the zip file; you are not validating the signature of the zip file. See OneIdentity/safeguard-ps.
The following instructions are also provided should you wish to use OpenSSL or would like more information on what the PowerShell cmdlet does.
- 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>
Manage audit log signing certificates
Go to Audit Log Signing Certificate:
- web client: Navigate to Certificates > Audit Log Signing Certificate.
The following properties and controls are available to manage your audit log signing certificate.
Table 24: 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. |
| Use Default |
Click Use Default to reset the certificate back to the default supplied by Safeguard for Privileged Passwords. |
| 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)
|
