Technical Anshu
Tutorials Blog
🔒 File Transfer Security

Plain FTP Is Insecure Switch Your NAS to SFTP or FTPS

The DSM checkbox honestly labels it: FTP service, no encryption. This page shows what no encryption looks like on the wire, and how to move to SFTP or FTPS without breaking your users.

✍️ Technical Anshu🗄️ Synology DSM⏱️ 6 minute read
🎥 The setup video enables FTP and SFTP side by side — watch it, then harden it with this page

FTP is the oldest door on your NAS and the only one that introduces itself to the whole network. On plain FTP, the username, the password and every file travel as readable text. Anyone who can listen on the path — a compromised PC on the same Wi-Fi is enough — can read them. Here is what that really means, and the two encrypted exits Synology already gives you.

What a network sniffer sees — plain FTP vs SFTP (fake example password)
Plain FTP login
USER ravi PASS Sunrise-Example-123 ← readable by anyone listening RETR invoice-oct.pdf ← file name and contents readable
SFTP login
SSH-2.0 encrypted session ← handshake visible, contents are not kex_exchange ... a91f 04bc 77d2 ... ← no password, no file names
Illustrative capture with an invented example password — on plain FTP the real one would be just as readable; on SFTP there is nothing to read.
1

What Plain Actually Means

When DSM's FTP tab says Enable FTP service (No encryption), the words in brackets are the whole story. The control connection on port 21 carries commands — including USER and PASS — exactly as typed, and the data connection carries the file itself unchanged. There is no scrambling anywhere in classic FTP. It was designed in 1985 for a small, trusting academic network, and it behaves like it.

2

Who Can Actually Read It

Be precise, not dramatic: reading FTP traffic needs a listening position — the same LAN, a tapped cable, a rogue device, or any hop on an internet path. That is why plain FTP inside a wired office LAN is a small risk, plain FTP over office Wi-Fi is a real risk (the air is shared), and plain FTP across the internet is not a risk but a donation — of your password first, then your files.

3

Exit One — SFTP, the Better Default

SFTP replaces the whole design with SSH encryption: one port (22), everything sealed, and support in WinSCP, FileZilla and every script you will ever write. On Synology you enable it via Control Panel → Terminal & SNMP → Enable SSH service, then connect with the same username and password you already use. For most people this is the end of the story: turn plain FTP off entirely and keep SFTP.

4

Exit Two — FTPS, When the Other Side Insists on FTP

Some older software and devices can do FTP and nothing else — except their slightly newer sibling, FTPS. On the same DSM FTP tab, tick Enable FTPS (FTP over SSL/TLS). In FileZilla, the matching choice is FTP over TLS. The password and data are then encrypted, though FTPS keeps FTP's awkward habit of opening a range of passive data ports, which your firewall must allow.

5

The Migration Checklist

  1. Enable SFTP (SSH service) and, if legacy gear needs it, FTPS
  2. Tell your users the new connection details and test with one friendly user first
  3. Watch the File Transfer logs for a week to see who still arrives on plain FTP
  4. Untick Enable FTP service (No encryption) and note the date — anyone who complains now has a name and a fix

Devices that genuinely cannot encrypt get a tiny, read-only, LAN-only exception — not a network-wide plain door.

🔴 The one rule that covers almost everything: plain FTP + internet = never. Plain FTP + shared Wi-Fi = asking for trouble. Plain FTP + wired LAN + legacy device = a small, deliberate exception — with SFTP doing all the real work.

🎥 See FTP and SFTP Enabled in the Video

The full Synology File Services setup, including the FTP tab and the WinSCP SFTP test on port 22.

▶️ Watch Full Video
❓ Common Questions (FAQ)

My FTP password is strong. Does that protect me on plain FTP?

No. On plain FTP a strong password is simply a strong sentence read aloud — it travels as readable text, so anyone listening copies it exactly and reuses it. Strength does not help; encryption does.

My scanner or old software only supports FTP. What do I do?

First check for an FTPS option in its settings — many devices have one hiding. If it truly only speaks plain FTP, keep it on the wired LAN, give it its own limited account with access to one folder, and never open that door to the internet.

If I turn plain FTP off, do my SFTP users lose anything?

Nothing. SFTP is a separate service on Synology (it comes with the SSH service), with the same accounts and folders. Users just connect with the SFTP protocol selected in WinSCP or FileZilla instead of plain FTP.

This guide is based on the Technical Anshu FTP security video • Stuck on any step? Ask in the video comments — you will get an answer 🙏