Hi all!
For Monday's #ImpervaInsights I wanted to share with you a frequently asked question our Customer Success team recieves:
We are about to migrate a client of ours over to Imperva Cloud WAF, however they are querying why a wildcard certificate is generated for their domain instead of just the full domain? I think they are wary of a certificate existing for their entire domain instead of just the domain we host for them.
What do our product experts have to say?
The reason why we use a wildcard certificate is to allow you to add new sub-domains to the same generated certificate without going through the validation process once again and to create a new certificate to each new sub-domain that was added.
When we generate a certificate, it is a wildcard certificate, and two SANs for the naked domain and for the wildcard (sub-domain, including the full domain). Thus, you can inform your client that they have no reason to be worried, because both domains will be protected under the same certificate.
What additional questions have you recieved from clients or fellow teammates when migrating to Cloud WAF?
#CloudWAF(formerlyIncapsula)#AllImperva------------------------------
Christopher Detzel
Community Manager
Imperva
Dallas TX
------------------------------