File Transfer Protocol

What Makes FTP Risky in Practice

File Transfer Protocol is simple and widely compatible, but its classic design assumes a trusted network. That assumption is the core security problem: usernames, passwords and file contents can travel in cleartext, so anyone with packet visibility may be able to read, replay or reuse them.

Because FTP separates control and data channels, it can also behave unexpectedly in firewalled or proxy-heavy environments. The protocol is still encountered in legacy estates, embedded systems and partner integrations, where operational convenience often outlasts the original security assumptions.

Exposure, Monitoring, and Legacy Dependencies

FTP exposure is usually discovered through asset inventory, external scan results, firewall rules and vendor documentation. The practical question is not only whether an FTP service exists, but whether it is reachable from untrusted networks, whether it still carries sensitive data, and whether a safer transfer method is available for the same workflow.

In mixed environments, the risk increases when FTP is used for scheduled batch jobs, partner exchanges or admin access. Those uses often become invisible over time, so a protocol that was meant for convenience can turn into a persistent weak point in the file-transfer chain.

Where organisations are standardising on safer transfer patterns, the surrounding Managed File Transfer (MFT) Security Guide is useful context for understanding how legacy file movement is hardened, monitored and governed.

Safer Replacement Patterns

For most business uses, FTP should be treated as a migration candidate rather than a long-term target. Secure replacements such as FTPS, SFTP or a managed file transfer platform reduce the chance that credentials or payloads can be intercepted in transit, and they make access control and logging much easier to enforce consistently.

Replacement is not only about encryption. It is also about stronger identity handling, tighter account scoping and better auditability around who can send or retrieve files. If the business process depends on anonymous or shared access, the protocol choice is often masking a larger governance problem.

The Secure File Transfer Buyers Guide helps frame the selection questions that matter when organisations move away from legacy file transfer protocols.

Why Protocol Choice Still Matters to Defenders

Defenders should care about FTP because it is both a security exposure and a visibility problem. If the protocol remains enabled, security teams need to know which systems still speak it, which credentials are in use, and whether file movement crosses networks where interception or tampering is plausible.

Protocol-level risk also matters because attackers often target the weakest transfer path first. A legacy file-transfer service can become a convenient foothold for credential theft, data theft or misuse of trusted exchange channels, especially when the service is reachable from the internet or tied to privileged automation.

Network teams often find it helpful to compare FTP with other risky or replacement protocols using the Network Ports and Protocols Security Guide, especially when deciding which services should be exposed, replaced or segmented.

For teams investigating whether file-transfer traffic is being used as a covert transport, MITRE ATT&CK T1071 Application Layer Protocol is a useful reference for understanding how adversaries abuse ordinary protocols for command-and-control or stealthy exfiltration.

Related resources from NHI Mgmt Group

• How does File Transfer Protocol over TLS work?
• What are the key File Transfer Protocol over TLS best practices?
• File Transfer Protocol Secure
• Trivial File Transfer Protocol (TFTP)