• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

PCI Scan Fail : Apache 2.2.3 - Plesk V 9.3.0

psingh

Basic Pleskian
Dear Friends,

Did any once come across this before.. I am having PCI Compliance problem with my server :

Current : Apache 2.2.3 - Plesk V 9.3.0
suggested : Apache 2.2.16 or higher..


However, i don't see any update available in Plesk Control panel..

Did anyone come across this problem, to become PCI Compliance.

How do i go ahead with this upgrade... any help is appreciated..

Thank you,
PS
 
Last edited:
My server failed on this too, how did you resolve it?
 
I got around this issue by hiding the version number of the Apache the server is running by editing /etc/httpd/conf/httpd.conf configuration file using these commands:

ServerSignature Off
ServerTokens Prod

I now have another issue with openssh version, I have the most up to date but pci compliance thinks its vulnerable...
Is it possible to hide openSSH version number from pci compliance scan?
 
Last edited by a moderator:
Back
Top