Any web page that transfers sensitive data to a server should be protected by a Secure Socket Layer (SSL) certificate. Whenever you see a small padlock on the left-hand side of your browser’s address bar, it tells you that this page is secured by an SSL certificate, and that the data you send from it to a data centre is fully authenticated and encrypted.
This is now a required standard by all major browsers, which is why we provide up to three single domain certificates to all Engaging Networks clients that can be used to protect their Engaging Networks web pages. However, you may also wish to handle your own security too, which is why we have the three installation options available:
Option 1 – We obtain a certificate and install it for you
We’ll provide you with an order form to fill out, and then once that’s completed we can take care of the rest for you. You’ll just need to be sure that you can approve the certificate order from one of the mailboxes below:
The cost for this is included in your Engaging Networks subscription, so there’s no additional invoicing or payments required.
Option 2 – purchase your own certificate and get a CSR from us
You can purchase your own certificate and send it securely to us, along with the associated private key so we can install it on our servers. Your Egnyte account is a perfect way to transfer these files securely – please don’t transfer the private key by email! If you need us to, we can generate a Certificate Signing Request (CSR) for your certificate vendor, so that they can produce the necessary certificate file for you. Contact the support team for more information.
Option 3 – you already have your own certificate you would like to use
Finally, if you have a certificate already, we can install that on our servers for you at no extra charge (again, this is covered in your subscription). As with option 2, we’d just need you to transfer the certificate and private key to us securely.
If you are using a secure certificate over https, you will need to create a secure HTML template. Please see the separate tutorial on setting up https templates.