Security Insights · Secure file transfer · 8 min read
Secure File Transfer vs Secure File Sharing: What's the Difference?
Secure file transfer vs secure file sharing: how SFTP, FTPS, HTTPS, AS2 and managed file transfer differ from end-to-end encrypted sharing and when to use each.
Secure file transfer and secure file sharing are often treated as the same thing, but they solve different problems. Transfer moves a file and protects it on the way. Sharing gives people controlled access to a file for as long as they need it, and can take that access away.
This guide explains each one, including managed file transfer (MFT), compares six common options and sets out how to choose.
What is the difference between secure file transfer and secure file sharing?
Secure file transfer moves a file from one system or person to another and protects it on the way, typically with SFTP, FTPS, HTTPS or AS2. Secure file sharing gives people ongoing, controlled access to files: permissions, expiry dates, revocation and a record of who opened what. Transfer ends at delivery; sharing continues after it.
After a transfer, the recipient holds their own copy, managed by their own systems. With sharing, the file stays where the sender put it, and the sender keeps deciding who can open it.
What is secure file transfer?
Secure file transfer moves a file between two systems, or between a person and a system, over an encrypted, authenticated connection. The common methods are:
- SFTP runs as a subsystem of Secure Shell (SSH), a protocol for secure remote login and other secure network services over an insecure network, standardized in RFC 4251 to RFC 4254.
- FTPS adds Transport Layer Security (TLS) to the older File Transfer Protocol, as described in RFC 4217.
- HTTPS upload sends a file through a web form, portal or API over TLS. TLS 1.3, defined in RFC 8446, is "designed to prevent eavesdropping, tampering, and message forgery." NIST's TLS guidelines, SP 800-52 Rev. 2, required US government TLS servers and clients to support TLS 1.3 by January 1, 2024.
- AS2, defined in RFC 4130, exchanges structured business data such as EDI or XML over HTTP. Messages are signed and encrypted with S/MIME, and the sender can request a signed receipt, a Message Disposition Notification (MDN), as evidence of delivery.
For ports, authentication and firewall differences between the first two, see SFTP vs FTPS.
What encrypted file transfer protects
Encrypted file transfer usually means encryption in transit. RFC 8446 describes TLS as a secure channel between two communicating peers, and SSH protects its session the same way. Once the file arrives, whether it's encrypted in storage depends on the receiving server. NIST's SP 800-53 Rev. 5 treats these as separate controls: SC-8 for transmitted information and SC-28 for information at rest. AS2 also encrypts each message, but the receiving AS2 system decrypts it on arrival.
What is managed file transfer (MFT)?
Managed file transfer is a product category, not a protocol, so features vary. An MFT platform usually runs transfers over the protocols above and adds:
- Scheduling and automation, with retries and alerts when a transfer fails.
- Central management of users, trading partners, keys and certificates.
- One place for transfer logs and reports.
Typical jobs include scheduled data feeds between systems, files exchanged with banks and payroll providers, and EDI with trading partners. An MFT server that stores files and can decrypt them is a target in its own right. In June 2023, CISA and the FBI reported that a ransomware group had exploited a previously unknown vulnerability in a managed file transfer product to steal data from its underlying databases. The lesson applies to any server that holds both the files and the keys to read them.
What sharing adds: access after delivery
Secure file sharing gives specific people controlled, ongoing access to files that stay in one place. Instead of pushing out copies, the sender grants access and keeps managing it:
- Permissions that match each person's role, from view only to editing, in line with the least privilege principle in NIST SP 800-53 (AC-6).
- Expiry dates that end access automatically.
- Revocation that ends access at once, for example when a project closes.
- Collaboration, such as co-editing, version history and signatures.
- An audit log of who viewed, downloaded or changed each file.
A key difference between sharing platforms is who holds the encryption keys. A platform that holds the keys can decrypt stored files, just as a transfer server can. With end-to-end encryption, files are encrypted on the sender's device and decrypted only on the recipient's, so the platform stores ciphertext it can't read. Our secure file sharing page covers the topic in full.
Secure file transfer vs secure file sharing compared
The table compares five transfer options with end-to-end encrypted file sharing.
| SFTP | FTPS | HTTPS upload | AS2 | Managed file transfer | End-to-end encrypted file sharing | |
|---|---|---|---|---|---|---|
| What it is | File transfer inside an SSH session | FTP with TLS added | A file sent to a web form, portal or API over TLS | Signed, encrypted business messages over HTTP | A platform that automates and logs transfers over these protocols | Ongoing, permissioned access to files encrypted on users' devices |
| Defined in | SSH: RFC 4251 to 4254 (SFTP itself is an expired IETF draft) | RFC 4217 | TLS 1.3: RFC 8446 | RFC 4130 | No standard: a product category | No standard: a product category |
| What's encrypted | The connection | The connection | The connection | Each message, plus the connection if HTTPS is used | Connections; stored files depend on the platform | The file itself, from the sender's device to the recipient's |
| Who can read stored files | The server operator | The server operator | The receiving service | The receiving AS2 system | The platform operator | The people given access |
| Proof of delivery and logging | Server logs, if configured | Server logs, if configured | Application logs, if configured | Signed receipts (MDNs) | Central logs and alerts | Usually an audit log of views and downloads |
| Control after delivery | None: the recipient has a copy | None | None | None | Depends on the platform | Permissions, expiry dates and revocation |
| Best suited to | Scheduled system-to-system jobs | Existing FTP systems and partners | Collecting files from people and apps | EDI with trading partners | High-volume, automated business transfers | Sensitive documents people read, edit and sign |
Where transfer and sharing overlap
The line between them isn't fixed. Both rely on TLS or SSH to protect the connection. Some MFT platforms offer person-to-person transfers through a web portal, and a sharing platform can handle a one-off delivery. Collecting files is the clearest overlap: an HTTPS upload portal and a sharing platform's upload link both receive documents from people outside the organization.
The more useful question is what happens after the file arrives: who can read it where it's stored, whether access can be withdrawn, and what gets logged. Beyond SFTP looks at why protecting the connection alone leaves those questions open.
How to choose
- Systems sending files to systems on a schedule: SFTP, or an MFT platform once the number of jobs and partners grows.
- Trading partners exchanging EDI who need proof of delivery: AS2, often run through an MFT platform.
- Existing FTP systems and partners: FTPS adds encryption without replacing them.
- Receiving files from customers or the public: an HTTPS upload portal or a sharing platform's upload link.
- Documents people need to read, edit or sign, or that may need to be withdrawn: secure file sharing, with end-to-end encryption if the files are sensitive.
Many organizations need both. Three questions settle most cases: does anyone need access after delivery, who can decrypt the file where it's stored, and what must be logged?
Where DekkoCORE fits
DekkoCORE is on the sharing side. Files are encrypted on the user's device with AES-256 keys before they're uploaded, and DekkoCORE stores only ciphertext and never has the keys to open them, so not even DekkoSecure can read them. Each share gets one of seven permission levels, an optional expiry date and instant revocation. Every view, download, signature and version is logged, and the audit log exports as CSV.
It also covers some jobs people use transfer tools for. There are no file size limits, an Upload Accelerator app for Windows handles large and bulk uploads, and submission links let people upload files through a secure link or QR code with no account or app. DekkoCORE runs in the browser and is a standalone platform, not an add-on to another storage service.
Common questions
Frequently Asked Questions
Is secure file transfer the same as secure file sharing?
No. Secure file transfer protects a file while it moves from one system or person to another, and its job ends at delivery. Secure file sharing gives people ongoing access with permissions, expiry dates, revocation and an audit log, so the sender stays in control after the file arrives.
What is managed file transfer used for?
Managed file transfer (MFT) automates, schedules and logs routine file transfers between systems and with trading partners, such as data feeds and EDI. MFT platforms usually run over SFTP, FTPS, HTTPS or AS2 and add central management and reporting.
Is SFTP the same as managed file transfer?
No. SFTP is a protocol for moving files over an SSH connection. Managed file transfer is a platform that usually supports SFTP alongside other protocols and adds scheduling, automation, alerts and central logging.
What is encrypted file transfer?
Encrypted file transfer protects a file while it travels, usually with TLS (for FTPS and HTTPS) or SSH (for SFTP). The receiving server decrypts the data as it arrives, so protection while the file is stored depends on that server's own encryption at rest.
What is AS2 used for?
AS2, defined in RFC 4130, is used to exchange structured business data such as EDI and XML documents between trading partners over HTTP. Messages are signed and encrypted with S/MIME, and the sender can request a signed receipt as evidence of delivery.
When should you use file sharing instead of file transfer?
Use secure file sharing when people need to read, edit or sign documents, or when you may need to withdraw access later. Use secure file transfer for scheduled, machine-to-machine jobs where the receiving system takes ownership of the file.