How to Secure Data Transfer in 2026: TLS, SFTP, Encryption and Passkeys

The weak points in data transfer are rarely the encryption algorithms. They are the places where encryption is missing or quietly bypassed: an FTP login sent in clear text, an email relayed over an unprotected hop, a file-transfer server left unpatched, or a cloud account opened with a phished password.

The fixes below close those gaps for individuals and small businesses: TLS 1.3 and HTTPS, SFTP or FTPS in place of FTP, file-level and end-to-end encryption, the real limits of VPNs and email encryption, managed file transfer, phishing-resistant sign-ins, and the state of post-quantum cryptography in September 2026. A checklist at the end turns it into tasks.

What secure data transfer has to protect

A transfer is secure when three things hold: nobody on the network path can read the data, nobody can change it without being detected, and you are really connected to the party you meant to reach. TLS, the protocol behind HTTPS, is built for exactly that; the TLS 1.3 specification (RFC 8446) describes its goal as preventing eavesdropping, tampering and message forgery.

The second question is where the encryption stops. Encryption in transit (TLS, SSH) protects data between your device and a server, but the server can read what it receives. End-to-end encryption keeps data locked until it reaches the recipient’s device, so the service in the middle cannot read it. Most decisions in this guide come down to which of the two a given transfer needs.

Use TLS 1.3 and HTTPS on every site and service

Version matters. NIST SP 800-52 Rev. 2, the federal TLS configuration guideline, requires government servers and clients to support TLS 1.2 with approved cipher suites and required TLS 1.3 support by January 1, 2024. NIST added a note in May 2026 that the document is under review, so a revision is likely. The IETF formally deprecated TLS 1.0 and 1.1 in RFC 8996 back in March 2021.

Prefer TLS 1.3 wherever both sides support it. RFC 8446 removed static RSA and Diffie-Hellman key exchange, so every TLS 1.3 session has forward secrecy: a server key stolen next year cannot decrypt traffic recorded today. It also encrypts every handshake message after the ServerHello, which hides more connection details than TLS 1.2 did.

Browsers are closing the last plain-HTTP gap. Google says Chrome 154, due in October 2026, turns on Always Use Secure Connections by default, so Chrome will ask before loading a public site that lacks HTTPS. An older version of this article listed plain HTTP as a secure option; it never was, because nothing in HTTP itself encrypts the page or form data.

Certificates are also getting shorter lives. Under CA/Browser Forum Ballot SC-081v3, adopted in April 2025 with no votes against, maximum certificate validity fell to 200 days on March 15, 2026, drops to 100 days in March 2027 and reaches 47 days in March 2029. Manual renewals will not keep pace. Use a host or CDN that renews automatically, or an ACME client with a free authority such as Let’s Encrypt, which issues browser-trusted certificates without human intervention.

What to do on your own sites and devices:

• Redirect every HTTP request to HTTPS, then enable HTTP Strict Transport Security once all pages and assets load securely.
• Disable TLS 1.0 and 1.1 on web servers, load balancers, mail gateways and NAS boxes. Keep TLS 1.2 only for clients that cannot do 1.3.
• Scan public-facing hosts with Qualys SSL Labs’ free SSL Server Test, which grades protocol versions, cipher suites and certificate chains.
• Check older printers, scanners and point-of-sale gear. If a device only speaks TLS 1.0, isolate it on its own network segment or plan its replacement.

Replace plain FTP with SFTP or FTPS

Plain FTP should not carry anything sensitive. RFC 2577, the IETF’s FTP security considerations, points out that standard FTP sends passwords in clear text, and file contents cross the network unencrypted too. Anyone positioned on the path can capture both.

Two secure replacements exist. Despite the similar names, they are different protocols:

Protocol	How it is secured	Best fit
FTP	Not at all: login and files travel in clear text	Public, non-sensitive downloads only
FTPS	FTP with TLS added (RFC 4217)	Partners whose systems already speak FTP
SFTP	Runs inside an SSH session, normally on port 22	Most new setups, scripts and server admin

SFTP is usually the simpler choice because it rides on SSH, which listens on port 22 by default, instead of juggling FTP’s separate control and data connections through firewalls. The OpenSSH sftp client performs all operations over an encrypted SSH transport and supports public key authentication, so automated jobs do not need stored passwords. OpenSSH 9.0 (April 2022) switched the scp command to the SFTP protocol by default, and OpenSSH 10.0, released April 9, 2025, made the hybrid post-quantum key exchange mlkem768x25519-sha256 its default.

You do not need special software to start. OpenSSH has been available on Windows since Windows 10 build 1809, and WinSCP is a free graphical SFTP, SCP, S3 and FTP client for Windows.

