CFT file encryption and decryption
While CFT ensures all data is encrypted at-rest and in-transit by default, you can enable PGP or SLIFT for an additional layer of end-to-end security. This ensures that only the intended recipient can access the file contents, even outside of the CFT environment.
Understanding the encryption and decryption flow
This flow describes how CFT will handle encryption and decryption in a transfer.
Sender → Decrypt (if enabled) → Scan → Encrypt (if enabled) → Receiver
PGP vs SLIFT
PGP is the modern industry standard and is recommended over SLIFT. SLIFT should only be used if you cannot use PGP keys or have a specific use case that requires it — PGP is the default recommended option.
If you’re ready to learn more, refer to the following sections:
Signature verification
In addition to encryption, CFT provides signature verification to check the authenticity of the sender. Currently, only PGP type is supported. For more details, refer to File signature verification.
