The traditional FTP protocol sends commands and data in “the clear” over the network/internet. This FTP data could be intercepted by an attacker, which could then be viewed and altered before sending it on to the receiver.
If you are sending sensitive data over the internet, then you may want to consider the FTPS (FTP over SSL) protocol for securing data. The following image shows a model of the communications.
When the Project executes, the Job Log will contain the HTTP Response Body from the DLP server that includes the status code. In this example, the "Credit Cards.txt" file contains sensitive data and the Project failed when the error code was returned . In this example, the DLP server was configured to redact text which removed the sensitive information and replaced them with asterisks. The redacted version was returned in the encapsulated HTTP response body and can be saved to the job log or a file.
FTPS creates an encrypted tunnel between two computer systems and will protect against the following attacks:
IP spoofing, where a remote host sends out packets which pretend to come from another, trusted host
IP source routing, where a host can pretend that an IP packet comes from another, trusted host
DNS spoofing, where an attacker forges name server records
Interception of cleartext passwords and other data by intermediate hosts
Manipulation of data by attackers in control of intermediate hosts
FTPS uses a combination of
asymmetric
(public key) cryptology and
symmetric
cryptology to provide strong encryption and optimal performance.
Both the server and the client can be authenticated (trusted) through the use of X.509 Certificates. In other words, certificates will help ensure that each party is truly who they say they are.