• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Help with the compliance with Trustwave

Andres1

New Pleskian
Hi guys im new here!

I only have a problem with the compliance and is with the FTP

This is the problem:

Vulnerability said:
Unencrypted
Communication Channel
Accessibility

CVSS Score said:

Severity said:

Compliance Status said:


Policy Violation

Port:
tcp/21
The service running on this port appears to make use of a
plaintext (unencrypted) communication channel. The PCI DSS
forbids the use of such insecure services/protocols. Unencrypted
communication channels are vulnerable to the disclosure and/or
modification of any data transiting through them (including
usernames and passwords), and as such the confidentially and
integrity of the data in transit cannot be ensured with any level of
certainty.

CVSSv2: AV:A/AC:H/Au:N/C:C/I:C/A:N
Service: ftp

Evidence:
Details: Unencrypted authentication is allowed prior to TLS
negotiation
AUTH TLS Supported: true
AUTH TLS Required: false
Command Sent: USER trustkeeper
Response Received: 331 Password required for trustkeeper

Remediation:
Transition to using more secure alternatives such as SSH instead
of Telnet and SFTP in favor of FTP, or consider wrapping less
secure services within more secure technologies by utilizing the
benefits offered by VPN, SSL/TLS, or IPSec for example. Also, limit
access to management protocols/services to specific IP addresses
(usually accomplished via a "whitelist") whenever possible.


Im use ProFTPD it was installed with plesk 12!

I only need fix this problem, this is the seventh time that i install plesk!


Thanks a lot!
 
Hello IgorG!

I use that guide but I don't understand well the part to ProFTPD!

When I make the steps, I can't connect to server anymore in with ftp!
 
Make sure that port 21 is open and not firewalled at least.
 
Hahahaha now i have problem with SMTP, IMAP and FTP i dont have any idea what happened!!
Contact Support Team in this case. I think that without investigating this issue directly on your server nobody on this forum can help you.
 
I recently went through the exercise of PCI compliance with Trustwave. First of all, you simply can't have the FTP port open or else you will fail the compliance check. SSH will also trigger complaints, which leaves out SFTP! So my solution was to disable FTP entirely and then to add a firewall rule restricting SSH to the IPs I use. Trustwave can't see SSH and therefore I pass. (Another advantage of this is that it shuts out the thousands of SSH hack attempts you'll get if you leave the port open.)

For mail, I had to make sure that IMAP required SSL. SMTP required SSL for authenticated users and relaying was disabled. It took me several iterations with courier and postfix (I ended up switching to dovecot for IMAP and am much happier with that.)
 
Back
Top