• Turn plain FTP off on the server. Leaving it enabled as a fallback invites clients to use it.
• Use SSH keys rather than passwords for SFTP accounts, and lock each account to its own folder.
• For FTPS, require TLS on both the control and data channels. RFC 4217 lets a server refuse commands until the session is protected.
• Check the server’s host key fingerprint the first time you connect, and treat an unexpected change as a warning sign.

Encrypt the file itself when the server should not see it

TLS and SSH protect the trip, not the destination. Once a file lands on an SFTP server, a cloud drive or a mail server, anyone with access to that system can open it unless the file was encrypted before it left your machine. For a one-off sensitive document, the process is short:

1. If the recipient has an OpenPGP public key, encrypt the file to that key with GnuPG, the free OpenPGP implementation. Only the matching private key can decrypt it.
2. If they do not use OpenPGP, create an encrypted archive with 7-Zip, which offers AES-256 encryption in 7z and ZIP formats, using a long random passphrase.
3. Send the passphrase through a different channel, such as an end-to-end encrypted messenger or a phone call. A password in the same email as the attachment protects nothing.
4. Once the recipient confirms they have the file, delete the shared copy or expire the link.

Do not use TrueCrypt. Its official SourceForge page says development ended in May 2014 and warns that it may contain unfixed security issues.

Cloud storage: encrypted is not the same as end-to-end encrypted

Mainstream cloud services encrypt your files on their side, which protects against a stolen disk but not against the provider or anyone who compromises it. Dropbox encrypts files at rest with 256-bit AES and uses TLS in transit, yet its end-to-end encrypted team folders, where only folder members hold the key, are limited to Business Plus, Advanced and Enterprise teams.

Apple users have a stronger option. Advanced Data Protection raises the number of end-to-end encrypted iCloud data categories from 15 to 25, adding iCloud Backup, Photos and Notes. The trade-off is recovery: Apple holds no keys, so losing your devices and recovery methods means losing the data. Apple also says it can no longer offer Advanced Data Protection to new users in the United Kingdom.

Firefox Send, which older guides recommended for encrypted sharing, is gone; Mozilla announced its end of life in September 2020. For current services, TechEngage’s roundup of ways to send large files free over the internet is a starting point. Check whether each one is end-to-end encrypted or only encrypted in transit before uploading anything confidential.

Use end-to-end encrypted messaging for sensitive conversations

CISA’s Mobile Communications Best Practice Guidance, last revised in March 2026, tells highly targeted people to use only end-to-end encrypted communications and names Signal as an example of a free app that works across iPhone and Android. It was written for officials and executives after telecom-network espionage, but the logic applies to anyone discussing contracts, payroll or medical details over chat.

The same guidance lists problems encryption alone does not solve:

• Social engineering: attackers claim your account has been compromised, then trick you into steps that hand them control of it.
• Linked devices: review the linked-devices list in each messaging app, keep it to devices you need, and remove anything unexpected.
• Invite links and QR codes: do not scan group invitations or QR codes from unknown sources.
• Metadata: even when message content is encrypted, check what the app collects and stores about who you talk to and when.
• SMS: CISA notes that SMS messages are not encrypted and can be read by an attacker with access to a carrier’s network.

Everyday texting between iPhone and Android is catching up. Apple says end-to-end encrypted RCS began rolling out in beta on May 11, 2026, for iPhones on iOS 26.5 with supported carriers and Android phones on the latest Google Messages. A lock icon marks protected chats; without it, assume the conversation is not end-to-end encrypted.

Off-the-Record Messaging (OTR), which this article previously described as a tool that encrypts emails, was never an email tool. It was built for desktop instant-messaging clients such as Pidgin, and the newest item on the OTR project’s news page is a security update from March 2016. For apps that people actually use today, see TechEngage’s comparison of private messaging apps for secure chats.

What email encryption protects, and what STARTTLS does not

Between mail servers, the usual protection is STARTTLS, which upgrades an SMTP connection to TLS. RFC 3207, the standard that defines it, is blunt about two limits. SMTP is not end to end, so TLS between one pair of servers does not protect the message across the other hops. And a man-in-the-middle can delete the server’s STARTTLS offer, leaving the connection to continue unencrypted unless both sides are configured to require TLS.

Every server along the way also stores the message in readable form. STARTTLS stops casual interception on the network; it does nothing about a compromised mailbox, a malicious insider or a breached provider.

Businesses can close the downgrade gap for mail they receive with MTA-STS (RFC 8461), which lets a domain tell sending servers not to deliver unless TLS with a trusted certificate is available. Google Workspace’s MTA-STS documentation explains that supporting servers will then send to your domain only over authenticated connections using TLS 1.2 or higher.

