• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

PCI Compliance - Panel Self-signed certificate

ShotgunFront

New Pleskian
Hi,

We are running a server with Plesk on and trying to pass a PCI scan.

This scan has an issue with Plesk's self signed SSL certificate.

Whilst Plesk should not enter into the remit of the PCI scan because it is accessible from the domain we are getting scanned at port 8443 it is showing up.

I see two options - firstly, we could actually use a valid SSL for Plesk but I dont see how, because we have multiple domains on this server, so can't specify a single domain to purchase the SSL for..

..The other thing is that this domain doesnt need access to plesk via port 8443. We access Plesk by using our servers IP with the port on the end - is there a way we could stop the domain being able to access this port, which would stop the PCI scanner accessing it?


Thanks,
Tim
 
Back
Top