Storing and transferring business files safely
Decide where business files are stored and how they're sent, verify recipients, protect portable copies and plan how each handoff ends.

A client needs a payroll export, a supplier needs drawings, or an application needs a nightly file. Each handoff has different requirements. The recipient, information and delivery process matter as much as the storage product.
For each recurring task, tell staff which route to use. They should know where the working copy belongs, how to send it and whom to contact when the usual method won’t work.
Start with the file and its owner
Identify the business owner, intended recipient and purpose. Check whether the file contains personal information, confidential client material or records subject to a contractual restriction.
Prepare only the information needed. Inspect hidden worksheets, comments and attachments before exporting. Keep the main copy where the team normally stores it, so an emailed or downloaded copy doesn’t become the only record of the work.
Use the cloud-storage selection guide if you’re choosing a service. For a service you already use, check that it’s meant to hold this kind of information and that its sharing settings fit.
Use a managed sharing route for collaboration
For a document people will revise together, a controlled link can keep work in one location. Choose the intended recipient and the access they need. Test external access with a sample file before sending sensitive material.
Microsoft’s OneDrive sharing guidance explains its link options. An Anyone link can be forwarded and used without authentication. A link for specific people restricts who can use it, but doesn’t remove other permissions already granted.
The cloud-sharing guide covers effective permissions and access removal. Check your service and licence before relying on expiration or download restrictions.
Treat attachments as delivered copies
An attachment can be saved, forwarded and retained independently of the message. When the information calls for it, use the encrypted email or file-transfer service your organization has chosen.
If that process uses a separately encrypted file, confirm the recipient can open it and agree how they’ll receive the secret through an independently verified channel. A second email to the same compromised mailbox doesn’t provide useful separation.
Encryption protects content within its defined scope. It won’t check a request, fix a wrong address or tell you whether the recipient’s device is safe. Confirm an unusual destination change using contact details you already trust.
Protect portable and local copies
When a physical handoff is necessary, use a company-owned drive that’s on your equipment list. Confirm encryption, controlled recovery keys, custody and the recipient’s ability to read the files.
The Cyber Centre’s baseline controls recommend organization-owned encrypted portable media with asset controls. Keep a record of who holds a drive and what it contains. A label on the drive or a password prompt doesn’t mean the files are encrypted, so check.
Apply the same care to downloads on laptops. Decide whether a local copy is needed, how it’s protected and when it should be deleted. Keep any records the retention policy requires.
Give automated transfers their own controls
A recurring export needs an owner, restricted access and a failure route. Have IT confirm the transfer protocol, destination identity, credential storage, logging and receipt checks. Avoid sharing a staff member’s account for an unattended job.
SFTP can protect a connection when configured correctly. The process still needs to verify the destination, restrict the receiving account and protect the files after arrival. A VPN protects the network connection. It has no say in who can read a file.
Use sample data to test both delivery and failure. Check what happens to incomplete transfers and temporary copies.
Close the handoff
Confirm receipt through the agreed process. Remove temporary access when it ends and follow the retention rules for copies. Withdrawing a link doesn’t retrieve files already downloaded.
Report a mistaken recipient or lost drive promptly through your privacy and incident process. Preserve the details so the responsible team can assess what was exposed.
Contact us to review recurring file handoffs and give your team a usable storage and transfer process.


