Secure file sharing with clients means a method that protects the file in transit, limits who can open it and leaves a record of who did. Pick by recipient, sensitivity and volume from five methods: file request link, form upload, client portal, encrypted email and SFTP. The FTC Safeguards Rule asks for encryption in transit or approved alternative controls.
Secure file sharing with clients means a method that protects the file in transit and limits who can open it. It also leaves a record of who did. Pick the method by who is on the other end, how sensitive the file is and how many files move.
This guide compares five secure file transfer methods in both directions, sending and receiving. It then checks the choice against the one line of the FTC Safeguards Rule that bears on file transfer. The rule is US law, so this guide is written for US firms.
What are the main ways to share files securely?
Five methods cover the usual client exchanges. Each has a natural home.
- A file request link: the client opens a link and drops files into a folder you control.
- An upload field on a web form: the client answers questions and attaches files in one step.
- A client portal: a login where both sides post and collect files over a long engagement.
- Encrypted email: a message and attachment protected end to end, opened through a link or a plug-in.
- SFTP: a protected transfer between two systems, usually scripted.
None of them is the right answer for every client. The table below does the sorting.
Which method fits which recipient?
Start with the person on the other end. A method the client cannot use ends with an unprotected attachment anyway.
| Method | Client needs an account? | Password option | Record of activity | Fits best |
|---|---|---|---|---|
| File request link | Often no | Often yes | Uploads land in your folder | Occasional clients sending you files |
| Form upload | No | Not needed | Each submission is logged | New clients, first documents |
| Client portal | Yes | Login | Usually full history | Long engagements, many files both ways |
| Encrypted email | Sometimes | Sometimes | Depends on the tool | Sending one sensitive file out |
| SFTP | Yes, for a system | Keys or login | Server logs | System to system only |
Dropbox's file request is a fair example of the first row. The uploader needs no Dropbox account and files go to a private folder, according to Dropbox's help page. A password is optional, per the same page. SFTP sits at the other end. It suits another firm's system, not a client with a phone and a scanned passport.
Is sending a file the same as receiving one?
No, and mixing them up is how gaps appear. When you send, you control the recipient list. When you receive, anyone holding the link can usually upload.
That changes the checks. To send documents securely, confirm the recipient and protect the file. For receiving, make each request link specific to one client and one job. Close it once the files arrive. A standing upload link on a public page is an inbox for strangers.
How do you pick by sensitivity and volume?
Two questions settle most cases: how bad would a leak be, and how many files will move?
| A few files, once | Many files, ongoing | |
|---|---|---|
| Low sensitivity | Request link or form upload | Shared folder with named access |
| High sensitivity | Request link with a password, or encrypted email | Client portal with multi-factor login |
When a link carries a password, send the password by a different channel. A text message for a link sent by email works. Anyone who intercepts one channel then has half of what they need.
What does the FTC Safeguards Rule mean for file transfer?
For a covered firm, one line does most of the work here. The FTC's guide to the rule says customer information is encrypted on your system and in transit, or protected by alternative controls your Qualified Individual approves. The rest of the program sits in the accounting security checklist, from multi-factor login to the 30-day breach notice.
Does the rule apply to your firm, and does it ban email?
Coverage depends on what you do, not your job title. Tax preparation firms are among the 13 example entity types in 314.2(h), and mortgage brokers are listed too, per the FTC guide. Accountants are not named. Entities holding information on fewer than 5,000 consumers are exempt from certain provisions under 314.6, per the same page.
The rule does not ban email. It requires customer information to be encrypted in transit or protected by approved alternative controls. Plain attachments make that hard to show. Your own adviser and your state's rules decide the details for your firm.
What about files already sitting in sent email?
If your firm ever emailed returns or IDs, copies still sit in sent folders. Switching method today does not move them.
- Search sent mail for attachments by file type and by common client document names.
- Save anything you must keep into the client's file in your document system.
- Delete the email copies under your retention policy.
- Turn on multi-factor login for every mailbox that remains.
It is a dull afternoon. It also shrinks the pile that a single stolen password exposes.
How do you make the secure route easy for clients?
Clients pick the easiest route offered. Make the secure one the easiest.
- Skip the account for a one-off request. The client portal guide covers when a login earns its place.
- Send one link per request, named for what you need.
- Offer a paper or in-person fallback for clients who cannot manage a link.
- Tell clients how you will contact them, so a fake request stands out.
Clients are told to distrust any email that asks for personal details, so a careless request looks like a scam. Make yours easy to verify. The guide to requesting sensitive information by email turns the phishing warning signs into rules for your own requests.
Where does the new client's first form fit?
The first secure exchange is usually the enquiry form, before any file moves. It already holds names, phone numbers and the reason someone needs help. Start it from one of the form templates. The lead capture software page covers what that first form should ask. If the form vanishes for visitors who decline cookies, the Lead Source blog explains why consent tools block contact forms.
The secure forms guide covers what protects a submission from the browser to your records. The encrypted forms page covers locking the values while keeping the source readable. The same form is where Lead Source records the new client's channel, campaign and landing page, as form tracking explains. File exchange starts later, with whichever method above fits the client.