• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

PCI Compliance

E

EdwardDekker

Guest
Hi,

I want to ask the development team of Parallels to make all of the new installations of Plesk PCI Compliance ready.
Please delete ciphers below 128-bit encryption and disable SSLv2 by default when Plesk will be installed or updated.

Kind of regards,
Edward
 
Hello Edward,

We have a guide and a tool to enable PCI compliant mode in Plesk. Please checkout our documentation. This cannot be a default option, as PCI compliance involves certain restrictions which aren't good for everyone.

Regards
 
Hello Sergey,

Yes i know that i could be using the manual for the PCI compliance that i can use to secure the Plesk installation.
But i want to suggest that Parallels disable the weak and old ciphers below 128 bit.

Edward
 
Last edited by a moderator:
You must log in or register to reply here.

Similar threads

O
Question OpenLitespeed extension for plesk
Replies
2
Views
3K
Ohya
O
T
Question Need clarification on disabling ProFTPD in Plesk
Replies
1
Views
2K
scsa20
scsa20
ModulesGarden
Input Plesk Extended module now ready for the next-gen WHMCS 9.0!
Replies
0
Views
2K
ModulesGarden
ModulesGarden
A
Issue Hostname and subscription with same domain name - SSL issues
Replies
7
Views
4K
Andrea Bampi
A
TorbHo
Question New password hashing option for email accounts
2
Replies
24
Views
11K
Tobias Sorensson
T
Back
Top