Installing an SMTP certificate
It is recommended that you not use the default SMTP client certificate provided with Safeguard for Privileged Passwords.
To replace the default SMTP client certificate with your own, the certificate must have the following:
CSRs may be installed in the following formats.
- Install Certificate generated from CSR including:
- DER Encoded Files (.cer, .crt, or .der)
- PEM Encoded Files (.pem)
- Install Certificate with Private Key including:
- PKCS#12 (.p12 or .pfx)
- Personal Information Exchange Files (.pfx)
To install a SMTP signing certificate
- Go to SMTP Certificate:
- web client: Navigate to Certificates > SMTP Certificate.
The SMTP Certificate pane displays the following information for the SMTP certificates stored in the database.
-
Click the Add Certificate button for the SMTP certificate to be replaced. Select the appropriate option:
- Install Certificate generated from CSR
- Install Certificate with Private Key
- Browse to select the certificate file and click OK.
- Once installed, this new certificate will replace the default certificate listed on the SMTP Certificate pane.
To use the default certificate
- To use the default SMTP certificate provided with Safeguard for Privileged Passwords, go to SMTP Certificate:
- web client: Navigate to Certificates > SMTP Certificate.
- Click the Use Default button for the SMTP certificate to be replaced with the default.
- On the warning Use Default dialog, type in the word Default to confirm you will be returning to the default certificate.
- Click OK.
SSL/TLS Certificates
Safeguard for Privileged Passwords enables an Appliance Administrator to upload SSL certificates with private keys or enroll SSL certificates via a CSR.
Initially, the default self-signed SSL certificate used for HTTPS is listed and assigned to the appliance. This default certificate is not a trusted certificate and should be replaced.
Go to the following selection, based on your client:
- web client: Navigate to Certificates > SSL/TLS Certificates.
To display the following information for the SSL/TLS certificates, select a certificate.
Table 30: SSL Certificates: Properties
Subject |
The name of the subject (such as user, program, computer, service, or other entity) assigned to the certificate when it was requested. |
Appliances |
Lists the name of the appliance to which the certificate is assigned. |
Issued By |
The name of the certificate authority (CA) that issued the certificate. |
Thumbprint |
A unique hash value that identifies the certificate. |
Alternate DNS Names |
Additional or alternate host names (such as, sites or common names) that were specified when the certificate was requested.. For more information, see Creating an audit log Certificate Signing Request.. |
Alternate IP Addresses |
Additional or alternate host names (such as, IP addresses or common names) that were specified when the certificate was requested. For more information, see Creating an audit log Certificate Signing Request.
For the default self-signed SSL certificate, the name and IP address of the appliance is used. |
Invalid Before |
A start date and time that must be met before a certificate can be used. |
Expiration Date |
The date and time when the certificate expires and can no longer be used. |
Use these toolbar buttons to manage SSL certificates.
Creating an SSL/TLS Certificate Signing Request
When creating a CSR, you uniquely identify the user or entity that will use the requested certificate. Safeguard for Privileged Passwords allows you to upload or enroll SSL certificates using CSRs. Once uploaded or enrolled, the SSL certificate is added to the SSL certificate store allowing you to assign it to one or more Safeguard for Privileged Passwords Appliances.
To create a CSR for SSL
- Go to the following selection, based on your client:
- web client: Navigate to Certificates > SSL/TLS Certificates.
- Click Add Certificate and select Create Certificate Signing Request (CSR).
- In the Certificate Signing Request dialog, enter the following information:
-
Subject (Distinguished Name): Enter the distinguished name of the person or entity to whom the certificate is being issued in the proper format like: cn=common name,ou=organizational unit,o=organization. Using the format example, cn=sam doe,ou=marketing,o=mycompany. Maximum length is 500 characters.
- Click Use Distinguished Name Creator to create the distinguished name based on your entries in Fully Qualified Domain Name (required), Department, Organization, City/Locality, State/County/Region, and Country.
-
Subject Alternate Names (DNS): Optionally, enter the Data Source Name (DNS) name of the server that will be protected by this certificate. For example, this might be the DNS names of all of the appliances in the Safeguard for Privileged Passwords cluster.
If the DNS name changes, you must generate a new certificate.
-
Subject Alternate Names (IP Address): Optionally, enter the IP addresses of the server that will be protected by this certificate. For example, this might be the IP addresses of all the appliances in the Safeguard for Privileged Passwords cluster.
If the IP address changes, you must generate a new certificate.
-
Key Size: Select the bit length of the private key pair. The bit length determines the security level of the SSL certificate. A larger key size is more secure but encryption is slower.
-
Click OK. You are prompted with a message like: Please save and submit the following Certificate Signing Request to a Certificate Authority (CA).
- Click Save to save the CSR to a file. If you do not save the CSR, you will have to generate another one.
- In the Certificate Signing Request pane, click Refresh to update the list of certificates added.
Installing an SSL/TLS certificate
To install an SSL/TLS certificate, the certificate must have at least the following:
To install an SSL certificate
- Go to the following selection:
- web client: Navigate to Certificates > SSL/TLS Certificates.
- Click Add Certificate and select Upload Certificate.
- Browse and select the certificate file then click Open.
-
On the dialog box, enter the case sensitive passphrase to import the certificate. If the certificate does not have a private key passphrase, leave the field empty and click OK.
-
After the certificate has been uploaded, assign the certificate to one or more appliances. For more information, see Assigning an SSL/TLS certificate to appliances..
You may also upload the certificate's root CA to the list of trusted certificates. For more information, see Trusted CA Certificates..
|
Caution: Improper access to the private SSL key could compromise traffic to and from the appliance. For the most secure configuration, create a Certificate Signature Request (CSR) and have it signed by your normal signing authority.
Then use the signed request as your Safeguard for Privileged Passwords SSL Webserver Certificate. This way, no administrator will have access to the private SSL key that is used by Safeguard for Privileged Passwords and the traffic will be secure. |