Protecting the message content itself takes end-to-end email encryption. S/MIME, now at version 4.0 in RFC 8551, adds digital signatures for authenticity and encryption for confidentiality, using a certificate for each person. The hurdles are setup and plan tiers: the sender needs the recipient’s certificate before encrypting, and Google supports hosted S/MIME in Gmail only on Enterprise Plus, Frontline Plus and Education Fundamentals, Standard and Plus editions.

Microsoft 365 organizations can use Microsoft Purview Message Encryption, which Microsoft says works with recipients on Outlook.com, Yahoo, Gmail and other services; the older Office 365 Message Encryption has been deprecated. For a single confidential attachment to an outside contact, an encrypted file with a separately shared passphrase is often quicker than any of these.

None of it helps if someone takes over the mailbox, so secure the account first. TechEngage’s guide to protecting your email from hackers covers MFA, passkeys, app passwords and recovery settings.

VPNs: a useful tunnel with real limits

A VPN encrypts traffic between your device and the VPN server. Beyond that server, traffic travels the internet with whatever protection the destination offers, so a VPN does not make plain FTP or unencrypted email safe from end to end. For the mechanics, see TechEngage’s explainer on what a VPN is and how it works.

On public Wi-Fi a VPN matters less than it once did. The FTC’s consumer advice says that because most websites now encrypt the data they exchange, connecting through public Wi-Fi is usually safe, as long as you check for HTTPS. That holds for cafe networks and for passwords found through hotspot-sharing apps such as WiFi Map, though a VPN still helps with apps that do not use TLS.

CISA’s mobile guidance goes further for highly targeted people and advises against personal VPNs altogether: they shift risk from your internet provider to the VPN provider, often add attack surface, and many free and commercial services have questionable security and privacy policies. A VPN your employer requires for internal systems is a separate case.

For businesses, the VPN gateway is itself a target. In January 2024 CISA issued Emergency Directive 24-01 after attackers exploited Ivanti Connect Secure and Policy Secure appliances to capture credentials and plant web shells. If you run a VPN appliance, patch it as urgently as your public website, require MFA for every login, and weigh whether a cloud service that grants access app by app would expose less of your network.

Managed file transfer for recurring business transfers

When a company exchanges files with partners on a schedule (payroll exports, insurance claims, lab results, supplier feeds), a managed file transfer (MFT) platform replaces a mess of scripts and shared logins. Progress MOVEit Transfer, for example, advertises encryption in transit and at rest, tamper-evident logging, activity tracking and centralized access controls, which is what an auditor asks for when they want to know who sent what, and when.

The downside is concentration. An internet-facing MFT server holds a great deal of sensitive data in one place, and ransomware crews go after exactly that. A joint CISA and FBI advisory says the CL0P gang began exploiting a SQL injection flaw in MOVEit Transfer (CVE-2023-34362) on May 27, 2023, stealing data from the underlying databases. In September 2025 Fortra disclosed CVE-2025-10035 in GoAnywhere MFT with a CVSS score of 10.0, and Microsoft reported that Storm-1175, a group known for Medusa ransomware, was exploiting it.

Who needs MFT: organizations with regulated data, many external partners or automated transfers that must be logged. Who can skip it: a small team sending a handful of files a week is usually better off with a business cloud storage plan that enforces MFA, expiring share links and audit logs, which leaves server patching to the provider.

If you run an MFT server yourself:

• Keep the admin console off the public internet.
• Subscribe to the vendor’s security advisories and apply critical patches within days. A product appearing in CISA’s Known Exploited Vulnerabilities catalog means attacks are already happening.
• Enforce MFA or single sign-on for every account, and delete dormant partner logins.
• Set retention rules so files are removed after pickup instead of piling up for years.

Lock down the accounts that move the data: MFA and passkeys

Encryption does not help when an attacker signs in as you. CISA’s MFA guidance says any MFA is better than none, calls phishing-resistant MFA the standard to aim for, and notes that the only widely available phishing-resistant method is FIDO/WebAuthn authentication.

Passkeys are the everyday form of FIDO. Google’s passkey documentation explains the key property: a passkey works only on the website or app it was registered for, and the browser or operating system enforces that, so a look-alike phishing page cannot collect a usable login. CISA’s mobile guidance ranks hardware FIDO security keys as the most effective option, accepts passkeys as an alternative, and tells people to stop using SMS as a second factor.

