FTPS can protect the login and still leave the file transfer exposed
FTP with TLS is usually described as a secure version of FTP, but the control channel and the data channel are separate. RFC 4217 defines extensions that let a client negotiate TLS with AUTH TLS , set protection with PBSZ and PROT , and protect subsequent commands and transfers. A service that upgrades the login but leaves the data connection in cleartext has not secured the file contents.
Use explicit TLS with verified certificates
Explicit FTPS starts with a normal control connection and then requests TLS. That makes the greeting and capability negotiation visible before the protected session begins, which is not the same as an end-to-end encrypted protocol. The client should verify the server certificate and hostname instead of accepting any certificate presented on the FTP port.
Require protected data connections for file contents. Review whether PROT P is mandatory and whether the server falls back to clear data for older clients.…