Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Cleartext FTP
Cyber Security

Cleartext FTP

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Cyber Security

Cleartext FTP is file transfer over the File Transfer Protocol without encryption for the control channel or the data channel. Usernames, passwords and transferred files can be read in transit, so it exposes credentials and content to interception on the network.

How Cleartext FTP Works

Cleartext FTP transfers files using the File Transfer Protocol without encrypting either the control channel or the data channel. That means the session is functionally usable for moving files, but the protocol itself does not protect what is said or sent between client and server. On untrusted networks, this design choice makes the communication readable to anyone who can observe traffic.

In practice, FTP separates commands from transferred content, so the protocol exposes more than just the file payload. Login dialogue, directory navigation, and transfer instructions can all be visible in transit, which is why cleartext FTP is usually treated as a legacy transport rather than a secure default.

Why Cleartext FTP Is Dangerous

The main weakness is not just that files can be intercepted, but that authentication material travels in the clear as well. If usernames and passwords can be captured, an observer may gain direct access to the file service, and the same exposure can affect any later activity that depends on those credentials.

This matters because file transfer is often used for business data, operational feeds, backups, or partner exchange. When the protocol offers no confidentiality, the security of the transfer depends entirely on the network path being trusted, which is a fragile assumption on shared, routed, wireless, or otherwise monitored infrastructure.

A secure file transfer design should use an encrypted alternative such as SFTP or FTPS, or a managed transfer platform that can enforce encryption, logging, and access control. Managed File Transfer (MFT) Security Guide and Secure File Transfer Buyers Guide both speak to the operational differences that matter when replacing legacy file transfer protocols.

How Organisations Check Exposure to Cleartext FTP

Exposure assessment starts with inventory. Organisations need to know where FTP is still enabled, which services depend on it, whether any external-facing endpoints accept FTP sessions, and whether any scripts, integrations, or partners still authenticate through it. Legacy file transfer often persists because it is embedded in automation rather than intentionally chosen.

Internet exposure is especially important because cleartext FTP becomes much riskier once it is reachable outside a tightly controlled internal segment. Teams should also review vendor guidance and asset ownership records, because FTP may appear on appliances, legacy servers, or shared platforms that are not obvious from central application inventories.

Operationally, the question is whether any business process still depends on a protocol that cannot protect credentials or content in transit. If so, the organisation has a visibility problem as much as a transport problem, because hidden FTP usage can survive long after teams believe it has been retired.

Safer Replacement Patterns and Control Expectations

The right replacement depends on the business use case, but the target state should preserve confidentiality, integrity, and accountability without forcing users back onto an obsolete protocol. For many environments, that means shifting to SFTP, FTPS, or a managed transfer service that can handle partner onboarding, audit logging, retention, and access review.

Cleartext FTP should be treated as a transitional exception only, not as an acceptable steady-state design. If a system still requires it, compensate by isolating the host, restricting network paths, limiting who can connect, and accelerating migration to an encrypted transfer method. Those controls reduce exposure, but they do not remove the core weakness of cleartext transport.

From a governance perspective, the important control decision is whether file transfer is being managed as part of a deliberate security architecture or tolerated as a legacy convenience. The difference shows up later in incident response, because encrypted alternatives preserve far more trust when a transfer workflow has to be investigated or rebuilt.

What To Do After Cleartext FTP Is Found

If cleartext FTP is discovered, the priority is to determine what credentials, files, and partner integrations may already have been exposed. That review should include configuration owners, service accounts or automation using the endpoint, and any records that would show whether the service was reachable from untrusted networks.

Then the organisation should plan migration to a secure transfer method and verify that the old service is disabled, not merely undocumented. Where replacement takes time, reduce the blast radius by constraining access, monitoring for unusual transfers, and ensuring that anyone who can still use the protocol is explicitly accountable for the risk.

Common misunderstanding: FTP is sometimes treated as harmless because it is familiar and functionally simple. In security terms, simplicity does not offset the fact that the protocol exposes both authentication and content to passive interception.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementCleartext FTP exposes credentials in transit, so authenticator lifecycle and protection materially apply.
SC-8 — Transmission Confidentiality and IntegrityFTP without encryption fails the core requirement to protect data and commands while traversing the network.
Recommendation — Replace exposed FTP credentials and manage rotation, storage, and reuse under IA-5. Use SC-8 to require encrypted transfer channels for file movement and credentials.
CIS Controls v8CIS-13 — Network Monitoring and DefenseCleartext FTP creates observable traffic that should be detected and reduced through network visibility controls.
Recommendation — Monitor for FTP use on the network and remove exposed cleartext transfer paths.
ISO/IEC 27001:2022A.8.24 — Use of cryptographyCleartext FTP is a transport choice that should be replaced with cryptographic protection for sensitive transfers.
Recommendation — Apply A.8.24 to require encryption for file transfer channels carrying sensitive data.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org