Managed File Transfer Glossary

FTPS file transfer is a secure extension of the file transfer protocol (FTP) that incorporates transport layer security (TLS) over the standard control and data channels. Clients and servers can negotiate explicit TLS on port 21 or use implicit TLS on port 990 with X.509 certificates to verify identity. Encryption masks credentials and payloads from interception and tampering so organizations can satisfy data security requirements from regulations such as HIPAA, GDPR and SOX requirements while keeping familiar file transfer operations in place.

File transfer protocol (FTP) servers with Pretty Good Privacy (PGP) encryption protect files at rest and in motion. Data is packaged into PGP-encrypted archives before transmission, then moved over FTP or secure variants like FTPS or SFTP and decrypted at the client destination. This approach lets organizations maintain familiar FTP workflows while adding strong public key encryption, signing and integrity checks that meet compliance demands across regulated industries.

A file transfer protocol (FTP) server is network software used to negotiate data and file transfer requests between clients and data storage. It publishes directories, enforces user permissions and supports secure file transfer variants such as FTPS and SFTP. Organizations deploy FTP servers to automate bulk uploads, share large files and integrate legacy workflows with modern encryption and auditing controls.

FTP secure (also known as FTP over SSL or FTPS) secures traditional file transfer protocol (FTP)-based sessions by adding transport layer security (TLS) encryption to protect credentials and data as they move between clients and servers. FTPS can operate in explicit mode, where the TLS handshake starts after the USER command, and implicit mode, which upgrades the connection immediately upon connection. IT teams often choose FTPS to support legacy FTP workflows while meeting compliance rules for data security.

A file transfer protocol (FTP) port is the numbered gateway that carries protocol traffic between an FTP client and an FTP server. By default, port 21 handles the control channel that exchanges login credentials and commands, while port 20 or a negotiated high port carries file data in active or passive mode. Administrators can, however, remap, restrict, forward or monitor their FTP ports to meet firewall rules and security policies.

FTP over SSL, also known as FTP secure or FTPS, secures traditional FTP-based sessions by encrypting control and data channels with transport layer security (TLS) or its predecessor SSL. The method adds improved authentication through digital certificates and supports explicit or implicit security modes to help organizations meet data security mandates while using familiar FTP commands.

File transfer protocol (FTP) file transfer is the process of moving files between a client and a server over TCP/IP using the FTP protocol. FTP commands allow users to upload, download, manipulate files and view directory contents. FTP supports user authentication, passive or active ports, binary or ASCII data types and resume capability. However, the protocol lacks native encryption and has largely been deprecated in favor of FTPS or SFTP for secure workflows.

Federal Information Processing Standards (FIPS) compliant means that a hardware component or software application, such as a file transfer server, uses cryptographic modules validated by NIST’s Cryptographic Module Validation Program (CMVP) to protect its systems and data. FIPS-compliant systems receive a third-party validation that confirms that their algorithms, key management and physical protections meet FIPS 140-2 or 140-3 standards for handling sensitive but unclassified data. In managed file transfer (MFT) and file transfer protocol (FTP) software, FIPS compliance ensures SFTP, FTPS and HTTPS services rely on tested cryptography libraries, which helps regulated organizations meet federal security mandates.

Federal Information Processing Standard (FIPS) publications set U.S. government cybersecurity standards for data encryption. Publication 140-3 establishes functional requirements and an accreditation program for cryptographic modules that replaces the prior FIPS 140-2 and mirrors global rule ISO/IEC 19790:2012. Federal agencies, their contractors, their service providers and any other organization that handles sensitive data or protected information in the administration of a federal program must be FIPS compliant.

FIPS stands for Federal Information Processing Standard. These publications list rules for keeping government data secure. FIPS 140-2 gives the steps for testing cryptographic tools made by private sectors. It checks if those tools meet federal security rules. This version of the standard will stay in use until September 2026. After that, FIPS 140-3 will replace it.

File transfer protocol (FTP) is a largely deprecated method that organizations used to exchange files over a TCP/IP network. The protocol allows users to upload, download, delete or change files on remote systems, but it does not encrypt exchanged credentials or data. As such, secure options like FTPS and SFTP have replaced FTP for most file transfer requirements.