• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Security Auditing on Pleak 8.4

F

fatangel

Guest
Hello,

We have a Unix server with Plesk 8.4 installed. We're currently working with SecurityMetrics to tighten the security of a website. Right now, they're complaining about the services on port 8443. Example:

Synopsis : The remote web server uses a version of PHP that is affected by multiple flaws.
Description : According to its banner, the version of PHP installed on the remote host is older
than 5.2.6.

As we understand it, the various services and modules for the Plesk Control Panel (on port 8443) work separately from the services and modules for customer websites (port 80); and thus, the security vulnerabilities of the control panel do NOT affect the security of the customer's website.

However, SecurityMetrics is refusing to listen to the explanation above.

1) Is our understanding of how the server works correct?
2) Can the above be explained in a different manner that will help them understand?
3) Beyond upgrading to Plesk 8.6 are there any other ways to work around the complaints?

thanks,

Ken
 
Back
Top