FTP sends files without native encryption, which leaves usernames, passwords, and content vulnerable during transit. SFTP uses SSH to encrypt the session and support authenticated transfer, making it far better suited to mainframe environments that move sensitive or regulated data. The key distinction is that SFTP protects both confidentiality and integrity while FTP does not.
Why FTP and SFTP Behave Differently on Mainframe Transfers
FTP and SFTP solve the same business problem, moving files between systems, but they do it with very different security properties. On mainframes, that difference matters because transfers often carry payroll, account, batch, or operational data. FTP exposes the session contents to anyone who can observe the network path, while SFTP wraps the transfer in SSH protection.
That makes SFTP the safer default when the file itself, the login credentials, or the integrity of the transfer must be protected. In practice, the protocol choice is not just about connectivity, it is about whether the transfer path can tolerate exposure or must preserve confidentiality end to end.
What FTP Leaves Exposed, and What SFTP Adds
FTP was designed for simple transport, not for secure transport. It does not natively encrypt the control channel or the data stream, so credentials and file contents can be intercepted or altered in transit if the network path is not otherwise protected. That is why plain FTP is a poor fit for sensitive mainframe workloads, even when the source and target systems themselves are well governed.
SFTP uses SSH to authenticate the session and encrypt traffic while the transfer is in flight. That gives you confidentiality, integrity, and a stronger trust boundary for the exchange itself. It also changes the operational model: instead of relying on the surrounding network to be trustworthy, you rely on authenticated, encrypted transport that is much more suitable for cross-zone, partner, or regulated transfers.
Why the Difference Matters in Mainframe Operations
Mainframe file transfers are often part of batch processing, partner exchange, or downstream processing chains, so the protocol choice affects more than a single hop. If FTP is used, the exposure is not limited to the file content, because usernames and passwords can also be captured and reused. If SFTP is used, the transfer is better protected against passive interception and tampering, which reduces the blast radius of a network observation point or an untrusted intermediary.
That distinction becomes especially important where the transfer carries regulated records, privileged job inputs, or files that could influence production processing. A secure protocol does not fix poor access governance by itself, but it does remove one of the most common weaknesses in legacy file movement, unprotected transit.
Risk and Threat Considerations
FTP’s main risk is exposure of both secrets and payloads during transit, which creates easy opportunities for sniffing, replay, and unauthorized reuse of credentials. It also makes integrity harder to trust, because an attacker who can influence the path may be able to observe or modify what is sent.
Failure mechanism: The transfer channel is not encrypted, so a passive observer or an intervening system can capture usernames, passwords, and file content, then reuse or alter them.
Impact: The result can be credential compromise, data disclosure, corrupted transfers, and a wider incident if stolen credentials are accepted elsewhere in the environment.
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.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | FTP and SFTP differ in how credentials are protected in transit. |
| SC-8 — Transmission Confidentiality and Integrity | The core difference is whether file transfer traffic is encrypted in transit. | |
| Recommendation — Protect transfer credentials with managed rotation and transmission safeguards. Use encrypted transport to preserve confidentiality and integrity during transfer. | ||
| CIS Controls v8 | CIS-3 — Data Protection | Mainframe transfers often move sensitive data that should not traverse in cleartext. |
| Recommendation — Encrypt sensitive data in transit and restrict cleartext transfer protocols. | ||
| ISO/IEC 27001:2022 | A.8.24 — Use of cryptography | SFTP relies on cryptography to secure transfer sessions over untrusted networks. |
| Recommendation — Require cryptographic protection for file transfers carrying sensitive information. | ||
Practitioner Guidance
What to verify: Confirm whether any mainframe transfer path still uses FTP for sensitive data, partner exchange, or automated batch feeds. If it does, treat that as a transport risk, not just a legacy compatibility choice.
Decision rule: If the transfer carries anything confidential, regulated, or operationally sensitive, prefer SFTP or another encrypted transfer mechanism over FTP. If a legacy endpoint cannot yet be changed, require compensating controls around the path, the account, and the file contents rather than assuming the network is safe.
What practitioners underestimate: The security issue is not only the file, it is also the authentication material used to reach the file endpoint. Once those credentials are exposed, the transfer mechanism can become an entry point for broader misuse.
Practitioner takeaway: For mainframe file transfer, the right question is whether the protocol protects the session itself, because that determines whether confidentiality and integrity survive the journey, not just whether the file arrives.
Related resources from NHI Mgmt Group
- Guide: Mainframe Identity and RACF Security Guide
- SFTP (SSH File Transfer Protocol)
- How should organisations secure mainframe file transfers when FTP is still in use?
- What breaks when organisations keep using plaintext FTP for sensitive transfers?
- Why do AI prompts create more data loss risk than traditional file transfers?
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org