agradmin
asked on
Wilcard SSL certificate failing PCI scan
We recently upgraded the SSL certificate on our primary website to a wildcard certificate. The was to encompass our development and staging sites within the certificate and to reduce complexity/costs at the hosting site.
Now we are seeing a PCI scan failure - with the scanned URL (www.'domain.com') no longer matching the name on the certificate (*.'domain.com') the PCI scan engine is unable to trust the certificate. I have tried to dispute the PCI failure (as a false positive) but so far tis has been denied.
Other than reverting back to individual certificates does anyone out there have suggestions as to how to work around this? I can't believe we are the only company using wildcard certificates and it seems that if these diminish the level of trust then they may not be suited to transactional sites.
Thanks in advance.
Now we are seeing a PCI scan failure - with the scanned URL (www.'domain.com') no longer matching the name on the certificate (*.'domain.com') the PCI scan engine is unable to trust the certificate. I have tried to dispute the PCI failure (as a false positive) but so far tis has been denied.
Other than reverting back to individual certificates does anyone out there have suggestions as to how to work around this? I can't believe we are the only company using wildcard certificates and it seems that if these diminish the level of trust then they may not be suited to transactional sites.
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.