NIST’s updated authentication guideline, SP 800-63B-4, points the same way: services at its AAL2 level must offer at least one phishing-resistant option. It also overturns two habits this article used to recommend. Services must not force periodic password changes (only after evidence of compromise), and they must not impose composition rules such as mandatory symbols. Length counts for more, and a password used as the only factor must be at least 15 characters.

• Turn on passkeys or security keys first for email, cloud storage, your password manager, and any admin, banking or MFT account.
• Remove SMS as a fallback wherever the service allows it. TechEngage’s walkthrough on turning on two-factor authentication covers the major platforms.
• Use a password manager to generate long, unique passwords for everything that does not support passkeys yet; the guide to keeping your passwords secure explains the basics.

Post-quantum cryptography: where it stands in September 2026

The quantum risk to data transfer is mostly a future one with a present-day catch: encrypted traffic recorded now could be decrypted later by a sufficiently powerful quantum computer. That harvest-now, decrypt-later scenario is what Apple describes post-quantum encryption as designed to prevent.

The core standards are finished. On August 13, 2024, NIST published FIPS 203, 204 and 205: ML-KEM for key establishment, ML-DSA as the main digital signature standard, and SLH-DSA as a hash-based signature backup. In March 2025 NIST selected HQC as a backup to ML-KEM that relies on different math, with a final standard expected in 2027.

Deployment is furthest along for key exchange, almost always in hybrid form, where a classical X25519 or elliptic-curve exchange is combined with ML-KEM so the connection is designed to hold up against both classical and quantum attackers:

• Browsers: Google moved Chrome’s hybrid key exchange to the final ML-KEM standard in Chrome 131.
• Apple platforms: iOS 26, iPadOS 26, macOS Tahoe 26 and visionOS 26 automatically offer X25519MLKEM768 in TLS 1.3 connections.
• SSH: OpenSSH 10.0 uses a hybrid ML-KEM key exchange by default, as noted in the SFTP section above.
• Standards: the IETF published RFC 10024 in August 2026, defining X25519MLKEM768 and two other hybrid groups for TLS 1.3.
• Real traffic: Cloudflare said in April 2026 that more than 65% of human traffic to its network was post-quantum encrypted, and it is targeting full post-quantum security, including authentication, by 2029.
• Messaging: Signal added its Sparse Post Quantum Ratchet in October 2025, and Apple’s iMessage PQ3 protocol began rolling out with iOS 17.4.

Signatures and certificates are the unfinished half, which is why Cloudflare’s 2029 target singles out authentication. NIST’s draft transition plan, IR 8547, proposes deprecating 112-bit-strength algorithms such as RSA-2048 after 2030 and disallowing quantum-vulnerable algorithms like RSA and ECDSA after 2035.

For individuals, the practical step is staying current on browsers, operating systems and SSH clients; the protection arrives through updates. Businesses have more homework. Confirm that web servers, load balancers and firewalls accept hybrid key exchange, since Apple warns that some legacy servers fail to read the larger TLS ClientHello messages these connections send. Then list any data that must stay confidential into the 2030s, because that is the data harvest-now, decrypt-later attacks are after.

Secure data transfer checklist

For individuals

• Keep your browser and phone operating system updated, and do not enter anything sensitive on a page without HTTPS.
• Use Signal or another end-to-end encrypted app for sensitive conversations, and look for the lock icon in RCS chats.
• Encrypt confidential files with 7-Zip AES-256 or GnuPG before emailing or uploading them, and send the passphrase separately.
• Turn on passkeys or security keys for email, cloud storage and your password manager, and drop SMS codes where possible.
• Check each messaging app’s linked-devices list and remove anything you do not recognize.
• Expire or delete share links once the recipient has the file.
• Do not rely on a personal VPN as a general fix; use one for a specific need, from a provider whose privacy policy you have actually read.

For small businesses

• Disable TLS 1.0 and 1.1, enable TLS 1.3, and automate certificate renewal before lifetimes shrink to 100 days in March 2027.
• Shut down plain FTP. Move partners to SFTP with key authentication, or FTPS with TLS required on both channels.
• Publish an MTA-STS policy for your mail domain, and use S/MIME or Purview Message Encryption for sensitive outbound mail.
• Require phishing-resistant MFA for administrators, finance staff and anyone with access to file-sharing, VPN or MFT systems.
• Patch internet-facing VPN, MFT and file-sharing servers on an emergency schedule, and watch CISA’s KEV catalog for products you run.
• Review who can access shared folders and partner accounts every quarter, and delete what nobody uses.
• Ask hosting, CDN and firewall vendors about hybrid post-quantum TLS support, and make it a requirement in the next hardware refresh.

Secure data transfer FAQs